FAQ: Terminal Server Licensing

Q: Can a Windows 2000 license server pass out licenses to a Windows 2003 Terminal Server?

A lot of people have emailed me questions about different things, so I figured that I'd start answering them via the web instead of one-by-one via email.

Q: Can a Windows 2000 license server pass out licenses to a Windows 2003 Terminal Server?
A: No. Windows 2003 Terminal Servers must get licenses from a license service running on a Windows 2003 server. However, Windows 2003 license servers can also pass out licenses to Windows 2000 Terminal Servers.

Q: Can I install the Windows 2003 Terminal Server licensing service on a Terminal Server?
A: Yes. In fact, many people do this in smaller environments, especially if the domain is Windows 2000-based and they don't want to upgrade any other servers to Windows 2003.

Do you have a question about Terminal Server licensing that's not listed here? If you've read the stuff on my site and you still can't find the anser, send me your question and I'll post the answer here.

Join the conversation

69 comments

Send me notifications when other members comment.

Please create a username to comment.

This message was originally posted by Ravikiran on March 30, 2004
But the Microsoft Open License is purchased one(Not Temparory). Will it show any duration period ? Or expiry date should not be there like Win XP clients?
Cancel
This message was originally posted by Brian Madden on March 29, 2004
Hi Ravikiran. From your description, it sounds like everything is functioning as it's supposed to. The Windows XP clients use their built-in licenses, and other platforms get the random duration licenses.
Cancel
This message was originally posted by Ravikiran on March 29, 2004
I have installed a TS CAL 50 copies( Microsoft open License). License server activation and license key installtions completed successfully. But when I connect any thin client, the server issues the Licenses to the clients and it shows an expiry date between 50 to 90 days to every client.But when I connect a winxp licensed system to the server,the server issues a permanant built in license to that system which won't be having any expiry date . I tried activating and installing licenses several times .I have reinstalled the windows 2000 server OS(service pack 4) and reset the thin clients to actory settings and tried to connect the server .But the same problem exists. How I can solve this problem ?
Cancel
This message was originally posted by Brian Madden on April 8, 2004
Hi Ravikan. You're right. All licenses (even full ones) are only issued for 52-89 days, and then renewed. This is so that a broken client device doesn't "steal" a license forever. Check out our white paper on licensing for more information.
Cancel
This message was originally posted by Ravikiran on April 7, 2004
Hi Brian , I am not able to identify that the problem with TS CAL or Thin Clients . Is there any chances of Thin Client problem ? Because the win Xp clients won't be having any expiry date . Only Thin clients will have different expiry dates for the Installed License. And there is no chance of server OS problem ,because I have formatted and reinstalled the OS with latest service pack .still it is not working.And if I change the server date to the expiry date and login from any client ,the server extends the expiry date for another 52 to 89 days for that particular client.Is it the right way for issuing licenses for a Microsoft open License purchased ?
Please clarify my doubts. I am awaiting.
Cancel
This message was originally posted by Neil Fowler on May 27, 2004
I have recently installed a Win2003 Server running Terminal Services with 6 Device CALs installed on the Licensing Server. I need to release the CALs which have been issued to devices as they will be used by a new set of workstations. At present these are not due to expire until mid July. Is there any way a can release them manually or change the expiry date ?

Thanks

Neil
Cancel
This message was originally posted by an anonymous visitor on July 4, 2004
What you can do is uninstall the terminal server licensing server, (using Add/Remove Programs >> Windows Components) and then re-install it. Then ring up Microsoft clearing house and re-install the licenses.
Cancel
This message was originally posted by Bryan Fister on July 22, 2004
Does the grace period on a 2003 Terminal Server become null and void if it sees a 2000 License Server?
Cancel
This message was originally posted by Kenny on August 19, 2004
I have observed the folowing recent behaviour when connecting to a Windows 2000 TS \ Windows 2003 License Server.
XP Service Pack 2 cannot issue a client license (understandable as we have none available)
Uninstall SP2 and XP Service Pack 1 uses the Built-in client license (i.e. correct behaviour)
I have struggled to find documentation of such a change, has XP SP2 ceased to use a built-in TS client license?
Cancel
This message was originally posted by Jimbo on October 5, 2004
Windows 2000 Server hosting Citrix Metaframe XP.

