Connection session 0

How to use the Windows Server 2003 terminal service to connect to and hide console sessions

System promptNote: This articleArticleThe content is applicable to other versions of Windows (excluding the version you are using ). The content of this article may not apply to your computer. View Windows XP Help and Support Center

To hide a console session, first open the Remote Desktop Connection to a server based on Windows Server 2003 from another computer. By default, Windows Server 2003 Remote Desktop Connection utility is installed in all versions of Windows Server 2003. You can use this utility or the mstsc command line utility described in "how to connect to console sessions", but it should be omitted-ConsoleSwitch. After opening the session, start the command prompt in the session, and then type the following command to start the hidden session in the console:

Shadow 0

After entering and sending this command, you will receive the following message:

When you negotiate a remote control license, your session seems frozen. Please wait...

In the console session on the server, you will receive the following message:

Domain / User Name Requesting remote control of your session.
Are requests accepted?

If the user clicks "yes" on the console session on the server, you will automatically connect to the console session on a remote server based on Windows Server 2003. If the server console user clicks "no" or does not respond, you will receive the following error message at the command prompt on the remote computer:

Remote control failed. Error Code 7044
Error [7044]: The request to control another session remotely was denied.

To disconnect a hidden session from the remote end, press Ctrl + * (on the keyboard) and you will return the established original session to the server based on Windows Server 2003.

If you log on to the console of the server running the terminal service and try to hide the session of another user in the console of the computer, you will receive the following error message:

Your session may appear frozen while the remote control approval is being negotiated. Please wait...
Remote control failed. Error Code 7050.
Error [7050]: 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.

If remote control is not configured for a Windows Server 2003-based server, you will receive the following error message:

Remote control failed. Error Code 7051
Error [7051]: The requested session is not configured to allow remote control.

To configure a Windows Server 2003-based server to allow remote control, follow these steps:

1. Open the Group Policy Management Unit (gpedit. MSC ).
2. In the left pane, expand the manage template branch under the "Computer Configuration" branch.
3. Expand the "Windows Components" branch.
4. Click the terminal service folder.
5. In the right pane, double-click "set rules for remote control of terminal service user sessions ".
6. On the "Settings" tab, click "enabled ".
7. In the options box, click full control with user authorization, and then click OK ".

Back to Top