Share via

Windows Server 2022 CALS not being used when users log into a 2019 Server

Velazquez, Erick 20 Reputation points
2025-08-14T20:52:41.92+00:00

Hello all,

We recently migrated to a new RDS Licensing Server on Windows Server 2022 and pointed all other Remote Desktop Session Host (Terminal Server) servers running Windows Server 2019 to this new licensing server.

All configuration steps were followed, but when a user logs into a 2019 Session Host, the RDS Licensing Manager shows that instead of using the 2022 pool of volume licenses, it creates a new pool: “Windows Server 2019 CALs – Per User”.

These entries are marked as Built-in Overused, with no licenses available, yet they continue to increment as users log in.

It was my understanding that 2022 CALs should be used even for 2019 session hosts. We have 250 Windows Server 2022 CALs under our Campus agreement with upgrade rights, but the 2022 pool is not being utilized, and a new category is being created instead.

Is this expected behavior, or is there something we are missing in the configuration?

Thank you for your time,

Erick

Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade
0 comments
Accepted answer
  1. Quinnie Quoc 1,085 Reputation points Independent Advisor
    2025-08-15T10:22:07.6266667+00:00

    Dear Erick,

    Thanks for the detailed explanation—this is a great question, and I can see how the current behavior would be confusing given your setup and licensing rights.

    You're absolutely right in your understanding: Windows Server 2022 CALs should be valid for Windows Server 2019 Session Hosts, especially under a Campus agreement with upgrade rights. However, the behavior you're seeing—where the RDS Licensing Manager creates a separate pool for “Windows Server 2019 CALs – Per User” and marks them as Built-in Overused—is not uncommon and can stem from how the licensing server interprets CAL availability.

    What’s Likely Happening

    • The RDS Licensing Manager UI doesn’t always reflect license inheritance correctly. Even though 2022 CALs are valid for 2019 hosts, the manager may still show a separate pool for 2019 CALs and flag them as overused.

    This is mostly a visual/reporting issue, not a functional licensing failure. Users are still being granted access under valid CALs, but the UI doesn’t consolidate them under the 2022 pool.

    What You Can Do

    1. Verify Licensing Mode on Session Hosts
      • Ensure all 2019 Session Hosts are set to Per User licensing mode and are correctly pointing to the 2022 Licensing Server.
    2. Confirm License Installation
      • On the 2022 Licensing Server, confirm that the Windows Server 2022 CALs (Per User) are installed and activated.
    3. Ignore the “Built-in Overused” Label
      • Microsoft has acknowledged that this label can appear even when valid CALs are being used. It doesn’t necessarily indicate a compliance issue.
    4. Optional: Contact Microsoft Support
      • If you need formal confirmation for audit or compliance purposes, Microsoft Support can validate that your 2022 CALs are being applied correctly to 2019 hosts under your agreement.

    I hope my answer is useful for you.

    Best regards,

    Quinnie Quoc.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.