This error usually means the Remote Desktop Session Host cannot get a license from an RD Licensing server, or the licensing check is timing out.
Check these items in order:
- Verify the RD Licensing configuration on the RD Session Host
- Open Local Group Policy Editor:
gpedit.msc - Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing
- Open Use the specified Remote Desktop license servers
- Set it to Enabled
- Enter the license server name
- Open Set the Remote Desktop licensing mode
- Set it to Enabled
- Choose Per Device or Per User as appropriate
- Open Local Group Policy Editor:
- If using an RDS deployment, verify deployment settings in Server Manager
- Open Server Manager
- Go to Remote Desktop Services > Overview
- In Deployment Overview, select Tasks > Edit Deployment Properties
- Select RD Licensing
- Confirm the licensing mode and licensing servers are correct
- Check whether the licensing grace period has expired
- If the grace period has expired and no valid license server is configured, connections are denied.
- Typical related signs include messages such as:
- "The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license."
- "A licensing error occurred while the client was attempting to connect (Licensing timed out)."
- Check the license server and connectivity
- Make sure the Remote Desktop Licensing service is running on the license server.
- Make sure firewalls are not blocking required ports between the RD Session Host and the RD Licensing server.
- Check Event Viewer for licensing-related errors
- On the RD Session Host:
- Applications and Services Logs > Microsoft > Windows > RemoteApp and Desktop Connections
- Applications and Services Logs > Microsoft > Windows > TerminalServices-LocalSessionManager
- Applications and Services Logs > Microsoft > Windows > TerminalServices-RemoteSessionManager
- On the RD license server:
- Applications and Services Logs > Microsoft > Windows > TerminalServices-Licensing
- Relevant events include:
- Event ID 1088: licensing grace period expired and no license server registered
- Event ID 1010: could not locate a license server
- Event ID 1004: cannot issue a client license
- On the RD Session Host:
- If the issue is tied to license certificate corruption, refresh the X509 certificate registry keys
- Warning: registry changes are risky. Back up the registry first.
- This is relevant when errors include security-related disconnects or the RD License Diagnoser reports X.224 protocol stream errors.
If this is an Azure Windows VM and only temporary access is needed, one documented workaround is to connect with:
mstsc <File name>.RDP /admin
That disables licensing for just that connection.
- Cannot connect to RDS because no RD Licensing servers are available
- Cannot connect to RDS because no RD Licensing servers are available
- "Your session will be disconnected in 60 minutes" message when you connect to RDS
- Troubleshoot Remote desktop disconnected errors
- Remote Desktop license server isn't available when you connect to an Azure VM
- Troubleshooting specific RDP error messages to a Windows VM in Azure