Remotely control a session

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

To remotely control a session

Open Terminal Services Manager.
Right-click the session you want to monitor, and then click Remote Control.

The Remote Control dialog box appears.
In Hot key, select the keys you want to use to end a remote control session, and then click OK. The default hot key is CTRL+* (using * from the numeric keypad only).

When you want to end remote control, press CTRL+* (or whatever hot key you have defined).

Notes

You must have Full Control permission to remotely control another session.
To open Terminal Services Manager, click Start, click Control Panel, double-click Administrative Tools, and then double-click Terminal Services Manager.
To configure remote control settings for a connection, use Terminal Services Configuration. Remote control can also be configured on a per-user basis by using the Terminal Services Extension to Local Users and Groups and Active Directory Users and Computers.
Before monitoring begins, the server warns the user that the session is about to be remotely controlled, unless this warning is disabled. Your session might appear to be frozen for a few seconds while it waits for a response from the user.
When you enter the remote control session, your current session shares every input and output with the session you are monitoring.
Your session must be capable of supporting the video resolution used at the session you are remotely controlling or the operation fails.
The console session can neither remotely control another session nor can it be remotely controlled by another session.
You can also use the shadow command to remotely control another session.

Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.