SPLA 2003 Terminal Server CAL question....

[Guest]

We have several 2003 Servers using Terminal Services as an app server. We
have an SPLA volume license agreement and we are using that license for our
terminal servers.

I've followed the directions for it to the letter. This license shows up in
TS licensing as Windows Server 2003 - Terminal Server Per User CAL Token. It
shows type as volume license, total as 1, available as 1, but issued as 0.

We also have in TS Licensing a line for temporary per device CAL tokens, and
that is what everyone is being issued (issued is listed as 92).

The only reason I even went and looked at all of this is because when I
logged on this morning to that machine it gave me a message stating that in
15 days my temp CAL was going to expire. So I got to looking around here and
discovered that the default license type in TS is per device so I changed it
to per user. Now when I log on, I no longer get that message, but what has
me worried is that it still shows no volume license per user CALs as being
issued.

What I'm worried about is that in 15 days our tokens are going to start
expiring. Is there any way I can check to see if I now have a non temporary
license?

TIA
--Shawn

 

[Guest]

I have an almost identical situation. We also have a couple TS servers in a
farm. We purchased and installed 55 "Terminal Server Per User CALs" The
Terminal Server license program shows the 55 unused user licenses. We
also have 92 temporary licenses issued per machine. I just received the
expiration warning this morning.

The difference is that I changed the license mode over to "per user" in the
terminal services configuration\server settings over 90 days ago. If anyone
has some input as to what I missed it would help. I have till Feb. 27th. to
get this resolved.

 

[Vera Noest [MVP]]

This is by design, since Per User licenses are currently unmanaged.
You won't see the "available" count decrement.
The fact that you don't get any "license will expire" messages
anymore is prooof that all is well. Keep an eye on your EventLog,
license problems are reported there, loud and clear.

Documented here:

822134 - The Function of Terminal Server CALs in Windows Server
2003
http://support.microsoft.com/?kbid=822134

 

[Vera Noest [MVP]]

Since you get an expiration warning, you have a problem (Shawn
doesn't).
I would double-check that your TS is *still* in Per User licensing
mode. There is a bug in 2003, which makes it sometimes switch back
to Per Device mode. That would explain your situation. If this
turns out to be the problem, phone Microsoft support and ask for
this hotfix:

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
http://support.microsoft.com/?kbid=834651

 

[Guest]

Awesome. You rock. Thanks a million.

This is by design, since Per User licenses are currently unmanaged.
You won't see the "available" count decrement.
The fact that you don't get any "license will expire" messages
anymore is prooof that all is well. Keep an eye on your EventLog,
license problems are reported there, loud and clear.

Documented here:

822134 - The Function of Terminal Server CALs in Windows Server
2003
http://support.microsoft.com/?kbid=822134

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---