Clues on Installing Windows 2000 Terminal Services
- Set up Windows 2000 server.
- Go into Add/Remove Programs | Windows Components and add "Terminal
Services". If you don't want it to be a multi-user app server just yet, choose
to install it in "Admin mode" when it prompts you on your way back out.
- Install the Terminal Services Client onto a client machine. You can do
this several ways. The easiest is to download the latest version of the client
from Microsoft:
http://microsoft.com/windowsxp/pro/downloads/rdclientdl.asp
Alternatively, you can create the client diskettes from the server's Admin
Tools menu or just copy the source files over (I think they are in
Winnt\System32\Clients), but the downloadable client is much newer and nicer.
- Start the client. With the newer versions you can just go to "Start | Run"
and type "mstsc"; older versions will have the client accessible from a
"Terminal Services Client" folder off the Start Menu. The newer version can
also be reached from "Accessories\Communications\Remote Desktop Connection".
Type in the IP address or name of the server running TS and you can connect!
- If switching to application mode, you want to make SURE you install
Service Pack 3 for Windows 2000 before you go into full scale deployment; you
want the licensing enhancements it contains. DO NOT wait until you are
already issuing licenses to clients for this; if you do, you will have to redo
all your work later.
Command Line Install of Terminal Services
You can indeed install Terminal Services from the commandline; and there are
a few reasons why you might want to do such a thing.
- It can be faster and lower-maintenance if you have the command line handy.
- If you've screwed up and forgotten to add TS to a server that needs it and
is now five hundred miles away, you can possibly give someone a command to
run; much easier than a GUI walkthrough
- Same scenario, but if you have remote console access of some kind (such as
telnet) then you can do it yourself.
The technique involves careful use of rundll32's INF file install ability,
the TSOC.INF file, and correct section calls.
Possible Problems with Command Line Install
It's not perfect; here are a few things to remember:
- You need to reboot after installing Terminal Services.
- The system needs to copy source files. Make sure it has them
available and knows where they are if you don't have GUI access.
- Terminal Services will NOT show up as installed in Windows Components if
you install it this way.
Here's the rundll32 command to install Windows 2000 Terminal Services in
Remote Admin mode:
%SystemRoot%\System32\rundll32.exe setupapi,InstallHinfSection TerminalServices.FreshInstall 128 %SystemRoot%\inf\tsoc.inf
Back to main Terminal Services page