“No remote desktop license server available” is a common error when using Remote Desktop Connection to connect to Windows Server. The error indicates that the client cannot make a remote desktop connection to the server even though previous connections to the server were successful and there are no changes to the RDSH server.
In this quick guide, we will show the causes and solutions to use when you encounter the no remote desktop license server.
Symptoms of the “No Remote Desktop License Servers” Error
There are many symptoms of the no remote desktop license server error. Below are a few to watch out for:
Remote Desktop Services
The most common symptom is when the client computer cannot access the Remote Desktop Service and the error messages below pop up:
The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.
Remote Desktop Session Host
When you sign in to Remote Desktop Session Host (RDSH) as an administrator and you check the RD License Diagnoser, you will encounter the following error messages:
 The grace period for the Remote Desktop Session Host server has expired, but the RD Session Host server hasn’t been configured with any license servers. Connections to the RD Session Host server will be denied unless a license server is configured for the RD Session Host server.
 License server
Fix 1: Check the RD Licensing Configuration
The Remote Desktop Services license server is responsible for giving CALs to users and devices when they try to access the RDSH. When there are errors with the licensing configuration, you can experience the no remote desktop license server error.
Use the Server Manager and RD Licensing Manager to verify the RD Licensing server has the right configuration. You should confirm the following:
- The proper installation of the Remote Desktop role
- Activation of the license server
- There is a CAL for every user and device
If there is a problem, you need to configure the licensing. There are two ways to configure the RD licensing.
Fix 1A: Configure licensing that includes the RD Connection Broker role
Open the Server Manager on the RD Connection Broker computer
Select Remote Desktop Services
Navigate to Overview > Edit Deployment Properties > RD Licensing
Select the Edit Deployment Properties option
Select the Remote Desktop licensing mode (Per User or Per Device).
Note: Domain jointed servers can use both Per User and Per Devices, while Workgroup servers can only use Per Device.
Specify a license server and click select Add.
Fix 1B: Configure licensing that includes only the RD Session Host role and the RD Licensing role
Open the Local Group Policy Editor on the RDSH computer
Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing.
Right-click Use the specified Remote Desktop license servers and click Properties.
Enter the license server name and click OK (if you have more than one server, use commas to separate their names).
Right-click Set the Remote Desktop licensing mode, and click Properties.
Choose Per User or Per Device under Specify the licensing mode
Fix 2: Delete the Grace Period key From the Registry
If the error is due to the expiration of the Grace Period, you must delete the reg_binary registry parameter named L$RTMTIMEBOMB. Follow the steps below on how to go about the process.
Login to the server
Open the Command Prompt as an administrator
Type the command regedit.exe to open the Registry
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Select the GracePeriod
Right-click on GracePeriod Key
Click Advanced, and then click the Owner tab.
Under Change owner to, click the new owner, and click OK.
Add the new user
Delete the L$RTMTIMEBOMB
Exit the Registry and reboot the server.
V2 Cloud Is Easier
RDC is an effective way of accessing a computer remotely as individuals or as a workgroup. However, it is a complex procedure. Furthermore, the world is going toward using the Cloud as servers, and V2 Cloud is a cloud desktop infrastructure that you should try.
V2 Cloud allows users to access data remotely. We offer a desktop application that allows RDP connections for Windows, Mac, Linux, Raspberry Pi, Android, and Apple. Our app doesn’t require any IT knowledge and ensures the highest security standard with SSH encryption.
Don’t want to use an app? You can still access your V2 Cloud remote computer in a web browser with just a few clicks without having to install anything.