Administering Site Licensing

The License Logging service, which runs on each computer running Windows Server 2003, assigns and tracks licenses when server resources are accessed. To ensure compliance, licensing information is replicated to a centralized licensing database on a server in the site. This server is called the site license server. A site administrator, or an administrator for the site license server, can then use the Microsoft Licensing tool in Administrative Tools program group to view and manage licensing for the entire site. This new license tracking and management capability incorporates licenses not just for file and print services, but for IIS, for Terminal Services, and for BackOffice products such as Exchange or SQL Server.

The Site License Server

The site license server is typically the first domain controller created in a site. To find out what server is the license server for a site, open Active Directory Sites And Services, expand to select the Site node, and then right-click Licensing Site Settings and choose Properties. The current site license server is displayed, as shown in Figure 9-11.

Figure 9-11 Identifying and changing the site license server

To assign the site license server role to another server or domain controller, click Change and select the desired computer. To retain the licensing history for your enterprise, you must, immediately after transferring the role, stop the License Logging service on the new license server, then copy the following files from the old to the new licensing server:

■ (/0Systemroot%\System32\CpLcfg contains the purchase history for your organization.

■ 0/systemrootP/\L\s\lAsuser.lls contains user information about the number of connections.

■ %Systemroot%\Lls\Llsmap.lls contains license group information. After all files have been copied, restart the License Logging service. Administering Site Licenses

After you have identified the site license server for a site, you can view the licensing information on that server, opening Licensing from the Administrative Tools program group. The Server Browser tab in Licensing (as shown in Figure 9-12) enables you to manage licensing for an entire site or enterprise.

EFT

CGNTGSO.COM - Licensing

0

License View Options Help

Si iil JLl

Purchase History | Products View | Clients Server Browser 1

E3 Jjj!. CONTOSO j |.g SERVER01

§ Windows Servei

§ Systems Management Servei 2003 I i-S SQL1 - jj!. millennium j |..g bob j ¿-¡BJ hub-inf-101 ¿j^ workgroup

For Helpj press F1

|num |

à

Figure 9-12 The Server Browser tab of the Microsoft Licensing administrative tool

Figure 9-12 The Server Browser tab of the Microsoft Licensing administrative tool

The Server Browser page of Licensing allows you to manage any server in any site or domain for which you have administrative authority. You can locate a server and, by right-clicking it and choosing Properties, manage that server's licenses. For each server product installed on that server, you can add or remove per-server licenses. You can also, where appropriate, convert the licensing mode. Remember that per-server licensing mode issues a license when a user connects to the server product. When a user disconnects from the server product, the License Logging service makes the license available to another user.

The server properties also allow you to configure license replication, which can be set on a server using its Licensing properties in Control Panel. By default, license information is replicated from a server's License Logging Service to the site license server every 24 hours, and the system automatically staggers replication to avoid burdening the site licensing server. If you want to control replication schedules or frequency, you must manually vary the Start At time and Start Every frequency of each server replicating to a particular site license server.

To manage Per Device or Per User licensing, click Licensing from the Administrative Tools program group, then choose the New License command from the License menu. In the New Client Access License dialog box, select the server product and the number of licenses purchased. Licenses are added to the pool of licenses. As devices or users connect to the product anywhere in the site, they are allocated licenses from the pool, with one license for each device or user. After a pool of licenses is depleted, license violations occur when additional devices or users access the product.

The Purchase History tab in Licensing (as shown in Figure 9-13) provides a historical overview of licenses purchased for a site, as well as the quantity, date, and administrator associated with the addition or removal of licenses.

Figure 9-13 The Purchase History tab of the Microsoft Licensing administrative tool

To view cumulative information about licensing and compliance, click the Products View tab. This tab shows how many licenses have been purchased and allocated to users or devices (in Per Device or Per User mode) or the number of licenses purchased for all servers in the site and the peak connections reached to date (in Per Server mode). You can also determine compliance using the licensing status symbols shown in Table 9-2.

Table 9-2 Licensing Status Symbols

Symbol

Licensing Status

The product is in compliance with legal licensing requirements. The number of connections is less than the number of licenses purchased.

The product is not in compliance with legal licensing requirements. The number of connections exceeds the number of licenses purchased.

The product has reached the legal limit. The number of connections equals the number of licenses purchased. If additional devices or users will connect to the server product, you must purchase and log new licenses.

License Groups

Per Device or Per User licensing requires one CAL for each device. However, the License Logging service assigns and tracks licenses by user name. When multiple users share one or more devices, you must create license groups, or licenses will be consumed too rapidly.

A license group is a collection of users who collectively share one or more CALs. When a user connects to the server product, the License Logging service tracks the user by name but assigns a CAL from the allocation assigned to the license group. The concept is easiest to understand with examples:

■ 10 users share a single handheld device for taking inventory A license group is created with the 10 users as members. The license group is assigned one CAL, representing the single device they share.

■ 100 students occasionally use a computer lab with 10 computers A license group is created with the 100 students as members, and is allocated 10 CALs.

To create a license group, click the Options menu and, from the Advanced menu, choose New License Group. Enter the group name and allocate one license for each client device used to access the server. The number of licenses allocated to a group should correspond to the number of devices used by members of the group.

Was this article helpful?

0 0

Post a comment