It sounds like you've done a commendable job so far setting up your Remote Desktop Services (RDS) environment. However, the issue you're encountering—where the server doesn't seem to release the licenses, restricting your connections to just two devices—can be quite frustrating. Let's dive into some potential causes and solutions.
### Potential Issues and Solutions
1.
License Server Activation:
-
Check Activation: Ensure your License Server is properly activated. Sometimes licenses are installed, but the server itself isn't activated.
-
Steps to Verify: Open the Remote Desktop Licensing Manager, right-click on the server name, and see if it shows "Activate Server."
2.
Recent Licensing Installation Delay:
-
Propagation Time: If you've recently added or converted licenses, it may take some time for these changes to propagate.
-
Steps to Verify: Check the status in the Remote Desktop Licensing Manager. If the licenses show as installed and available, the issue may lie elsewhere.
3.
Group Policy Configuration:
-
Check GPOs: Ensure your Group Policy settings are accurately pointing to the correct License Server and License Mode (Per Device in your case).
-
Steps to Verify:
- Run
gpupdate /force on the server.
- Open
gpedit.msc and navigate to
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing.
- Confirm the licensing settings (License server name and Mode).
4.
License Over-allocation:
-
Check Allocation & Usage: Ensure that the licenses are not over-allocated. Per Device CALs can sometimes become “stuck” or improperly counted.
-
Steps to Verify:
- Open the Remote Desktop Licensing Manager.
- Check the number of allocated licenses and compare it to the number of devices.
5.
RD Licensing Diagnoser:
-
Use Diagnostics Tool: While you mentioned the Remote Desktop Licensing Service Diagnostic Tool showed no problem, rechecking won't hurt. This tool often provides clues.
-
Steps to Verify:
- Open the RD Licensing Diagnoser.
- Look for any non-obvious issues or warnings.
6.
Event Viewer Logs:
-
Check Logs: Event Viewer can be a goldmine for uncovering hidden issues.
-
Steps to Verify:
- Open Event Viewer (
eventvwr.msc).
- Navigate to
Applications and Services Logs > Microsoft > Windows > TerminalServices-Licensing.
- Look for any errors or warnings related to licensing.
### Additional Recommendations
- Restart RDS Services: Sometimes a quick restart of the Remote Desktop Services can refresh connections.
- Server Reboot: If all else fails, a full reboot might help clear any temporary issues.
### Summary
1. Verify that the License Server is activated.
2. Ensure that the licenses are properly installed and configured in the Group Policy.
3. Check if there’s a delay in the propagation of newly installed licenses.
4. Confirm that licenses are not over-allocated.
5. Use the RD Licensing Diagnoser to uncover any hidden issues.
6. Check Event Viewer for detailed logs and errors.
If after checking all of the above, the issue persists, consider reaching out to Microsoft support for further assistance, as there may be a deeper issue at play.
Good luck troubleshooting—may your RDS environment soon be free-flowing with licenses! If you have any more details to provide or further questions, feel free to ask!
