Terminal Server License CALs are not being accessed

Posted on 2007-09-29
Medium Priority
Last Modified: 2012-05-05
Hi, I have a member server with Windows Server 2003 that several people need to access through Remote Desktop.  I purchased the terminal service license CALs and followed the Knowledgebase Article 325869 to activate the terminal service licenses.  I first setup this Server 2003 member server as a License Server and then installed the terminal services CALs and everything went through without a problem.  When I access Terminal Server Licensing, the CALs show they are there and ready to go.  However we still get the error message that we have exceeded the connection limit when we try to remote more than the initial two remote connections that are default, so the licenses aren't being seen by Terminal Services.

I read that Terminal Services will try to connect to a Licensing Server on a DC, and the only DC locally to this member server is a Windows 2000 DC.  I've also read that 2003 Licensing is unable to come from a 2000 Licensing Server.  So the Terminal Services on this Member Server is not seeing the Licensing Server on itself.  I read that there is a registry change that needs to be made so the Terminal Server will find the licensing on itself and not a DC, but not sure what the change is.  How can I make this member server see the Licensing Server that is already setup and ready to go on itself?

I have made this question worth 500 points because I have people waiting on me right now.  Thank you very much for any information I can get.

Question by:TheNewLobo
LVL 85

Accepted Solution

oBdA earned 2000 total points
ID: 19984446
Just to exclude the maybe too obvious: did you actually install terminal services in application mode on this machine (from the Add/Remove Windows Components wizard)? The standard Remote Desktop is limited to 2 connections, whether or not TS CALs are available.
If the TS is indeed running in application mode, open the Terminal Services Configuration MMC on it, and make sure that
1. The Terminal Services Mode (Per User or Per Device) is set to the same type as the TS CALs you've installed on the license server.
2. The License Server to use is defined as well (you can do that in the TS config MMC as well if SP1 or later is installed, just can't remember where exactly).

Author Comment

ID: 19985227
oBdA, it wasn't too obvious for us.  We hadn't installed Terminal Services.  I was told that it was installed when they initially setup the machine, so I didn't even think to check that.

We installed Terminal Services, it gave a message saying some programs may not work correctly through Remote, however everything has worked great.  Thank you for your help.


Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article we will discuss all things related to StageFright bug, the most vulnerable bug of android devices.
The article covers five tools all IT professionals should know about, as they up productivity by a great deal!
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…
Hi friends,  in this video  I'll show you how new windows 10 user can learn the using of windows 10. Thank you.

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question