Server 2012 Terminal Server License Server – Connection issue

Server 2012 RDS License Connection Issue

A known issue for Server 2012 – Terminal Server License Server with an instance of RDS license server installed, preventing connection for the client.

There are a few tricks for getting around the 2012 terminal server licensing connection issue, we’ve shown some steps below to hopefully help you with the problem, or at least buy a bit of time to get around it.

The error message when trying to connect presents;

“The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator.”

No Remote Desktop license servers

Event Viewer

The event viewer presented an event relating to the license server expiring its grace period even though it is fully licensed.

“The Remote Desktop Session Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Session Host server, use the Remote Desktop Session Host configuration tool.”

Remote desktop specified license

“The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses.

An RD Licensing server is required for client connectivity to the RDS. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.”

RD Licensing Grace Period

Fix and workaround

The official solution is to activate the RDS/TS CAL License server, and point the Server to a License server with User/Device License.

If you receive this issue find the following key in the registry (of the terminal server license machine)

HKLM\System\CurrentControlSet\Control\Terminal Server\RCM

If the key: ‘Grace Period’ is present. The license service has not correctly removed the entry, in this instance, will force the server to always run in an unlicensed mode.

Simply delete the Grace Period key (obviously make a backup beforehand)

You may need to give permission to delete this key.

The license server will then need rebooting but should allow the connections through after this.

For more Business IT related posts, please navigate to the Main General Menu and select Business IT from the drop down menu.

We hope you sort your 2012 terminal server licensing issue and we were able to help, or at least rule out one of the many.

5 thoughts on “Server 2012 Terminal Server License Server – Connection issue

  1. Thanks a lot for sharing this answer !
    I had exactly the same problem with my WS2012 RDS server, my CALs were activated and worked for 120 days then no remote desktop available! I deleted the registry key Grace Period, rebooted the server, and it works !!

  2. Thanks for the detailled help.
    Howether, if this has worked for 2 of my 3 servers; one graceperiod registry key doesn’t want to be deleted from one serve. Any idea?
    Still tred to use elevated/Advanced rights in regedit.

    Lionel COUSTEIX

  3. I did the procedure and the registry key “RCM\graceperiod” is back after restarting the session hosts servers, any ideas? WS 2012

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.