Licensing issues and warnings in event log

[John Goins]

This same message has been appearing in my win2003 terminal server event log
each day since 1-11-2006. I have 2 license servers running in this domain.
All servers and license servers are in per seat or device. Each license
server shows 25 per seat or device cals available. What do I need to do to
fix this potential problem?



Thanks

Jay Goins

Termservice event 1009

The terminal server licensing grace period is about to expire on 1/11/2006
and the service has not registered with a license server with installed
licenses. A terminal server license server is required for continuous
operation. A terminal server can operate without a license server for 120
days after initial start up.

 

[Vera Noest [MVP]]

You're using a mixture of old and new terminology, as well as a
mixture of server licensing mode versus TS licensing mode
terminology, so I am not really sure about your setup.

The term "Per Seat" licensing applies to server licensing mode, but
it is obsolete. The Per Seat mode has been changed to the "Per
Device or Per User" mode in 2003.
Recommended reading:
Licensing Overview for Windows Server 2003
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/overv
iew.mspx

Terminal Server licensing mode is always either "Per User" or "Per
Device"

It seems that your TS cannot locate the Terminal Services Licensing
Server. You can verify this with the lsreport and lsview utilities
from the Resource Kit.
Another possibility is that you have installed one type of TS CALs
(let's assume "Per User"), but that your Terminal Server is
configured with the default licensing mode of "Per Device".

Could you please check your TS Licensing Manager again and report
exactly which type of TS CALs are installed there?

And on which OS are your TS Licensing Servers running? If they run
on W2K servers, this won't work. A 2003 TS must connect to a 2003
LS, since a W2K LS doesn't understand the new types of TS CALs.

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

 

[John Goins]

Sorry to be confusing. Everything is win2003. On terminal server licensing
it says "Windows server 2003 - Terminal server per user cal token open
25 25 not applicable.

In control panel, licensing, it says: Windows Server and Per Device or Per
User is selected.


we are getting event id 1009 as stated below.

Thank you for your help.

Jay Goins

 

[Vera Noest [MVP]]

OK. So you have installed "Per User" TS CALs on the TS Licensing
Server. Per User licenses are currently unmanaged, that's why they
are listed as N/A. That's nothing to worry about, but you have to
make sure that your Terminal Server also uses the "Per User"
licensing mode. The default is "Per Device".
You can check this from Administrative Tools - Terminal Services
Configuration - Server Settings - Licensing Mode
If it's set to Per Device mode, it will look for a Device TS CAL
and will not issue your Per User TS CALs.

Check this article, it explains that even after you have
switched licensing mode on the TS, your Per User TS CAL count will
not be decremented:

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
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

 

[John Goins]

Thank you for your help. Everything was set up as you said so I kept looking
for a solution.

The solution according to Microsoft is to add a registry key:

http://support.microsoft.com/?kbid=885013

Once again, thank you.
If this does not work, I will let you know. The error is only reported after
my server reboots.

Jay Goins