This article will assist you in troubleshooting the “No licenses available” problem in a setup that comprises an RDSH server and a Remote Desktop for Licence Server.
The following user messages might be causing this problem:
If the RD Licensing Diagnoser reports other issues, such as “The RDP protocol component X.224 discovered an error in the protocol stream and has disconnected the client,” there may be an issue with the license certificates. Such issues are frequently related with user messages such as the following:
The client was unable to connect to the Terminal server due to a security fault. Try connecting to the server again after ensuring that you are logged in to the network.
Refresh the X509 Certificate registry keys in this situation.
A fully functional and activated 2012 Remote Desktop Session Host server displayed the following message:
This was a simple setup on one server with the: connection broker, Session Host and Licensing server with 2012 CAL’s installed.
Even though the licensing seems to be configured correctly, in server manager:
and powershell:
Licensing diagnostics:
everywhere you look, everything seems to be OK. But the license manager shows something odd:
No licenses are being used? This server was used since late 2012. Some interesting things could also be found in the event logs, the following events appear:
EventID: 1130
Source: TerminalServices-RemoteConnectionManager
The Remote Desktop Session Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Session Host server, use the Remote Desktop Session Host Configuration tool.
and:
EventID: 1128
Source: TerminalServices-RemoteConnectionManager
The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.
The solution was to delete the REG_BINARY in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Only leaving the default.
Note: you must take ownership and give admin users full control to be able to delete this key.
After a reboot the server should be working again, licenses are now being used:
Although everything seemed to be ok and configured correctly with valid licenses, it seems that the setup was still in a 180 day grace period, even though it was correctly configured.
A possible bug in RDS 2012?
The Remote Desktop Session Host (RDSH) job is part of Remote Desktop Services (RDS). RDSH may host Windows session-based apps and desktops, which can be remotely shared with users. Users may access this via a web client on a compatible browser or a Remote Desktop client, which is available for Windows, macOS, iOS, and Android devices. Users must be connected to a network in order to access programs or desktops remotely.
Follow this link www.chipin.ae/blog for other IT tips and solutions from Chipin