<throws down gauntlet>
What is supposed to happen when the license count is reached and another User tries to log on?

On ours it logs off an existing User!!!!!!!!! SURELY this must be a BUG!?!?!?

Also, does this behavior change as a result of Windows Updates or Citrix Hotfixes & Feature Releases?

More to the point, how can I make it behave correctly, i.e. do NOT log off a already-validated user, I don't CARE what Microsoft was smoking!!
</gauntlet>

I actually haven't seen this yet, but every Citrix User in this org has confirmed having been kicked at one time or another. <shakes head in stunned disbelief>
Cancel
This message was originally posted by Harried Contractor on October 5, 2004
Win2k + Citrix MF XP. Sporadic, randomly disorganized patches/fixes/updates/etc./etc.

2-User LAN to DSL to Internet to DSL to Win2k/Citrix on 31 user LAN. 100Mb/s all, except, of course, for the DSLs, which run 200+ kb/s on 2Wire.com's test.

1- Users get disconnected repeatedly for no apparent reason.
2- Users can press a key, count "one one-thousand two one-thousand..." up to as much as five one-thousand before the result appears on the screen. When they reported it, my inside (100Mb) LAN connection was smokin', but the Console response was brutally slow.

Question: Just another Citrix, not-yet-ready-for-prime-time, wait-for-a-hotfix bug, or did the vendor (eGroup, CHS) just screw us? (Vendor has nothing but excuses since Day One, but we need to get productive!)
Cancel
This message was originally posted by Janakan Rajendran on October 20, 2004
Hi Jimbo, I have the same trouble, but we have Citrix MF on W2K3 server...did u find any solution? would appreciate if u share that with me.

Regards
Cancel
This message was originally posted by Dominic on December 1, 2004
I am just new to Citrix environment, do you need to have Terminal Server Licences server running to run Citrix thin clients? And if so, does the TS CALS get renewed by the LIcense server after its expiry?
Cancel
This message was originally posted by Brian Madden on December 6, 2004
Use the forum instead. http://forum.brianmadden.com
Cancel
This message was originally posted by Darkow on December 6, 2004
We have a Win 2003 Terminal Server with a Win 2000 domain controller. The License server is installed on the 2003, the licenses have been activated and set as per user. When people connect, however, no licenses are issued. Is this due to temp licenses still in effect, or is there a way to force the licenses to be used?
Cancel
We have a similar issue with fast network on both ends. Does any one have a recommendation on monitoring tools that might help troubleshoot TS slowness?
Cancel
Sounds familiar.

Our TS runs smoothly with 20 Users, but access to the file server (2xGbit) ist awfully slow. File operations from the TS to every other PC in the network is ok, from every PC to the TS or the File Server, too, access from File Server to TS is a mere blink of the eye, but you die while just opening or saving a 500k excel-sheet from a Terminal-Session.
We are now crawling around this problem by transferring the active data of the terminal users directly on the TS's HDD, but this is not a solution.

Might it be, that the file server is "over-roled"? It's configured for file-server, DC, app-server (IIS), print server and terminal server (remote adminstration).
Cancel
Have you checked the settings of link speed in the switch/es and on the NIC:s??
Some of these settings are maybe in conflict.
Cancel
Hi there,

I need help regarding the following question: A network with 2000 only (servers and workstations: no SA, no WinXP) is moving to Windows 2003. The Windows 2000 Terminal Servers will carry on serving Windows 2000 Professional machines. ONLY the Terminal Server Licensing Sever should move to a Windows 2003 Server.
Do we need new CAL's? Can one activate the Windows 2000 TS CALs on the new server? Any link or so for that?

Thanks for your help!
Cancel
You can choose to activate 2000 TS licensing on the Windows 2003 Server. It's an option when you activate your TS Licensing Server. No new licenses is necessary if still running w2k terminal servers.
Cancel
i ve two locations connected through ISDN, i have installed the terminal services licenses on the remote location, but i am not able to access it when that server goes down. so i wanna shift that license server to my local server. can i do that, urgent reply will be appriciated.thanks!

Cancel
have three locations called A(a.t.com),B(b.t.com),C(c.t.com) and i have exchange server2003 installed on my DC and DC(T.com) is in the same subnet as domain A ,

