|
LDAP://CN=TS-Enterprise-License-Server,CN=,CN=sites,CN=configuration,DC=,DC=com
|
| bet | 21/37 | | Sana | 30.03.2021 | | Hajmi | 0,83 Mb. | | #13798 |
| LDAP://CN=TS-Enterprise-License-Server,CN=,CN=sites,CN=configuration,DC=,DC=com
The terminal server then attempts to locate any domain license servers by querying all domain controllers within its site, and then all domain controllers within its domain.
Important
Although it is possible for non-domain controllers to be license servers in Windows Server 2003, it is important to note that domain license servers are not automatically discovered. You must configure a preferred license server on all terminal servers that need to communicate with non-Domain controller license servers configured as domain license servers. Enterprise domain license servers deployed on non-domain controllers are automatically discovered.
The terminal caches the names of license servers that it locates in the following locations of the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Parameters\EnterpriseServerMulti (Enterprise license servers)
HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Parameters\DomainLicenseServerMulti (Domain license servers)
If no license server is found, the terminal server attempts a discovery once every hour. After a license server is located, no discovery will be attempted until all of the cached license servers in the Terminal Server registry are unavailable.
|
| |
