How to Fix Remote Desktop Error: No Remote Desktop License Servers Available

Quick Answer

The Remote Desktop error "The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license" occurs when a Windows Server Remote Desktop Session Host (RD Session Host) cannot obtain a required Remote Desktop Services Client Access License (RDS CAL) from an available licensing server.

To resolve this issue, verify that the Remote Desktop Licensing role is installed and activated, appropriate RDS CALs are available, the correct licensing mode and license server are configured, and network communication between the Session Host and licensing server is working.

What Does This Error Mean?

Remote Desktop Services (RDS) allows multiple users to connect to a Windows Server and access hosted desktops or applications. In an RDS deployment, the RD Session Host must obtain the appropriate licensing through a Remote Desktop Licensing server.

When the Session Host cannot locate a suitable licensing server or obtain an appropriate license, users may be disconnected or prevented from establishing new remote sessions.

The error does not necessarily mean that the licensing server is physically offline. Incorrect configuration, unavailable CALs, incompatible license versions, Group Policy conflicts, and network communication failures can produce similar symptoms.

Common Causes

• RD Licensing role not installed: The environment does not have a properly configured Remote Desktop Licensing server.
• Licensing server not activated: The licensing server has been installed but has not been activated.
• Missing RDS CALs: The licensing server does not contain the required Client Access License packs.
• Incorrect licensing mode: The Session Host is configured for Per User or Per Device licensing incorrectly.
• Incorrect licensing server name: The Session Host points to an unavailable or incorrect server.
• Expired grace period: The applicable RDS licensing grace period has expired without a working licensing configuration.
• Network connectivity failure: DNS, firewall rules, routing, or network restrictions prevent communication with the licensing server.
• Licensing service problems: The Remote Desktop Licensing service is stopped or malfunctioning.
• CAL version incompatibility: The available CAL version is not suitable for the Session Host deployment.
• Group Policy conflict: Domain or local policies specify incorrect licensing settings.

How to Fix the Remote Desktop Licensing Error

1. Run Remote Desktop Licensing Diagnoser

Start with RD Licensing Diagnoser because it can identify licensing configuration problems on the affected Session Host.

1. Sign in to the affected Windows Server.
2. Open Server Manager.
3. Select Tools.
4. Navigate to Terminal Services > RD Licensing Diagnoser.
5. Review the reported licensing problems.
6. Check the configured licensing server and licensing mode.

Look for messages indicating that the licensing server is unavailable, the licensing mode is not configured, or the grace period has expired.

Use the diagnostic results to determine which troubleshooting procedure is relevant rather than changing multiple settings without identifying the problem.

2. Verify That the Remote Desktop Licensing Role Is Installed

The Remote Desktop Licensing role service must be installed on the server designated to provide RDS CALs.

1. Connect to the intended licensing server.
2. Open Server Manager.
3. Select Manage > Add Roles and Features.
4. Navigate to Server Roles.
5. Expand Remote Desktop Services.
6. Check whether Remote Desktop Licensing is installed.

If the role is missing, install it on an appropriate Windows Server and complete the licensing configuration.

Installing the role alone does not activate the server or install CALs.

3. Activate the Remote Desktop Licensing Server

An RD Licensing server must be activated before it can issue installed RDS CALs.

1. Open Server Manager on the licensing server.
2. Select Tools > Remote Desktop Services > Remote Desktop Licensing Manager.
3. Locate the licensing server.
4. Check its activation status.
5. If it is not activated, right-click the server name.
6. Select Activate Server.
7. Follow the activation wizard and complete the process using an available supported activation method.

After activation, verify that the server is displayed as activated in Remote Desktop Licensing Manager.

4. Check Whether RDS CALs Are Installed

Server activation does not automatically provide Remote Desktop Services CALs. The appropriate license packs must be installed separately.

1. Open Remote Desktop Licensing Manager.
2. Expand the licensing server.
3. Review the installed license packs.
4. Check the CAL type, version, and available quantity.
5. Verify that the CALs are appropriate for the Session Host version and deployment.

If the required CALs are missing, obtain the appropriate licenses through an authorized Microsoft licensing channel and install them using the licensing manager.

Do not purchase additional licenses until you have confirmed that missing or insufficient CALs are actually the problem.

5. Configure the Correct Licensing Mode

Remote Desktop Services supports two main licensing modes:

• Per User: Licensing is associated with individual users accessing the RDS environment.
• Per Device: Licensing is associated with devices connecting to the RDS environment.

The selected licensing mode must match the organization's licensing arrangement. Workgroup deployments require Per Device CALs.

Configure licensing through Server Manager

For deployments that use an RD Connection Broker:

1. Open Server Manager on the RD Connection Broker server.
2. Navigate to Remote Desktop Services > Overview.
3. Select Tasks > Edit Deployment Properties.
4. Open the RD Licensing section.
5. Select the appropriate licensing mode.
6. Specify the RD Licensing server.
7. Apply the configuration.

Configure licensing through Group Policy

For Session Host deployments without an RD Connection Broker, configure the licensing settings through Group Policy.

1. Sign in to the affected RD Session Host using an administrator account.
2. Press Windows + R.
3. Run the following command:

gpedit.msc

Navigate to:

Computer Configuration
> Administrative Templates
> Windows Components
> Remote Desktop Services
> Remote Desktop Session Host
> Licensing

Configure the following policies:

Use the specified Remote Desktop license servers

1. Open the policy.
2. Select Enabled.
3. Enter the hostname or fully qualified domain name (FQDN) of the licensing server.
4. Apply the setting.

Set the Remote Desktop licensing mode

1. Open the policy.
2. Select Enabled.
3. Choose Per User or Per Device, as appropriate.
4. Apply the setting.

If multiple licensing servers are configured, enter their names separated by commas.

Note: Domain Group Policy can override local Group Policy. Check the effective policy if your local changes do not take effect.

6. Check the Remote Desktop Licensing Service

The licensing service must be running on the licensing server.

1. Connect to the licensing server.
2. Press Windows + R.
3. Run:

services.msc

1. Locate Remote Desktop Licensing.
2. Check its current status.
3. If stopped, investigate the service and related event logs.
4. If appropriate, start the service.

If the service fails to start, review the error message and Windows event logs to identify the underlying problem.

7. Verify Network Connectivity to the Licensing Server

The RD Session Host must be able to locate and communicate with the licensing server.

Check the following:

• Both servers are powered on and connected to the expected network.
• The licensing server hostname resolves correctly through DNS.
• The Remote Desktop Licensing service is running.
• Windows Firewall and network firewalls permit the required communication.
• Network routing and security policies do not block the connection.

Microsoft documents Windows Server network requirements in its Service overview and network port requirements.

Do not disable the firewall completely to troubleshoot this problem. Identify the required traffic and configure narrowly scoped firewall rules where necessary.

8. Check Applied Group Policy Settings

A domain policy may override the local licensing configuration.

On the affected Session Host, open Command Prompt as an administrator and run:

gpresult /h "%USERPROFILE%\Desktop\RDS-GroupPolicy.html"

This command creates an HTML report showing the applied Group Policy settings.

1. Open the generated report.
2. Review the Remote Desktop Services policies.
3. Check the specified licensing server.
4. Check the selected licensing mode.
5. Identify whether a domain policy is overriding the intended configuration.

If an incorrect domain policy is responsible, ask the domain administrator to update the relevant Group Policy Object.

9. Verify RDS CAL Version Compatibility

The CAL version must be compatible with the RD Session Host version. The licensing server must also support the installed CAL version.

For example, a Windows Server 2016 licensing server cannot issue Windows Server 2019 RDS CALs.

Check the Windows Server version on the Session Host and licensing server, along with the version of the installed CAL packs.

Refer to Microsoft's Remote Desktop licensing troubleshooting documentation for the applicable compatibility information.

10. Review Remote Desktop Licensing Event Logs

Event Viewer can provide additional information when the licensing service is unavailable or cannot issue a license.

1. Open Event Viewer on the licensing server.
2. Navigate to:

Applications and Services Logs
> Microsoft
> Windows
> TerminalServices-Licensing
> Operational

1. Review recent errors and warnings.
2. Note the event IDs, timestamps, and descriptions.
3. Compare the events with the time when the Remote Desktop connection failed.

Also inspect the System log for relevant service, DNS, network, or security errors.

11. Investigate Workgroup Licensing Authentication

Workgroup-based RDS deployments can have additional authentication requirements when the Session Host communicates with a separate licensing server.

Microsoft documents additional requirements following the security update associated with CVE-2024-38099. In applicable workgroup environments, the RD Session Host's Network Service account must have access to the credentials required for licensing server communication.

