Client licensing for Windows 2000 Server Terminal Services?

[gmoney007]

Hi All,

I'm having a Windows 2000 server problem. We are trying to set up Windows 2000 server so that we can run apps from remote locations (application server mode). We have been working on setting up a Terminal Services Licensing Server, but have hit a snag.

We found the following MS support page telling us how to activate a terminal services licensing server:
http://www.microsoft.com/windows200.../WINDOWS2000/en/server/help/ts_lice_c_015.htm

OK, no problems. Our server says it is activated and all that nice stuff.

Now, as I understand it, we need to install client license packs to allow our other computers to connect to the server and be properly licensed. We open Terminal Services Licensing, and right click on the server that is acting as a Terminal Services Licensing server. We select "Install Licenses" from the popup menu.

Now, a wizard pops up asking for "the license code found in your product packaging." What license code, and in which product packaging? I tried serial numbers from various flavors of Windows (XP Pro and 2k Pro), but these came back as "invalid product" (in the case of 2k pro) or "invalid license code" (in the case of XP pro). There is another instruction page out there (which can't be directly linked to) that gives instructions for installing a client license pack. The text is as follows:

BEGIN INSERTED TEXT

* To install client license key packs using the Internet

Open Terminal Services Licensing
In the console tree, right-click the license server for which you want to install key packs, and then click Install Licenses.

The previous steps are not necessary if the Licensing wizard is already started.

In Program and Client License Information, provide the required information for your licensing program to receive your key packs, and then click Next.

Microsoft processes your request, and installs the encrypted client license key pack on your license server.

Click Finish to complete the process.

The license server can now issue licenses to clients that connect to a Terminal server.

Note

To open Terminal Services Licensing, click Start, point to Programs, point to Administrative Tools, and then click Terminal Services Licensing.
You cannot install client license key packs until your license server is activated.
Contact the Microsoft Customer Support Center if you receive an error during the client license installation process. To find the nearest phone number, you must first go to Licensing Wizard Properties and select Telephone as the connection method, right-click the license server, and then click Install licenses to display the appropriate number.

END INSERTED TEXT

The wizard that pops up does not have *any* place to supply "Program and Client License Information".

Am I missing something? I thought I'd ask everyone before I tried calling the MS tech support line. Apparently, this costs $210/hour!

Thanks!

 

[sml]

You need to buy TSCALs for each client that's connecting; I think Microsoft will license you TWO connections for administration purposes for free with Terminal Services, after that you start shelling it out. These are NOT the same as your XP/2000 serial numbers.

 

[Tallgeese]

Originally posted by: sml
You need to buy TSCALs for each client that's connecting

Not necessarily true, as explained below.

I think Microsoft will license you TWO connections for administration purposes

True. Terminal Services in Admin mode allows two simultaneous Administrator connections

after that you start shelling it out. These are NOT the same as your XP/2000 serial numbers.

Mmmmmm....not quite. From Microsoft Knowledge Base Article - Q291807:

According to the end-user license agreement (EULA), if you are using a licensed version of Windows 2000, you do not have to purchase a Windows 2000 Terminal Services Client Access license to connect to a server that is running Windows 2000 Terminal Services. However, you must still deploy and activate a server that is running Terminal Services Licensing.

Anything running W2K Pro or WinXP Pro (Home probably DOESN'T count) already has the TS license included in the OS cost (VERY compelling reason for folks to upgrade from older OSes). If your License Server is activated, you should be able to look at the licensing console and see the licenses automatically issuing for W2K and WinXP machines.

License packs are needed for older desktop OSes (Win3.1, Win9x, WinNT, and PROBABLY Win XP Home).

 

[gmoney007]

Hi Guys,

Thanks for the input!

So, TallGeese, if I have legal copies of Win2k and XP Pro, can you think of any reason why the serial numbers from these products wouldn't work? I know that the XP Pro install is activated but NOT registered. I'm not sure of the status on the Win2k licenses. Do you think that could be the problem?

I thought about this before, but wasn't sure it was the problem since 2k server gave me "invalid product" errors. I assumed that meant that the serial number from the Win OS was not the proper information to give.

Thanks!

 

[ivwshane]

I've always been confused with regards to MS's TS but maybe these links will help.

TS licensing
Installing and configuring

 

[Tallgeese]

Originally posted by: gmoney007
if I have legal copies of Win2k and XP Pro, can you think of any reason why the serial numbers from these products wouldn't work?

Uhhhh....because you don't need to enter them? As I've seen it in a production environment, the Licensing Server, once it is activated, will automagically show licenses for Win2K and WinXP Pro workstations. No other config or licenses are required, UNLESS you are using previous desktop OSes (Win 3.x, Win 9x, Win ME, Win NT 4 Workstation).

since 2k server gave me "invalid product" errors, I assumed that meant that the serial number from the Win OS was not the proper information to give.

Correct. TS License Pcks are COMPLETELY different from the OS licenses. However, Win 2K and Win XP Pro workstations do not require separate TS licensing (as was the case in the NT 4 TS era) now, as the TS license is INCLUDED in the OS cost.

 

[lowtech1]

You don't need "TSCALs" for Win2k Client & up, but you still need to activate the licences. You can activate the Licences with MS to get the TS server to work (you can activate by the net or by phone).

After installing TS Licensing server click: Administrative Tools > Terminal Services Licensing > All server > [your_server] > Action > Install Licences (or right_click your_server > Licensing).

You must install the most recent Win2k SP2 to get the TS Licensing to work, because most OEM Win2k Server CD with SP2 on it doesn't work (thanks MS for this fudged up & keep their customer in the dark).

You may need to install the TS License patch recovery to get TS server to work, but it is recommended by MS to wait till Win2k SP3 release for the fix if you have no problem (it took me over 2 months to figured out all of MS fudged up a year ago...It would save me a lot of time & frustration if these fudged up was documented then).

You must install the MS Office Tool Kit to get the MS Office apps to install & work under TS server (you may want to apply all MS Office patches to get it to work).

You can use "Add/Remove Programs" to install applications on the TS server, but I can't seemed to get this method to work. The other method work perfectly is to run the change user command to install the apps.

At dos console type:
change user /execute or change user /install change user /query

/execute = execute mode - normal TS mode that should be running when TS clients are logon the TS server.
/install = install mode - change to this mode to install apps on the TS server.
/query = query mode - tell you if execute or install mode is running (point less command, because you could just run the /execute or /install command to make sure it is the mode that you want to be in).

Win2k TS Client have problems with translating TS server 8 bits colors to 256 colours on client side, therefore you may want to install the Universal TS Client (Remote Desktop for WinXP). It will fix the translation if you have colour gradation of blue or any other hues that translate to greys (no more same or similar colour/hue of grey text on grey background).

Another solution is to install Openoffice or Staroffice on your MS TS server to save the damned licensing.

You might want to look into getting Linux desktop & uses rdesktop to get Linux clients to connect to MS TS_server.

Eventually I wil have Linux clients/workstation connect to X server, if the boss give me the okay.

Good luck.