How to install RDS license server 2022

Remote Desktop Services (RDS) sessions on Windows Server are time-limited without proper licensing. A compliant deployment typically requires 

(1) enabling the Remote Desktop Licensing role, 

(2) activating the license server, 

(3) installing RDS CALs (Client Access Licenses), and 

(4) configuring your RD Session Host (RDSH) to use the correct licensing mode and license server. This guide explains How to install RDS license server 2022 on Windows Server 2022 with practical, step-by-step instructions for IT pros.

What this covers: installing the Remote Desktop Licensing role service, activation (online/phone/web), installing RDS CALs (including a Windows Server 2022 Remote Desktop Services CAL (5 User CAL) example), configuring licensing mode (Per User or Per Device) and license server discovery (GPO/registry), verifying CAL issuance, and common errors such as grace period warnings and “cannot contact license server.”

Before you start (prerequisites for a compliant setup)

1) Confirm what you’re licensing (feature → benefit)

• RDS CALs (Per User / Per Device): grant the right for users or devices to access RDS. Benefit: keeps your RDS deployment compliant and avoids session denials after grace periods.
• RDS License Server: the server role that stores and issues RDS CALs. Benefit: central license management and reporting via Remote Desktop Licensing Manager.
• RD Session Host (RDSH): the server running user sessions. Benefit: provides remote desktop sessions while relying on the license server for CAL issuance.

2) Choose your licensing mode: Per User vs Per Device

• Per User: best when users connect from multiple devices (laptop + desktop + home PC). Benefit: fewer CALs in many “many devices per person” environments.
• Per Device: best for shared workstations (shift work, kiosks, call centers). Benefit: predictable licensing when many people share the same endpoints.

3) What you need on hand

• Windows Server 2022 with administrative access.
• Network connectivity for online activation (or access to phone/web activation if offline).
• Time synchronization (NTP) and correct system date/time. Licensing and certificates can fail with clock drift.

4) Placement guidance (single server vs dedicated license server)

• Small environments: the license server can be installed on the same machine as the RD Session Host.
• Medium/enterprise: consider a dedicated license server. Benefit: simpler role separation and centralized RDS CAL management.

Step 1 — Install the Remote Desktop Licensing role on Windows Server 2022

This is the core installation step for How to install RDS license server 2022. You can do it via Server Manager (recommended for most admins) or PowerShell.

Option A: Install via Server Manager (GUI)

1. Sign in to the server that will host RD Licensing.
2. Open Server Manager → Manage → Add Roles and Features.
3. Choose Role-based or feature-based installation → select your server.
4. In Server Roles, expand Remote Desktop Services and select Remote Desktop Licensing.
5. Continue through the wizard, accept required features if prompted, and click Install.
6. When complete, confirm the role service is installed (no reboot is usually required, but follow prompts if asked).

Option B: Install via PowerShell

1. Open Windows PowerShell as Administrator.
2. Run:

   Install-WindowsFeature -Name RDS-Licensing -IncludeManagementTools

3. Verify installation:

   Get-WindowsFeature RDS-Licensing

Post-install check: Remote Desktop Licensing Manager

Open Remote Desktop Licensing Manager (often shown as RD Licensing Manager):

• Server Manager → Tools → Remote Desktop Services → Remote Desktop Licensing Manager

You should see your license server listed (or you can add it).

Step 2 — Activate the RDS license server (Online, Phone, or Web)

Activation registers your license server so it can issue RDS CALs. Activation is not the same as installing CALs both steps are required.

Activate using Remote Desktop Licensing Manager

1. Open Remote Desktop Licensing Manager.
2. Right-click your server name → Activate Server.
3. Choose a connection method:
   • Automatic connection (recommended): uses the server’s internet connectivity.
   • Web Browser: use a separate machine with internet if the server is restricted.
   • Telephone: use phone activation if required by your environment.
4. Enter requested company information (use accurate administrative contact details).
5. Finish the wizard. When successful, the server status shows as activated.

Common activation pitfalls (and how to avoid them)

• Proxy/Firewall blocks: allow required outbound connectivity for activation, or use Web/Telephone method.
• Incorrect system time: fix NTP/time zone and retry.
• Limited admin rights: run the console elevated and ensure local admin permissions.

Step 3 — Install RDS CALs on Windows Server 2022

Once the license server is activated, install the CALs you legally own. Your entitlement details determine what you enter in the wizard (program type, agreement/authorization numbers, or license key/pack information depending on channel). This is where your Windows Server 2022 RDS license key or entitlement data (if applicable to your licensing program) may be used.

Install CALs using the Install Licenses wizard

1. Open Remote Desktop Licensing Manager.
2. Right-click the activated server → Install Licenses.
3. Select the appropriate License Program that matches how you purchased the CALs (choose carefully; mismatching program types is a common cause of failure).
4. Enter the required information for your program (for example, agreement/authorization identifiers or other entitlement details provided with purchase).
5. Select the license type and quantity:
   • RDS Per User CAL or RDS Per Device CAL
   • Example: Windows Server 2022 Remote Desktop Services CAL (5 User CAL) if that is what you purchased.
6. Complete the wizard and confirm the installed packs appear under the server in Licensing Manager.

Feature → benefit: installing CAL packs

• CAL packs visible in Licensing Manager: you can track type (Per User/Per Device), quantity, and issuance. Benefit: easier compliance reporting and renewal planning.
• Central storage of entitlement: CAL packs are associated with the license server. Benefit: RDSH servers can discover and use a shared license source.

Step 4 — Configure RD Session Host to use the license server and licensing mode

RDSH must be told which license server to use and which mode (Per User/Per Device). If you skip this, sessions may rely on discovery and may fail after grace period conditions.

Option A: Configure via Group Policy (recommended)

Use domain GPO for consistent, auditable configuration.

1. Open Group Policy Management on a domain controller or admin workstation.
2. Create or edit a GPO linked to the OU containing your RD Session Host servers.
3. Navigate to:

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

4. Enable Set the Remote Desktop licensing mode and choose:
   • Per User or Per Device (must match the CALs you installed)
5. Enable Use the specified Remote Desktop license servers and enter your license server FQDN (or multiple, one per line if you have more than one).
6. On each RDSH, run:

   gpupdate /force

Option B: Configure via local policy / registry (workgroup or small setups)

If you’re not using a domain, you can configure locally on the RDSH. The exact approach can vary by environment, but the goal is the same: set the licensing mode and specify the license server(s). For consistency and auditability, prefer GPO whenever possible.

Confirm the RDSH can reach the license server

• Check DNS resolution (FQDN resolves correctly).
• Verify network connectivity between RDSH and the license server.
• Ensure security policies/firewalls aren’t blocking required RDS licensing communication.

Step 5 — Verify CAL installation and issuance (Windows Server 2022, plus cross-version check for 2019)

Verification is part of compliance: you should be able to show the license server is activated, CALs are installed, and the RDSH is configured for the right mode.

Check in Remote Desktop Licensing Manager

• Expand your license server node and confirm the installed CAL packs are listed.
• Review pack details: version, type (Per User/Per Device), total and available.
• For Per Device CALs, you can typically see issued device licenses in the console.

How to check CAL License in Windows Server 2019 (cross-version verification)

If you are validating an older environment or migrating, the verification method is broadly similar in Windows Server 2019: use Remote Desktop Licensing Manager to confirm activation status and installed CAL packs, and confirm the RDSH licensing mode and specified license server settings. This can help ensure consistent configuration before/after a cross-version move to Windows Server 2022.

Optional: Use RD Licensing Diagnoser on the RD Session Host

1. On the RDSH, open Server Manager → Tools → Remote Desktop Services → RD Licensing Diagnoser.
2. Review whether the server reports:
   • Correct licensing mode
   • Discoverable/specified license server
   • Available CALs for the chosen mode

Troubleshooting (secondary): common RDS licensing issues

Use this section to resolve errors without changing the licensing intent of your deployment. Avoid “workarounds” that bypass licensing; instead, correct configuration and entitlement problems.

Issue: “Remote Desktop Session Host server is within its grace period”

• Cause: RDSH is running before licensing is fully configured.
• Fix: ensure the license server is activated, CALs are installed, and GPO sets both licensing mode and specified license server; then run gpupdate /force and re-check with RD Licensing Diagnoser.

Issue: “The remote session was disconnected because there are no Remote Desktop License Servers available” / cannot contact license server

• Cause: DNS/network/firewall issues, wrong server name in GPO, or license server not reachable.
• Fix:
  • Verify the license server FQDN in the GPO matches the actual server name.
  • Confirm name resolution and basic connectivity between RDSH and the license server.
  • Check that the Remote Desktop Licensing service is running on the license server.

Issue: Licensing mode mismatch (Per User vs Per Device)

• Cause: RDSH is configured for Per Device but only Per User CALs are installed (or vice versa).
• Fix: align the RDSH licensing mode to the CAL type you own, or install the correct CAL type if your requirements changed.

Issue: CALs installed but not issuing (especially Per User)

• Cause: configuration not applied to RDSH, license server discovery issues, or environment policy conflicts.
• Fix: confirm the GPO applies to the RDSH, re-run Diagnoser, and verify the specified license server list. Ensure the license server is activated and shows installed packs.

Decision and compliance checklist (what “done” looks like)

• Remote Desktop Licensing role installed on the intended Windows Server 2022 host.
• License server activated successfully (online/phone/web method recorded in admin notes).
• RDS CAL packs installed and visible in Remote Desktop Licensing Manager.
• RD Session Host configured for the correct licensing mode (Per User or Per Device).
• RD Session Host configured to use the specified license server(s) (preferably via GPO).
• RD Licensing Diagnoser shows no blocking licensing errors.
• Purchase and entitlement documentation stored for audit purposes.

If you’re planning a cross-version move (for example, checking a Windows Server 2019 setup before standardizing on 2022), use the same verification steps to confirm your licensing mode and CAL inventory are consistent with your intended deployment.