| Event Id | 1010 |
| Source | TermService |
| Description | The terminal services could not locate a license server. Confirm that all license servers on the network are registered in WINS\DNS, accepting network requests, and the Terminal Services Licensing Service is running. |
| Event Information | After you specify a default Terminal Services license server, the above event is logged every six hours on a server that is running Terminal Services.
CAUSE : This event is logged every six hours if the normal Terminal Services Licensing discovery process does not succeed. However, this event does not mean that unlicensed clients are unable to connect because the server that is running Terminal Services cannot locate a license server. Even if you set a default Terminal Services license server, the event continues to be logged. If you are able to verify by testing with a new client that Terminal Services licenses are being issued by this Terminal server, you can safely ignore the errors in the event log of the server because they simply indicate that the Terminal Services license server autodiscovery process failed to locate a license server. Microsoft recommends that you use the DefaultLicenseServer registry value to reduce any issues with the Terminal Server Licensing discovery process. STATUS : Microsoft has confirmed that this is a problem in the Microsoft products [ windows2k Server and Advanced server] This issue does not occur in Microsoft Windows Server 2003. |
| Reference Links | Event 1010 is reported after specifying default license server Windows 2000 Terminal Services in Windows NT 4.0 Domain Cannot Find Windows 2000 Terminal Services Licensing Server |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.