How License Service Keeps Track of License Usage

MORE INFORMATION

Configuration

When you install or upgrade a server or a license-aware application, you select the license mode.

If you select the Per Seat mode, you may specify the Master Server and the Replication Frequency (if you work in a domain, all the domain servers use the PDC Master Server definition).

The Master Server will centralize all license data for your organization:

• Purchase licenses history (updated with License Manager utility).
• Client access usage (replicated by all servers to the Master Server at each specified replication time).

Client Definition and Usage

A Per Seat server logs all client connections and replicates this data to the Master Server.

The Master Server gathers all the client information. Each new client consumes one license (even if this client works with several servers). If no more licenses are available, the License Logging Service on the Master Server logs an Event ID 201 in the local application log file.

With Per Seat licensing, a client access license applies to a specific computer. After a computer has a client access license assigned to it, any user of that computer can access any Windows NT Server product on the network. Using the Per Seat license mode allows an unlimited number of computers with client access licenses to connect to each server.

Configuration files

The license service uses the following files to store license data:

• Purchase history: %systemroot%\System32\Cpl.cfg
• Connection history: %systemroot%\System32\LLS\Llsuser.lls
• Group information: %systemroot%\System32\LLS\Llsmap.lls

These files are created when the License Manager service starts.

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
   Llsuser.lls
   Llsmap.lls
3. Restart the License Logging service.
4. Re-add the appropriate license information.