Deploy Windows Server 2003 Terminal Services

■ Install Terminal Server

In Windows Server 2003, Terminal Services is not installed by default, we need to manually add:

Click "Start → Control" Panel → Add or Remove Programs, click the Add/Remove Windows Components tab in the Add or Remove Programs dialog box. Then check the "Terminal Server" option in the "Components" list. A warning dialog about IE security configuration may pop up, click the "Yes" button to close it and click the "Next" button.

In the "Select Default Permissions for Application Compatibility" dialog box, the system gives two installation modes, "Full Security Mode" and "Loose Security Mode". We select "Full Security Mode" and click the "Next" button. There is no need to insert the installation CD, and after the file is copied, click the "Finish" button.

■ Configure the terminal server

1. Granting User Permissions

By default, only the System Administrators group (Administrators) and System Group Users (SYSTEM) have access to and full control of the Terminal Server, and members of the Remote Desktop Users group. Only have access rights without full control. In many cases, the default permission settings often does not fully meet our actual needs, so we also need to give special permission to users to connect remotely:

Click "Start → Administrative Tools → Terminal Services Configuration, double-click the RDP-Tcp connection in the right pane in the Terminal Services Configuration dialog that opens. Open the RDP-Tcp Properties dialog. Then switch to the "Permissions" tab, click the "Add" button, fill in the user name (such as hanjiang) to be given permission in the "Enter the object name source" edit box and click the "OK" button.

After returning to the "RDP-Tcp Properties" dialog box, click the user "hangjiang" you just added in the "Group and User Name" list, and then check the check box in the permission list box as needed. For example, we check the Allow Guest Access and User Access check boxes (Figure 1).

2. Limit the number of concurrent connections

By default, Terminal Services does not limit the number of remote connections, and only allows two concurrent management remote desktop connections. Considering the problem of saving server system resources, we can limit the number of concurrent connections to ensure that the server maintains high performance. The setting method is as follows:

In the "RDP-Tcp Properties" dialog box, switch to the "Network Card" tab. In the NIC drop-down list, select the NIC that uses the RDP-Tcp protocol, then click the "Maximum connections" radio button and adjust the concurrent connection value (for example: 20) in the spin box on the right.

3. Set the local resources available to the client

In the "RDP-Tcp Properties" dialog box, switch to the "Client Settings" tab, you can check the items in the "Disable the following items" area to limit the client Use of resources. For example, after checking the "Audio Mapping" check box, the server-side sound will not be played by the client's sound card. Sometimes the user's needs are just the opposite, such as the need to use a local printer. Then you must ensure that "Windows Printer Mapping" and "LPT Port Mapping" are unchecked (Figure 2).

■ connecting terminal server

1. Installing the client

To remotely connect to the terminal server, the user first needs to install the client. Assuming that the Windows Server 2003 system directory is on the C drive, you can find the client installer in the "C:\\Windows\\System32\\Client\\Tsclient\\Win32" directory. Distribute the client installer to the client and complete the installation through My Network Places or other means.

2. Remote Connection

Click “Start→All Programs→Remote Desktop Connection” on the client, and click the “Options” button in the dialog box that opens to switch to the detailed login dialog. Type the IP address of the terminal server in the "Computer Name" edit box, type "hanjiang" in the "User Name" edit box and click the "Connect" button. After the Windows login dialog appears, type the password for the authorized username to complete the connection.

Tip: Of course, in order to successfully connect to the terminal server, you must ensure that the "Remote Desktop" connection is allowed: right click on "My Computer" → execute "Properties" → switch to "Remote" tab → check Select the "Allow users to connect to your computer remotely" checkbox.

■ Application example

Assume that the user "hanjiang" is not in the unit, but needs to run an application in the Windows Server 2003 environment of the unit server. At this time, he can install the terminal server client on the local machine, and then connect to the terminal server of the unit through "Remote Desktop Connection" to operate