Install the terminal server
In Windows Server 2003, the terminal service is not installed by default, and we need to add manual:
Click Start → Control Panel → Add or Remove Programs, click Add / Remove Windows Components tab in the Add or Remove Programs dialog box. Then check the Terminal Server option in the Component list. At this time, a warning dialog for IE security configuration may pop up, click the "Yes" button to turn it off and click the "Next" button.
In the Open "Select the Default Permissibility" dialog for the Application Compatibility, the system gives two installation modes, "complete security mode" and "loose security mode". Let's choose "Full Safety Mode" and click the "Next" button. No need to insert an installation disc, the file is copied, click the "Finish" button.
■ Configure Terminal Server
1. User permissions
By default, only system administrator group users (Administrators) and system group users have access and full control of the terminal server, and members of the remote desktop user group (Remote Desktop Users) only have access to access, without full control. right. In many cases, the default permission settings often do not fully meet our actual needs, so we also need to give certain permissions for remote connection of certain users:
Click Start → Administration Tools → Terminal Services Configuration, double-click the "RDP-TCP" connection in the right pane in the Terminal Services Configuration dialog box. Open the RDP-TCP Properties dialog. Then switch to the Permissions tab, click the Add button, fill in the username (such as Hanjiang) prepared to give privileges in the Enter Object Name Source editing box and click the "OK" button.
Returns the "RDP-TCP Properties" dialog box, in the Group and User Name list, click the user "hangjiang" just added, then check the check box in the permissions list box as needed. For example, we check the "Guest Access", "User Access" check box (Figure 1).
2. Limit the number of concurrent connections
By default, the terminal service does not limit the number of remote connections and only two concurrently managed remote desktop connections. Considering the resource problem of 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:
Switch to the Network Card tab in the RDP-TCP Properties dialog. In the NIC, select the NIC using the RDP-TCP protocol, then click "Most Connection Number" radio box, and adjust the concurrent connection value (for example: 20) in the fine tuning box on the right.
3. Set local resources available for clients
Switch to the Client Settings tab in the RDP-TCP Properties dialog box, you can check the items in the "Disable the following item" area to limit the use of client resources. For example, after checking the "Audio Mapping" checkbox, the server's sound will not pass through the client's sound card.
Play. Sometimes the demand for users is just the opposite, such as the local printer must be used. Then, the "Windows Printer Mappings" and "LPT port mapping" must be guaranteed (Figure 2).
■ Connect the terminal server
1. Install the client
Users want to remotely connect to the terminal server, first need to install the client. Suppose Windows Server 2003 system catalogs in C, then find the client installer in the C: / Windows / System32 / Client / Tsclient / Win32 directory. Divide the client installer to the client through "online neighbor" or other means and complete the installation.
2. Remote Connection
Click Start → All Programs → Remote Desktop Connections on the client, and click the Options button to switch to the Detailed Login dialog box in the open dialog. Type the IP address of the Terminal Server in the Computer Name editing box, type "Hanjiang" in the User Name editing box and click the Connection button. You can complete the connection after the Windows login dialog box is used. Tip: Of course, if you want to successfully connect to the terminal server, you must ensure that "Remote Desktop" connection is allowed: Right-click "My Computer" → Perform "Properties" → Switch to "Remote" tab → check "Allow users to remotely connect Go to your computer check box.
■ Application instance
Suppose the user "hanjiang" is not in units, but it is necessary to run an application in the Windows Server 2003 environment of the unit server. At this time, he can install the terminal server client in the local machine, and then operate with the "Remote Desktop Connection" to the unit's Terminal server.