This step-by-step article describes how to install Windows 2000 Terminal Services in Remote Administration mode. When you use Terminal Services, remote client computers can gain access to Windows-based programs that are running on the server. Windows 2000 Server and Windows 2000 Advanced Server include Terminal Services client software to support 16-bit and 32-bit Windows-based clients. When you use Terminal Services in Application Server mode, Terminal Services provides a multiple-session environment for server-side computing. When you use Terminal Services in Remote Administration mode, you can use Terminal Services to gain access to either physically or logically distant servers.
Before you install Windows 2000 Terminal Services, review the following concepts:
Server: The server is the computer on which nearly all of the computing resources reside. The server is used in the Terminal Services networking environment. The server receives and processes the key strokes and mouse movements that take place at the client. The server displays the desktop and the programs that are running on the server in a window on the client.
Messaging: Messaging is the communication that occurs between the server and clients by using Remote Desktop Protocol (RDP). RDP is an program-layer protocol that relies on Transmission Control Protocol/Internet Protocol (TCP/IP).
Client: The remote desktop that is running on the server is displayed in a window on the client. When you start programs on the client, these programs are actually running on the server.
You can install Terminal Services in either of the following modes:
Remote Administration mode: When you use Terminal Services in Remote Administration mode, the server accepts only two Terminal Services client connections. When you use this mode, you do not require licensing; however, only members of the Administrators group can gain access to the server. It is recommended that you use this mode for non-Terminal Services servers to configure remote control-type access to remote servers.
Application Server mode: When you use Terminal Services in Application Server mode, the server accepts more than two simultaneous connections by non-administrators. When you use this mode, you must install the Terminal Services Licensing service on a domain controller (you can install this service on any server in a workgroup environment). You also require a Terminal Services Client Access License if you use any non-Windows 2000 Professional-based clients.
How to Install Terminal Services in Remote Administration Mode
To install Terminal Services in Remote Administration mode on the domain controller, log on to server as an administrator, and then follow these steps:
Click Start, point to Settings, click Control Panel, and then double-click Add/Remove Programs.
Click Add/Remove Windows Components.
After the Windows Components Wizard starts, click to select the Terminal Services check box, and then click Next.
For more information about the subcomponents that are included in Terminal Services, click Details. The following sub-components are displayed:
Client Creator Files: Windows uses these files to create installation disks for Terminal Services client computers.
Enable Terminal Services: Windows uses this component to configure the Terminal Services software on your computer.
On the Terminal Services Setup page, click Remote Administration mode, and then click Next.
NOTE: You do not need a Terminal Server Client Access License to run Terminal Services in Remote Administration mode. Therefore, Terminal Services Licensing is not configured for the scenario that is described in this article. A maximum of two concurrent connections are automatically allowed on a Terminal server in Remote Administration mode.
If you are prompted, insert your original installation media.
When the installation is completed, click Finish, and then click Close.
If Terminal Services does not run as expected, check the Internet Protocol (IP) address. Issues may occur if you provide an invalid IP address.
If a program does not run as expected, consider the following issues:
Programs that lock files or dynamic-link library (DLL) files may not run properly. This issue can occur if more than one user is trying to use the same program at the same time.
Programs that use a computer name or an IP address for identification purposes may not run properly. This issue can occur if more than one user at a time runs the program while using the same information.