Review Microsoft's instructions before changing authentication settings:

License Remote Desktop session hosts.

Do not apply workgroup-specific configuration changes to domain-joined deployments without confirming that they are relevant.

Advanced Troubleshooting: Refresh Remote Desktop Licensing Certificate Information

In some cases, RD Licensing Diagnoser may report certificate-related problems, including an X.224 protocol error. These problems can involve corrupted or inconsistent licensing certificate information on the RD Session Host.

The affected registry location is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM

Microsoft documents a procedure involving the following certificate-related values:

• Certificate
• X509 Certificate
• X509 Certificate ID
• X509 Certificate2

Only perform the documented refresh procedure when diagnostic evidence indicates a certificate-related licensing problem.

For the exact procedure and recovery requirements, consult Microsoft's RDS licensing troubleshooting guidance.

How to Verify That the Problem Is Resolved

After correcting the licensing configuration, perform these checks:

• Remote Desktop Licensing Manager shows the licensing server as activated.
• The appropriate RDS CAL packs are installed.
• The RD Session Host references the correct licensing server.
• The licensing mode matches the organization's CAL arrangement.
• RD Licensing Diagnoser no longer reports the original licensing problem.
• The Remote Desktop Licensing service is running.
• Network communication between the Session Host and licensing server is working.
• Users can establish new Remote Desktop sessions successfully.

If the problem continues, collect the latest RD Licensing Diagnoser output and relevant Event Viewer messages before making further changes.

Important Remote Desktop Licensing Considerations

Administrative Remote Desktop Connections Are Different from RDS Sessions

Windows Server provides a limited administrative remote access facility for server management. Under applicable licensing terms, up to two simultaneous remote administrative connections are supported without RDS CALs for those administrative connections.

This administrative facility is not a substitute for properly licensing a multi-user RD Session Host deployment.

Do Not Reset the Licensing Grace Period as a Permanent Fix

Resetting the licensing grace period does not install valid CALs or repair an unavailable licensing server. Configure the proper licensing infrastructure instead of relying on grace-period resets.

Do Not Reinstall Remote Desktop Services Before Diagnosing the Problem

Removing and reinstalling RDS roles does not automatically activate a licensing server, install CALs, or correct network and Group Policy problems. Diagnose the specific licensing failure before considering disruptive changes.

Frequently Asked Questions

Why does Remote Desktop say no license servers are available?

The RD Session Host cannot obtain a required RDS CAL from a suitable licensing server. This may be caused by missing licensing configuration, an inactive server, unavailable CALs, network problems, or an expired grace period.

How do I check whether my Remote Desktop Licensing server is working?

Open Remote Desktop Licensing Manager and check the activation status and installed CAL packs. Run RD Licensing Diagnoser on the Session Host to identify configuration and communication problems.

What is the difference between Per User and Per Device RDS CALs?

Per User CALs are assigned to users, whereas Per Device CALs are assigned to devices. The licensing mode must match the applicable licensing arrangement and deployment requirements.

Can I use Remote Desktop without RDS CALs?

Windows Server supports limited administrative remote access for server management under applicable licensing terms. Multi-user RD Session Host deployments require appropriate RDS licensing.

Does restarting the Remote Desktop Licensing service fix the problem?

It may help if the licensing service has stopped or become temporarily unresponsive. It will not resolve missing CALs, incorrect licensing modes, incompatible licenses, or Group Policy conflicts.

How long is the Remote Desktop licensing grace period?

Microsoft documents a 120-day grace period for an RD Session Host. Once it expires, the Session Host requires a valid licensing configuration and appropriate RDS CALs.

Can Group Policy cause the Remote Desktop licensing error?

Yes. Local or domain Group Policy can specify an incorrect licensing server or licensing mode. Use Group Policy Results to identify which policies are actually applied.

Will reinstalling Remote Desktop Services fix the licensing error?

Not necessarily. Reinstallation does not automatically provide valid CALs or repair an unavailable licensing server. Identify the cause using RD Licensing Diagnoser before considering role reinstallation.

Sources

• Microsoft Learn – Cannot connect to RDS because no RD Licensing servers are available
• Microsoft Learn – License Remote Desktop session hosts
• Microsoft Learn – Remote Desktop licensing mode is not configured warning
• Microsoft Learn – Guidance for troubleshooting RDS Licensing
• Microsoft Learn – Service overview and network port requirements for Windows