Remote Desktop session host (RDSH) is a role in Remote Desktop Services (RDS) that host Windows applications or desktops. These are accessible via the Remote Desktop connection. The Remote Desktop Services license server issues CALs to users and devices when they access the Remote Desktop session host. This erased when a user attempts to log on may experience two problems. One where a remote desktop license server is not available and a second access denied due to security concerns. The error you see would be:
Remote session has been disconnected because no remote desktop license server is available to provide a license
Although we are looking at the missing remote desktop license servers, we are also sharing what needs to be done if the cause of this is a security issue. So let’s see what caused the problem. To do this, we need to log into the RD session as a domain administrator and open the RD License Diagnostic.
Causes of Missing Remote Desktop License Servers
- Signs of Missing Remote Desktop License Servers: If the recorder has messages that speak of the RDSH grace period has expiredand the server has not been configured with any license server. It can also indicate where it is indicated License server
is not available and indicates network connectivity issues; a service stopped, etc. In this case, you must configure the RD license service. - Network / certificate issues: If you see another problem that talks about network protocols, a disconnected client, and then their security error. In this case, you must update the registry keys of the X509 certificate.
Remote session has been disconnected because no remote desktop license server is available to provide a license
Depending on the problem you have discovered, follow the methods to resolve the problem.
- Configure the RD license service
- Update the registry keys of the X509 certificate
- Activate the group policy linked to the license server and to the policy
1]Configure the RD license service
The RD Licensing Service ensures that each license is validated and is available to provide a license. Follow the steps to resolve it through Server Manager.
- Open Server Manager and access Remote Desktop services.
- In Deployment overview, select Tasks, and then select Edit deployment properties.
- Select Remote Desktop License, then select the appropriate license mode for your deployment (per device or per user).
- Enter the fully qualified domain name (FQDN) of your RD license server, then select Add.
- If you have multiple RD license servers, repeat step 4 for each server.
2]Update the registry keys of the X509 certificate
Be sure to follow the instructions carefully as we will have to modify the registry. So be sure to back up the registry so that you can restore it in the event of a problem. Once done, we will remotely have the registry keys of the X509 certificate, restart the computer, then reactivate the RD license server. Follow these steps on each of the RDSH servers to reactivate the RD license server:
Open the registry editor and navigate to the following path
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerRCM
From the Register menu, select Export registry file. Enter exported – Certificate in the File name , then select to save. Right click on each of the following values, select Remove, then select Yes to check the deletion:
- Certificate
- X509 certificate
- Certificate ID X509
- X5092 certificate
Once deleted, quit Registry Editor and restart the RDSH server. Once the server is restarted, it will automatically update the keys.
3]Activate group policy
It is applicable to stand-alone servers., You must then activate two policy settings, which are available on the following path when you access them via gpedit.msc on the server.
Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostLicensing
- Use the specified Remote Desktop license server – Enabled.
- Set the Remote Desktop license mode – Enabled.
You can also check if the license mode and add the fully qualified domain name of your RD license server and check if you have created a collection of sessions and make your RDSH server part of the group.
All of these should help you resolve the lack of available remote desktop license servers to provide a licensing issue.
