Hi
Maybe this will help:
Problem:
========
"License usage for product SMB Server 5.0 is nearing the maximum number of
per server licenses purchased. Consult License Manager from the
Administation tools folder for more information."
Resolution:
==========
How to reset License Manager information
SUMMARY
=========
If you want to reset the information license manager displays, you can
delete or rename three files.
MORE INFORMATION
================
To reset the license manager information:
1. Stop the License Logging service.
2. Delete or rename the following files on the primary domain controller or
the enterprise server:
Cpl.cfg, which contains all of your purchase history and is located in
%Systemroot%\System32.
Llsuser.lls, which contains the user information on number of connections
and is located in %Systemroot%\System32\Lls.
Llsmap.lls, which contains License group information and is also located
in %Systemroot%\System32\Lls.
3. Restart the License Logging service.
4. Re-add the appropriate license information.
For additional information, please see the following article in the
Microsoft Knowledge Base:
194065 - How to Reset License Manager Throughout an Enterprise
The information in this article applies to:
o Microsoft Windows Server 2003, Standard Edition
o Microsoft Windows Server 2003, Enterprise Edition
o Microsoft Windows Server 2003, Datacenter Edition
o Microsoft Windows 2000 Server
o Microsoft Windows 2000 Advanced Server
o Microsoft Windows 2000 Datacenter Server
o Microsoft Windows NT Server 3.51
o Microsoft Windows NT Server 4.0
More Information:
==============
The operating system enforces Per Server connections, but not Per Seat. So
when those events are talking about "no license was available for user
SYSTEM using product SMB Server 5.0" - it means that it just so happened
that the connection that exceeded the Per Server licenses was a SMB
connection, it could've just as easily been a TermService connection, etc.
Per Seat / Per Server licenses don't mean anything. Microsoft holds people
accountable to their actual usage, meaning if you set Per Server to 1000,
but you only have 200 connections, if Microsoft audits you, they expect
there to be 200 licenses purchased.
That being the case, the easiest workaround for this problem is just to
increase the number of Per Server licenses specified in the OS.
They could also switch to Per Seat, because Per Seat never enforces any
connection limit on the server.
They could also disable the License Logging Service, but since there is not
much documentation saying it is OK to do so, some may push back on this.
Also, Exchange won't install if the License Logging service is disabled.
316631 - XADM: How to Turn Off the License Logging Service
http://support.microsoft.com/?id=316631
Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.
