This step-by-step article describes how to use the Remote Control feature in Windows Terminal Services.
Using the Remote Control feature in Windows Terminal Services allows authorized users to interact with other users’ sessions. A common use for Remote Control might be in helpdesk scenarios.
Check the following items when you are using the Remote Control feature in Terminal Services:
Verify User Permissions
Verify that the user has permission to initiate Remote Control. Administrators, by default, can use Remote Control with other users’ sessions. Users do not have this right. To give specific rights for groups other than Administrators:
- Start the Terminal Services Configuration tool.
- Double-click the connection you want to modify.
- Click the Permissions tab.
- Click Advanced, and then click Add.
- Specify the user or group you want to add so the user or group can use Remote Control.
- After adding the user or group, the Permission Entry dialog box appears. Click to select the Allow column for Remote Control.
- Click OK.
- Click OK, and then click OK.
Remote Control from the Console
Remote Control does not work from the console. This behavior is by design.
To initiate a Remote Control session:
- Open a Terminal Server Client session to the Terminal Server.
- When the session is running, start Terminal Services Manager.
- Connect to the server on which the user is logged on.
- Right-click the user’s name, and then click Remote Control.
- By default, the user is prompted to accept the Remote Control session. When the user accepts your request you can interact with the user’s environment.
Remote Control Console Session
You cannot remotely control the session labeled Console. This behavior is by design.
Remote Control with Similar Client Protocols
Remote Control only works with similar client protocols. Microsoft Remote Desktop Protocol (RDP) can only remotely control other RDP clients.
Reference by : http://www.microsoft.com