Explain that win2003 Terminal Services is connected to and implicitly using

In Windows Server 2003, when you use Terminal Services, you can connect to a console session (session 0) and simultaneously open a hidden session to the session (provided You cannot connect from this console session). With this additional feature, you can remotely log in to a Windows Server 2003-based server running Terminal Services and interact with Session 0 as if you were physically in front of the console of your computer. The session can also be hidden so that the remote user and the local user who is actually in front of the console can see and interact with the same session.

How to connect to a console session

When you connect to a console session on a Windows Server 2003-based server, you do not need any other users to log in to the console session beforehand. Even if no one is logged into the console, you can log in as if you were actually in front of the console.

To connect from a Windows Server 2003-based remote computer, open a command prompt and type the following command:

mstsc -v: servername /F -console

where mstsc is the executable for the remote desktop connection, -v specifies the server to connect to, /F specifies the full screen mode, and -console is the instruction to connect to the console session.

When you use this command, you will open a remote desktop session, and when the login information is verified, you are connected to a console session running on a Windows Server 2003-based server. If a user is currently using a console session on that computer, you will receive the following error message:

The user 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? Then, the user of the current console session will be logged out and you will receive a message. Indicates that the computer is currently locked and only the administrator can unlock it.

Note: If the console session user and the Terminal Services session user are the same user, you will be able to connect as normal.

How to hide a console session

To hide a console session, first open a remote desktop connection to a 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 use the utility or the Mstsc command-line utility described in the section "How to connect to a console session", but the -console switch should be omitted. After opening the call, start a command prompt in the session and type the following command to start a hidden session of the console:

shadow 0

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

When negotiating a remote control license, your session seems to be frozen. Please wait... In the console session on the server, you will receive the following message:

Domain \\ Username Requesting remote control of your session.

Accept the request? If the console session user on the server clicks "yes", you will automatically connect to the console session on the Windows Server 2003-based remote server. If the user of the server console clicks "No" or does not respond, you will receive the following error message at a 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 the hidden session from the remote side, press Ctrl + * (on the numeric keypad) and you will be returned to the established Windows-based The original session of the server for Server 2003.

If you log in to the console of a server running Terminal Services and try to hide another user's session in that computer's console, you will receive the following error message:

Your session Please 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 based on Windows Server 2003 The server is not configured to allow remote control, 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 Operation:

Open & ldquo; Group Policy & rdquo; management unit (Gpedit.msc).

In the left pane, expand the "Administrative Templates" branch under the "Computer Configuration" branch.

Expand the "Windows Components" branch.

Click the <quo;Terminal Services” folder.

In the right pane, double-click “Setting Rules for Remote Control for Terminal Services User Sessions”.

On the “Settings' tab, click “Enabled”.

In the “Options" box, click “ Full Control by User Authorization", then click “OK”.