• The Remote Session Was Disconnected Because There Are No Terminal Server License Servers Available
• The Remote Session Was Disconnected Because There Are No Terminal Server License Servers

The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license Windows Server Remote Desktop Services (Terminal Services). This article provides information on troubleshooting an error indicating that no Remote Desktop license servers are available in Windows Server 2012.

Remote Desktop Protocol (RDP) basically helps us to connect two system at distant location. We’ve already seen how to enable, disable the Remote Desktop connection using RDP protocol. However, when you establish a Remote Desktop connection on Windows 8.1, 8, 7 or Vista operating systems, sometimes licensing errors may arise. Generally, in such cases, you’re likely to receive following error:

The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer. Please contact the server administrator.

The root cause behind this issue is that the Terminal Server (TS) is not able to locate license server. Thus as a result of this, you received the message and are unable to bridge a Remote Desktop connection.

If you face this problem on Windows Server, it is better to check if the license server is correctly installed, and Terminal Server Licensing service is running perfectly on it. If this doesn’t helps, you need to follow these steps:

Making mistakes while editing the Windows Registry could affect your system adversely. So be careful while editing registry entries and create a System Restore point before proceeding.

1. Press Windows Key + R combination, type put regedit in Run dialog box and hit Enter to open the Registry Editor.

The Remote Session Was Disconnected Because There Are No Terminal Server License Servers Available

2. In the left pane of Registry Editor, navigate here:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing

3. In the above shown window, right click on the MSLicensing key and select Export. This will let you to save this registry key in terms of registry file as a backup. Now right click same registry key and select Delete.

Provide the registry key delete confirmation by clicking Yes option here:

After deleting you must close Registry Editor and restart the machine. When next time, the Remote Desktop client is started, the deleted registry key will be rebuilt, consequently solving the problem.

Hope this helps!

Related Posts:

Hi

I am wondering if could please assist with an issue we have in our Citrix XenDesktop 7.6 deployment?

We have deployed a Citrix XenDesktop 7.6 deployment following the instruction provided within 'Getting Started with Citrix XenDesktop 7.x' chapters 1/2 , by Packt Publishing..(Author Craig Thomas Ellrod)..

Specifications:

Citrix Xenserver 6.5 (on physical machine), Citrix XenCenter, Studio and Storefront

software installed

The Remote Session Was Disconnected Because There Are No Terminal Server License Servers

Physical: XenServer 6.5 (IBM System x3650)

VM1: Citrix XenCenter (win 7/8 and win2012 VMs are used in the deployment)

VM2: Delivery Controller, Studio, License Server

VM3: Storefront

VM3: Citrix Director

VM4: Domain Controller, DHCP, DNS, LDAP and CA

Problem:

When logging into the UI, and attempting to start a virtualized application/desktop we get the following error message.

'The remote session was disconnected because there are no Terminal Server License Servers available to provide a license. Please contact the server administrator.

The environment was fine but we encountered this before. This error happens after the Remote Desktop license has expired after 120 days.. and previously we had to resolve this issue by re-installing a new windows 2012 server and re-install all related software on the 2012 as the template. This is specific to windows 2012, is that correct?

I have done some checking on the citrix knowlege base:

1. Tried the steps in this article before the expiry occured but no luck..

2. Looked at this link

3: Information about a hotfix for this type of problem:

is this required to be installed on win2012 vm (including the template machine)

Please assist, is there a solution we can apply with out removing and re-creating new VMs as we will encounter this problem again after 120 days?

Thank you

/martin