Thin down with Windows 2000 Terminal Server

Windows 2000 Terminal Services (WTS), unlike Windows NT 4.0 Terminal Server, is built into the base OS, so you don't need a totally different version of Windows to get terminal server functionality.

WTS runs in two modes of operation — Application Server mode and Remote Administration mode. In Application Server mode, WTS functions in classic fashion as a multi-user version of Windows NT. Each connection must have a separate Terminal Server client license allocated to it. Unlike Windows NT Terminal Server, where you can bump your license count at will, Windows 2000 requires installation of a Terminal Services Licensing Server on a Windows 2000 domain controller or member server. The Licensing Server is a program that verifies the key codes on separately purchased client licenses that you install on the server (verification can also be done over the phone). Those licenses and the Licensing Server need to be installed within 90 days, or WTS is disabled. Microsoft's Terminal Server Licensing document outlines the licensing requirements in detail.

If you haven't moved to Active Directory yet, Microsoft suggests you install the Licensing Server on a Windows 2000 member server that you plan to promote to an Active Directory domain controller. By doing this, you won't have to re-install licenses or experience downtime on your terminal servers when you move to Active Directory.

When planning your first Terminal Server for Application Server use, you should consult Microsoft's white paper on Terminal Services Scalability, which helps you decide how much RAM and processor power you need to deploy your applications based upon tasks the applications' users will perform. For example, WTS is more RAM-intensive than it is CPU-intensive, so if you expect to roll out a middle-of-the-road data entry and database application to 35 users, you'll need a good gigabyte of RAM, even though a single, mid-range Pentium III processor will suffice. If you aim to scale a WTS-based application with multiple servers, you'll have to look at Citrix's Metaframe and Citrix Load Balancing as a potential add-on, because Microsoft doesn't currently offer clustering services for Terminal Servers.

If you're upgrading from an older terminal server product, read Microsoft's Upgrading to Windows 2000 Terminal Services guide, which goes into depth on NT 4.0 Terminal Server and Citrix Metaframe migration issues.

WTS's other mode, Remote Administration, meets a different need. It practically eliminates the need for remote console programs like Computer Associate's RemoteIT (Remotely Possible) and Symantec's pcAnywhere. WTS in Remote Administration mode performs significantly better and uses less network overhead than these third-party add-ons, and doesn't take up a significant amount of system resources when running, so you can feel safe putting it on all of your Windows 2000 servers. In Remote Administration mode Windows 2000 allows only the Administrator account to utilize WTS, and does not require additional licenses or a Licensing Server. Administrative mode is a great way to consolidate systems management tools, especially if you need to perform remote network administration or want to deploy a complex database-dependant tool, like Compaq's Insight Manager, to a number of people in your support group.

If you'd like to experiment with Remote Administration mode on your Windows 2000 Server, go to the Control Panel and choose Add/Remove Programs. Choose Add/Remove Windows Components, pick Terminal Services from the selection box in the Windows Components Wizard, and choose Remote Administration Mode.

You'll want to share the WTS client install directory from

\%SYSTEMROOT%\system32\clients\tsclient\net\win32

and install it on your support workstations.

Terminal Services is clearly one of the best ways to put Windows 2000 Server to use with the least amount of migration pain. With its built-in Remote Administration capabilities it's also a good way to begin experiencing Windows 2000 in your support group, because you don't have to upgrade your NT 4.0 and Windows 98 desktops to Windows 2000 Professional right away to reap Windows 2000's benefits.

Jason Perlow is a computer industry freelance writer covering Windows 2000 and Linux. He runs the New Jersey-based systems integration firm Argonaut Systems and can be reached at perlow@hotmail.com.