Temporary TS CALs still being issued



We are in the midst of upgrading from Server 2000 to Server 2003. The
majority of our clients are running 2000 Pro SP 4 (and we do not plan to
upgrade them soon). Our DCs are still running Server 2000 SP 4 and still
have a TS CAL Server running on one of them (some legacy TS Servers will
remain on 2000 until they are no longer needed). Because of this, our 2003
TS CAL Server is running on one of our domain member servers. Our TS Servers
have been pointed to use the 2003 TS CAL server via the registry using the
scripts from a Microsoft published TS Architecture document. Initially, due
to some miscommunication the servers were configured in Per Device mode while
the TS CAL Server contained only User CALs. All servers are now set to be in
Per User mode.

So, the situation is that our 2003 TS CAL Server occasionally issues about 5
or 6 Temporary Device CALs a day. Users can still login, but they get the
popup message about their CAL expiring in x days even though the TS Servers
are in Per User mode. Once the device CALs associated with their
workstations expire, they can still log in. The TS CAL Server is not heavily
loaded, but I'm wondering if the problem is due to network latency or
something like that? Is there any way to clean out the expired temporary
Device CALs? Being able to manage the list might make it easier to figure
out the pattern here. Is there a limit on the number of TS Servers a TS CAL
Server can service? We have ~8 physical servers and ~20 virtual servers.
Are we putting too much of a burden on the TS CAL Server that we need to
create a partner for it to use for load balancing?

Thanks in advance for any help you can provide.

Vera Noest [MVP]

I can't exclude network problems completely, but I think that the
most likely cause for this behaviour is that one of the Terminal
Servers is *not* (anymore?) in the Per User licensing mode.
Either it was missed from the beginning, or you have this issue:

834651 - Terminal Services licensing mode changes from Per User or
from Per Device to an invalid value after you add or remove a
Windows component

Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question