Microsoft KB Archive/270898

= Permissions Required to Install a Terminal Services Enterprise License Server =

Article ID: 270898

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server

-



This article was previously published under Q270898



SUMMARY
This article discusses the requirement to have the proper permissions when you install a Terminal Services Enterprise License Server.



MORE INFORMATION
When you install a Terminal Services License Server which can have multiple users, you must be logged on to the server with an account that is a member of the Enterprise Admins group or a member of the Domain Admins group in the root domain of the forest.

If you are logged on with an account that is not a member of one of the preceding groups, the installation process can complete successfully, but servers that are running Terminal Services in the site may not be able to discover the license server.

This issue can be resolved if you remove the Terminal Services License Server, and then reinstall it using an account that has the correct permissions. When the Terminal Services License Server is installed and made available to multiple users, it creates an object in Active Directory under the Configuration container. By default, only the Enterprise Admins group and the Domain Admins group of the root domain have the proper permissions to create this object.

The full path to the object is:

CN=TS-Enterprise-License-Server,CN= ,CN=Sites,CN=Configuration,DC=

The Terminal Services server may also periodically log event 1010. The following event message may be displayed on your computer screen:

The terminal services could not locate a license server. Confirm that all license servers on the network are registered in DNS/WINS, accepting network requests, and the Terminal Services Licensing Service is running.

Keywords: kbenv kberrmsg kbinfo kbtermserv KB270898

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.