Article ID: 277917
Article Last Modified on 3/1/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q277917
SYMPTOMS
After you install Terminal Server Licensing on a server,in a Windows 2000 domain, servers may not be listed in the Terminal Services Licensing tool, and you may receive a warning message that indicates that no license servers were detected. In the System event log, TermServLicensing may report an error with Event ID 29, and Service Control Manager may report an Event ID 7024:
CAUSE
Terminal Services Licensing has been installed on a server that is not in a workgroup or on a server that is not a domain controller (DC) for the domain it is based in.
RESOLUTION
To resolve the issue, install Terminal Services Licensing on a DC in a Windows 2000 domain environment. You can run Terminal Services Licensing on a member server that is part of a workgroup or a Windows NT 4.0 domain. The DC does not need to run the Terminal Services service in a Windows 2000 domain, just the Terminal Servers Licensing service.
STATUS
This behavior is by design.
MORE INFORMATION
A Terminal Services License server is only required for workgroups/domains where the Terminal Services mode has been set to "Application Mode". It is not required for "Remote Administration" mode. Remote Administration mode is limited to concurrent clients that connect to the server by using RDP.
The Terminal Services Licensing service can be added or removed by using the Add/Remove Windows Components portion of the Add/Remove Programs tool in Control Panel.
To make a server a DC, use the Dcpromo.exe tool.
For additional information about Terminal server licensing, please see the following Microsoft Web site and articles:
287687 Terminal Services Licensing Enhancements
Additional query words: 7024 29 Terminalsvr Licence TermServLicensing
Keywords: kbenv kberrmsg kbprb KB277917
