How to allow Windows Server 2019 Datacenter for RDP of more than two concurrent connections

Andrew Pine 0 Reputation points
2026-06-05T19:01:44.4133333+00:00

We have setup RDP server manager and license manager, but we still can only have two concurrent connections. I have adjusted the gpedit to allow 10, but no luck. I should have a grace period of 180 days for licenses, until I get mine purchased, but still no luck.

Thoughts?

Windows for business | Windows Server | User experience | Remote desktop clients
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-06-05T19:02:12.8333333+00:00

    On Windows Server 2019, more than two concurrent RDP connections require Remote Desktop Session Host (RDSH) plus a properly configured Remote Desktop Licensing server with valid RDS CALs. The two-connection limit is the default “Remote Desktop for Administration” mode; simply raising the connection limit in Group Policy does not bypass licensing.

    To allow more than two concurrent sessions during the grace period and after CALs are installed, verify these items:

    1. Verify the grace period and licensing configuration
    • Check the current grace period:
      • Command Prompt: 
            wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TerminalServiceSetting WHERE (__CLASS !="") CALL GetGracePeriodDays
      • Or PowerShell: 
            $obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
    $obj.GetGracePeriodDays()
    • Verify which license servers and licensing mode the RDSH sees: 
        $obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
  $obj.GetSpecifiedLicenseServerList()
  $obj.LicensingType
      If no license server or wrong mode is configured, the server may still enforce the two-session behavior.
    1. Configure the RD Session Host to use the RD Licensing server and mode

    If the deployment consists of only RD Session Host and RD Licensing roles, configure licensing via Group Policy (domain GPO or local policy on the server):

    1. Open gpedit.msc (or GPMC for a domain GPO) on the session host.
    2. Navigate to: Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Licensing.
    3. Configure the license server:
      • Open Use the specified Remote Desktop license servers.
      • Set to Enabled.
      • Enter the RD Licensing server name(s) in License servers to use.
    4. Configure the licensing mode:
      • Open Set the Remote Desktop licensing mode.
      • Set to Enabled.
      • Choose Per Device or Per User according to the intended CAL type.
    5. Apply the policy and run gpupdate /force, or restart the server.
    6. Ensure the licensing registry values are correct (if using direct registry configuration)

    On the RDSH, confirm the licensing mode and license server list in the registry:

    • Licensing mode (Per User = 4): 
        reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core" /v LicensingMode /t REG_DWORD /d 4
    • Specified license servers: 
        reg add "HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers" /v SpecifiedLicenseServers /t REG_MULTI_SZ /d "<FQDN / IP License server>"
    • Restart the server after changing these values.
    1. Verify connectivity between RDSH and RD Licensing server

    If the RD Session Host cannot contact the RD Licensing server, licensing will fail and connections can be blocked even during or after the grace period.

    • Test RPC port 135 connectivity from the RDSH to the license server: 
        telnet <FQDN / IP License Server> 135
    • Ensure required RDS ports are open on any firewalls between the RDSH and the licensing server.
    1. Confirm CALs and roles
    • Ensure the RD Licensing server is installed, activated, and has RDS CALs installed.
    • If the RD Session Host role was added only for testing and more than two concurrent users are not required, removing the RD Session Host role will revert to the default two administrative connections: 
        dism /ONLINE /Disable-feature /FeatureName:Remote-Desktop-Services
      (Use with caution; this removes the RDSH role.)

    If all of the above are correctly configured and the grace period is still active, the server should allow more than two concurrent RDS sessions. Once the grace period expires, valid RDS CALs on the licensing server are required.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Quinnie Quoc 11,835 Reputation points Independent Advisor
    2026-06-06T01:09:54.08+00:00

    Hello Andrew Pine,

    The reason you are limited to two concurrent RDP sessions is that by default Windows Server only allows two administrative connections. Even if you configure gpedit to allow more, that setting applies to Remote Desktop Services (RDS) sessions, not the built‑in admin connections. To support more than two users, you must install the Remote Desktop Session Host role and configure it under Remote Desktop Services. Once the Session Host role is active, the server will use the RDS licensing model, and you will indeed have a 180‑day grace period before client access licenses (CALs) are required.

    Without the Session Host role, the system will ignore your gpedit changes and enforce the two‑connection limit. Verify in Server Manager that the “Remote Desktop Services” role is installed and that the “RD Session Host” service is running. Only then will the licensing manager and grace period apply, allowing up to the number of users you configure. Until that role is installed, you are restricted to administrative use only.

    If my answer is useful for you, please hit Accept the answer to support me.

    Thank you,

    QQ.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.