A is connected to B through ISDN and to C through DialUP(demand dial). i am able to send emails from A to B and C, but A is not routing emails between C and B i.e am not able to send emails from C to B. all the connectors and default and no routing group is present. all configuration is default.
Cancel
This should be posted in the correct forum but here goes.

You'll have to reinstall the licenses on a new server and then get with the Microsoft clearinghouse to free up the licenses. You cannot transfer anything between license servers.

Jeff
Cancel
I want to use built in TS come with winxp and win 2000 pro.
Can i install Terminal Server Licensing on win2000 server for users use win xp and win 2000 pro, and install citrix metaframe presentation server 3.0 on win2003 or i must install it on win2000
Cancel
Hi there,

The answers to your questions can be found at the following link:

https://www.brianmadden.com/content/content.asp?ID=136

Good luck!

\\ijdemes
Cancel
I have reinstalled the licencing server and licenses with MS but when i run the TS licencing application i then have to connect to the name of the local Windows 2003 server which i am currently looged in to before licences show up. The reason for reinstalling is that the local techs renamed some of the local pc's and ran the server out of device licences and also left the licence applet in this disfunctional state. We tried reinstalling the open licence pack which appeared to work but to no avail , no licenses are available to pc's attempting to login to the terminal server. The local tech in the nprocess of reissuing the licences, deleted all registry keys from local pc's too, so now no-one gets in.
Cancel
Has anyone else been able to verify this?

I have a w2kts_sp4/w2kdc_licsrv_sp4 environment with similar problems.
All XP clients are issued temp licenses.
License server service has been reinstalled and activated but XP clients are still only issued temp licenses.
Eventlog on TS's does not show anything.
Cancel
Hrmppphhhhhh....forget all...turns out that the users have XP home on their laptops - or rather as one said to me:"we all got our laptops on the company software agreement so of course they're all XP professional home edition :)
Cancel
I've activated TS using per User CAL license. I've installed it on win2003 domain controller. I use 3 terminal server with Citrix Server, and all of them are member of that Domain. Client access TS from windows 2000 professional. The problem is why the CAL license doesn't issued to user? I buy 50 User CAL, none of them is issued to user. Do anybody can help me,please? Thanks.
Cancel
The reason is that the windows2003 per-user licensing engine is NOT implementated in the windows2003 product, therefore the license pool is not addressed when the user connect to a TS box.
Cancel
Hi,

We have a strange problem which I believe is 2 separate problems -
We have 2 Win2K3 Server in Site A and one Win2K TS Server in Site B. In Site A, we have users on neoware terminals connecting with no probs; Site B has its own license server with 15 CALS (because these cals are Win2K and the server is win2k). The problem is that even though clients connect to server in SITE B, it goes to Site A and look for Win2K3 CALs? Why is that?

The 2nd part of the problem is that we are getting messages "temporary client licence will expire in 11 days" - but from what I have read, this is normal?
Cancel
where would i install terminal server lisneces is it on a the terminal server or on a domain controller???
Cancel
WE AHVE THE SAME ISSUE

I HAVE CHANGED THE SERVER TO PER DEVICE AND NO LICENCES ARE ISSUED HOWEVER USERS ARE ABLE TO LOG IN OK

BEFORE WHEN IT WAS IN PER USER MODE IT WOULD ONLY ISSUE TEMPORARY LICENCES AND I WOULD HAVE TO REDO IT EVERY 120 DAYS

ANY HELP WOULD BE GOOD WE HAVE 2 WTS2003 SERVERS IN A 2000AD
Cancel
please can you expand on this ?

does taht mean that wts2003 only works when in per device mode ?
Cancel
I am running a Terminal Server with an activated licensing server on it. I am deploying Wyse thin clients and have been getting a "The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your administrator" on the the thin client. No error in the event viewer. I had deleting the MSLicensing key in the registry of the thin clients b/c this is the fix on Windows. I have now noticed that this is only a short term solution and also creating multiple TS CAL's per thin client.
Cancel
I have a very similar problem. A few cllients from site A getting the above message,
when they are trying to connect to the server, while clients from Sites B,C and D
do not any troubles. Do you find a solution ?
Please send your reply to: schechik@scor.com
Cancel
You can refer this link http:
If none sucessful, you can export the registry client from other site and export it to affected PC. Basically it emulate the same PC from other site so terminal server was though from the same PC.

