Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Another person confused about Terminal Services and licensing

Status
Not open for further replies.

PPettit

IS-IT--Management
Sep 13, 2003
511
US
Here's the setup:
We've got a new 25-user Win2k3 server which is used to run our accounting system. We're all using Remote Desktop Connection to access the application. This includes our remote offices as well. Our vendor insists that we don't need TS CAL's because of the "built-in" or "free" CAL's on our workstations (all have either Win2k Pro or WinXP Pro).

Problem: We're getting the message about the temporary licenses about to expire. Naturally, I need to get this taken care of before we actually start using the new server.


After reading various KnowledgeBase articles and FAQ's, I'm still a little confused.

Tell me if I'm correct or not:

I have to buy TS CAL's for every user or computer accessing our accounting system because the "built-in" Win2k and WinXP TS CAL's are not valid (or were never "built-in" in the first place, according to MS) for connecting to Win2k3 via a Remote Desktop client.

I need to set up Terminal Server AND TS Licensing services since I'm using RDP. In my case, these will be on the same server since we currently have a low user count (15 at most).

I should use "per-user" licenses because the majority of our users are remote users and don't always access the accounting system from the same machine each time.

One last question:
Our vendor set the server in a workgroup instead of a domain and did not install Active Directory. Should we add the server to our existing domain and enable AD as well?


Any assistance would be appreciated.
 
PPettit,

I will try my best to help. I just went through the EXACT same situation. After much arguing and bickering with our software vendor etc... I finally figured out that 2003 does not function the same as 2000 (I swear it was like no one believed me when I said I can't get permanent licenses). Basically, we had previously bought an XP cal with every workstation purchased from Dell which is what made us assume that this would automatically work (just like 2k). I had to activate the server, call our software vendor to get an agreement number, then call microsoft. They EASILY gave me a 2003 terminal server key to license all 180 licesnse on the server and voila......activated once again.

I would suggest getting whatever agreement # you have and calling microsoft because whatever the case is, if you don't have the info you can't activate. This can also be done online through TS license manager via wizard.

Hope this helps a little...
 
Your vendor is incorrect. Every client connecting to a 2003 terminal server requires a terminal server CAL. The built-in pool is only for 2000 and XP clients connecting to a 2000 TS.

It is also important to note that NO client has a built-in license. The built-in pool exists on your TS license server, and 2000 terminal servers can pull a license from that pool on behalf of 2000 and XP clients. 2003 TS cannot pull from this pool.
 
Actually, you are both right and both wrong.

Microsoft will allow a so called included CAL for xp pro IF xp pro was purchased prior to some early date in 2003.

If you purchased your xp pro after that date, you would not be entitled to the TS CAL.

Also, 2000 and 2003 are different. 2000's Terminal Services had a choice of Remote Admin or Application mode.

The remote admin function in 2003 is not a function of Terminal Services anymore. You can activate Remote Admin for the server even if you don't use Terminal Services. You can find it on your System Properties, Remote Tab.

If you have decided that you need Terminal Services in addition to the remote admin, you have to activate the licensing server within some random time frame. You activate it even if you have no clients.

Also, you can easily reset the Terminal Services expiration date for your pc's by simply un-installing terminal services, and then re-installing it :)
 
The date is before April 24, 2003. You have to call the Microsoft Clearinghouse to get the license keys.

If you install terminal services, the time you have to activate is not random. It is 120 days. You then have an additional 120 to install licenses.

I dont think uninstalling and reininstalling the TS will get around the grace period because it should still have the same server ID. Even if this did work, it is a violation of the EULA.
 
A minor update:

I talked to my vendor again and he sent me KnowledgeBase article 187614. It was written with Win2k in mind but it worked for me. It's titled "Removing Terminal Server Licenses from an RDP Client". In short, to clear the license cache, all you need to do is delete the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing

This makes the server give you a brand new temporary license. It reset the date that the license was given and the date that it will expire.

This will get rid of the expiration warnings for now, but it's not a good or long-term fix, in my opinion.
 
No it isn't. Your vendor should be helping you to purchase the appropriate TS CALs. Temporary licenses only last for 90 days.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top