Terminal Services Licensing in Mixed Windows 2000 & 2003 Environments

Written on Mar 10 2004 Filed under: Tip, Microsoft Remote Desktop, Licensing 21,660 views, 23 comments

by Bob de Kousemaeker

Situation
A site has an existing Microsoft Windows 2000 Terminal Services environment. For specific applications they want to use Microsoft Windows Server 2003 Terminal Services features, so new Microsoft Windows Server 2003 servers are added to the existing environment.

Questions and Answers

How are Windows Server 2003-issued TS licenses validated on Windows 2000 Terminal Servers that communicates with a Windows 2000 TS license server?
If the client has a valid 2003 TS license, Terminal Services will accept the license, and not need to communicate with the original TS license server.

Can devices with a valid 2003 TS license connect to Terminal Services, even though the TS license server that issues the license is unavailable to the Terminal Services server?
Yes.

Device-based TS licenses are stored in the registry of a specific device. Where are user-based 2003 TS licenses stored?
Per-user licenses aren't tracked right now. They aren't stored anywhere.

Does user-based Windows Server 2003 TS licensing require a Windows Server 2003 TS license server to be installed on a domain controller?
No. You need a Windows Server 2003 TS license server, but it doesn't have to be on a DC.

How is a Windows Server 2003 Enterprise TS license server discovered, when installed on a Windows Server 2003 Server that is member of a Windows 2000 domain?
LDAP, or checking all the DCs, or using the registry.

Same question, but installed on a Windows Server 2003 stand alone server?
Broadcast, or using the registry.

How can we 'upgrade' an existing Windows 2000 TS license server on a Windows 2000 domain controller to become a Windows Server 2003 TS license server on a member server?
You can dcunpromo, then upgrade, but it may be easier to set up a new license server.

Can device-based Windows Server 2003 licenses, that are already issued, be converted to user-based licenses?
Depends on your license agreement.

If a Windows Server 2003 TS license server is installed on a member server in a Windows 2000 domain and the same domain contains also a Windows 2000 TS Licensing Server, how is the appropriate TS license server discovered?
If the LS is installed in Enterprise mode, it will be found on a member server. More information is given in the licensing white paper. 
 
Mixed Environment Scenarios

Scenario A: Windows 2000 TS license server and Windows Server 2003 TS license server

This scenario uses a separate TS license server for Windows Server 2003 Terminal Services. This server is installed on a Windows Server 2003 server.

New connections to Windows 2000 Terminal Services will be issued a license by a ‘known’ Windows 2000 TS license server. When connecting to Windows Server 2003 Terminal Services with this license, a new license will be issued by a ‘known’ Windows 2003 TS license server, because the previous license is not valid for Windows Server 2003 Terminal Services.

New connections to Windows 2003 Terminal Services will be issued a license by a ‘known’ Windows 2003 TS license server. When connecting to Windows Server 2000 Terminal Services with this license, the license is accepted without the need of the original Windows Server 2003 TS license server.

Discovery of Windows 2003 Licensing Services installed on a stand alone server can be forced by setting a registry key (Q279561). The order of discovery in case of a member server has to be tested first.

Scenario B. Upgrade current Windows 2000 TS license server to Windows Server 2003

When the current Windows 2000 TS license server is upgraded to a Windows Server 2003 TS license server, already purchased and issued licenses are preserved. The license type will NOT be upgraded, by this upgrade process. The ability to upgrade already purchased licenses to 2003 TS CALs depends on the license agreement.

The process exists of a dcunpromo of the existing Windows 2000 TS license server to a member server. After dcunpromo, an upgrade of the operating system can be performed. However, it may be necessary to re-activate the License Server after the upgrade has been completed. To re-activate your license server that is upgraded from Windows 2000, start the Terminal Server Licensing tool and choose Re-activate Server from the Action menu while the server is highlighted.

Both Windows 2000 Terminal Services and Windows Server 2003 Terminal Services will request the new Windows Server 2003 TS license server for licenses.

It is not advised to install the Windows Server 2003 TS licensing server on a stand alone server. When Windows Server 2003 TS licensing server is installed on a member server, the discovery should be done through LDAP.

Comments

Guest wrote Windows 2003 Downgrade

on Sun, Dec 12 2004 1:21 PM

This message was originally posted by John on March 12, 2004
We have upgraded our Windows 2000 licensing server to Windows 2003 LS and activated Windows 2003 cal's we have then downgraded our ts server to 2000 from 2003 and de-activated 2003 cal's and activated 2000 cal's, but we are now in a situation where windows 2000 cal's expire and will not re-license themselves without hacking the registry. Do you have any suggestions that may help us out. thanks..John