Cheers,
Jimmy
Cancel
I am having the exact same problem. I cannot be making registry keys and stuff all the time to make these terminals work. Wyse or MS needs to adress this problem with a real fix.
Cancel
Why do we need to delete MsLicensing key
Cancel
If you need to clear the client's TS CAL from their registry, deleting this key does it.  Actually, you only need to delete the Store00x key that applies to the specific CAL, but since the information is encrypted and most people only have one Store00x key anyway, deleting the MSLicensing key gets it all.
Cancel
ORIGINAL: Guest

I am running a Terminal Server with an activated licensing server on it. I am deploying Wyse thin clients and have been getting a "The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your administrator" on the the thin client. No error in the event viewer. I had deleting the MSLicensing key in the registry of the thin clients b/c this is the fix on Windows. I have now noticed that this is only a short term solution and also creating multiple TS CAL's per thin client.
Cancel
I have seen this issue come up a couple of time the client side is xp home and the server is Server 2k I get the the server disconnected the session because of an error in the license protocol, is this related to SP2 does anyone has a fix for it plase help
Cancel
I'm having the same problem.  If you come up with a fix, please post it!

I'm running terminal server 2000 with only the 5 cals that come with it.
I have a new remote location being setup and the XP Media Centers (2002 SP2) can connect fine,
but the XP Pro (2002 SP2) boxes get the error...
"The remote computer disconnected the session because of an error in the licensing
protocol. Please try connecting to the remote computer again or contact your administrator".

The error is not related to number of connections, as there are only 2 other connections at
the time the server is giving the error.  The event viewer on the server, under system, is
throwing the error "The terminal server cannot issue a client license" (Event ID: 1004).
Under applications, it warns when terminal server is nearing it's maximum connections, but
this is just because 3 or 4 connections are present.

I have tried removing the licensing key from the workstation and replacing it with the regkey
from one of the XP Media Center boxes that isn't having a problem.  I've also tried replacing
the RPC client (mstsc.exe) on the Pro box with the one from the Media Center.  I'm not
positive that the OS difference is significant, but it's the only obvious difference in the machines.

Thanks for any help!
Michelle
Cancel
I'm getting the exact same problem "The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your administrator" I'm also using around 150 Wyse V90 XPE terminals. I found that If I log in as administrator and from there start a terminal session to the server as administrator, the license is renewed and the user can use the new license for the next few months. Obviously a problem as I have to do this 150 times every couple months...
 
Anyhow, I think it is an XPE permissions or timing issue at the workstation since I don't have these issues at my standard WinXP workstations. If it's permissions it would explain why logging into a terminal session from the administrators desktop would fix the problem. But the problem seems to be intermittent in its timing. So I wonder if the server doesn't attempt to create this license but gets cut off by the computer going on to other things before finishing the license update...
 
Any thoughts are appreciated.
 
 
Cancel
ORIGINAL: Guest

I am having the exact same problem. I cannot be making registry keys and stuff all the time to make these terminals work. Wyse or MS needs to adress this problem with a real fix.
Cancel
ORIGINAL: Guest

I am having the exact same problem. I cannot be making registry keys and stuff all the time to make these terminals work. Wyse or MS needs to adress this problem with a real fix.

KUT MET PEER
Cancel
anyone have any problem when you attatched a printer on the Wyse v90 Thin Client that they cease to print.  You have to reboot the thin clinet to make work again.  I understand about the print spooling thing but is there away around it?
Cancel
See [link=http:ianmadden.com/content/content.asp?ID=44
Cancel
https://www.brianmadden.com/forum/commentpost.aspx?do=reply&messageID=32750&q=1&toStyle=tm
Cancel
I'm an administrator of a Windows 2003 server, and using Terminal services, i'm not able to log users off through the server.  The error that i get when trying to log the users off is:

Session(ID 0) reset failed
(Error 5 - Access is denied)

How do i get rid of this error?
Cancel
Grant yourself rights to Reset sessions on the RDP-Tcp connector, or make yourself and Administrator.

Shawn
Cancel
ORIGINAL: Guest

where would i install terminal server lisneces is it on a the terminal server or on a domain controller???

Good question.  Install licensing server in a domain controller is a better choice than terminal server.  However, it depends upon your environment as well.  There are 2 or more licensing servers in Enterprise level.
Cancel
The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator
Cancel
My advice,
 
Try to connect another TS server, then log off and try to log on the problematic server again.
It helped me.
Good luck
Cancel
I would like to know if my licensing is correct with the following scenario:
 
1 fileserver in City A with Server 2003 + 5 user CALs and
1 terminal server in City A with Server 2003 + 5 user CALs and 10 Term Serv CALs
1 fileserver in City B with Server 2003 + 5 user CALs
 
The 5 users on fileserver in City A and 5 users on fileserver in City B will be accessing the terminal server.  
They will be using MS Office on the Terminal Server.
 
My questions are:
1) Do I have enough server user CALs for the Terminal Server?  Or do I need 5 more?
2) Do I need to purchase a license for each user that will be using MS Office on the terminal server?  For example,
if 10 users will be using Office on the Terminal Server, do I need to purchase 10 licenses of Office? 
Cancel
We have 2 Win 2000 Terminal Servers which we used with windows 2000 professional built in licencing
 
