Forum Discussion
Noob needs help with RDP Services
The root cause
You’re seeing the “Remote Desktop Licensing Mode is not configured” message because:
The RDS deployment wizard expects a domain-joined environment with an RD Connection Broker role,
But your server is stand-alone (workgroup), so that central role doesn’t exist.
Server Manager therefore blocks RDS configuration through the GUI when you log on with a local account.
The correct approach for a single, workgroup RDS host
You can still activate licensing and remove the warning by using PowerShell or Local Group Policy.
Option 1: Configure via Group Policy
On the same 2019 server:
Open gpedit.msc
Go to
Computer Configuration →
Administrative Templates →
Windows Components →
Remote Desktop Services →
Remote Desktop Session Host →
Licensing
Enable these two settings:
Use the specified Remote Desktop licensing mode → set to Per User or Per Device (depending on your CAL type).
Specify the Remote Desktop license servers → enter the server’s own name, e.g.
localhost
Close the editor and run:
gpupdate /force
Reboot the server.
Option 2: Configure directly with PowerShell
# Replace mode with 2 for Per User, 4 for Per Device
$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
$obj.ChangeMode(2)
$obj.SetSpecifiedLicenseServerList("localhost")
Then verify:
$obj.GetSpecifiedLicenseServerList()
What about your existing licenses?
You do not need to remove or reinstall the RD Licensing role — your licenses stay safe in the Remote Desktop Licensing Manager (licmgr.exe).
Just make sure the Remote Desktop Licensing service is running and the mode matches your CAL type.
Summary
Keep the RD Licensing role — don’t uninstall it.
Set the licensing mode and server via Group Policy or PowerShell.
Reboot and confirm the warning disappears in Server Manager → Remote Desktop Services → Overview.
Workgroup setups don’t need an RD Connection Broker; everything runs on one host.
- JuJuBeeOct 08, 2025Copper Contributor
Thanks for the response. It almost seems like MS wants everyone to run a DC with AD on prem. We are totally cloud AzureAD. They should work on this scenario.