Installing Terminal Services on Windows 2000 Professional
=========================================================

Written by: Skywing. Credits: http://dev.remotenetworktechnology.com/ts/ts2kinstallclues.htm for the TS command-line install settings.

You must be a member of the Administrators group in order to perform this procedure. It would probably also be a good idea to back up your Registry when doing this; incorrectly setting your Windows 2000 product identification information could very easily result in a nonbootable system.

1) Install Service Pack 3 and all the latest updates for the Windows 2000 Professional machine. Optimally, you should patch up your Windows 2000 Server files at this point.

2) Start REGEDT32 (NOT REGEDIT) and go to HKEY_LOCAL_MACHINE\System\ControlSet002\Control\ProductOptions and set REG_MULTI_SZ "ProductSuite" to "Enterprise
Terminal Server
" (yes, those are linebreaks). [u]DO NOT TOUCH[/u] ProductType.

3) Restart Windows 2000, [u]making sure to select the "Last Known Good Configuration" option from the boot menu[/u]. You MUST use the Last Known Good Configuration for this boot, a normal boot will NOT suffice!

4) Copy TsOc.inf, TsOc.pnf, LicenOc.inf, LicenOc.pnf, Machine.inf, and Machine.pnf from %SystemRoot%\inf on a Windows 2000 Server install to %SystemRoot%\inf on the Windows 2000 Professional machine. You might be able to extract these from the CAB files on a Windows 2000 Server (or higher) CD-ROM.

5) Copy tsoc.dll and licenoc.dll to/from %SystemRoot%\System32\Setup.

6) Copy these files to a directory of your choosing on the Windows 2000 Professional machine. You can find them in a variety of places on a Windows 2000 server install; most are in %SystemRoot%\System32, %SystemRoot%\System32\Drivers and %SystemRoot%\Application Compatibility Scripts. Use Find for Files if you can't find some of them.

7) Run the following command: %SystemRoot%\System32\rundll32.exe setupapi,InstallHinfSection TerminalServices.FreshInstall 128 %SystemRoot%\inf\tsoc.inf. When prompted for a source location, enter in the directoy you picked earlier. You might be prompted twice for the file location, with the installer having added "i386" to the end of the path; remove this and hit Retry. Ignore any ".001" files which can't be located. Cancel out any Windows File Protection dialogs which might appear at this time (keep the "unrecognized file versions").

8) Edit %SystemRoot%\inf\SysOc.inf and add the following lines under [Components]: LicenseServer=LicenOc.dll,EntryProc,LicenOc.inf,,6 and TerminalServices=TsOc.dll, HydraOc, TsOc.inf,,2.

9) Go to Add/Remove Programs and select Add/Remove Windows Components. Select Terminal Services > Enable Terminal Services and Terminal Services Licensing (if you don't already have a licensing server, or are going to be using Application Server mode), and proceed with the installation. Point the installer to the directory you selected above and let it copy files. Ignore any ".001" files which might not be located, and once again, exit any Windows File Protection dialogs.

10) Restart Windows 2000.

11) Check to make sure that you have a "Terminal Services" (servicename=TermService) in your services listing (Control Panel > Administrative Tools > Services). If not, retry the installation steps above, perhaps rebooting in between them.

12) Start REGEDT32 (NOT REGEDIT) and go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\Root and change the security permissions via the Security menu as follows: Add an entry for "Full Control" for "Administrators".

13) Apply the following .reg files: LEGACY_TERMDD.reg, LEGACY_TDTCP.reg, and LEGACY_RDPWD.reg.

14) Restart the computer or terminate and restart Terminal Services and start the drivers mentioned above with 'net start <drivername>', where <drivername> excludes the LEGACY_ tag.

15) Remove the permissions you changed in step 12. You should have a functional Terminal Services installation on Windows 2000 Professional at this point.

It's likely that you can copy many of the files mentioned above from a Windows 2000 server CD-ROM. The installer should be intelligent enough to navigate the CD-ROM itself if you've got one (or have downloaded an image of one and extracted it to your harddrive).

I was just about to say the same thing.