Show
This article help you troubleshoot the "No licenses available" error in a deployment that includes an Remote Desktop Session Host (RDSH) server and a Remote Desktop Licensing server. Applies to: Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 SymptomsClients cannot connect to Remote Desktop Services, and they display messages that resemble the following: The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Access was denied because of a security error.Sign in to the RD Session Host as a domain administrator and open the RD License Diagnoser. Look for messages like the following: 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 <computer name> is not available. This could be caused by network connectivity problems, the Remote Desktop Licensing service is stopped on the license server, or RD Licensing isn't available.CauseThese issue could be caused by the following user messages:
In this case, check the RD Licensing configuration. If the RD License Diagnoser lists other problems, such as "The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client", there may be a problem that affects the license certificates. Such problems tend to be associated with user messages, such as the following: Because of a security error, the client could not connect to the Terminal server. After making sure that you are signed in to the network, try connecting to the server again. In this case, refresh the X509 Certificate registry keys. Check the RD Licensing configurationYou can check the RD Licensing configuration by using Server Manager and RD Licensing Manager. Verify the following: Configure licensing for an RDS deployment that includes the RD Connection Broker role
Configure licensing for an RDS deployment that includes only the RD Session Host role and the RD Licensing role
Refresh the X509 Certificate registry keys
Important Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong. To resolve this problem, back up and then remove the X509 Certificate registry keys, restart the computer, and then reactivate the RD Licensing server. Follow these steps.
Note Perform the following procedure on each of the RDSH servers. Here's how to reactivate the RD Licensing server:
Additional troubleshooting methodsIf you verify that the licensing configuration is correct, but the system still isn't correctly issuing CALs, follow these steps: To open RD Licensing Diagnoser, open Server Manager, and select Tools > Terminal Services > RD Licensing Diagnoser.
The top window of the RD Licensing Diagnoser lists problems that the diagnoser has detected. For example, you might see a message that resembles the following:
The RD Licensing Diagnoser Information section shows more information about the problem, including its possible causes and the steps to follow to remediate it. The following table shows which RDS CAL and RD Session Host versions are compatible with one another.
The following table shows which RDS CAL and license server versions are compatible with one another.
For more information, see RDS CAL version compatibility. If you use domain-joined servers for your RDS deployment, you can use both Per User and Per Device CALs. If you use workgroup servers for your RDS deployment, you have to use Per Device CALs In that case, Per User CALs aren't permitted. |