How to Connect to the Console SessionWhen you connect to the console session of a Windows Server 2003-based server, no other user has to be already logged on to the console session. Even if no one is logged on to the console, you are logged on just as if you were sitting at the physical console.
To connect from the remote Windows Server 2003-based computer, open a command prompt, and then type the following command:
When you use this command, you open the Remote Desktop session, and when the logon is authenticated, you are connected to the console session that is running on the Windows Server 2003-based server. If a user is currently working on the console session at the computer, you receive the following error message:
domain\username is logged locally on to this computer. The user has been idled for
number minutes. The desktop is unlocked. If you continue, this user's session will end and any unsaved data will be lost. Do you want to continue?
Note: If the console session user and the Terminal Services session user are the same, you can connect without any problems.
How to Shadow the Console SessionTo shadow the console session, first open a Remote Desktop connection to the Windows Server 2003-based server from another computer. By default, the Windows Server 2003 Remote Desktop Connection utility is installed in all versions of Windows Server 2003. You can either use this or the Mstsc command-line utility that is described in the "How to Connect to the Console Session" section, but omit the -console switch. After you open this session, start a command prompt in the session and type the following command to start the shadow session to the console:
If the user of the console session on the server clicks
YES, you are automatically connected to the console session on the remote Windows Server 2003-based server. If the user on the server's console clicks NO or does not respond, you receive the following error message at the command prompt on the remote computer:
Error :The request to control another session remotely was denied.
If you are logged on to the console of the server that is running Terminal Services, if you try to shadow another user's session from the console of the computer, you receive the following error message:
Remote Control Failed. Error Code 7050.
Error :The requested session cannot be controlled remotely.
This may be because the session is disconnected or does not have a user logged on. Also, you cannot control a session remotely from the system console and you cannot remote control your own current session.
Error : The requested session is not configured to allow Remote Control.
- Open the Group Policy snap-in (Gpedit.msc).
- In the left pane, under the Computer Configuration branch, expand the Administrative Templates branch.
- Expand the Windows Componentsbranch.
- Click the Terminal Servicesfolder.
- In the right pane, double-click Sets rules for remote control of Terminal Services user sessions.
- On the Setting tab, click
- In the Options box, click Full Control with users' permission, and then click OK.
Article ID: 278845 - Last Review: Sep 11, 2011 - Revision: 1