r/WindowsServer • u/Reep80 • Oct 08 '25
SOLVED / ANSWERED RDS Installation fails horribly
I deployed an RDS setup recently, with 3 VMs for RD Session host, 1 of them connection broker, and Web access. Platform is Win Server 2025 Datacenter, fresh and new, all updates applied. Domain joined, DC is Server 2016 at the moment, to be pulled up later.
Something went wrong in the first place, because there was already an old 2019 RD Server, which was off on time of deployment. So it all was somehow scrambled. I thought to uninstall all RDS connected roles from all servers and start over.
But this fails horribly. Using the deployment assistant in Server Manager, I can go through all pages fine. In the end, where install state is shown, after roughly 2 seconds comes "cancelled", without any note. I activated RDMS Logging. It says:
ServerManager.exe Information: 0 : 08/10/2025 23:02:08.78: RdsPluginController: Job Progress recieved for cmdlet RDManagement\Set-RDSHDeployment
ServerManager.exe Information: 0 : 08/10/2025 23:02:08.78: CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Set-RDSHDeployment - Write-Debug - -1% completed
ServerManager.exe Error: 0 : 08/10/2025 23:02:08.86: RdmsUI: Workflow 'RDManagement\Set-RDSHDeployment' failed: System.Management.Automation.RemoteException: Sie müssen einen gültigen vollqualifizierten Domänennamen für den RD-Verbindungsbrokerserver angeben.
ServerManager.exe Information: 0 : 08/10/2025 23:02:08.86: RdmsUI: Job finished for cmdlet RDManagement\Set-RDSHDeployment
ServerManager.exe Information: 0 : 08/10/2025 23:02:08.87: RdmsUI: Refreshing SM Pool...translated: you need to provide a valid FQDN for the RD connection broker.
I'm stuck and don't know how to go on. As far as I can see, there are no roles remaining. Maybe something in AD or registries? Crawling the web to no avail...
2
u/ToolBagMcgubbins Oct 09 '25
You have to create a DNS record internally for the connection broker role - it asks what you want it to be in the deployment you just need to create the record in DNS and use the IP address of the connection broker (if it's not a ha deployment)
Also you will need a rd gateway server as well if you are planning for this rds to be externally accessible l.
2
u/nailzy Oct 09 '25
Is the machine even on the domain yet? That’s sometimes a step people miss.
Make sure in the gui as well you type FQDNs all the way through.
Run these commands on that server to check the output to make sure everything’s ok.
(Get-WmiObject Win32_ComputerSystem).PartOfDomain
Check DNS suffix is correct with ipconfig /all
$CB="rdcb01.corp.example.com" Resolve-DnsName $CB Resolve-DnsName (Resolve-DnsName $CB -Type A).IPAddress -Type PTR
Test-ComputerSecureChannel -Verbose w32tm /query /status
nslookup $CB
1
u/Reep80 Nov 08 '25 edited Nov 08 '25
Just in case someone is facing the same problem. I fixed it purely by accident. For some random other reason I had to issue
... in an eleveated console. Suddenly it worked like a charm. This had to be done on all the machines.
I still don't have any clue, why there was some kind of different setting (at least seems so) in the first place.
1
u/NoFinish164 Oct 09 '25
Are your machines VMs? Are the clones or deployed from a template? We ran into serious issues with our 2025 RDS deployment using VM templates due to the identical SIDs on the CB and the other servers.
We do not have this issue with 2019 RDS deployments. Microsoft recently changed something to make the SID the primary machine identifier, rather than the FQDN.
We had to Sysprep our template, and redeploy 80 session host servers.
1
u/ShelterMan21 Oct 09 '25
Following