Microsoft offers three licensing modes, per server, per device or per user, and per processor:
- With per-server licensing, CALs are associated with specific servers. You must have a CAL for each user that accesses a given server, so you need to purchase sufficient CALs to cover the maximum number of clients that can connect to that server at any time.
- With per-device or per-user licensing, each CAL is associated with a specific user, computer, or device. Clients are licensed to connect to any server on the network as long as each client has a CAL for each type of server accessed, eg: Windows Server 2003, SQL Server, Exchange Server, and so on).
- A few server products, eg: SQL Server 2000, offer per-processor licensing. CALs are not required as the server itself is licensed, based on the number of processors installed.
If you choose per-server licensing when installing Windows Server 2003, you can opt to change later to per-user or per-device licensing. It is not possible to change from per-user or per-device licensing to per-server licensing.
To manage licensing for a site you need to know the proper licensing server, which you can locate as follows:
- Open the Active Directory Sites and Service snap-in and select the site that you want to work with, then right-click the Licensing Site Settings object in the details pane and select Properties.
- The licensing server for the site appears at the bottom of the window in the Licensing Computer section. You can change it by clicking the Change button.
- Click OK when you are finished.
The default licensing server for a site is the first domain controller installed in the site. A site license server does not have to be a domain controller, but it should be located in the same site as a domain controller.
Windows Server 2003 has two licensing utilities by default. The Licensing icon in Control Panel lets you configure licensing for the local server, but if you click Start > All Programs > Administrative Tools > Licensing, you launch the Enterprise Licensing tool for sites and domains.
Before you can use either of these tools, the License Logging service must be running on the server that you are working on. This service is not started automatically, so it must be started manually. You must be a member of the Administrators group for the local server or the domain on which you want to manage licensing.