Microsoft RDS Networking issue

mad4x4

Member
Join Date
Mar 2009
Location
ST CYrus
Posts
352
The problem we have is that a SERVER 2016 RDS HOST machine will not change the path to read the new SERVER2016 RDS LICENSE server. Instead, it keeps looking at the old one, which failed.

We have tried to execute the Powershell commands on the Host to reconfigure, but it's not working. The only machine that has a broker running is EWS, We have 2 License servers called DOMCONT1 & TERTIARY

Set-RDLicenseConfiguration -LicenseServer @("DOMCONT1.PIPELAY.LOCAL","TERTIARY.PIPELAY.LOCAL") -Mode PerUser -ConnectionBroker "EWS.PIPELAY.LOCAL"


RDS Diagnoser keeps telling us that it cannot contact domcont.pipelay.local which is the old License and domain server that died rather than DOMCONT1.PIPELAY.LOCAL.

2022-08-16_13-57-30.jpg 2022-08-16_13-58-28.jpg
 
You don't happen to have a GPO configured that's using the old server do you?

Typically, you would just open Server Manager, Go to Remote Desktop Services, Overview and hit the RD licensing under deployment overview to start configuring that server.
 

Similar Topics

Does anybody use for remote tech support? Quick Assist, QA, comes with Windows 10 and 11 so it is "free" QA uses HTTPS for security but I wonder...
Replies
1
Views
1,380
I have been playing w/ my Microsoft 365 account. Found this as I was looking for Visio. Apparently there is this form app. I just started one...
Replies
2
Views
1,053
I'm wondering what people do these day when Excel is needed on an offline computer. Look at Microsoft Store's link, it seems it does require...
Replies
9
Views
2,537
I'm building a FT View SE Network Distributed application on Microsoft Windows Server 2016 Datacenter. Original application was FT View SE v8.2...
Replies
2
Views
2,344
As cyber security concern and compliance requirement increases in my world. We are being pressed to at least do periodic patching review but not...
Replies
2
Views
1,409
Back
Top Bottom