Windows Remote Desktop

Generally, the operating systems used by our company's servers are Windows 2000 Server or Windows 2003, and the Remote Desktop of these two versions is very different from Windows XP, in versions 2000 and 2003, if the server itself has logged on to the system desktop and runs some services or applications on it Program If other computers on the network access the system desktop through Remote Desktop Connection at the same time, these enabled services and applications will not be seen, because the Remote Desktop Connection in the 2000 and 2003 systems does not use the currently logged-on processes, instead, a new process is used to enable the session connection.

Using a new process to enable session connection makes it inconvenient for actual use. For example, you have logged on to the server and started the Domino Mail System, if you need remote management, you cannot configure it after the connection is connected. If you start the Domino service on the Remote Desktop, a prompt is displayed indicating that the program and application have been started. In addition, for some built-in system services such as IIS and FTP services, if the local machine has been started, you will not be able to perform any operations and settings after you connect to the remote desktop using a new session. This kind of non-human nature is still quite common.

In contrast, Windows XP does not have this problem, because in Windows XP, when another user connects to the local computer from the network, the current user will automatically log out and quit, users who connect to the Remote Desktop through the network will see the desktop information displayed before the cancellation. In this way, the non-human problems of Windows 2000 and Windows 2003 Remote Desktop can be solved perfectly.

Solution:
1. Remote Desktop Connection Control settings:

You can set parameters in the Remote Desktop Connection component to solve the problem that Multiple Remote Desktop accesses cannot share the console.

Step 1: Start the remote desktop settings window through "Start> Control Panel> remote desktop settings.
Step 2: Set the Remote Desktop on the Root Node of the console on the left to add a new connection.
Step 3: In the new connection settings window, there is an option to "connect to the console". You can check it with a check box. In this way, when we connect to the server through "Remote Desktop" again, we will automatically connect to the "console" to share the display information of the current desktop.

TIPS: in other cases, we want to restrict each user to one session. That is to say, no matter how many people connect to the server over the network, as long as they use the same account, they will share the same desktop display. The method is to set "Server Settings" in "terminal service configuration" and "restrict each user to use one session" to "yes.

2. Connection command settings:

We have discussed how to fundamentally solve the problem of non-human nature of Windows 2000 Server and Windows 2003. We have set our system to allow multiple users to connect to and share a remote desktop session. However, in most cases, we want the server to continue to maintain this dedicated remote desktop session connection function. What should we do if we want to temporarily log on to the server console? In fact, we can start with the connection command.

Step 1: click "Start> Run" on the taskbar ".
Step 2: Enter "mstsc/console" (without quotation marks) in the "run input" column and press enter to start the remote desktop program.
Step 3: add the parameter/console command to start the Remote Desktop. After the connection is established, the console of the target system is automatically connected, that is, the shared console function mentioned above.

TIPS: If you want to save a step, you can choose "Start> RUN> enter XXX. xxx. xxx. xxx/Console Command, and then press enter to implement the same functions as described above, where xxx. xxx. xxx. XXX is the IP address of the server.

Summary

Through the two methods we introduced, One fundamentally solves the problem that Windows 2000 Server and Windows 2003 systems cannot share the console; the other is to help us temporarily implement the shared console function. The two methods are suitable for different situations. You can select them based on your company's actual situation. After the settings are complete, the Windows 2000 Server and Windows 2003 system will only allow one session to operate at the same time. When other users in the network have successfully connected through the Remote Desktop, the currently logged-on session is automatically logged out.