RDS 2019 CAL with built-in overused is issued, not the RDS 2022 CAL that was purchased

Question

The environment configuration is as follows:

Domain name:test.rds.local

RDS license server: hostname rds-license (OS: Windows Server 2022, license version: RDS 2022 CAL for per user)

RDS session host server: hostname rds-host (OS: Windows Server 2019)

Although the user can connect to the RDS session host server, 2019 CAL is being issued insted of purchased 2022 CALs. In addition, the license status here is “Built-in Overused”.

Therefore, no license is issued from 2022 RDS CAL.

RDS CAL is backward compatible, so there should be no problem. And there is no error in RD Licensing Diagnosis. I believe that the correct behavior is to issue the license from 2022 RDS CAL. I would appreciate it if you could tell us the cause of the problem and how to deal with it.

Answer 1

The issue you are experiencing, where the RDS 2019 CAL is being issued instead of the purchased RDS 2022 CALs, could be due to the compatibility between the RDS session host and the licensing server. While RDS CALs are backward compatible, the licensing server must also be properly configured to issue the correct CALs based on the session host version.

In your case, the RDS session host is running Windows Server 2019, which can issue RDS 2019 CALs but may not be configured to utilize the RDS 2022 CALs effectively. Additionally, the "Built-in Overused" status indicates that the licensing server has exceeded its available licenses, which could prevent it from issuing new licenses correctly.

To address this issue, consider the following steps:

1. Check License Configuration: Ensure that the RDS licensing configuration is correct, and that the RDS license server is activated and has the appropriate CALs installed.
2. Verify Compatibility: Confirm that the RDS session host and the RDS license server versions are compatible. The RDS 2022 CALs should be installed on the license server, and the session host should be able to utilize them.
3. Review Licensing Mode: Make sure that the licensing mode (Per User or Per Device) is set correctly for your deployment.
4. Resolve Overuse: Address the "Built-in Overused" status by either increasing the number of available licenses or ensuring that licenses are being freed up correctly.
5. Use RD Licensing Diagnoser: Although you mentioned there are no errors in Licensing Diagnosis, it may be worth running it again to ensure there are no underlying issues.

By following these steps, you should be able to troubleshoot and resolve the issue with the RDS CALs being issued.

---

References:

• Cannot connect to RDS because no RD Licensing servers are available
• RDS Licensing troubleshooting guidance