After you remove a program from your computer, you can no longer access the CD drive or the DVD drive successfully. The CD drive or the DVD drive does not appear. Or, you receive an error message when you try to access the drive. This article contains two methods to resolve this problem. One of the methods requires that you manually modify the Windows registry to remove the UpperFilters registry entry and the LowerFilters registry entry. You must restart the computer after you follow the steps in this article.

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B314060

Run -> CMD -> mstsc /?

After upgrading to SP1 RC1 for Vista I could not get into the console anymore.

with the /admin addon is works again!

mstsc.exe /admin /console

MSTSC /console is now MSTSC /admin

Although the /console switch no longer has any effect on Server 2008 and Vista Terminal Server connections, a new switch called the /admin switch has a similar effect when you use it to connect to a Server 2008 server with the Terminal Services role. When you use this switch with MSTSC, connections don’t consume Terminal Services CALs.

The /admin switch involves elevated rights. If a user has the authority to use the /admin switch but has been marked with Deny Users Permissions To Log On To Terminal Server, he or she will be able to connect using mstsc /admin. Also, if a terminal server is in drain mode (no new sessions are accepted), an /admin session can still be created. The /admin sessions don’t count toward the session limit that may be configured on a terminal server to limit the number of sessions.

In Windows Server 2003, you can start the RDC client (mstsc.exe) with the /console switch to remotely connect to the physical console session on the server (also known as session 0). In Windows Server 2008, the /console switch has been deprecated. (For more information, see the ?Why the /console switch is no longer needed? section of this article.) In Windows Server 2008, session 0 is a non-interactive session that is reserved for services.

You can use the new /admin switch to remotely connect to a Windows Server 2008-based server for administrative purposes. The /admin switch is introduced with RDC 6.1. RDC 6.1 is included with the following operating systems:

? Windows Server 2008

? Windows Vista Service Pack 1 (SP1) Beta and RC

? Windows XP Service Pack 3 (SP3) Beta and RC

Note   RDC 6.1 (6.0.6001) supports Remote Desktop Protocol (RDP) 6.1.

RDC 6.1 does not support the /console switch. However, for backward compatibility, you can use the /admin switch to connect to the physical console session on a Windows Server 2003-based server. For example, to connect from a Windows Vista SP1 RC-based client to the physical console session of a Windows Server 2003-based server, you can run the command mstsc.exe /admin.

If you try to use the /console switch with the RDC 6.1 client, the behavior is as follows.

Scenario

Behavior

You type mstsc.exe /console at the command prompt, and then connect to a remote server that does not have Terminal Server installed.

The /console switch is silently ignored. You will be connected to a session to remotely administer the server.

(For more information about the Windows Server 2008 behavior, see the ?Behavior when you connect to a server that does not have Terminal Server installed? section of this article.)

You type mstsc.exe /console at the command prompt, and then connect to a remote server that has Terminal Server installed.

The /console switch is silently ignored. You will be connected to a standard Remote Desktop session that requires a Terminal Services client access license (TS CAL).

In the RDC client UI, you specify Computer_name /console in the Computer box (where Computer_name represents the name of the remote computer to which you want to connect), and then click Connect.

You receive the following error message:

?An unknown parameter was specified in computer name field.?

In the .rdp file, you specify /console in the ?full address? property, and then try to start the Remote Desktop connection.

You receive the following error message:

?An unknown parameter was specified in computer name field.?

In the .rdp file, you specify the ?connect to console? property, and then start the Remote Desktop connection.

The property is silently ignored. You will be connected to a session that requires a TS CAL.

As a developer, you programmatically call the put_ConnectToServerConsole function or the get_ConnectToServerConsole function of the IMsRdpClientAdvancedSettings interface.

The function fails, and returns S_FALSE.

Why the /console switch is no longer needed

In Windows Server 2003, starting a Remote Desktop session by running mstsc.exe with the /console switch is used for the following reasons:

? To connect to session 0. Some applications install and run only in session 0 because they need to communicate with services that run in session 0, or display UI that is displayed in session 0.

? To connect back to an existing session on the physical console. Because the physical console session in Windows Server 2003 is always session 0, the only way that you can reconnect to this session is by using the /console switch.

In Windows Server 2008, the /console switch functionality is no longer needed for the following reasons:

? Improved application compatibility ensures that legacy applications that need to communicate with services in session 0 will install and run in sessions other than session 0. Additionally, if the service that is associated with an application tries to display UI in session 0, a built-in capability in Windows Server 2008 and in Windows Vista enables the user to view and to interact with the session 0 UI from the user?s session. Windows Server 2008 session 0 is a non-interactive session that is reserved for services. Therefore, there is no need for a user to have to explicitly connect to this session.

Note   For more information about session 0 isolation in Windows Vista, see ?Impact of Session 0 Isolation on Services and Drivers in Windows Vista? (http://go.microsoft.com/fwlink/?LinkId=106201).

? Because the physical console session is never session 0, you can always reconnect to your existing session on the physical console. Reconnecting to your existing physical console session is controlled by the “Restrict Terminal Services users to a single remote session” Group Policy setting, available in the Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Connections node of the Local Group Policy Editor. You can also configure this setting in the UI by using Terminal Services Configuration. (The Restrict each user to a single session setting appears under Edit settings, in the General section.)

Behavior of the /admin switch

You can start the RDC 6.1 client (mstsc.exe) with the /admin switch to remotely administer a Windows Server 2008-based server (with or without Terminal Server installed). However, if you are connecting to remotely administer a Windows Server 2008-based server that does not have the Terminal Server role service installed, you do not have to specify the /admin switch. (In this case, the same connection behavior occurs with or without the /admin switch.) At any point in time, there can be two active remote administration sessions. To start a remote administration session, you must be a member of the Administrators group on the server to which you are connecting.

Behavior when you connect to a server that does not have Terminal Server installed

If you (as a member of the Administrators group on the destination server) start a Remote Desktop session to a Windows Server 2008-based server that does not have the Terminal Server role service installed, the following behavior is true for the remote administration session:

? Time zone redirection is disabled.

? Terminal Services Session Broker (TS Session Broker) redirection is disabled.

? Plug and Play device redirection is disabled.

? The remote session theme is changed to Windows Classic.

? Terminal Services Easy Print is disabled.

Behavior when you connect to a server that has Terminal Server installed

If you (as a member of the Administrators group on the destination server) start a Remote Desktop session to a Windows Server 2008-based server that has the Terminal Server role service installed, you must specify the /admin switch to connect to a session to remotely administer the server. The following behavior is true for the session:

? You do not need a TS CAL to connect remotely to administer a terminal server.

? Time zone redirection is disabled.

? Terminal Services Session Broker (TS Session Broker) redirection is disabled.

? Plug and Play device redirection is disabled.

? The remote session theme is changed to Windows Classic.

? Terminal Services Easy Print is disabled.

Developer resources ? Changes to APIs

If you are using RDC 6.1, you can no longer use the ConnectToServerConsole property of the IMsRdpClientAdvancedSettings interface to specify whether the Remote Desktop ActiveX control should attempt to connect to the server for administrative purposes. Instead, you must use the ConnectToAdministerServer property of the IMsRdpClientAdvancedSettings6 interface to connect to the physical console session on a Windows Server 2003-based server, or to the session that is used for administrative purposes on a Windows Server 2008-based server.

Remote Desktop Connection (Terminal Services Client 6.0)

http://support.microsoft.com/default.aspx/kb/925876

Terminal Services Team Blog

http://blogs.msdn.com/ts/default.aspx

1. via the keyboard
   The easiest way to lock Windows XP is by simply pressing the Windows logo key and the letter L (for Lock) on a Microsoft Natural Keyboard or any other compatible keyboard that includes the Window key. Doing so will pop up the Unlock Computer Password box.
2. via a Shortcut.
   If you don’t have a keyboard with a Window key or simply don’t like the keyboard method, then here’s how you can make a desktop shortcut to lock your computer.
   Right click an empty area of your desktop, choose New/Shortcut and enter this line as the command line:
              rundll32.exe user32.dll, LockWorkStation
   Click Next. Name the shortcut whatever you prefer and click Finish. That’s it.
   If you’d like to change the icon, just right click the shortcut and go to Properties/Shortcut/Change Icon.
3. via the command line
   The above command line can also be used at a DOS prompt to lock your computer. One simple way you can do it would be by clicking Start/Run, typing CMD and then entering the command and pressing Enter.
4. via a bat file
   This is similar to a Windows shortcut method. But it’s a DOS version. If you’ve never created a bat (batch) file, but would like to try this method, simply open a new text file (such as with Notepad) and type the following commands:
             @echo off
             rundll32.exe user32.dll, LockWorkStation
             cls
   Save the file with a .bat extension, such as Lock.bat, and you’re done. Double click to make the file run.
5. Press the Windows key and the L key (WinKey+L) at the same time

Additionally, you can create a new shortcut, with the following command line:

rundll32.exe user32.dll,LockWorkStation

Copy the new shortcut to your Quick Launch bar and you have one click access to locking the desktop.

Services are added from the Command Prompt. You need to know the actual service name as opposed to what Microsoft calls the Display Name. For example, if you wanted to create or delete the Help and Support service, the name used at the Command Prompt would be “helpsvc” rather than the Display Name of “Help and Support”. The actual service name can be obtained by typing services.msc in Run on the Start Menu and then double clicking the Display Name of the service. Once you know the name;

To Create A Service

• Start | Run and type cmd in the Open: line. Click OK.
• Type: sc create <service name>
• Reboot the system

Fig. 01

To Delete A Service

• Start | Run and type cmd in the Open: line. Click OK.
• Type: sc delete <service name>
• Reboot the system

Fig. 02

If you prefer to work in the registry rather than through the command prompt to delete services;

• Click Start | Run and type regedit in the Open: line. Click OK.

• Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

• Scroll down the left pane, locate the service name, right click it and select Delete.

• Reboot the system

Standard File and Folder Permissions

    * Read(R) – View attributes, contents, and permissions. Can synchronize.
    * Write(W) – Can change attributes, and file contents. Can create files or folders. Can synchronize.
    * Read(R) and Execute(E) – Can change sub folders, perform read operations, and execute a file.
    * List Folder Contents – Can perfrom read and execute permissions on folders. Can view folder contents, attributes, permissions. Can synchronize and change to subfolders.
    * Modify – Perform Read, Execute, and Write permissions along with ability to delete.
    * Full Control – Can perform Modify functions (above), take ownership, and modify permissions.

Permissions assigned to directories are inherited (default) by all files and subdirectories that are contained in the directory. The inheritance option, selected by default, may be deselected. Each file or directory has an Access Control List (ACL). To set permissions for additional users or groups, they are added to the ACL of the file or directory. Windows Explorer or the Cacls command line utility can be used to set permissions.

Special File and Folder Permissions

On the file or folder properties dialog, click the “Security” tab and the “Advanced” button to assign special file or folder permissions.

    * Traverse Folder/Execute File – .
    * List Folder/Read Data – .
    * Read Attributes – The user can read the attributes (archive, compress, hidden, etc.) of the file, but not read the contents of the file.
    * Read Extended Attributes – .
    * Create Files/Write Data – .
    * Create Folders/Append Data – .
    * Write Attributes – .
    * Write Extended Attributes – .
    * Delete Subfolders and Files – .
    * Delete – The user can delete the file.
    * Read Permissions – The user can read the file.
    * Change Permissions – Lets the user change permissions for the file, but not view or change the contents of the file.
    * Take Ownership – The user can take ownership of the file, but can’t give it back.

These permissions can be applied to directories, files, and subdirectories with one of the following selections:

    * This folder, subfolders and files
    * This folder only
    * This folder and subfolders
    * This folder and files
    * Subfolders and files only
    * Subfolders only
    * Files only

File or Folder Creation, Moving, Copying and Permissions

    * Created Files or folders – Inherit permissions of the folder they are created in.
    * Moved or copied files or folders in the same NTFS volume – Keep their own original permissions.
    * Moved or copied files or folders in a different NTFS volume – Inherit the NTFS permissions of the destination folder.
    * Movement to any FAT volume – All permissions are lost.

Moving Files

When permissions are changed on a folder, by default, permissions are replaced on files in the folder, but not on subdirectories. This may be changed using the provided checkboxes such as “Replace Permissions on Subdirectories”. When files are moved on NTFS partitions, if they are moved from one partition to another, it is as though they were copied. If files are moved to another folder, they retain their normal attributes including compression attribute reguardless of the attributes of the parent folder they are being moved to. When files are copied to another folder, they will adopt the attribute s of the folder they are being copied to.
NTFS File and Share Permissions

When these permissions are different, the most restrictive permissions are applied. The share and NTFS file permissions must overlap in order for the user to have the permission. That means to read a file, the user must have both read share and read NTFS permission.

When a user has full control permission for a folder, the permissions will apply to the files in the folder even though permission for an individual file in the folder may be set to NO ACCESS for that user.When a file or folder is moved, it retains its current permissions, but when it is copied, it inherits the permission of the parent folder or partition it is being copied to.
Ownership

If the owner’s user is a member of the administrators group, the owner is the administrators group. Administrators do not have access to all resources, but they may take ownership of any resource. Once ownership is taken, it cannot be given back. Also taking ownership of a resources changes all existing permissions for that resource.
Delegated Permissions

Permissions that can be delegated include:

    * Create, delete, and manage user groups.
    * Create, delete, and manage user accounts.
    * Manage group policy links – Gourp policies assigned by organizational unit may be modified.
    * Modify group membership.
    * Read all user information.
    * Read user account passwords.

Setting Permissions

   1. Right click on the file or folder.
   2. Select properties
   3. Select the security tab on the properties sheet.
   4. Click on the permissions button.
   5. If the file you selected is a subdirectory there are the following check box choices:
          * Replace permissions on subdirectories – Permission changes are applied to all sub folders.
          * Replace permissions on existing files – Permissions are applied to all files in the folder. If both are selected, permissions are applied to all sub folders and files in all files in the folder and its sub folders.
   6. Click on OK to exit the permissions box and OK to exit the properties box.

Disk Quotas

Disk quotas are used to track the use of disk space for each user. They are normally disabled and are only supported on NTFS file systems. Quotas are tracked per partition and per user using ownership information to account for resource use. Compressed file sizes are measured according to the uncompressed file size.

Disk quotas may be viewed and administered by using the “Disk Management” tool to select the properties dialog box of the disk or volume. The “Quota” tab contains quota information and management functions. Quota management must be enabled. Warning levels may be set and hard limits may also be set. Disk space may be denied to users who exceed their quota limit. The events may be logged when the user exeeds their warning and/or quota limit.

Windows Explorer can be used to setup and monitor disk quotas. Windows Explorer local disk properties tabs:

    * General
    * Tools
    * Hardware
    * Sharing
    * Security
    * Quota – Used to enable quota management, deny disk space if the quota is exceeded, limit the disk space and set where the disk quota warning is given. You can also log when the user exceeds their warning level or quota level. The “Quota Entries” selection box is used to view quota utilization for the volume. To modify the quota levels for any given user, double click the user’s entry.
    * Web Sharing

http://support.microsoft.com/kb/307545

1. Run REGEDIT from Start>Run
2. Click on File, then select Connect Network Registry
3. Type the remote computer IP or host name in the Enter the object name to select and the click OK.
4. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server, in the right panel, seelct fDenyTSConnection (REG_DWORD). Change the value data from 1 (Remote Desktop disabled) to 0 (Remote Desktop enabled).
5. Close the regeidt.

open up Regedit.exe and manually change the registry value HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lanmanserver\parameters\srvcomment.

Note. Be forewarned that even though this change is made in the registry the new description might not take effect until the computer has rebooted. Just something to keep in mind.

Connection to a remote Registry how to: Run -> regedit -> File -> Connect Network Registry.

Windows SteadyState runs on genuine copies of Windows XP Professional, Windows XP Home Edition, and Windows XP Tablet PC Edition. And, Windows SteadyState is offered at no charge to Windows Genuine Advantage customers!

What?s New in Windows SteadyState
Windows SteadyState includes many new features and enhanced capabilities. Windows SteadyState is not simply a redesign of the Shared Computer Toolkit; we listened to you, our customers, to better understand how we could provide a solution that could really help you manage and maintain your shared computer environments.
It?s Easier to Use

• Easier to set up ? Installation has been simplified and the improved Windows Disk Protection feature in Windows SteadyState does not require repartitioning.
• Easier to use ?
  • The Windows SteadyState UI has been redesigned to help make common tasks easier to manage from one location.
  • With simplified user restriction settings, you can choose a High, Medium, or Low restriction level for each user account.
  • Windows SteadyState enables you to import and export user accounts from one computer to another.
  • Ongoing support efforts include a fully-revised Windows SteadyState Handbook (included in both PDF and XPS formats), updated Help content included with the download, new online demos, and the new Windows SteadyState Community Web site.

It?s More Secure for You and Your Users

• Increased Protection for All Users ? Windows SteadyState includes more Windows and program feature restrictions, as well as support for Windows Update. Windows SteadyState also enables you to restrict user access to local programs.
• Windows Genuine Advantage (WGA) ? There are significant risks to running a non-genuine copy of Windows. Only genuine Windows customers are able to receive Windows product downloads, Windows updates other than security-related updates, and special offers. Windows SteadyState requires that your copy of Windows is genuine before installation. For more information, please visit the Windows Genuine Advantage Web site.

Features Included with Windows SteadyState
Windows SteadyState includes the following features to help you manage your shared computers:

• Getting Started ? Provides the initial steps to help you during your first time use of Windows SteadyState.
• Windows Disk Protection ? Help protect the Windows partition, which contains the Windows operating system and other programs, from being modified without administrator approval. Windows Disk Protection helps protect the Windows operating system and all files on the computer from permanent change. Any changes made by shared users when they are logged on to the computer are removed when the computer is restarted. Windows SteadyState allows you to set Windows Disk Protection to remove all changes upon restart, to remove changes at a certain date and time, or to not remove changes at all.
• User Restrictions and Settings ? The user restrictions and settings can help to enhance and simplify the user experience. Restrict user access to programs, settings, Start menu items, and options in Windows XP. You can also lock shared user accounts to prevent changes from being retained from one session to the next.
• User Account Manager ? Create and delete user accounts. You can use Windows SteadyState to create user accounts on alternative drives that will retain user data and settings even when Windows Disk Protection is turned on. You can also import and export user settings from one computer to another?saving valuable time and resources.
• Computer Restrictions ? Control security settings, privacy settings, and more, such as preventing users from creating and storing folders in drive C and from opening Microsoft Office documents from Internet Explorer?.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=d077a52d-93e9-4b02-bd95-9d770ccdb431

Instructions

To run and install Windows SteadyState:

1. Inititate the session as an an Administrator for the shared computer or as a member of the group of Administrators.
2. Run the installation file SteadyState_Setup_LOC.exe. To start SteadyState_Setup_LOC.exe, double click on the file icon.
3. Click Validate to confirm that the Windows copy is original. You can click Cancel to exit the assistance wizard to install Windows SteadyState.
4. When you correctly finish the verification process, a page will appear with Licensing Terms for the Microsoft software.
5. If you agree with the terms, click I Accept the licensing terms, and click Next to install Windows SteadyState.
6. Click on Finalize to complete the instilation of Windows SteadyState.

Windows SteadyState Handbook (PDF)
Windows SteadyState Handbook (XPS)

The shutdown command can be use via the command prompt, the remote shutdown dialog window, or in a batch file.  You can logoff, shutdown, or restart a computer with this tool.  You can even set the shutdown tool to perform a task at a certain time on certain days and to many computers at one time using a batch file.

This is a good tool to easily shutdown or restart lots of computers on a network at one time.  It can also be handy for helpdesk technicians when fixing remote computers.

The Switches

The shutdown command has a few options called switches.  You can always see them by typing shutdown -? in the command prompt if you forget any of them.

Usage: shutdown [-i | -l | -s | -r | -a] [-f] [-m \\computername] [-t xx] [-c "c
omment"] [-d up:xx:yy]

-i: Display GUI interface, must be the first option
-l: Log off (cannot be used with -m option)
-s: Shutdown the computer
-r: Shutdown and restart the computer
-a: Abort a system shutdown
-m \\computername: Remote computer to shutdown/restart/abort
-t xx: Set timeout for shutdown to xx seconds
-c ?comment?: Shutdown comment (maximum of 127 characters)
-f: Forces running applications to close without warning
-d [u][p]:xx:yy: The reason code for the shutdown u is the user code p is a planned shutdown code xx is the major reason code (positive integer less than 256) yy is the minor reason code (positive integer less than 65536)

Please note: I?ve noticed using a switch with a – sign doesn?t work sometimes. If you are having trouble try using a / in place of – in your switches.

Examples

shutdown ?m \\computername ?r ?f  This command will restart the computer named computername and force any programs that might still be running to stop.

shutdown ?m \\computername ?r ?f ?c ?I?m restarting your computer.  Please save your work now.? ?t 120  This command will restart the computer named computername, force any programs that might still be running to stop, give to user on that computer a message, and countdown 120 seconds before it restarts.

shutdown ?m \\computername ?a  This command will abort a previous shutdown command that is in progress.

Using a Batch File

You can create a file that performs the shutdown command on many computers at one time.

In this example I?m going to create a batch file that will use the shutdown command to shut down 3 computers on my home network before I go to bed.

Open notepad and type the shutdown command to shut down a computer for each computer on the network.  Make sure each shutdown command is on its own line.  An example of what should be typed in notepad is below.

shutdown ?m \\computer1 ?s
shutdown ?m \\computer2 ?s
shutdown ?m \\computer3 -s

shutdown -m \\computer1 -s -t 1

this will shutdown computer1 in 1sec

Now I?ll save it as a batch file by going to file, save as, change save as type to all files, give the file a name ending with .bat.  I named mine shutdown.bat.  Pick the location to save the batch file in and save it.

When you run the batch file it?ll shutdown computer1, 2, and 3 for you.

Make sure firewall is turned off or have these port open in the firewall

Port need to be open:

TCP 139
TCP 445
UDP 137
UDP 138

Display a local share
NET SHARE sharename
Display a list of computers in the current domain.
NET VIEW
To see a list of shares on a remote computer
NET VIEW \\ComputerName
To see a list of all shares in the domain:
NET VIEW /DOMAIN
To see a list of shares on a different domain
NET VIEW /DOMAIN:domainname
To see a list of shares on a remote Netware computer
NET VIEW /NETWORK:NW [\\ComputerName]

1. Install EMCO Remote Desktop 1.0 on your machines.
2. Configure Firewall on your machines( Please see the next session for more information about configuring Firewall on your machine)
Configuring Firewall
To configure Firewall on your machines perform the following steps:

3. Move to Control Panel.
4. Double click the Windows Firewall icon located in the Control Panel to launch the Windows Firewall applet.

5. Windows Firewall dialog box will appear on the screen.

6. Switch to the General tab.

7. If Firewall is turned on; make sure Don?t allow exceptions check box is unchecked.

8. Switch to Exceptions tab.

9. Check the File and Printer Sharing checkbox.

10. Click the Add Program button.

11. Add Program dialog box will appear on the screen.

12. Click the Browse button.

13. File open dialog box will appear on the screen.
14. Locate the NetServer.exe in %SYSTEM32% and click Open button.

15. Click Change Scope button.

16. Change Scope dialog box will appear on the screen.

17. Click the My network (subnet) only radio button.

18. Click OK button.
19. Click OK again in Add a Program dialog box.

20. Click Add Port button.

21. Add a Port dialog box will appear on the screen.

22. Type RPC\DCOM in the Port Name textbox.

23. Type 135 in the Port Number textbox.

24. Click TCP radio button to select it.

25. Click Change Scope button to set the scope of this port.

26. Change Scope dialog box will appear on the screen.

27. Click the My network (subnet) only radio button.

28. Click OK button.
29. Please repeat the steps from 20 to 27 to add the following ports as well:
a. 136
b. 139
c. 445
d. 5910
30. Click OK button again in Add a Port dialog box.
31 . Click the OK button in the Windows Firewall dialog box.
32 . You are now ready to run EMCO Remote Desktop 1.0 on this machine.

Backup the Windows registry

1 . Click the Start button and then click All Programs > Accessories > Run.

2 . In the Run dialog box, type the following text:

regedit

3. Click OK.

4. In the User Account Control window, click Continue.

5. On the File menu, click Export.

6. In the File name box, type a name that you will remember, such as Registry Backup.

7. select a location where you want to save the Registration Entries (.reg) file.

8. Click Save.

Manual steps to back up the registry in Windows Vista or in Windows XP

Windows Vista

1. Click Start, type systempropertiesprotection in the Start Search box, and then press ENTER.
If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.

2. Wait for Windows to search for available disks and most recent restore points. In the System Properties dialog box, on the System Protection tab, click Create,

3. Type a name for the restore point and then click Create.

4. After the restore point has been created successfully, click OK two times.

Note If System Restore is turned off, click to select the local disk, click Apply and then click Create.

Windows XP

1. Click Start, click Run, type %SystemRoot%\system32\restore\rstrui.exe, and then click OK.

2. On the Welcome to System Restore page, click Create a restore point, and then click Next .

3. On the Create a Restore Point page, type a name for the restore point and then click Create

4. After the restore point has been created, click Close.

Note If System Restore is turned off, you receive a message that asks whether you want to turn on System Restore now. Click Yes. Then, in the System Properties dialog box, click to clear the Turn off System Restore check box, click OK, and then repeat this step.

Manual steps to restore the registry in Windows Vista or Windows XP

Use System Restore to undo registry changes in Windows Vista or in Windows XP

Windows Vista

1. Click Start, type systempropertiesprotection in the Start Search box, and then press ENTER.
If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.

2. In the System Properties dialog box, on the System Protection tab, click System Restore,

3. In the System Restore dialog box select Choose a different restore point, and then click Next

4. Select the restore point that you want to use, and then click Next.

5. Confirm your restore point, and then click Finish System restore restores the selected Windows Vista configuration and then restarts the computer.

6. Log on to the computer. When the System Restore confirmation page appears, click OK..

Windows XP

1. Click Start, click Run, type %SystemRoot%\System32\Restore\Rstrui.exe, and then click OK.

2. On the Welcome to System Restore page, click Restore my computer to an earlier time (if it is not already selected), and then click Next .

3. On the Select a Restore Point page, click the system checkpoint. In the On this list select the restore point area, click an entry that is named “Guided Help (Registry Backup),” and then click Next. If a System Restore message appears that lists configuration changes that System Restore will make, click OK.

4. On the Confirm Restore Point Selection page, click Next. System Restore restores the previous Windows XP configuration and then restarts the computer.

5. Log on to the computer. When the System Restore confirmation page appears, click OK..

Some variants of the Zlob family, the so called DNSChanger, adds rogue DNS name servers to the registry of Windows computers and network settings of Macintosh computers[1] and therefore could potentially re-routes traffic from legitimate web sites to other suspicious web sites.

http://www.castlecops.com/p1021763-New_direct_install_zlob_rogue_virus_protect.html
http://www.symantec.com/security_response/writeup.jsp?docid=2005-042316-2917-99
http://parasitedb.com/parasite-zlob.html
http://forums.techguy.org/malware-removal-hijackthis-logs/580666-solved-win32-zlob-trojan-removal.html

Modified Connect.asp and manyservers.htm (zipped)

The Remote Desktop Web Connection ActiveX control allows you to access your computer through Remote Desktop, via the Internet, from another computer using Internet Explorer. You must be using Internet Information Services (IIS) to host a Web site to use this feature.

Remote Desktop Web Connection provides most of the same functionality as the Remote Desktop Connection software.

Note: Users of Windows Server 2003 do not need to download this package. They can manually add this package from Add/Remove in the Control Panel. This package is offered as a convenience to Microsoft customers.

The Remote Desktop Web Connection ActiveX control allows you to access your computer, via the Internet, from another computer using Internet Explorer. You can download the software on this page and run setup to install the ActiveX control and sample Web page on any computer running Internet Information Server 4.0 or higher.

Supported Operating Systems: Windows 2000; Windows 2000 Service Pack 2; Windows 2000 Service Pack 3; Windows NT; Windows Server 2003; Windows XP; Windows XP Media Center Edition.

Terminal Services Procedures

Logging On and Off Terminal Servers
Use Your Haas NT username and password to login to the Terminal Services. Please make sure the Log on to drop down field is set to Haas.
Please be sure to press CTRL-ALT-END or click the logoff button on the desktop to end your session. Just closing your browser will leave your session open, causing problems later.

Storing Personal Files
Store all Personal Files on your network drives (i.e. H:) or on your local machine drives. Files stored on the local Terminal Server drives will be deleted.

Transferring Data Between Your Local Machine and The Terminal Servers
With the recent upgrade to Windows Server 2003, you can now access your local drives in your terminal session.
1. When you first click the connect button, make sure the check box next to Connect your local disk drives to the remote computer is checked.
2. If you open My Computer in the terminal session all your local drives will be listed under other. Use the drive as you would any other drive.

Printing to your Local Printer
Terminal Services uses printer redirects. In doing so, you can open a terminal session and print to your locally installed printers at home or the office.

Connection Tips and Tricks (Hot Keys)
(top)
Terminal Services Keyboard Shortcuts

Keyboard Shortcut
Function

Alt+Del
Displays the active application’s Control menu.

Alt+Home
Opens the Windows Start menu within the client session.

Alt+Page Down
Cycles (from right to left) through the current taskbar programs.

Alt+Page Up
Cycles (from left to right) through the current taskbar programs.

Ctrl+Alt+Break
Toggles the client session between windowed and full-screen modes.

Ctrl+Alt+End
Opens the Windows Security dialog box, similar to pressing Ctrl+Alt+Del on the local workstation’s keyboard.

Ctrl+Alt+Ins
Cycles through the current taskbar programs in the order in which the user started them.

Ctrl+Alt+Plus (+)
Copies a snapshot of the entire client-session desktop area to the clipboard, similar to pressing Print Screen on the local workstation’s keyboard.

Ctrl+Alt+Minus (-)
Copies a snapshot of the active client window to the clipboard, similar to pressing Alt+Print Screen on the local workstation’s keyboard.

Installing Remote Desktop Web Connection on Windows XP Pro

To install Remote Desktop Web Connection

1. Open Add or Remove Programs in Control Panel.

2. Click Add/Remove Windows Components.

3. Select Internet Information Services, and then click Details.

4. In the Subcomponents of Internet Information Services list, select World Wide Web Service, and then click Details.

5. In the Subcomponents for World Wide Web Service list, click the Remote Desktop Web Connection check box, and then click OK.

6. In the Windows Components Wizard, click Next.

7. Open Internet Services Manager.

8. Expand the folder hierarchy until you reach the local computer name\Web Sites\Default Web Site\tsweb folder.

9. Right-click the tsweb folder and then click Properties.

10. Click the Directory Security tab on the Properties dialog box.

11. In Anonymous access and authentication control, click Edit.

12. Check the Anonymous access check box on the Authentication Methods dialog box, and then click OK twice.

Install Remote Desktop Web Connection on Windows Server 2003

To install Remote Desktop Web Connection

1. Open Add or Remove Programs in Control Panel.

2. Click Add/Remove Windows Components.

3. Select Internet Information Services, and then click Details.

4. In the Subcomponents of Internet Information Services list, select World Wide Web Service, and then click Details.

5. In the Subcomponents for World Wide Web Service list, click the Remote Desktop Web Connection check box, and then click OK.

6. In the Windows Components Wizard, click Next.

7. Open Internet Services Manager.

8. Expand the folder hierarchy until you reach the local computer name\Web Sites\Default Web Site\tsweb folder.

9. Right-click the tsweb folder and then click Properties.

10. Click the Directory Security tab on the Properties dialog box.

11. In Anonymous access and authentication control, click Edit.

12. Check the Anonymous access check box on the Authentication Methods dialog box, and then click OK twice.

If you double-click a drive or folder, Search Companion may start and the drive or folder may not open. If you configure settings for other actions that are associated with drives or file folders (for example, Open Command Window Here or Print Directory Listing), Windows may perform one of these actions instead of starting Search Companion.

This problem occurs even if you do not create a new action, edit existing actions, or change the default action in the Edit File Type dialog box.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To resolve this problem, edit the registry to set the value data for the Default string value in the registry keys that are described in the "Cause" section of this article to none:

1.Start Registry Editor (Regedt32.exe).

2.Locate and then click the Default value under the following keys in the registry if this problem occurs with folders:

HKEY_CLASSES_ROOT\Directory\shell

If this problem occurs with drives:

HKEY_CLASSES_ROOT\Drive\shell

3.Click Modify on the Edit menu.

4.Type none in the Value data box, and then click OK.

5.Quit Registry Editor.