CALs Windows 2003 Server, Users are getting license from Temporary pack and not from the CAL Token w

[Nimesh]

We had purchased 40 CALs licenses (User). After activation now it
showing three packs in the Terminal Server Licensing MMC screen as
below mentioned:
Product
Type Total Available Issued
Existing Windows 2000 server - Terminal Services CAL Token (Per
Device) Built-In Unlimited Unlimited 0
TemporaryLicensesfor windows server2003-Terminal Server PerDevice
CALToken Temporary - - 7
Windows 2003 - Terminal Server Per User CAL Token
Volume License 40 40 0
All the server are Windows 2003. Users connecting to the server are
getting license from Temporary Pack, where as they should be getting
license from third option (As above).Please can you help us in finding
out why it is happening, and what should be the solution for this?
We have made registry changes in the terminal servers to make these
servers point to License server as mentioned below:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers\"LicenseServerName"]

This twmporary pack is showing Last Date 13 Oct.
Please can you suggest what the problem is and how to resolve it.

Thanks in advance,

Nimesh

 

[TP]

Make sure your Terminal Server is set to Per User license mode.

You can change it in Terminal Services Configuration. Even after
you change the mode, your per user license count will not decrement
because per user licenses are unmanaged.

Thanks.

-TP

 

[Nimesh]

Thanks for your reply.
I have already the Terminal Server as Per user license mode by setting
up Licensing as "Per User" in Terminal Services Configuration. But no
help. Please can you tell me, how to make per user license managable?
May be this can help.
Thanks,

Nimesh

 

[Vera Noest [MVP]]

You can't make Per User licenses "managed", that's something that
Microsoft has to build into the next Terminal Server version
(hopefully).

Is there anything in the EventLog on the Terminal Server?
Check this article:

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

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

 

[Nimesh]

Thanks for the article. We are facing the same problem but registry
setting is as required, 4 for Per User mode.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\LicensingCore
was already set to 4. And in event viewer I am not getting any event
regarding Terminal Server. Please can you suggest any solution. Should
I go ahead and install the patch mentioned in the aboce link?
Or is any there any other reason.
Thanks,

Nimesh

 

[Vera Noest [MVP]]

No, never install a patch for a problem that you don't have!

If there are no Events in the EventLog on the TS, the licensing mode
on the terminal server is Per User, and your TS Licensing Server
still hands out temporary Per Device licenses, I have no idea what
the problem can be.

I suggest that you call Microsoft Support.

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

 

[TP]

Nimesh,

Please confirm that you are still having a problem by testing to
see if licenses are being issued. Follow the following steps
to test:

1. On a workstation, delete the following registry key, which
holds the TS license:

HKLM\SOFTWARE\Microsoft\MSLicensing

2. Use the above workstation to connect to one of your
terminal servers using the remote desktop client.

3. On your TS Licensing server, check and see if a new
temporary license was issued.

If things are working correctly, the TS Licensing server will
NOT issue a fresh temporary license in the above test. It
also will not issue a Per User license.

When all of your terminal servers are in Per User mode,
the TS Licensing server is not used. Even if you stop the
TS Licensing service clients will still be able to connect to
your terminal servers. I recommend leaving the TS licensing
service started so that no "unable to locate a ts licensing server"
events are logged on your terminal servers, but this is cosmetic.

Thanks.

-TP

 

[TP]

I hope they don't build a way to manage Per User licenses in the
next version. It is nice having things the way they are now.

-TP

 

[Nimesh]

Thanks. I deleted HKLM\SOFTWARE\Microsoft\MSLice­nsing from a work
station and connected to terminal server from this workstation. But TS
Licensing server has not issued any temporary license. So this means
everyting is fine? I have some quries:
1. If everyting is fine then why Windows 2003 - Terminal Server Per
User CAL Token is not issuing any license.
2. If things are not as required, is it going to creating any problem?

 

[TP]

Based on your test, your system appears to be running fine.

As I mentioned, Per User licenses will not be issued. This is
normal.

If you like you can repeat the same test with all of the
workstations that were issued temporary licenses.

Thanks.

-TP