segibson77
asked on
Windows 2003 Terminal Server Licensing: User CALS but devices still take temporary device token
Hi,
We have Windows 2003 Terminal Server enabled on a Windows 2003 Server (not DC). Domain Controller is Windows 2000 Server. Originally we were using the 120 day grace period to test the functionality of our application with Terminal Server and once this had passed we purchased 45 user CALS.
I have activated the server, installed the licences and made sure that it is set to "Per User" and understand thanks to the postings in this forum that the count doesn't decrease when using User CALS.
However my problem is as follows: If a user uses a new machine to log on, it still gets allocated a temporary device CAL, which means that the user gets that annoying message each time they log on about the temporary licence expiring.
Can anyone explain what is happening here? Have I missed some piece of config?
Is there anyway to fix it?
If so can I convert all the temporary device cals to user cals?
TIA.
Stuart
We have Windows 2003 Terminal Server enabled on a Windows 2003 Server (not DC). Domain Controller is Windows 2000 Server. Originally we were using the 120 day grace period to test the functionality of our application with Terminal Server and once this had passed we purchased 45 user CALS.
I have activated the server, installed the licences and made sure that it is set to "Per User" and understand thanks to the postings in this forum that the count doesn't decrease when using User CALS.
However my problem is as follows: If a user uses a new machine to log on, it still gets allocated a temporary device CAL, which means that the user gets that annoying message each time they log on about the temporary licence expiring.
Can anyone explain what is happening here? Have I missed some piece of config?
Is there anyway to fix it?
If so can I convert all the temporary device cals to user cals?
TIA.
Stuart
ASKER
Thanks Deb, but I have already checked this and the registy value on the terminal server is set to 4 for "per user".
Any other ideas?
Stuart.
Any other ideas?
Stuart.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It may help to check out this which describes a bug, just in case configuration changes have resulted in a switch.
Terminal Services Licensing mode changes from Per User to Per Device after you add or remove a Windows component
http://support.microsoft.com/?kbid=834651
Deb :))