Issues with RDS CAL License Migration to New License Server

Vaun Harper 0 Reputation points
2024-10-14T03:27:28.28+00:00

I have migrated an RDS CAL license pack to a new license server, and the test RDSH servers are connected to the new license server. However, the new user sessions aren't being issued licenses according to RD Licensing Manager.

There are two RDS CAL license packs installed on the original RD License server. I have migrated the least used CAL pack across to the new license server. A GPO has been configured and applied to the test RDSH servers, to point them to the new license server. I have confirmed the GPO has applied, and when I check the RD Licensing Diagnoser on the test RDSH servers, I can see the correct license server is listed with the correct number of available licenses. I have used four different user accounts to log in at the same time; however, none of the users are issued licenses from either the old or the new RD License servers.

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Yanhong Liu 14,205 Reputation points Microsoft External Staff
    2024-10-16T03:06:45.1566667+00:00

    Hello,

    Based on your description, you can try the following steps to troubleshoot and solve this problem.

    1. Activation Status: Ensure that the new RD License Server is activated. In RD Licensing Manager, the server should be listed as "Activated."
    2. GPO Settings: Double-check your Group Policy settings to ensure they are correctly configured. Specifically, verify the following settings:
      • Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing:
        • Use the specified Remote Desktop license servers
        • Set the Remote Desktop licensing mode (either Per User or Per Device, as appropriate)
    3. Licensing Mode: Make sure that the licensing mode on the new RD License Server matches the mode specified on your test RDSH servers.
    4. RD Licensing Diagnose:
      • Check the RD Licensing Diagnose on the RDSH servers once more to confirm there are no warnings or errors.
      • Ensure it shows the new license server and the available CALs.
    5. Event Viewer: Check the Event Viewer on your RD License Server and RDSH servers for any related errors or warnings. Look under "Applications and Services Logs" -> "Microsoft" -> "Windows" -> "TerminalServices-RemoteConnectionManager" and "TerminalServices-Licensing."
    6. Firewall and Network Configuration: Ensure that there are no network issues preventing communication between the RDSH servers and the new license server. Verify that the necessary ports (typically TCP 135, 139, 445, and 3389 for RDS) are open and not blocked by a firewall.

    Best Regards,

    Yanhong Liu

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

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.