Skip to content
CRA Audio ID Now Live Learn More

Windows Server 2019 Remote Desktop Services License Free

If you installed the RDS Session Host role and you are getting errors saying "The remote session was disconnected because there are no Remote Desktop client access licenses available," you have likely exceeded the grace period or the server cannot find a licensing server.

If you are within the 120-day grace period but still get errors: This often happens if the RDS Licensing Role Service is installed but no CALs are added. For the grace period to function correctly, sometimes it is best to remove the "Remote Desktop Licensing" role service from the server if you are only testing.

To remove the licensing role:

There is no legitimate “license-free” path to full Remote Desktop Services on Windows Server 2019. For multi-user Remote Desktop functionality, purchase and deploy RDS CALs and a licensed Windows Server, or use supported alternatives (Azure Virtual Desktop, Windows 365, or third-party remote access products) depending on scale, budget, and feature needs.

If you want, I can:

The most accurate feature to highlight regarding "free" Remote Desktop Services (RDS) on Windows Server 2019 is the 180-Day Grace Period.

Here are the specific details of this feature:

Feature: 180-Day Evaluation Grace Period


Important Clarification on "Free" usage: While the grace period is free, the permanent feature of Windows Server 2019 that allows free remote access is strictly limited to Remote Administration. windows server 2019 remote desktop services license free

While there is no permanent "free" license for Windows Server 2019 Remote Desktop Services (RDS), there are legitimate ways to use the service without immediate cost for specific durations or use cases. 1. 120-Day Licensing Grace Period

When you first install the RDS role on Windows Server 2019, Microsoft provides a 120-day grace period.

Functionality: During this time, an unlimited number of concurrent users can connect to the server without needing a Client Access License (RDS CAL).

Purpose: This period is intended for organizations to configure and test their RDS environment before purchasing permanent licenses.

Post-Grace Period: Once the 120 days expire, users will be blocked from connecting until a valid license server is configured and CALs are installed. 2. Free Administrative Connections

Windows Server includes a built-in allowance for administrative tasks that does not require additional RDS licenses.

Limit: Up to two concurrent connections are allowed for server management.

Requirement: These sessions are only for administrative purposes. If you plan to use the server as a primary workstation for multiple users, you must purchase RDS CALs. 3. Trial and Evaluation Versions If you installed the RDS Session Host role

You can download a Windows Server 2019 Evaluation version from the Microsoft Evaluation Center.

Duration: The OS itself runs for 180 days before requiring activation.

RDS Compatibility: You can still enable the 120-day RDS grace period within this 180-day OS evaluation window to test remote desktop features. Summary of Options Concurrent Users Administrative Mode Server maintenance RDS Grace Period Unlimited* Short-term projects/testing Evaluation OS Unlimited* Full OS and RDS feature testing *Note: Hardware capacity may limit actual user numbers. How To Reset 120 Day Grace Period on Windows Server RDS

While there is no permanent "free" version of Windows Server 2019 Remote Desktop Services (RDS), there are ways to access it without immediate payment for testing or administrative purposes. 1. The 120-Day Licensing Grace Period

When you first install the Remote Desktop Services role on Windows Server 2019, Microsoft provides a 120-day grace period Functionality

: During this window, the server operates with full RDS functionality without requiring a license server or Client Access Licenses (CALs). Connection Limits

: There is effectively no limit on simultaneous connections during this period, provided your hardware can support the load.

: This is intended for organizations to configure and test their environment before committing to a purchase. 2. Built-in Administrative Connections (Always Free) The most accurate feature to highlight regarding "free"

If you only need remote access for server management rather than hosting multiple users, you do not need RDS CALs at all. : Windows Server 2019 allows up to two concurrent remote connections specifically for administrative purposes. How to use

: Simply enable Remote Desktop in the System settings without installing the "Remote Desktop Services" role. 3. Testing and Lab Environments (Grace Period Reset)

For non-production lab environments, some administrators use a registry "hack" to reset the 120-day clock. Note that this is not supported for production : Create a snapshot or backup of your server. Registry Edit : Navigate to

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod Take Ownership : You must change the owner of the GracePeriod key to "Administrators" to gain delete permissions. Delete Key

: Remove the "Timebomb" registry entry and reboot the server to reset the 120-day counter. 4. Transitioning to Paid Licensing

Once the grace period ends, you must install and activate a license server to continue using RDS. Reset 120 day RDS Grace period on 2016 and 2019


There is no "free version" of RDS for standard users. However, there are two specific scenarios where you do not need to purchase RDS Client Access Licenses (RDS CALs):


When you first install the Remote Desktop Session Host (RDSH) role, the server enters an unlicensed mode. In this mode, it allows unlimited concurrent connections for exactly 120 days. This grace period is designed for testing, proof-of-concept, and application compatibility checks.

You can reset this grace period exactly one time using the winrm command or the WMI ResetGracePeriodLD method. After that, the server demands valid licenses.

After Day 120: The server will stop accepting new connections. Existing sessions may be blocked, and users will see an error: “The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer.”