Guest wrote Windows 2000 TS activation using Windows 2003 TS CAL license keys

on Sun, Dec 12 2004 1:22 PM

This message was originally posted by Prashanth on April 29, 2004
We have a Windows 2000 Server, on which the Terminal Server has already been activated, 5 TS CALs have been activated. We are now trying to activate additional 10 TS CALs. Since we can now purchase only Windows 2003 TS CALs (Windows 2000 TS CALs are no longer orderable), we obtained the same. We called the Microsoft Activation Center and read out our license server ID, along with the TS CAL license keys (we purchased 2 retail packs of 5 TS CALs each). We also specifically informed them that although we were reading out Windows 2003 TS CAL license keys, we required them to be activated on a Windows 2000 Server. So they went ahead and gave us the activation code, but it refuses to work, and throws an error message. Please see attachment for the detailed step by step screenshots.

We then tried calling them up again and requested for another activation code, but the same problem recurs

Guest wrote Terminal Services Problem....

on Sun, Dec 12 2004 1:22 PM

This message was originally posted by Will Landymore on May 11, 2004
I have a mixed environment of 2000 and 2003, with a 2000 DC. I can connect throught terminal services to all of the servers running 2000, but when I try to connect to one running 2003 it says that "the terminal server has ended the connection".
I have installed TS on the 2003 box and added my user account to the list in the remote tab, but I still can't connect.
What have I failed to do. All I want to do is remotely administer the 2003 servers like I do on the 2000 ones.

Guest wrote Top DOG

on Sun, Dec 12 2004 1:29 PM

This message was originally posted by an anonymous visitor on July 6, 2004

Guest wrote Windows 2003 TS CALs and Windows 2000 Terminal Services

on Sun, Dec 12 2004 1:31 PM

This message was originally posted by Citrix Dealer on August 25, 2004
We are doing a project now, with Windows 2000 Terminal Services Licensing. We ordered Windows 2003 TS CALs, per user type. We have been told by Microsoft that the Clearing House will issue us 100 Windows 2000 TS CALs (per device only, of course) to use for the project, because we are licensed for W2K3 TS CALs with downgrade rights. So, hope this works for us.

Guest wrote Who in the hell does Microsoft think they are?

on Sun, Dec 12 2004 1:50 PM

