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
segibson77Asked:
Who is Participating?
 
Debsyl99Connect With a Mentor Commented:
Hi

Well I was aware of the bug and other issues in relation to this (hence my posting it), but primarily from having researched it prior to an impending introduction of Windows 2003 servers into our current purely windows 2000 server domain. I'll post what I've come across so far so that you're at least aware of the possibilities, but I'd hang on until someone comes along with a definitive answer for you on this (I like to speak from direct experience on this issues but on this one I can't as yet so just making sure that's clear!).
I'd check out this post as it's referencing a potential problem in relation to 2003 terminal servers in a windows 2000 network (expand it all).
http://groups.google.co.uk/groups?hl=en&lr=&threadm=OH%24%233QsrDHA.3748%40TK2MSFTNGP11.phx.gbl&rnum=2&prev=/groups%3Fhl%3Den%26lr%3D%26selm%3DOH%2524%25233QsrDHA.3748%2540TK2MSFTNGP11.phx.gbl%26rnum%3D2

This would appear to suggest that if you have a windows 2003 terminal server that is also a license server in a 2000 server environment you need to perform a reg fix prior to applying any license packs. I don't know if this is the case in your situation but it never hurts to be aware of these things.

and relevant linked article to the above link (NOT suggesting that you do this!!!!!).
How to override the license server discovery process in Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=279561

I've also come across suggestions that so long as there are no errors in the event viewers relating to allocation of licenses, that if these temp licenses were allocated prior to application of the licensing pack that the user licenses will be used once the temp licenses have expired (even though at this stage you have no way of knowing this - don't you just love ms??).

BUT and it is a big BUT - wait for further comments which I'm sure you'll get. This post is more of a "registering an interest and sharing findings" which may or may not be relevant in your case, rather than posting a solution,

Hope that helps more than confuses,

Deb :))

0
 
Debsyl99Commented:
Hi
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 :))
0
 
segibson77Author Commented:
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.
0
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.