Using remote control

  • Article

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

Using remote control

You can monitor the actions of a client logged on to a terminal server by remotely controlling the user's session from another session. Remote control allows you to either observe or actively control another session. If you choose to actively control a session, you will be able to input keyboard and mouse actions to the session. A message can be displayed on the client session asking permission to view or take part in the session before the session is remotely controlled. You can use Terminal Services Group Policies or Terminal Services Configuration to configure remote control settings for a connection and Terminal Services Manager to initiate remote control on a client session. For instructions on configuring remote control, see Configure remote control settings. For instructions on using remote control, see Remotely control a session.

Windows Server 2003 family operating systems also support Remote Assistance, which allows greater versatility for controlling another user's session. Remote Assistance also provides the ability to chat with the other user. For more information, see Windows interface administrative tool reference A-Z: Remote Assistance.

Notes

  • Remote control can also be configured on a per-user basis using Group Policies or the Terminal Services Extension to Local Users and Groups and Active Directory Users and Computers.

  • The console session cannot remotely control another session, and a client session cannot remotely control the console session.

  • The computer used for your session must be capable of supporting the video resolution used at the remotely controlled client session. Otherwise, the operation fails.