Activating Windows Server 2019 RDS 10 User CAL

Name: Microsoft Windows Server 2019 RDS 10 User CAL
Brand: Microsoft
Availability: InStock

RDS CAL per user licences in Windows Server 2019 are required when specific users use the remote desktop services, regardless of the number of devices they connect from. The Per User model is particularly suitable for companies where one employee uses a desktop computer, laptop, and sometimes also a mobile device. In practice, this means that after installing the remote desktop services role, you still need to activate the licence server and add the appropriate CAL package, for example 10 User CAL.

Below, you will find a simple instruction prepared for the Windows Server 2019 environment, with a focus on the RDS CAL per user variant.

Step by Step

1. Check if the RDS licensing role is installed

On the server, open Server Manager, then go to Add Roles and Features. Make sure the Remote Desktop Licensing role is installed. If it's not, add it and complete the installation according to the wizard. After installation, a restart or service restart is usually required.

2. Run the Remote Desktop Licensing Manager

Go to:

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

The local license server should be visible in the console. If you see an information icon next to the server name indicating that it's not activated, you need to perform the next step.

3. Activate the license server

Right-click the server name and select Activate Server.

The activation wizard will start. The most commonly chosen method is Automatic connection, as the server connects directly to the Microsoft activation service. If the server doesn't have internet access, you can use the web browser or phone option, but in most cases, automatic activation is the fastest.

In the wizard, fill in your company's basic information, such as organization name and country. After completing the activation, you can immediately proceed to install the license package.

4. Install the 10 User CAL package

If you're prompted to install licenses after activation, select Start Install Licenses Wizard now. If not, right-click the server and select Install Licenses.

In the wizard, you need to specify the licensing program according to how the license was purchased. This is a crucial step, as selecting the wrong program type may prevent you from adding CAL correctly.

Next, enter the details you received when purchasing the license, such as the agreement number, authorization, or license key, depending on the license type. After correct confirmation, the Windows Server 2019 - 10 RDS User CAL package should appear on the server.

5. Set the licensing mode to Per User

Adding the license is not enough. The RDS session server must still know which mode to use.

This is usually set in one of two methods:

through Group Policy
through RDS deployment settings

In Group Policy, go to:

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

Enable the Set the Remote Desktop licensing mode setting and select Per User.

Then, enable Use the specified Remote Desktop license servers and enter the license server name, for example, SERVER01.

After saving the changes, run the command:

gpupdate /force

It's also a good practice to restart the service or the entire server if the configuration was previously inconsistent.

6. Verify the license server assignment

On the Session Host server, open RD Licensing Diagnoser. The tool will show if the session host sees the license server and if the Per User mode is set correctly. If everything is configured correctly, warning messages should disappear.

If you need help or have questions, please contact us at [email protected] or call 00 800 121 1654.

Verification

After completing the activation, it is worth confirming three things.

Firstly, in the Remote Desktop Licensing Manager, the server should have an activated status. Secondly, on the list of installed packages, the 10 User CAL package should be visible for the relevant system version. Thirdly, the RD Licensing Diagnoser should not report any errors related to the lack of a license server or inconsistent licensing mode.

In the Per User model, the system does not always maintain such strict, technical counting as in Per Device, so the administrator should also take care of formal compliance. In other words: if a company has purchased 10 user licenses, a maximum of 10 authorized persons should use the RDS services.

Problems

The most common problem is setting the wrong licensing mode. If User CAL is installed on the server and the Session Host operates in Per Device mode, warnings and irregularities will appear in the diagnostics.

The second common error is the lack of a license server specification in the group policies. Even an activated server with a correctly added CAL package will not be used if the session host does not know where to look for it.

Choosing the wrong licensing program in the license installation wizard can also be a problem. In such a situation, the system may reject the activation data. It is then worth checking the purchase document and ensuring that the correct type of license was delivered.

If the server does not have access to the internet, automatic activation may not be successful. In such a case, you should use browser or phone activation. The lack of internet access does not block deployment, but it requires a different activation path.

If you need help with activation or verifying the correctness of licenses, please contact us: [email protected] or call 00 800 121 1654.

FAQ

Does 10 User CAL mean 10 computers?

No. 10 User CAL means 10 users. Each of them can use several devices, provided that the licensing is set to Per User mode.

Do I need to activate the license server and add CAL separately?

Yes. First, you activate the RDS license server, and then you install the appropriate CAL package. These are two separate stages.

What to do if RD Licensing Diagnoser shows an error despite added licenses?

First, check the licensing mode, license server name, and applied GPO. In many cases, the problem results from discrepancies between Per User and Per Device or from the lack of a assigned license server to the Session Host.