Windows Server 2003 Terminal Server Licensing

We have a Windows Server 2003 box.  I just added the terminal server licensing component and added 14 CALs to the machine.  I used PER USER.  However, it won't honor the CALs.  It still won't allow more than 2 RDP sessions (even after several reboots).  I've added CALs to servers many times before and this has never been an issue.

Group policy on the terminal server is configured to allow PER USER connections.  The TERMINAL SERVICES and TERMINAL SERVER LICENSING services are both running.

Any thoughts?
Who is Participating?
zigafu2Connect With a Mentor Author Commented:
I found my problem.  In Terminal Services Configuration, the network adapter tab of the RDP-TCP properties (under the connections folder) was set to allow 2 connections.  Even though I have 10 new CALs, this is limiting me to 2.  I changed it to unlimited, and the problem has gone away.

I hope this info helps someone...

have you actually installed the terminal server role?  sounds like its not configured...go under administrative tools to manage your server.  add a role (terminal services)  this is how i do it.
Darius GhassemCommented:
Have you activated the licenses? Is the Terminal Server connected to this licensing server.
zigafu2Author Commented:
Thanks for your suggestions. I installed term services using add/remove programs (adding windows components).  I checked the Manage Your Server area and it does show TS configured.  I have also verified that the licenses were activated.  They show up in Terminal Services Licensing as PER USER terminal server CALs.  In this case, this server is both the terminal server and the license server.  
zigafu2Author Commented:
I found my own problem.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.