Remote Desktop Session Host (RDSH) is a role in Remote Desktop Services (RDS) that host Windows applications or desktops. These can be accessed using the Remote Desktop connection. The Remote Desktop Services license server issues client access licenses to users and devices when they access the RD Session Host. That cleared when a user tries to connect can face two issues. One where no Remote Desktop License Servers available and second access denied because of security issues. The error you see would be:
The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license
While we are looking at the missing Remote Desktop License Servers, but we also share what needs to be done if the cause of this is a security issue. So let’s find out what caused the problem. To do that, we will have to sign-in to the RD session as the domain administrator and open the RD License Diagnoser.
Causes of missing Remote Desktop License Servers
- Signs of missing Remote Desktop License Servers: If the logger has messages which talk about the grace period of the RDSH has expired, and the server hasn’t been configured with any license server. It may also message where it says License server <computer name> is not available and points out to network connectivity problems; service stopped, etc. In this case, you need to configure the RD licensing service.
- Network / Certificate Issues: If you see any other issue which talks about network protocols, disconnected client, and then its security error. In this case, you need to refresh the X509 Certificate registry keys.
The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license
Depending on the issue you discovered, follow the methods to resolve the problem.
- Configure the RD Licensing service
- Refresh the X509 Certificate registry keys
- Enable Group Policy related to licensing server and policy
1] Configure the RD Licensing service
RD Licensing service makes sure every license is validated, and it is available to provide a license. Follow the steps to fix it through the Server Manager.
- Open Server Manager and navigate to Remote Desktop Services.
- On Deployment Overview, select Tasks, and then select Edit Deployment Properties.
- Select Remote Desktop Licensing, then select the appropriate licensing mode for your deployment (Per Device or Per User).
- Enter the fully qualified domain name (FQDN) of your RD License server, and then select Add.
- If you have more than one RD License server, repeat step 4 for each server.
2] Refresh the X509 Certificate registry keys
Make sure to follow the instructions carefully as we will have to modify the registry. So make sure you back up the registry so you can restore it in case something goes wrong. Once done, we will have remote the X509 Certificate registry keys, restart the computer, and then reactivate the RD Licensing server. Follow these steps on each of the RDSH servers to reactivate the RD Licensing server:
Open the Registry Editor and navigate to the following path
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
On the Registry menu, select Export Registry File. Enter exported- Certificate into the File name box, then select Save. Right-click each of the following values, select Delete, and then select Yes to verify the deletion:
- Certificate
- X509 Certificate
- X509 Certificate ID
- X509 Certificate2
Once deleted, exit the Registry Editor and restart the RDSH server. Once the server reboots, it will refresh the keys automatically.
3] Enable Group Policy
It is applicable for the Standalone servers., then you need to enable two policy settings, which is available at the following path when accessed through gpedit.msc on the server.
Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing
- Use the specified Remote Desktop license server- Enabled.
- Set the Remote Desktop licensing mode- Enabled.
You may also want to check if the Licensing mode and add the FQDN of your RD Licensing server and check if you have created a session collection and make your RDSH server part of the group.
All these should help you fix the no Remote Desktop License Servers available to provide a license problem.
Related posts: