Riguy Index and Archive:
Microsoft Windows 2000 Terminal Services (Part 1)
Overview:Ø Microsoft Terminal Services (TS) allows for remote connectivity from virtually any MS client system to a server. The instructions here really contain several parts: installation and configuration on the server and installation and configuration on the client. In fact, I dragged this out into 3 parts total. I performed a Terminal Services installation in Remote Administration Mode on my home-based SOHO Local Area Network. Along the way, I 'snapped' these images (using 20/20 software).
Ø Before starting, it's always a good idea to check out the Start/Help documentation. The Microsoft Help documents are excellent. Type in "Terminal Services, best practices" into the Index keyword area for overviews and specifics:
Ø The best source of information on Microsoft Terminal Services is @ MS itself:
http://www.microsoft.com/windows2000/technologies/terminal/default.asp
The key point with TS is to choose which mode to install: Application versus Remote. Also, keep in mind licensing issues. From the Technet link below, verbatim:
· "Application Server. In Application Server mode, applications can be deployed and managed from a central location, saving administrators initial development and deployment time-as well as the time and effort required for maintenance and upgrades. Once an application is deployed using Terminal Services, many clients can connect-whether through a remote access connection, local area network (LAN), or wide area network (WAN). As well, clients can be Windows-based, Windows CE-based, or even non-Windows-based.
Licensing is required when deploying a Terminal Services-enabled server as an application server. Each client, regardless of the type of operating system and protocol used to connect to Terminal Services, must have the Terminal Services Client Access License (CAL) as well as a Windows 2000 Server CAL. Each copy of Windows 2000 Professional includes a Terminal Services CAL, but not a Windows 2000 Server CAL. Access from earlier versions of Microsoft Windows NT®, as well as clients using other operating systems, must purchase a Terminal Services CAL and Windows 2000 Server CAL, or the appropriate upgrade licenses.· Remote Administration. Terminal Services Remote Administration mode allows any server running Windows 2000 Server (for instance, a domain controller, or BackOffice® Server) to be administrated remotely with full access to all the built-in graphical user interface-based (GUI-based) administrative tools, as if the administrator was sitting right at the server. This ability to administer the server can be made available from any client device, including legacy MS-DOS®-based PCs, Windows 95 or Windows 98, Windows NT, or even non-Windows-based clients. This server management feature is an invaluable tool for quick and easy administration of large- and small-scale networks. Terminal Services has two built-in per-server connections specifically for Remote Administration. A Terminal Services CAL is not required to connect to Terminal Services in Remote Administration mode. "
An overview, including the definitions of Application versus Remote mentioned above, of Terminal Services can be found here:
Ø Install Terminal Services:
Keep in mind, per the Help Documents and Technet , Microsoft strongly advises installation on a member server, not on a domain controller. The resource drain from TS on a DC might be too much for some. Go into Control Panel if TS is not yet installed. Go into Add/Remove, then select components. Scroll down to locate TS, as well as TS Licensing if needed [see above definition/comparison of Application versus Remote mode]:
Ø Select the appropriate mode to use. Here, "Remote administration mode" is chosen:
Ø As "Configuring Components" screen begins, our friend, "Please insert the." appears. At this point, the i386 Directory from the Windows 2000 Server CD-ROM is needed:
Ø In my case, I browsed to where I have a copy of the i386 Directory (it's always good to simply copy the entire i386 Directory to a local or networked drive):
Ø The Install of Terminal Services is finished!
Ø In the Services window, via my favorite MMC (or, Start/Programs/Administrative Tools), I selected Terminal Services.
Ø Start the service via the old double-click. Be sure it is set for Automatic Startup type, unless starting the service manually is preferred:
