This step-by-step instruction guide describes how to configure Terminal Services in Windows 2000 Server for Remote Administration mode, which allows you to manage all of your computers remotely. This document describes how to install and configure Terminal Services, how to install and run the client, and briefly describes how to make Terminal Services work over firewalls.
Installing Terminal Services
You can install Terminal Services in two modes: Application Server mode and Remote Administration mode. Application Server mode is used for thin-client environments in which users have lightweight PCs and run programs remotely on the server instead of locally. Application Server mode requires a license for each connected user.
Remote Administration mode allows two low-resource simultaneous connections that are ideally suited for remote administration. No additional licenses are necessary, and the limit cannot be increased. This document describes Remote Administration mode.
To Install Terminal Services
- Insert the Windows 2000 Server CD-ROM into the CD-ROM or DVD-ROM drive.
- If a dialog box appears automatically after you insert the CD-ROM, click Install Add-on Components. If no dialog box appears, click Start, point to Settings, and then click Control Panel. Double-click Add/Remove Programs, and then click Add/Remove Windows Components.
- In the list of components, click to select the Terminal Services check box.
- Click to clear the Terminal Services Licensing check box if it is selected. You do not need this service for Remote Administration mode. Click Next.
- Click Remote Administration Mode, and then click Next.
- The Terminal Services Wizard runs and installs Terminal Services. Close the wizard when it is finished, and then reboot your computer if you are prompted to do so.
Connecting to Terminal Services
To connect to Terminal Services running on a server, you must use a Terminal Services client. The client is available on the server on which you installed Terminal Services, in the following folder:
Create a share on your server so that you can easily install the client on any computer.
To Create a Share on Your Server
- Use Windows Explorer to locate the %SystemRoot%\System32\Clients\Tsclient\Net\Win32 folder. Note that %SystemRoot% may be the C:\Winnt folder.
- Right-click the Win32 folder, and then click Sharing.
- On the Sharing tab, click Share this folder.
- Change the share name to TSClient.
- Click Permissions.
- Click to clear the Full control and Change check boxes. Only the Read permission should be selected.
- Click OK, and then click OK.
Follow the next steps on the computer from which you want to perform remote administration. The Terminal Services client runs on any 32-bit version of Windows, including Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows Millennium Edition (Me), Microsoft Windows NT 3.5x and 4.0, Microsoft Windows 2000 Professional, and various server versions. Connect to the share you created earlier. The share is named \\Servername
\TSClient, where Servername
is the name of the computer on which you installed Terminal Services. You do not have to follow the uppercase and lowercase convention that is used in this article.
To Install the Terminal Services Client
- Connect to the \\Servername\TSClient share that you created earlier.
- Double-click Setup.exe.
- Click Continue in the dialog box that appears, and then type your name and organization in the next dialog box.
- Click I agree (if you agree) when you see the license agreement.
- Click the large button in the next dialog box. You can change the installation path first, if you want to.
- Click Yes when you are prompted whether you want all users to have the same initial settings.
Using the Terminal Services Client
Before you can manage your Terminal Services servers remotely, you must create a connection to these servers. This procedure uses the Client Connection Manager tool to create icons for all of the Terminal Services servers you want to manage.
To Create a Connection to the Terminal Services Server
- Click Start, point to Programs, point to Terminal Services Client, and then click Client Connection Manager.
- When the Client Connection Manager Wizard starts, click Next.
- In the Connection name box, type a descriptive name for the connection.
- In the Server name or IP address box, type the server's name or IP address, or click Browse to search for the server. When you are done, click Next.
- Leave all automatic logon information blank. Using automatic logon information might present a security problem if a non-administrator has access to the computer from which you run the client. Click Next.
- Click a screen resolution that is appropriate for you. It is best to use the largest area you can select (the client does not let you select an area that is larger than your local screen can display). Do not select Full screen at this time; you can toggle between windowed and full screen modes later. Leaving the initial connection in a window helps reinforce the fact that you are working on a remote computer rather than your local workstation. Click Next.
- Leave the Enable data compression and Cache bitmaps check boxes clear. They are useful only if you are working over a slow dial-up link. Click Next.
- Leave the Start the following program check box clear. You want the client to display the server's desktop. Click Next. Change the icons if you want to. Click Next. Click Finish to complete the wizard.
This process creates an icon for your server. Double-clicking the icon connects you to the server. You can also right-click the icon to change the connection properties if you need to.
To Connect to the Server Using Terminal Services
- Double-click the server icon in Client Connection Manager.
- The Terminal Services client window appears and displays the server's logon dialog box. You might need to double-click the window's title bar to see it all.
- Type an appropriate set of credentials to log on to the server.
Typically, you will log on as some kind of administrator (local, domain, or enterprise).
- If you use correct credentials, you see the server's desktop.
Note that this is very different from using a remote-control product. You are not manipulating the keyboard, mouse, and screen at the server. Instead, you are logged on to the computer and have created a new session, but this session is displayed remotely, over Terminal Services, rather than locally at the computer. You do, however, have full access to the computer's programs just as if you were working at its local console.
Disconnecting the Terminal Services client
There is an important distinction between disconnecting from a session and logging off. If you only close the Terminal Services client window, your session remains active on the server. When you connect again, Terminal Services reconnects you to that session. Any programs that you left running in the session are still available. To end the session, you need to log off by using the remote computer's Start
menu. Note that this logs you off and ends the remote session. It does not log off the user at the computer's local console.
Useful Client Shortcut Keys
Collapse this tableExpand this table
|Key combination ||Function ||Similar local keys |
|CTRL+ALT+END ||Opens the Windows Security dialog box ||CTRL+ALT+DELETE|
|CTRL+ALT+BREAK ||Toggles the Terminal Services client display from window to full screen|
|ALT+INSERT||Cycles through running programs on the remote computer||ALT+TAB|
|ALT+HOME||Displays the remote computer's Start menu|
|ALT+DELETE||Displays the remote window's Control menu||ALT+SPACE BAR|
You can take screenshots with these shortcuts:
Collapse this tableExpand this table
|Key combination||Function||Similar local keys|
|CTRL+ALT+NUMBER PAD MINUS||Places an image of active window onto the TS clipboard||ALT+PRINT SCREEN|
|CTRL+ALT+NUMBER PAD PLUS||Places an image of the entire Terminal Services client on the Terminal Services clipboard||PRINT SCREEN|
TroubleshootingCannot Connect Because of a Firewall Between the Client and the Server
Terminal Services operates over TCP port 3389. If a firewall is protecting the server to which you want to connect, that firewall must permit inbound connections to the server's TCP port 3389. If you are running the client from behind a firewall, that firewall must permit outbound connections to TCP port 3389. Check with your firewall administrator for assistance.
Article ID: 300847 - Last Review: November 1, 2006 - Revision: 2.4
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
|kbhowto kbhowtomaster KB300847|