How to Install and Activate RDS CALs on Windows Server (Step by Step)

How do you install RDS CALs?

Install the Remote Desktop Licensing role, activate the license server in Remote Desktop Licensing Manager, then use Install Licenses to add your RDS CALs with the license code or agreement number. Finally, point your session hosts at the license server and set the licensing mode to Per User or Per Device, either in the deployment properties or with Group Policy.

Before you start

The whole job has four phases. Here is where each one happens and what you need for it.

Phase	Where you do it	What you need
Install the licensing role	Server Manager > Add Roles and Features	Admin account
Activate the license server	Remote Desktop Licensing Manager	Company information; internet or another computer with internet
Install the RDS CALs	Remote Desktop Licensing Manager > Install licenses	License code or agreement number
License the session hosts	Deployment properties, or Group Policy	License server name and licensing mode

Source: Activate the Remote Desktop Services license server, Install Remote Desktop Services client access licenses and License Remote Desktop session hosts.

Have these ready before you begin:

• Administrative rights on the server, which Microsoft lists as a prerequisite for activating the license server.
• Your company information, which the activation wizard asks for.
• Internet access on the computer running Remote Desktop Licensing Manager. The license server itself doesn’t require internet connectivity.
• The license code or agreement number provided when you purchased your RDS CALs. For RDS CALs from us, follow the instructions in your delivery email.

If the server you are using is still running a Windows Server 2025 evaluation, our guide to converting Windows Server 2025 evaluation to the full version covers moving it to a full edition.

Step-by-step: install and activate RDS CALs

Step 1: Install the Remote Desktop Licensing role

Add the Remote Desktop Licensing role in Server Manager, including the Remote Desktop Licensing Tools feature. Here are Microsoft’s steps:

1. Sign in to the server as an administrator.
2. In Server Manager, select Manage > Add Roles and Features.
3. Select Role-based or feature-based installation, then choose the server.
4. Check Remote Desktop Services, then select Next until you reach the Remote Desktop Services page.
5. Select the roles you want, including Remote Desktop Licensing, then select Add Features.
6. Select Next until you reach the Confirmation page, then select Install.

Step 2: Activate the license server

Open Remote Desktop Licensing Manager and activate the server with an online method. Microsoft’s activation steps are:

1. In Server Manager, select Tools > Remote Desktop Services > Remote Desktop Licensing Manager.
2. Select the server, then select Action > Activate Server.
3. Confirm the connection method, then select Next.

Choose one of these two connection methods:

• Automatic connection (recommended): this method communicates via the internet directly to the Microsoft Clearinghouse, outbound over TCP port 443. Enter your company information (first name, family name, company, and country or region), select Next, add any optional information, and select Next to the end. Clear Start Install Licenses Wizard now, select Finish, then use Action > Install Licenses when you’re ready for Step 3.
• Web Browser: use this method if the license server doesn’t have internet access, but you have internet access through another computer. Copy the URL for the Remote Desktop Licensing Web Site, complete the steps on that site from the other computer, then return and enter the license server ID.

Step 3: Install the RDS CALs

In Remote Desktop Licensing Manager, run Install licenses and enter your license code or agreement number. Follow Microsoft’s steps:

1. Open Remote Desktop Licensing Manager.
2. Right-click the license server, then select Install licenses.
3. Select Next on the welcome page.
4. Select the program you purchased your RDS CALs from, then select Next.
5. Enter the license program information, which in most cases is the license code or an agreement number, then select Next.
6. Select the product version, license type and number of licenses, then select Next.
7. Select Finish.

At step 6, the license manager contacts the Microsoft Clearinghouse to validate and retrieve your licenses. For RDS CALs bought from us, follow the instructions in your delivery email at step 4 and contact support if you are unsure.

Step 4: Set the licensing mode and license server

On the RD Connection Broker computer, open the deployment properties, choose Per User or Per Device, and add your license server. Microsoft’s steps are:

1. Open Server Manager > Remote Desktop Services > Overview.
2. Select Edit Deployment Properties, then RD Licensing.
3. Select Per User or Per Device.
4. Specify a license server, then select Add.

This step needs a license server with Per User or Per Device CALs already activated, which is why it comes after Step 3.

Step 5: Use Group Policy if you do not have a Connection Broker

If your deployment has only the RD Session Host and RD Licensing roles, set the license server and licensing mode with Group Policy instead. Use the Group Policy Management Console for the domain, or the Local Group Policy Editor on the session host, and go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing. Then:

1. Enable Use the specified Remote Desktop license servers and enter the license server name. Separate several names with commas.
2. Enable Set the Remote Desktop licensing mode and select Per Device or Per User.

Step 6: Check workgroup setups

If your session hosts are in a workgroup rather than a domain, use Per Device CALs. Domain-joined deployments can use both Per User and Per Device CALs, while workgroup deployments have to use Per Device CALs.

Since a security update, RD licensing servers require session hosts in a workgroup to present credentials, and Microsoft documents the extra credential step on its session host licensing page.

Want a hand with it? Contact support and we’ll fix it: support@solveditservices.com or use our contact page.

Which RDS CALs work with your Windows Server version

Version matters at two points: the session host and the license server.

• Session hosts: later RDS CALs can access earlier versions of Windows Server, but earlier RDS CALs can’t access later versions. For example, Windows Server 2022 RDS CALs connect to session hosts running Windows Server 2022 or earlier, but not to a session host running Windows Server 2025.
• License server: you can install RDS CALs on a license server running the same version of Windows Server as the RDS CALs or later.

In practice, Windows Server 2019 RDS CALs serve session hosts running Windows Server 2019 or earlier, and they install on a license server running Windows Server 2019 or later.

We carry Microsoft Windows Server 2022 Remote Desktop 5 User CALs and Microsoft Windows Server 2019 Remote Desktop 5 User CALs. For Windows Server 2025 session hosts, or for Device CALs, request a quote and we’ll put the right RDS CALs together for you. If you’re still choosing the server version itself, our Windows Server 2025 vs 2022 comparison may help.

Per User or Per Device?

Each user and device that connects to a Remote Desktop Services session host needs an RDS CAL, and the licensing mode you set in Step 4 or Step 5 decides which way you count. In a domain you can choose either. In a workgroup, the Step 6 rule applies and the answer is Per Device.

Our Remote Desktop Services (RDS) CALs explained post goes into how to choose.

The 120-day grace period

You don’t have to finish everything on day one. There’s a licensing grace period of 120 days during which no license server is required.

Once the grace period ends, clients need a valid RDS CAL issued by a license server before they can sign in to a remote session. Plan to finish Steps 1 to 6 well inside that window.

You also need Windows Server CALs

RDS CALs sit on top of your Windows Server CALs, not in place of them. Additive CALs must be licensed in addition to the corresponding Base CALs, and the RDS CAL is required in addition to the Base CAL for every user or device that uses Remote Desktop Services.

For the Base CALs, we carry Microsoft Windows Server 2025 – 1 User Client Access License (CAL) and Microsoft Windows Server 2022 – 1 Client User CAL. Our guide to Windows Server CALs: User CAL vs Device CAL helps you pick the type. If your session hosts run Datacenter, our guide to whether you need CALs for Windows Server Datacenter covers how CALs work there.

Where to get it

• RDS CALs for session hosts on Windows Server 2022 or earlier: Microsoft Windows Server 2022 Remote Desktop 5 User CALs.
• RDS CALs for session hosts on Windows Server 2019 or earlier: Microsoft Windows Server 2019 Remote Desktop 5 User CALs.
• Windows Server Base CALs: Microsoft Windows Server 2025 – 1 User Client Access License (CAL) or Microsoft Windows Server 2022 – 1 Client User CAL.
• Windows Server 2025 RDS CALs and Device CALs: ask us through Request a quote.

You’ll find them in our Windows Server category, linked in the steps below.

Why buy from Solved IT Services

• Solved IT Services is a Microsoft Solutions Partner and certified reseller.
• We have more than 12 years in the software licensing business.
• We have many industry relationships.
• We’re a US-based company with US-based support, and we offer 24/7 support. Contact support and we’ll fix it: support@solveditservices.com or use our contact page.
• We offer estimated delivery within 30 minutes or less from the time of purchase.
• SIS Guarantee: We guarantee full installation and full activation of every product we sell, or your money back.
• Customers share their experience with us on Trustpilot and BBB.

What to do next

1. Check your session host version and whether your servers are domain-joined or in a workgroup.
2. Work through Steps 1 to 6 above, in order.
3. For several servers, Windows Server 2025 RDS CALs or a business setup, request a quote.
4. Contact support and we’ll fix it: support@solveditservices.com or use our contact page.
5. Browse our Windows Server category, or contact our support team if you want help choosing.

Frequently asked questions

Does the RDS license server need internet access?

No. The license server itself doesn’t require internet connectivity, but the computer running Remote Desktop Licensing Manager needs it to activate the licenses. If the license server has no internet, the Web Browser method lets you activate through another computer.

Which activation method should I use?

Microsoft marks Automatic connection as the recommended method, which connects outbound over TCP port 443. If the license server has no internet access but another computer does, use the Web Browser method instead.

Can I use Windows Server 2022 RDS CALs on Windows Server 2025?

No. Windows Server 2022 RDS CALs connect to session hosts running Windows Server 2022 or earlier, but not Windows Server 2025. For a Windows Server 2025 session host, request a quote and we’ll put the right RDS CALs together for you.

What happens before RDS CALs are installed?

There’s a licensing grace period of 120 days during which no license server is required. After that, clients need a valid RDS CAL issued by a license server before they can sign in to a remote session.

Can I use Per User CALs in a workgroup?

No. Workgroup deployments have to use Per Device CALs, while domain-joined deployments can use either type. Workgroup session hosts also need an extra credential step, covered on the same Microsoft page.

Do I still need Windows Server CALs with RDS CALs?

Yes. RDS CALs are required in addition to the Windows Server Base CAL for every user or device using Remote Desktop Services. Plan for both when you place your order.

Where do I find the license code?

Microsoft says it’s the license code or agreement number provided when you purchased your RDS CALs. For RDS CALs from us, it comes in your delivery email, and we offer estimated delivery within 30 minutes or less from the time of purchase.