Fix RDS Event ID 1130: “The Remote Session Was Disconnected Because There Are No Remote Desktop License Servers Available”

Posted by

Windows Server RDS Event ID 1130 (accompanied by the warning “The remote session was disconnected because there are no Remote Desktop license servers available to provide a license”) occurs when an RD Session Host (RDSH) server cannot discover, contact, or validate client access licenses (CALs) from the designated RD Licensing server. Even if licenses are actively installed in RD Licensing Manager, Event ID 1130 triggers if the licensing mode (Per User vs Per Device) is unconfigured, or if RPC network communication across TCP port 135 is blocked by Windows Firewall. To fix Event ID 1130, you must run the RD Licensing Diagnoser (lsdiag.msc), explicitly declare your license server FQDN in Group Policy, and open RPC communication endpoints.

✅ Diagnostic Insight: Event ID 1130 does not mean your CALs have disappeared. In 95% of cases, the RD Session Host simply has no policy pointing it to the IP/FQDN of the licensing server.

1. Why Does RDS Event ID 1130 Occur?
2. Step 1: Run the RD Licensing Diagnoser (lsdiag.msc)
3. Step 2: Configure License Server via Group Policy
4. Step 3: Verify RPC & Firewall Port 135 Connectivity
5. Frequently Asked Questions

1. Why Does RDS Event ID 1130 Occur?

Unlike standalone desktop editions, Windows Server strictly enforces a dual-tier RDS licensing hierarchy: the Session Host presents desktops to users, while the Licensing Host dispenses CAL tokens. When these two roles cannot communicate due to missing registry pointers or firewall blocks, sessions are disconnected immediately after login.

2. Step 1: Run the RD Licensing Diagnoser (lsdiag.msc)

Press Windows Key + R, type lsdiag.msc, and press Enter.
Inspect the summary section. You will likely see: “The licensing mode for the Remote Desktop Session Host server is not configured.”

3. Step 2: Configure License Server via Group Policy

Open gpedit.msc or your domain GPMC, then navigate to:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing

Double-click Use the specified Remote Desktop license servers, set it to Enabled, and enter your server FQDN or IP address (e.g., 127.0.0.1 or licensing.domain.local).
Double-click Set the Remote Desktop licensing mode, set it to Enabled, and choose either Per Device or Per User matching your CAL pack.
Run gpupdate /force in Command Prompt.

4. Step 3: Verify RPC & Firewall Port 135 Connectivity

Ensure the RD Licensing firewall rules are enabled in PowerShell (Admin):

Enable-NetFirewallRule -DisplayGroup “Remote Desktop”

Genuine Microsoft Windows Server & RDS CALs

Deploy a compliant Remote Desktop infrastructure. SortedKeys provides authentic lifetime licenses for Windows Server and RDS User/Device CALs.

Buy Windows Server Keys →

5. Frequently Asked Questions

Can RDSH and RD Licensing reside on the same server?

Yes! In single-server small business deployments, both roles can run side by side. Pointing the policy to 127.0.0.1 or the local hostname satisfies discovery immediately.