This message was originally posted by Angry, Disgusted, Furious on September 16, 2004
The arrogance of those ^*&)(s to have us do all this extra crap and research JUST TO BE THEIR DAMNED POLICE!

I have spent more time researching all of this crap than working on the server.

So angry, I am going to refrain from saying anything else. I am sure everyone feels the same way. Who do these jerks think they are and where do they get off taking up admins times for all of this crap.

Oh, the best part is that none of this hurts the hackers. Oh no, actually, their life is easier because they bypass all the crap.

I hope MS crashes and burns and crashes and burns and they all go straight to the bottom of a deep well where it's cold and damp and they have to listen to the stupid startup sound OVER AND OVER AND OVER AGAIN all next to each other cramped up.

Then when they have had enough and donate their filthy money to the poor, we can sell them licenses to get out of the well. But after they pay us, we will say that they bought a license to get out of the well on Wednesday, which was yesterday and then when they want to get out today, we tell them to please hold.

We will then ask them for their registration key, but they will say they can't read it because it's too dark in the well. So we will sell them a flashlight. When they go to turn it on, they will see it has no batteries, we will then sell them batteries. The batteries will expire unless they read us their registration code.

Screw this, Linux, here I come baby. I am so ready and we will make the whole damn office use Firefox and Star/Open Office. Microsoft can go to the well.

Guest wrote TODAY I AM SWITCHING TO MACINTOSH

on Sun, Dec 12 2004 1:57 PM

This message was originally posted by Fed Up!! on November 19, 2004
"Angry" pretty much laid out what should happen to Microsoft. I have simply had it with having to reading 50 snippets of MS "support" files that are only found in bunches IF you search with exactly correct keywords, and when it is all over, it boils down to having to call "them" on the frigging telephone and, of course, pay them MORE money so that my users can run an application on my Server!!! That is what a server IS -- a place where users get SERVED files and apps. When I buy a server OS with X number of client licenses, why should I have to jump through hoops to allow my users to access the server and run a program? So, today, I am surfing over to Apple's website and begin the learning process needed to join my much happier acquaintences who run Apple server. They apparently have no problems with this kind of obtuse crap and when viruses and worms bring my domain to it's knees, they come over and help me out, because they aren't affected. Microsoft's nickle-and-diming, money-grubbing, lousy code and screw-you customer mismanagement has lost it a long-time customer. The days of "you can't get fired for picking Microsoft" are over -- my users want reliable computing and don't want to hear a bunch of excuses. Adios, Microsoft -- it has NOT been a nice journey.

Guest wrote Re: Terminal Services Problem....

on Thu, Feb 3 2005 1:36 PM

point the 2003 Terminalserver to the 2003 Licensing server by editing the registry. The knowledgebase article is mentioned above

Guest wrote Question

on Wed, Mar 30 2005 11:19 AM

Licensing Agreement /product keys for winxp/win2000/winme

Guest wrote Windows 2000 TS in Windows 2003 Domain

on Mon, Apr 4 2005 5:51 PM

We have rebuilt all our servers as W2K3 servers except one W2K/TS, and changed the domain name and now we're seeing weird licensing stuff. First, when I look on our W2K3 licensing server, there are all these licenses issued to users in the old domian. I clean everything out and reset as per MS but they come right back. Now, several months after the upgrade, the W2K/TS server says it cannot issue TS CALS. I have our W2K3 license sever specified as preferred and have stopped and restarted the licensing server for over 15 min. on the Licensing server. Anyone have any idea of what is going on? TIA.

Guest wrote Re: Who in the hell does Microsoft think they are?

on Wed, Jun 22 2005 12:19 AM

Life is hard.

Guest wrote RE: Question

on Tue, Dec 27 2005 7:14 AM

Hi there
 
 
I have a windows

Guest wrote RE: Question

on Tue, Dec 27 2005 7:20 AM

Hi there
 
I have a Windows 2000 Treminal server with 2003 cals, it seems like that the server doesnt issue the licenses out will it work or must I run Windows 2003 terminal server for the cals to be issued?
 
Please reply to stephanp@natsure.co.za
 
thx!

Guest wrote RE: screw microsoft

on Thu, Mar 23 2006 11:16 PM

what in God,s name do you think you are. you sell a product, sell the license and then the whole system cant work coz of the licence. i av a 2003 server with a license of ten clients but all of a sudden the clients cant access the server or worse they cant even do the basics like browsing. how do u expect to maintain your customers? microsoft, here comes your downfall.

Patrick Rouse wrote RE: screw microsoft

on Thu, Mar 23 2006 11:35 PM

Oh my God, you're right.  I'm burning all of my MSFT licenses as I write this, unplugging my servers, and running-out to get the Apple and Linux equivalent.
 
Damn, I just remembered, Apple and Linux don't make equivalent products.
 
 

Guest wrote windows 2000 terminal services CAL

on Mon, Apr 24 2006 11:13 AM

Dear All,
 
Please can any body send me the activation key for windows 2000 terminal services CAL 5 licenses
 
Awaiting for your help
 
Regards,
Talal

Shawn Bass wrote RE: windows 2000 terminal services CAL

on Mon, Apr 24 2006 12:50 PM

Ummmm, no.

Jeff Pitsch wrote RE: windows 2000 terminal services CAL

on Mon, Apr 24 2006 12:56 PM

HAHAHAHAHAHAHAHAHAHAHAHA
 
You've got to be kidding me
 

Patrick Rouse wrote RE: windows 2000 terminal services CAL

on Mon, Apr 24 2006 2:40 PM

Please also send you bank name, account number and routing code, along with PIN, web username & password, mother's maiden name, date and place of birth, and SSN.

Guest wrote wind 200 terminal servers licence key

on Wed, Dec 26 2007 6:23 AM

Please can any body send me the activation key for windows 2000 terminal services CAL 5 licenses at satadmn@yahoo.co.in

regards

sohani

 

Guest wrote RE: screw microsoft

on Tue, Sep 30 2008 12:12 PM

ROFL

Guest wrote Re: windows 2000 terminal services CAL

on Thu, Oct 23 2008 1:18 PM

My dear tech savvy !!!!!!!! you do not need to buy any license for 2000 based TS server . It only supports per device mode , all u need are clients based on 2k and above and a an activated License server

mccl13 wrote re: Terminal Services Licensing in Mixed Windows 2000 & 2003 Environments

on Wed, Dec 3 2008 10:42 AM

We are upgrading Our Citrix environment OS and Citrix Version. OS is going from Windows 2000 to Windows 2003 so we will need to purchase TSCALS. My questions is regarding the Windows 2003 Terminal Services License Server. We want to stand up the 2 environments for a while at the same time. Will the Windows 2003 TS License Server be able to still hand out 2000 (free) licenses and hold the purchased licenses for the new environment?

(Note: You must be logged in to post a comment.)

If you log in and nothing happens, delete your cookies from BrianMadden.com and try again. Sorry about that, but we had to make a one-time change to the cookie path when we migrated web servers.