Vernalex.com - Welcome

Display Name (?):

License Logging

Short Name (?):

LicenseService

Executable (?):

llssrv.exe

Library (?):

None.

Depends On (?):

None.

Supports (?):

None.

Description (?):

Monitors and records client access licensing for portions of the operating system (such as IIS, Terminal Server and File/Print) as well as products that aren't a part of the OS, like SQL and Exchange Server. If this service is stopped, licensing will be enforced, but will not be monitored.

OS (?):

2000 Server, Server 2003, Vista Server

Startup (?):

Default	Home	Workstation	Server	Minimal	Tweaked	Automatic
Disabled	Disabled	Disabled	Automatic	Disabled	Disabled	Disabled

Explanation (?):

The License Logging Service is used on Windows servers to monitor available licenses and to provide action when all licenses are consumed. It is used primarily for Microsoft owned products such as IIS, Terminal Services, File and Print services, VPN, SQL Server and Microsoft Exchange, although it is possible other applications could use it.

When used correctly the site license server should be the first domain controller created at a particular site (running on a PDC Emulator). In the Windows 2000 and on implementation each site collects site license information separately and this information can be viewed by the site administrator, and this data is replicated to a master license server that is administrated by the administrator of that server.

The master server centralizes the license data and can view the "purchase licenses history" and the "client access usage". Licences themselves come in two modes of per set and per computer, but a third mode of per connection is available in some server versions. The difference is that per seat allows a particular number of allowed connections to the entire system, the per computer grants access to all systems for a particular SID, and per connection means each server can be licensed for a number of simultaneous connections.

The system itself is one of trust though. Setting the number of licenses is as simple as setting the number you're licensed for. And, if you exceed the number of licenses that you own then you will receive an error code in your event log. Error code 201 is used in your application event log when a particular user has no available license for a particular product. When you near the amount of per server licenses you will receive error 26 in the system log and 221 in your application log. To the end user when a license count is exceeded they will not notice as their service will continue without halting. Is it the responsibility of the server administrator to make sure their connections are properly paid for.

If you running a server it is highly recommended that you leave this service set to automatic. But, if you disable this service then all applications will continue to work correctly at the cost of losing your license monitoring abilities.