We have since purchased a win 2003 terminal server which had to become the licencing master. Can you point our 2 windows 2000 servers to use win 2k3 terminal server as the master so we can manage the licences from one location??
Cancel
I had this issue for many months. It was the XPEmbedded Thin Clients that were eating multiple CAL's. The only fix I found was to re-image the Thin Clients to the latest build of the OS. Basically upgrading the Thin Clients to Service Pack 2. I got the image and instructions from Wyse Tech Support......
This was TRULY a hassle til I found the fix. Now all is well :-)
 
 
 
Cancel
Hi guys,
 
All of my servers are running on Win2000. I've activated my license server yesterday and I noticed that after doing that, there were 4 built-in licenses with no expiration.. I still didn't install my license pack yet... why do i have built-in licenses? do i still need to install my license pack or not?
 
thanks in advance guys...
Cancel
btw guys... my inquiry is for our windows 2000 terminal server...
Cancel
Ok...so here's my problem..I get the "Because of a protocol error, this session will be disconnected.  Please try connecting to the remote computer again.  This issue started after I switched from dial-up to DSL.  I have configured my router the correct way.  I am running Windows Server 2003 Web Edition.  I'm not sure what in the heck's going on....I've tried everything. I've tried specifying a port in my TCP/IP filter box (under Network Connections), I've tried setting up routing and remote access, remote desktops, and everything...please help
Cancel
Cancel
Hi,
i just had the same problem, but i noticed that some computer clients where able to access and not others with the error that the client gave an invalid license and the server couldn't sort a new one; so i just exported/imported the HKLM\Software\Microsoft\MSLicensing key; and now it's working perfectly.
 
Cancel
Any fix for the multiple Term server licenses?
Cancel
Dear sir.
We had the same problem in our office in Jerusalem. Two out ten computers couldn't loging to the server 2003. After getting in a few technition's and killing a few days work, we finally came across your answer in here and it worked right away.
Thank you ever so much, for answering on here, and saving - who knows how many headaches from poeple.
Blessed be you.
Shlomo
Cancel
ORIGINAL: Guest

I am having the exact same problem. I cannot be making registry keys and stuff all the time to make these terminals work. Wyse or MS needs to adress this problem with a real fix.
Cancel

how to identify the Terminal server license expiray date report collection of TS users.

please do the needful 

 

Cancel

 

Yes you need 1 liecense for one user for office

Cancel
I have a TS Lic Server 2003 that has 50 per device licenses & 74 Temp per device Licenses. Can I convert the 50 Per device Licenses to per User? Also what happens to the 75 Temp per device license once this is done? I only have 8 Terminal 2003 Servers that get licenses to login to  the domain. Thanks In Advsnce
Cancel

Yes. Once you install MS Windows Server's Terminal Server will give you a 90 days grace period to buy Terminal Server Access Licenses.

If you are running Citrix and dont buy the licences at day 91 the server will reject any clinets from accesing the metaframe server.

I learnt this the hard way. I bought Citrix Metaframe 4 presentaion server,,,  it ran 4 90 days, then gad to folk out big $$$ to buy 8 TS Cals from Microsoft. not happy Jan, 

Cancel

-ADS BY GOOGLE

SearchVirtualDesktop

SearchEnterpriseDesktop

SearchServerVirtualization

SearchVMware

Close