New RDS2016 Server not picking up licenses from RDS License Server
We set up a new RDS server that should pick up our licenses from the existing RDS2016 server.
The existing server licenses are all current. It has been placed in the correct groups in the domain and all looks good.
The new server is not configured as a license server. Under deployment, the server is set to look at the other server to pick up its licenses. The server does not seem to do this and is using its own grace period licenses.
When you enter the license diags the server tells me there are no licenses available for the session host server.
How do I go about getting the new server to pick up the licenses correctly?
The existing server licenses are all current. It has been placed in the correct groups in the domain and all looks good.
The new server is not configured as a license server. Under deployment, the server is set to look at the other server to pick up its licenses. The server does not seem to do this and is using its own grace period licenses.
When you enter the license diags the server tells me there are no licenses available for the session host server.
How do I go about getting the new server to pick up the licenses correctly?
Carl Webster
Did you configure the license settings on the server or via a GPO?
With 2016, the RDS AD licensing group isn't used (to the best of my knowledge). It needs to be set in one of 3 ways:
1. Server Group
2. GPO
3. WMI/CIM
https://docs.microsoft.com
You can check it easily enough with WMI (and set it to..)
Coralon
1. Server Group
2. GPO
3. WMI/CIM
https://docs.microsoft.com
You can check it easily enough with WMI (and set it to..)
$wmi = Get-WMIObject -ClassName Win32_TerminalServiceSetting -Namespace root/cimv2/terminalservices
$wmi.GetSpecifiedLicenseServerList()
$wmi.SetSpecifiedLicenseServerList('servername')Coralon
ASKER
Thanks for your input. It turns out it was a really simple one and that the main server was not actually apart of the Terminal Servers Group in the domain.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.