Hello,
Based on your description, you can try the following steps to troubleshoot and solve this problem.
- Activation Status: Ensure that the new RD License Server is activated. In RD Licensing Manager, the server should be listed as "Activated."
- 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)
- Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing:
- Licensing Mode: Make sure that the licensing mode on the new RD License Server matches the mode specified on your test RDSH servers.
- 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.
- 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."
- 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.