How to check terminal server license expired

Pure Capsaicin. DragonsRule This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Microsoft Licensing expert. Amberdawn Oct 19, at UTC. Are you getting this error every time a remote user tries to connect? Time limit. Yes im sure im properly entered the cals on RDS server. Ghost Chili. Amberdawn wrote: cant remember the license server ID.. Amberdawn wrote: cant post the screenshot because it was in my previous company:.

Well, if your colleague won't share screenshots it will be hard for us to help. Amberdawn wrote: what's on the partnumber? Here is an example of an RDS CAL part number: 6VCS Using a part number we can look up what you actually purchased and be able to tell you if it was the correct item and if it has an expiration or not. The part number, or the licensing documentation, will tell what licensing program was used. Just run the Licensing Manager and it will give you the status of the licenses.

Amberdawn Oct 20, at UTC. The most common root cause for these event log entries is a failure to discover the license server. License Servers must be discovered by Terminal Servers. Once located, a digital certificate exchange takes place so the terminal server can check CALs allocated to clients by the license server. Discoverability is critical. When launched on a terminal server, this utility will display any license servers that are discovered, and list the type of license server Domain or Enterprise , as seen in Figure 1.

If no servers are displayed in LSVIEW, either the license servers are offline, or they cannot be discovered by this terminal server. License Servers are discovered a few different ways, depending on which mode the license server was installed. When an Enterprise License Server is installed, an Active Directory registration is created under the configuration container in the site to which the license server host belongs.

When the license server is installed, the administrator performing the installation must have the appropriate rights in AD to create the object. If not, the registration may not complete and the terminal server may not be able to discover the license server. Under the properties of this object, look for the siteServers attribute and check the values. This identifies the registered license server s for the Active Directory site. For the full details on license server discovery, check out my articles on the subject, also available on this site.

To summarize, follow these suggestions to ensure your license servers are easily discovered:. Finally, some additional things to check here are basic network and RPC connectivity, and be sure the license server is online and the license service is started. Windows Server introduced the ability to control which terminal servers can access a particular license server through the use of a new group policy setting — License Server Security Group.

If you are leveraging this policy, be sure that the terminal server in question has been added to the policy so it can access the licensing services. Also check to see if the terminal server in question is the license server. There is a known issue in the new functionality where if the server that requests the license is the same machine as the license server, the operation fails.

For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.

To clean the client's license cache, just delete this key and its subkeys. The next time the client connects to the server, it will obtain another license. To clean the Macintosh client's license cache, delete the contents of this folder. The client will try to obtain a new license from the server the next time that it connects.

Also, you receive the following error message:. To resolve this problem, right-click the Remote Desktop Connection shortcut, and then select Run as Administrator. By default, the remote desktop connection runs as a user with the lowest user permissions.