Activation of Windows Server 2022 RDS 10 User CAL

Activation of Windows Server 2022 RDS 10 User CAL is necessary to legally and correctly provide users with remote desktop services in a corporate environment. In the RDS CAL per user model, the licence is assigned to a specific person, not a single device. This is a good solution when one employee accesses remote services from several computers, a laptop, or a tablet.

In practice, the process consists of two stages: first, the Remote Desktop Services licence server is activated, and then the purchased RDS User CAL licence package is installed and activated. Below, you will find a simple instruction that will help you go through the entire process in the Windows Server 2022 system.

Step by Step

1. Check if the RDS licensing role is installed

Manage -> Add Roles and Features

Make sure the following role is installed:

Remote Desktop Services -> Remote Desktop Licensing

If the role has not been added yet, install it and restart the server if the system requires it.

2. Open the Remote Desktop Licensing Manager

After installing the role, run the tool:

Remote Desktop Licensing Manager

You can find it in the Start menu or through Server Manager in the administrative tools section.

The local license server should be visible on the list. If there is no activation information next to its name, you need to perform this step manually.

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:

Automatically connect (recommended)

This is the fastest way, as long as the server has internet access. In the next steps, fill in the basic company data, such as the organization name, country, and contact details if necessary. After completing the wizard, the license server will be activated.

If the server does not have internet access, you can use activation via a web browser or by phone.

4. Install RDS 10 User CAL licenses

After activating the server, select the option to install licenses or right-click the server and select:

Install Licenses

In the wizard, select the appropriate licensing program. Depending on the purchase source, this may be a commercial license, Open License, or another model specified in the purchase documents. Then, enter the required data, primarily the license number or activation key received with the purchase.

It is very important to specify the correct license type during installation:

RDS Per User CAL

and the correct version corresponding to the environment, i.e., Windows Server 2022 or a compatible version accepted within the licensing rights.

After confirming the wizard, a pool of available licenses will appear on the server, for example:

10 RDS User CAL

5. Configure the licensing mode on the RDS server

Installing licenses is not always enough. The session host server must still know which license server to use and in which mode to operate.

Open:

Local Group Policy Editor

and go to:

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

Configure two policies:

Use the specified Remote Desktop license servers
Set the Remote Desktop licensing mode

In the licensing mode, select:

Per User

In the license server field, enter the name of the local server or its FQDN.

After saving the changes, refresh the policies with the command:

gpupdate /force

For certainty, you can also restart the server or the RDS-related service.

Checking

After completing the configuration, it's worth ensuring that everything is working correctly. To do this, open:

Diagnostyka licencjonowania usług pulpitu zdalnego

This tool shows whether the session host server sees the license server, whether the licensing mode is set correctly, and whether there are any errors related to CAL licenses.

Additionally, in the Menedżer licencjonowania usług pulpitu zdalnego, you can check if the 10 User CAL package has been installed correctly. With per-user licenses, the system does not always track usage as accurately as with per-device licenses, so it's especially important that the license status matches the actual number of users in the organisation.

If users can log in to remote sessions without error messages, and the diagnostics do not report any problems, the activation has been performed correctly.

Problems

The most common problem is setting the incorrect licensing mode. If Per Device is set on the session host server, but Per User licenses are installed, errors or warnings will appear. In this case, you need to correct the policy and refresh the settings again.

Another common problem is the lack of a specified license server. Even if the licenses have been added correctly, the session host may not detect them. You should then check the server name in the group policy and network communication between the roles.

It also happens that the administrator installs the licensing role but does not complete the activation of the server itself. As a result, the wizard accepts the configuration partially, but the licenses are not registered correctly. Therefore, it's always a good idea to check if the server status is Aktywowany.

If the problem concerns the key or license number, it's best to compare the data entered in the wizard with the purchase document. An error in one character can prevent activation.

If you need help with deployment or license verification, please contact us: [email protected] or call 00 800 121 1654.

FAQ

Can RDS User CAL be assigned to a user using multiple devices?

Yes. This is exactly what the per user model is for. One license covers one user, even if they connect to the server from multiple different devices.

Does Windows Server 2022 require separate RDS CAL licenses?

Yes. The standard Windows Server license does not replace the access licenses for remote desktop services. To legally use RDS, the appropriate RDS CAL is required.

What to do if the server shows a licensing error despite installed CALs?

First, check the licensing mode, license server name, and the result in the RDS diagnostic tool. Most often, the problem is due to inconsistent Per User and Per Device settings or the lack of an assigned license server. If you want to speed up the solution to the problem, write to [email protected].