Windows Server 2016 - Can't RDP on server due to an error in the licensing protocol

bmocanu 6 Reputation points
2020-12-18T12:13:54.59+00:00

Hi,

I have a Windows Server 2016 with the following roles installed:

  • Remote Desktop Licensing
  • Remote Desktop Session Host

The configuration is similar to this:
https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/install-rds-host-role-service-without-connection-broker

Added the CAL (per user) license and RDS server is activated. Group Policy objects configured accordingly.

Configuration seemed to work fine until my last server reboot. Now my users can't connect over RDP and they are getting this error message:
The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.

The only method I can get in is in console mode (bypassing the installed CALs) by using the mstsc /admin switch.

I'm all out of ideas. Any suggestions / hints on how to fix this would be highly appreciated.

Thanks in advance,
bmocanu

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
0 comments No comments
{count} vote

1 answer

Sort by: Most helpful
  1. Anonymous
    2020-12-21T03:02:47.34+00:00

    Hello @bmocanu

    When using per-device CALs, RDP needs to write a license to
    HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing and if it cannot, then you will get this message.

    Logged on as standard user does not have rights to write to registry location, whereas running RDC as administrator ensures that the app has the required permissions to modify the Registry.

    You may try delete the two folders underneath "hardware id" and "store" on client machine:

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\MSLicensing\HardwareID
    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\MSLicensing\Store

    49815-image.png

    Then on the client, run "Remote Desktop Connection" as administrator (just one time), from then on, it can be run as usual.

    However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. 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.

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Best Regards
    Karlie

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.