KluczeSoft.pl
Back to Help Center
Windows Server 2022
Activation Guide

## Activation of Windows Server 2016 RDS 10 User CAL To activate **Windows Server 2016 RDS 10 User CAL**, follow these steps: - First, ensure that your **Windows Server 2016** is properly installed and configured. - Next, you will need to install the **Remote Desktop Services** role. This can be done through the **Server Manager**. - Once the **RDS** role is installed, you can proceed to activate the **10 User CAL** license. ### Activation Steps 1. **Open the Command Prompt** as an administrator. 2. **Navigate to the directory** where your license files are stored. 3. **Run the command** to install the license key: ``` cscript slmgr.vbs /ipk <license_key> ``` Replace `<license_key>` with your actual license key. 4. **Activate the license** by running: ``` cscript slmgr.vbs /ato ``` 5. **Verify the activation status**: ``` cscript slmgr.vbs /dlv ``` ### Troubleshooting If you encounter any issues during the activation process, ensure that your **Windows Server 2016** and **RDS** are up to date. Also, verify that the license key is correct and not expired. ### Contact Support For any further assistance or questions regarding the activation of **Windows Server 2016 RDS 10 User CAL**, please do not hesitate to contact us at `[email protected]` or call `00 800 121 1654`. Our support team is ready to help you with any issues you may have. > Remember, it's crucial to use genuine **Microsoft** products to ensure the security and stability of your system. **KluczeSoft** is here to provide you with legitimate software solutions.

6 min czytania·Zaktualizowano dzisiaj

Activating Windows Server 2016 RDS 10 User CAL

The Remote Desktop Services in Windows Server 2016 require proper licensing configuration. If you are using the RDS 10 User CAL package, it means that licenses are assigned to specific users, not devices. This solution is particularly useful when one person connects to the server from multiple computers or locations.

Below, you will find a practical guide to activating the license server and installing the Windows Server 2016 RDS 10 User CAL package in Per User mode.

Step by Step

1. Open the Remote Desktop Licensing Manager

On the server that acts as the license server for RDS:

  1. Open Server Manager.
  2. Go to Tools.
  3. Select Remote Desktop Services.
  4. Click Remote Desktop Licensing Manager.

In the console, the local license server should be visible. If you see a warning icon next to its name, it means the license server has not been activated yet.

2. Activate the RDS License Server

  1. Right-click the server name.
  2. Select Activate Server.
  3. The activation wizard will start.
  4. Choose the connection method:
    • Automatic connection (recommended) – recommended if the server has internet access,
    • Web Browser – if you want to activate through a web browser,
    • Telephone – if activation will be done by phone.

Most often, the automatic option is sufficient. In the next steps, fill in the basic company data, such as name, country, and contact details. After completing the wizard, the license server should receive an active status.

3. Install RDS 10 User CAL Licenses

After activating the server, you can add the actual access licenses:

  1. Right-click the activated license server.
  2. Select Install Licenses.
  3. In the wizard, specify the appropriate licensing program compatible with your purchase. In practice, this depends on the type of key or contract number received.
  4. Enter the required license data, such as the contract number, authorization number, or key provided with the purchase.
  5. Choose the product:
    • Windows Server 2016 Remote Desktop Services CAL,
    • license type: Per User,
    • quantity: 10.

After confirmation, the licenses should appear on the list as installed and ready to use.

4. Set the Per User Licensing Mode

Installing CAL alone is not enough. You also need to specify the correct licensing mode for the RDS session server.

The easiest way to do this is through local or group policies:

  1. Run gpedit.msc or the appropriate GPO editor in the domain.
  2. Go to: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing
  3. Enable the Set the Remote Desktop licensing mode setting.
  4. Set the value to Per User.
  5. Enable the Use the specified Remote Desktop license servers setting.
  6. Enter the name or FQDN of the license server.

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

gpupdate /force

It's also a good practice to restart the service or the entire server if the configuration doesn't refresh immediately.

5. Verify Role Assignment and Communication

Make sure that:

  • the Remote Desktop Licensing role is installed,
  • the RDS session server can see the license server on the network,
  • the system firewall is not blocking communication,
  • the license server name is correctly resolved in DNS.

In a domain environment, it's also worth checking if the license server has been added to the Terminal Server License Servers group, if the organization uses the relevant security policies.

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

Checking

After completing the configuration, it's worth checking if the system is actually working in Per User mode and using the correct license server.

The most important places to check:

  • Remote Desktop Licensing Diagnoser – the tool will show if there are any errors in the licensing configuration.
  • Remote Desktop Licensing Manager – here you can check if the 10 User CAL package is visible as installed.
  • Server Manager – allows you to quickly notice warnings related to the RDS role.
  • Event Viewer – in case of problems, it's worth reviewing system logs and remote desktop service logs.

If everything has been configured correctly, the diagnoser should not report any errors related to the licensing mode or lack of a license server.

Problems

The most common problem is a mismatch of the licensing mode. If Per Device is set on the session server, and Per User licenses are installed, the system will report errors despite the CALs being correctly added.

Another common problem is the lack of a license server specified in the policies. In such a situation, the session server may not retrieve license information, even if the licenses are installed locally.

It also happens that the license server has been activated, but the wrong product type or incorrect licensing program has been entered. In this case, it's worth comparing the data with the purchase document again and ensuring that exactly Windows Server 2016 RDS User CAL is installed.

In environments without internet access, the problem is often the activation itself. In such a case, you should use the Web Browser or Telephone option and complete the process manually.

If licensing messages still appear after configuration, also check DNS, network connectivity, and domain policies. Often, the problem is not with the CALs themselves, but with communication between the session server and the license server.

If you need technical assistance, you can contact us: [email protected] or call 00 800 121 1654.

FAQ

Is RDS User CAL assigned to a computer?

No. User CAL is assigned to a user. This allows one person to access RDS from multiple devices.

Can RDS be used without activating the license server?

Only temporarily. After the grace period, remote desktop services will start reporting errors and access may be restricted. Ultimately, activating the license server is necessary.

What to choose: Per User or Per Device?

Per User is suitable when users work from multiple devices. Per Device is better suited for environments where multiple people use one workstation. For the RDS 10 User CAL package, the correct choice is, of course, Per User.

Microsoft

Microsoft Windows Server 2016 RDS 10 User CAL

Licencja dożywotniaWysyłka w 1 min
Kup w KluczeSoft

Related Articles

Microsoft Windows Server 2016 RDS 10 User CALActivation of WS 2019 StandardAktywacja WS 2019 EssentialsActivation of WS 2019 DatacenterActivating WS 2022 StandardActivation of WS 2022 Datacenter

Czy ten artykuł był pomocny?