Skip to main content
“The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license” appears when the Remote Desktop Session Host role is installed and its 120-day licensing grace period has ended without a licence server and RDS CALs. If you only need remote administration, remove the Remote Desktop Services role. If several users need sessions, install an RD licence server with RDS CALs and point the server at it.

​
Before you start

  • You need to sign in to remove or configure the role. Try an administrative session first: mstsc /v:203.0.113.10 /admin. If that is refused too, use the VNC console on a VPS, or open a ticket on a dedicated server.
  • Take a snapshot or backup before you remove server roles.
You may also see these related messages:

​
What the grace period is and what you are allowed without RDS

Microsoft documents two different ways to use Remote Desktop on Windows Server: An RDS CAL (client access licence) is the licence that lets one user or one device connect to an RD Session Host. Microsoft states: “There’s a licensing grace period of 120 days during which no license server is required. Once the grace period ends, clients must have a valid RDS CAL issued by a license server before they can sign in a remote session.”
Don’t use registry edits or scripts that “reset” the grace period. They circumvent Microsoft licensing and are not a fix. Remove the role or license it properly.

​
Cause 1: the RD Session Host role was installed but isn’t needed (most likely)

This happens when someone added Remote Desktop Services while trying to enable RDP or to allow more than two sessions. Check: in PowerShell as Administrator:
If Remote Desktop Session Host (RDS-RD-Server) is listed and you don’t run a multi-user server, this is the cause. Fix: remove the role.
1

Open the removal wizard

In Server Manager, click Manage > Remove Roles and Features, then Next until you reach Server Roles.
2

Remove Remote Desktop Services

Clear Remote Desktop Services (or only the role services you don’t need, such as Remote Desktop Session Host, Remote Desktop Licensing and Remote Desktop Connection Broker). Click Next, then Remove.
3

Restart

Restart the server when the wizard asks.
Microsoft also documents the command-line equivalent, run in an elevated Command Prompt:
After the restart, Remote Desktop works as before for administration, with two concurrent connections. Make sure Remote Desktop is still enabled in Server Manager > Local Server.

​
Cause 2: you need RDS, but licensing isn’t set up

If several people work on the server at once, you need the RD Session Host role, an activated RD licence server and enough RDS CALs. Check: in Server Manager, open the Tools menu and start RD Licensing Diagnoser. It lists the licensing mode, the licence servers it found and the problem. Fix:
1

Get RDS CALs that match your server version

A session host accepts CALs of its own version or newer. For example, Windows Server 2022 accepts 2022 and 2025 RDS CALs, and Windows Server 2025 accepts only 2025 RDS CALs. On a workgroup server (not in a domain) use Per Device CALs; Per User CALs need Active Directory.
2

Install and activate the licence server

Install the Remote Desktop Licensing role service, activate the licence server in Remote Desktop Licensing Manager and install your CALs. The licence server must run the same Windows Server version as the CALs or newer. Follow Activate the RDS license server.
3

Point the session host at the licence server

On the session host, run gpedit.msc and go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing. Enable Use the specified Remote Desktop license servers and enter the licence server name. Enable Set the Remote Desktop licensing mode and choose Per Device or Per User to match your CALs.
4

Apply and test

Run gpupdate /force, then run RD Licensing Diagnoser again. It should show no problems.

​
How to check it worked

Connect with Remote Desktop as normal (without /admin). The licensing message no longer appears. If you removed the role, Get-WindowsFeature -Name RDS-RD-Server shows it as not installed.

​
Frequently asked questions

​
Does Windows Server include RDS CALs?

RDS CALs are separate licences from the Windows Server licence itself. Two concurrent administrative connections don’t need them. Check your current licence with Windows Server activation and licensing.

​
Can I get more than two sessions without RDS?

No. More than two concurrent sessions need the RD Session Host role and RDS CALs.

​
What does mstsc /admin do?

It opens an administrative session to the server. Use it to sign in and fix licensing, not as a way to avoid licensing.

VPS and dedicated server guides

Every guide in this section.

Roles and features

Add and remove server roles.

Activation and licensing

Check your Windows Server licence.

Add a Remote Desktop user

Give another account RDP access.

Remote Desktop can't connect

Other RDP connection problems.
Checked against Microsoft Learn: License RDS with client access licenses, No RD Licensing servers available and Remote Desktop license server isn’t available on 4 November 2026. Steps were not tested on a live Windows server for this page. Licensing terms are Microsoft’s; check your licence agreement for your situation.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to upgrade your hosting? Use code KB20 at checkout for 20% off your first order!
Last Updated: November 2026