Windows Server - Terminal Server License Server not issuing Permanent licenses

Asked By Cindy on 29-Jun-10 12:43 PM

I have a licensed TSLS, recently I tried adding another TSLS and broke my original TSLS.  It has been releasing tokens, I have external users who cannot remote in, the error they are receiving is: The remote session was disconnected because there are no terminal server license servers available to provide a license. The activation status on the TSLS is activated. I've checked they're not still logged in on a previous session. Microsoft says that it means I have no TSLS configured and I'll have to reconfigure it, however I still have users who can connect.

Any ideas.

Devil Scorpio replied to Cindy on 29-Jun-10 01:21 PM

Hi Cindy,


The terminal server might not be able to locate the license server.


Perform the troubleshooting procedures described in The terminal server cannot locate the license server.


The client might have exceeded its Terminal Server Licensing grace period (, and a license server has not yet been installed or activated to issue the client a client access license (CAL). After a temporary license expires, a client can only connect to a terminal server if the license server can issue a permanent CAL.

Install Terminal Server Licensing, activate the license server, then purchase and install a sufficient number of CALs to support the clients in your organization. As a security best practice, consider Using Run as ( to perform this procedure.

To install Terminal Server Licensing


    Open Add/Remove Programs in Control Panel.

    Double-click Add/Remove Programs.

    Click Add/Remove Windows Components.

    In Terminal Server Licensing Setup, do one of the following:
      * Click Your entire enterprise to choose an Enterprise license server. You can only install an Enterprise license server on a domain controller or a member server in a domain (if the member server is running Windows Server 2003), not on a stand-alone server. This role is published to Active Directory. If you are installing an Enterprise License Server, you must meet one of the following conditions: 1) You must be a member of the Enterprise Admins group in Active Directory or 2) You must have the right to create the TS-Enterprise-License-Server object in the same site in which the license server will reside in Active Directory.

      * Click Your domain or workgroup to choose a Domain license server. If you select this option, the computer on which you install the license server does not have to be a domain controller, if the computer is running Windows Server 2003. However, if the computer is running Windows 2000, the computer on which you install the license server must be a domain controller or a stand-alone server in a workgroup. If the computer on which you plan to install the license server is in a workgroup, it can only be automatically discovered by terminal servers on the same subnet. If you are installing a Domain license server, you must be a member of the Administrators group on the local computer. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure.


    Provide the file system location where the license server database should be installed on the Terminal Server license server, click Next, and then click Finish.

    The default location for the license server database is systemroot\System32\LServer.

You can activate a Terminal Server license server by using one of three methods: Automatic, Web Browser, or Telephone. It is recommended that you activate a license server automatically, as described in the following procedure.

To activate a license server automatically.


    Open Terminal Server Licensing. To open Terminal Server Licensing, click Start, point to Control Panel, Administrative Tools, and then click Terminal Server Licensing.

    In the console tree, right-click the license server that you want to activate, click Activate Server, and then follow the instructions in the wizard.

    In the Activation method list, select Automatic connection (recommended), and then click Next.

    Follow the instructions in the wizard.

    If necessary, at a later time you can change any license server properties, such as activation method and company information, that you set during the activation process.

Best Regards :)

Cindy replied to Devil Scorpio on 29-Jun-10 03:25 PM


Thanks and I understand.  My issue is: Terminal Licensing Server is already installed, the license server is activated, and we have purchased and installed device CALs but the TSLS is still not issuing permanent licenses.  It seems I'll have to rebuild the TSLS database.

Thanks again.

Cindy replied to Cindy on 30-Jun-10 03:46 PM

This has been solved. The terminal server was not seeing the terminal server license server even though it was set in AD sites and services. Had to manually point it to the TSLS by editing the registry of the terminal server.


Added a key called LicenseServers within this key added another key which was the name of the Terminal Server License Server

This solved my issue, my users can connect again without receiving that error.

Ramu Soft replied to Cindy on 02-Jul-10 12:05 PM
Thanks Cindy for sharing the solution :-)