Yes its annoying that background Dell seems to leave as default when you login from Terminal services or remote dekstop, Funny thing is you cannot remove it simply by changing the wallpaper settings it has to be removed from the registry.

To Remove:
1) start –> run –> regedt32
2) Find the registry key –> HKEY_USERS.DEFAULTControl PanelDesktopWallpaper
3) remove the windowssystem32DELLWALL.BMP and leave the value blank then hit “OK”

You are done, no more annoying Dell wallpaper when you loginto remote desktop/Terminal services!

Article written by MyComputerAid.com

Post from: MyComputerAid.com Computer support

Remove the Dell background image in remote desktop

Dell offers some of the best customer service and warranty guidelines of any national manufacturer.  With 24/7 representatives available to handle your problems, and online information within easy reach, Dell systems are provided with ease-of-use in mind.

Most desktop and server systems come with a warranty which is valid for 1 to 3 years.  There are three main categories for service, full coverage (on-site repair), diagnosis service center repair, and diagnosis with User repairable components.  In addition, an warranty that has expired can be extended for a nominal charge, but does not include the cost of parts and labor.  One minor drawback is that all Dell warranties begin on the day the product is shipped by Dell, so the warranty “clock” has already begun ticking before you ever receive the product.

When calling Dell for service, always have your machine’s Service Tag available.  This is a 5 or 7 character code comprised of alpha-numeric characters, and can usually be found affixed to the rear of the machine.  Using this code allows customer service, as well as Dell technicians, easy access to the particular options installed on your computer.  This saves time, and provides much greater accuracy when determining hardware conflicts, software malfunctions, and other details.

In order help you keep your investment in top running condition, Dell also offers support for many common problems, such as virus detection and removal, add-on hardware installation and support, and even software and Internet support.  Common Microsoft products, such as MS Office, Word, and Works are supported, in addition to Adobe Acrobat.  Netscape, Internet Explorer, and Microsoft Outlook are a few of the Internet packages supported.

For a more detailed look at what is and is not covered by Dell warranties, please visit:
http://oit.nd.edu/support/service/dell.shtml

Article written by MyComputerAid.com

Post from: MyComputerAid.com Computer support

Dell warranty service explained

ERROR Message you may be troubleshooting:

Microsoft Visual C++ Runtime Library Runtime Error! Program: Program FilesSymantecBackup Execbeserver.exe
This application has requested the Runtime to terminate it in an unusual way. Please contact the application’s support team for more information.
OR

Could not load file or assembly ‘System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. Systemet could not find the file.

You must first do the Symantec fix: http://seer.entsupport.symantec.com/docs/287554.htm

If any components of the functions/features listed above are missing or corrupted, the Backup Exec Server service may fail to start with a C++ Runtime Error.  To diagnose why this issue is occurring, run the service in console mode per the following:
1. Launch a command prompt on the media server
a. Go to Start
b. Select Run
c. Type in CMD and press Enter
2. Change the path to the Program FilesSymantecBackup Exec directory on the disk partition that Backup Exec is installed on (default is the C: partition).  Type in the following and press Enter:
BEServer.exe  -console >> C:BEServer.txt
3. Locate the BEServer.txt file after the runtime error is displayed.  Review the document or submit it to Symantec Technical Support for assistance.

One possible reason that the service may not start after an upgrade or re-install of Backup Exec is covered in the example listed below:
Symptoms:
The Backup Exec Device and Media Service starts successfully but the following dialog boxes appear when attempting to start the Backup Exec Server service (Figures 1 & 2):
Figure 1
 
Figure 2
 

***********************************************************************************************************************************************************
The Windows System Event Logs shows:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID:       7022
Date:        14/02/2007
Time:        10:10:44
User:        N/A
Computer:     VM2003BE11D
Description:  The Backup Exec Server service hung on starting.
***********************************************************************************************************************************************************

The debug log from the BEServer.exe -console process will show the following at the end of the log:

[5272] 02/14/07 02:13:13 14 Reports: Using default language = ENU
[5272] 02/14/07 02:13:13 14 Reports: Initialize for language = 1
[5272] 02/14/07 02:13:13 14 Reports: Setting remote server locations.
[5272] 02/14/07 02:13:13 14 Reports: Loading any new reports.
[5272] 02/14/07 02:13:14 14 Reports: Report Engine started.
[5272] 02/14/07 02:13:14 14 Reports: Initializing CRF.

***If the logging stops at the “Initializing CRF” line above, then confirm that the following registry key/value exists:

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

1. Go to Start, Run, type REGEDT32 and press Enter.

2. Select the HKey_Local_Machine on Local Machine window.  Browse to the SoftwareSymantecCRF key and confirm that it exists.  When you click on this key, a Port value should show in the right window with a DWord value of 1d97 in hex or 7575 in decimal. (Figure 3)

Figure 3
 
***If the CRF key or Port value do not exist, create them and attempt to start the Backup Exec Server service again.

***********************************************************************************************************************************************************

If the BEServer -console debug does not stop at “Initializing CRF” and instead continues with the next line “Reports: Initialization Complete”, then look through the other entries in the log for errors.  Review the TechNotes in the Related Documents Section below or contact Symantec Technical Support for further assistance.

***After you are done that step you must then do this patch:

you probably have a different version of the System.EnterpriseServices assembly in the global cache. Or you don’t have it at all. You need to add the 2.0.0.0 version to the GAC.
In order to do that just drag the file at
“<windows_directory>Microsoft.NETFrameworkv2.0<your_subversion>System.EnterpriseServices.dll”
to the “<windows_directory>assembly” folder.

 Remember to check the properties of the file to be sure it has the appropriate version number!!!

(Images from Symantec and are copywrite symantec)

Article written by MyComputerAid.com

Post from: MyComputerAid.com Computer support

Backup exec will not start with Microsoft Visual C++ Runtime Library Runtime Error!