Deploy RD Session Host and RD Licensing separately on two Windows Servers within the same WorkGroup.

Question

I deploy RD Session Host and RD Licensing separately on two Windows Servers within the same WorkGroup（named WorkGroup）.

When I activate the RD licensing host and install per-device CALs, and configure the RD Session Host according to the Microsoft link, the RD licensing diagnosis tool shows that no licenses are available and prompts that it is in the grace period when I connect remotely to the RD Session Host. Can I deploy the RD Session Host and RD licensing host on two workgroup Windows Servers, and if so, how should I configure them to work properly? https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-license-session-hosts#ensure-an-rd-session-host-can-access-an-rd-licensing-server-in-the-same-work-group

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-license-session-hosts

Answer 1

Yes, you can deploy the RD Session Host and RD Licensing server on two separate Windows Servers within the same workgroup. However, there are specific configurations you need to ensure for them to work properly:

1. Use Per Device CALs Only: In a workgroup environment, you can only use Per Device Client Access Licenses (CALs). Make sure that you have installed only Per Device CALs on the RD Licensing server.
2. License Server Access: Ensure that the RD Session Host can access the RD Licensing server. If they are on different servers, you need to configure the RD Session Host to specify the name of the license server, as automatic license server discovery is not supported in Windows 2008 R2 and later.
3. Configuration Steps: You should configure the RD Session Host using the Remote Desktop Session Host Configuration snap-in to specify the license server. This includes:
   • Setting the licensing mode to Per Device.
   • Specifying the license server name.
4. Check Licensing Configuration: After configuration, use the RD Licensing Diagnosis tool to verify that the license server is activated and that it has the appropriate CALs installed. If the tool indicates that no licenses are available, double-check your configuration settings and ensure that the RD Session Host can communicate with the RD Licensing server.

By following these steps, you should be able to successfully deploy and configure the RD Session Host and RD Licensing server in a workgroup environment.

Answer 2

Hello Jonas Zhan,

Yes, you technically can deploy the RD Session Host and RD Licensing roles on separate servers within the same Workgroup, but the configuration you are attempting is failing due to a lack of mutual authentication between the servers. In a domain environment, the Session Host uses its computer account to authenticate against the Licensing Server to issue and validate Per-Device CALs. In a Workgroup, this trust relationship does not exist, causing the Session Host to fail when attempting to query the license pool remotely, which triggers the "Grace Period" warning you are seeing in the diagnosis tool.

The most robust solution for a Workgroup environment and the one I strongly recommend to eliminate this instability is to install the Remote Desktop Licensing role directly on the same server as the RD Session Host. This consolidation bypasses the network authentication requirement entirely because the Session Host effectively queries "localhost" for the licenses. You can migrate your existing CALs to this new local instance by using the "Manage RDS CALs" wizard within the RD Licensing Manager or by contacting the Microsoft Clearinghouse if an automatic migration fails. This is the industry best practice for Workgroup deployments to avoid exactly the issue you are facing.

If you are strictly required to keep the servers separate, you must hard-code the licensing configuration using Local Group Policy, as the GUI settings often fail to persist or authenticate correctly in non-domain scenarios. On your Session Host, run gpedit.msc and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing. You must configure two specific policies here: enable Set the Remote Desktop licensing mode and select Per Device, and enable Use the specified Remote Desktop license servers and enter the IP address of your Licensing Server. Using the IP address is critical here to rule out NetBIOS or DNS resolution failures common in Workgroups.

Additionally, you must ensure the Licensing Server allows the Session Host to communicate via RPC. On the Licensing Server, verify that the Windows Firewall has inbound rules enabled for Remote Desktop Licensing and File and Printer Sharing (SMB-In). Furthermore, please disregard the generic advice suggesting the "Remote Desktop Session Host Configuration snap-in" (tsconfig.msc), as that tool was removed from Windows Server starting with version 2012. You must rely on Group Policy or direct Registry modification (at HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core) for these settings on modern operating systems.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Answer 3

Hi Jonas Zhan,

I'm following up to see if the previous solution resolved your licensing configuration issue. To recap, the "Grace Period" error in a split-server Workgroup setup stems from the Session Host's inability to authenticate against a remote Licensing Server without Active Directory trust. The most reliable resolution is to consolidate the RD Licensing role onto the Session Host itself, eliminating the network authentication requirement. If separation is mandatory, you must strictly configure the licensing mode and server IP address via Local Group Policy (gpedit.msc) rather than the GUI to ensure the settings persist.

If the issue has been successfully resolved, please consider accepting the answer as it helps other people sharing the same question benefit too. Thank you!

VP