Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The terminal services licensing server <server name> has no permanent licenses for product "Windows 2000 Terminal Services Client Access License". Use Terminal Services Licensing administrative tool to register more licenses.
|English: Request a translation of the event description in plain English.|
According to T775305, to resolve this issue, ensure that the Terminal Services licensing mode configured on the terminal server matches the type of Terminal Services client access licenses (TS CALs) installed on the Terminal Services license server.
The most obvious fix (if this is the case) would be to buy more TS licenses. However, if the number of licenses is sufficient for the required clients, one may try to reset the license use by deleting the MSLicensing registry key (make sure you do a backup before that).
This issue can be caused by an invalid setting in the registry on your Microsoft Windows Server 2003-based computer that is configured as a terminal server using a Per User or Per Device licensing setting. This may unexpectedly change the terminal server licensing mode and cause the terminal server to obtain only temporary licenses. See ME834651 for details.
This Event ID might be related to a bug in Windows Server 2003. Check the link to Google Thread to find more information about this bug.
Woodrow Wayne Collins
Check T770371 - Microsoft Terminal Server Licensing for more information.
|Private comment: Subscribers only. See example of private comment|
|Links: Google Thread: TS Licensing switches Per User to Per Device|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated