Article ID: 239107
Article Last Modified on 6/23/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q239107
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SUMMARY
To select a specific license server for use with various Microsoft Windows 2000 Terminal Services servers in a domain or site, you can modify the registry to point to a particular license server. You can do this to specify that all Terminal Services servers work with a particular license server for accounting purposes, or if a Terminal Services server and the license server reside in different domains. Microsoft recommends that you use the DefaultLicenseServer registry value to minimize issues with the Terminal Server licensing discovery process.
MORE INFORMATION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To select a specific license server, locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters
Add the following value:
Name: DefaultLicenseServer
Data type: REG_SZ
Data value: ServerName
Substitute the NetBIOS name of the appropriate license server for ServerName. If the license server is located on a remote subnet, make sure the Terminal Services-based computer can resolve the NetBIOS name.
Selecting a specific license server enables administrators to select a license server at a site and have Terminal Services servers from various domains located at the same site. This enables the Terminal Services servers to use one license server, instead of requiring a local license server for each domain. Currently, Terminal Services servers work with license servers in their own domain, which may force them to use wide area network (WAN) links to find a license server, even if there is a license server from another domain located at the same site. The method described above enables the crossing of domains for license tracking and accounting.
Note Specifying the DefaultLicenseServer registry value adds one additional step to the typical discovery process. Even if the DefaultLicenseServer registry value points to a valid License Server, the typical discovery process still occurs. If it is unsuccessful, an error is logged.
Microsoft Windows Server 2003 uses a different registry value to specify a license server.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
279561 How to override the license server discovery process in Windows Server 2003 Terminal Services
Additional query words: 1010 1004
Keywords: kbenv kbinfo KB239107
