How to Fix the Remote Session Was Disconnected No License Servers

The remote session was disconnected License Servers

A user said that he was facing the problem of “The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license” when using Windows Server 2012. The problem made him unable to use the Remote Desktop anymore.

When connecting to a remote session in Windows Server 2012, 2016, 2019, you may encounter the remote session was disconnected no License Servers to provide a license problem. The following shows you the causes and solutions to this problem.

Reasons for no Remote Desktop Licenses Servers available

• The Remote Desktop Server does not authorize the Remote Desktop to configure the Remote Desktop Licensing.
• The system-default Registry Editor only allows a 120-day GracePeriod.
• The licensing model and server name are not configured using Group Policy.

Solutions to no Remote Desktop Licenses Servers available

If there’s no Remote Desktop License Server available, you can open RD Licensing Diagnoser on Windows Server 2012, 2016, 2019 to check whether there is a problem with the Remote Desktop licensing configuration.

How to open RD Licensing Diagnoser?

Navigate here: Control Panel > System and Security > Administrative tools > Remote Desktop Services > Remote Desktop Licensing Manager. If it is a Remote Desktop licensing or deadline problem, it will be displayed after the diagnosis by RD.

If the problem lies in licensing, then you need to reconfigure the RD licensing service. If the problem lies in the deadline, then you need to modify the time limit of the Registry Editor.

Configure the Remote Desktop Licensing

If the problem lies in licensing, then you need to reconfigure the Remote Desktop Licensing.

Step 1. Open the Server Manager, right-click Add Roles and Features in the Manage.

Step 2. Click Roles Services, choose to install the Remote Desktop Licensing, and fill in your personal information after the installation is complete.

Step 3. After installing the Remote Desktop Licensing, return to the Administrative tools, select the management tool, Remote Desktop Services.

Step 4. Open Remote Desktop Licensing Manager.

Step 5. Right-click the Server and select Activate Server.

Step 6. Click Next in the Activate Server Wizard to complete the installation of licensing. Then you have troubleshot the licensing problem.

Modify the deadline of the Registry Editor

Note: The following methods can only be used when you use RDS Server 2016 in a test environment. If you want to use RDS Server in a production environment, please continue to purchase RD CAL. 

If the licensing configuration seems to be correct and the RD Licensing Diagnoser does not find any errors, it may be that the deadline of the Registry Editor has been limited. Before modifying the Registry, back it up in advance to prevent unrecoverable situations. 

Step 1. Press WIN + R, and enter “regedit” to open the Registry Editor.

Step 2. Navigate here: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server > RCM > Licensing Core > GracePeriod. Then right-click it.

Step 3. In the Permission for GracePeriod window, select Administrator, tick Full control, and then click OK.

Step 4. After allowing Full Control for Administrators, right-click GracePeriod, click Delete, and click Yes on the Confirm Key Delete page. Then restart the system to make the registry take effect.

Use Group Policy to configure the licensing model and server name

Step 1. Press WIN + R, and enter “gpedit.msc” to open the Local Group Policy Editor. On the left pane, navigate here: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services.

Step 2. Find Remote Desktop Session Host and open it.

Step 3. On the right pane, find Licensing and open it.

Step 4. Find Use the specified Remote Desktop license servers and double-click to open it.

Step 5. Switch Not configured to Enabled, enter the corresponding server name in the License servers to use, and click OK to complete the configuration.

When you encounter the remote session was disconnected License Servers problem using Windows Server 2012 R2, 2016, 2019, 2022, the above-mentioned methods can help you solve it. When using the built-in Windows program Remote Desktop Connection, you should avoid problems such as license agreement errors, which may lead to serious consequences of server failure.

Realize remote control quickly and safely

Thus, we need a simple and fast method to avoid problems like the remote session was disconnected License Servers. At this time, we can choose a third-party remote control software, such as AnyViewer. It is perfectly compatible with multiple Windows versions, including Windows Server 2012 R2, 2016, 2019, 2022. 

Let’s take a look at its operation steps. First, download AnyViewer on both the client computer and the host computer.

Step 1. Install and launch AnyViewer on both your home and office computers.

Step 2. Go to Log in, and then click Sign up. (If you already have signed up on its official website, you can log in directly.)

Step 3. Fill in the signup information.

Step 4. Then you can see you successfully logged in to AnyViewer. Your device will automatically be assigned to the account you've logged in to.

Step 5. Log in to the same AnyViewer account on the two devices, then click Remote control to achieve unattended remote access.

Note: If you upgrade your account to Professional or Enterprise edition, then you’ll have more rights. You can assign more devices. Also, you can connect to another computer in privacy mode, which means you can black the screen and block the mouse and keyboard of the remote computer.

Conclusion

This article shows you three possible reasons why you encounter the problem of “The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license” when using Windows Server 2012, 2016, 2019. You can solve the problem by configuring Remote Desktop Licensing, modifying the deadline of the Registry Editor, or using the Group Policy to configure the license mode and server name, or you can directly use AnyViewer to realize remote control quickly and safely.

For the three solutions listed above, some operations may be troublesome for you and require a certain degree of computer operation ability, because improper operations may cause other problems. And users also reflected that they often encounter problems like your credential did not work, user account did not work, and clipboard did not work when using RDP, making it more difficult to use it. Compared to those solutions, AnyViewer is easy to operate. It allows you to work freely anytime and anywhere, saving you time and improving your work efficiency.