If no license tokens are available, the temporary Terminal Server CAL token will continue to function for 90 days. The license is stored in the client's registry. 32-bit RDP clients store their license under the key. Fixes Terminal Server License registry key VB script elevates itself as admin, creates a backup or Terminal Server Licensing Registry key, saves it to users Desktop folder (mslicensebackup.reg), removes the registry key and opens a new RDP connection to specified server (in YOURSERVER-FQDN).Helpfull to solve Citrix termi.

Learning has never been so easy!

Tech Level: 1

When using Citrix or RDP, a user might experience the following message upon connection:

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

This issue can be resolved typically by removing a registry key and reconnecting to the RDP or Citrix server.

3 Steps total

Step 1: Open the registry editor

While logged in as an administrator, click 'start'> 'run'

In the 'open' field, type 'regedit.exe' and click 'ok.'

Step 2: Locate and delete the MSLicensing registry key

Navigate to HKLMSoftwareMicrosoft key. Export this key for backup purposes.

Find the 'MSLicensing' subkey and delete it. Fight of characters ai map free download.

Terminal Server License Cost

Step 3: Retry your connection to Citrix/RDP

Once the key has been deleted, you can try to open the Citrix/RDP session in question again. Note that you do not have to close Internet Explorer (if accessing via this method).

If the problem persists, check the remote end to ensure there is a valid terminal services licensing server online and available.

These steps can also be performed remotely, pending you have admin rights, using a remote registry connection via regedit.

References

Terminal Server License Servers Group

Removing Terminal Server licenses from an RDP client

Terminal Server Licensing Registry Key

1 Comment

Pimiento
Albert6697 Sep 28, 2016 at 04:12pm
I ran into this issue because I installed the RDS role for testing on the server I was attempting to connect to and after the allotted period of time (60 or 90 days) I had to have RDS licensing so it blocked any incoming connections due to licensing. I simply removed the role, rebooted and was able to log in via RDP.

Terminal Server License Registry