Server 2019 RD-Connectionbroker Rolle broken after Windows Update
Hi, we have a RD session deployment with 1 Connection Broker/Web Access, 8 Session Hosts for RD and 1 Session Host for Apps and 1 License Server. All Servers are VM´s on VMware running Server 2019 DC running perfect for a year now. Some Weeks ago after an Windows update i noticed that i was no longer able to see and configure the deployment in Server Manager on the Connection Broker (I can see and in parts manage the deployment from other Servers Server Manager) Deployment is still working and users are able to connect, load balancing also works. On The Connection Broker it just says: "Es ist keine Remotedesktopdienste-Bereitstellung im Serverpool vorhanden. Führen Sie zum Erstellen einer Bereitstellung den Assistenten zum Hinzufügen von Rollen und Features aus, und wählen Sie die Installationsoption "Remotedesktopdienste" aus." Powershell get-rdserver output: PS C:\Windows\system32> get-rdserver get-rdserver : Der RD-Verbindungsbrokerserver ist nicht verfügbar. Stellen Sie sicher, dass Sie eine Verbindung mit dem RD-Verbindungsbrokerserver herstellen können. In Zeile:1 Zeichen:1 + get-rdserver + ~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-RDServer Eventlog: ID1280 "Die Remotedesktopdienste konnten keine Verknüpfung mit dem Verbindungsbroker auf dem Server "VSTSBro01.xxx.de" herstellen. Fehler: Die aktuelle asynchrone Nachricht wurde vom asynchronen Verteiler gelöscht, da eine neue Nachricht vorhanden ist, die die aktuelle Nachricht überschreibt." ID2056 "Der Remotedesktop-Verbindungsbrokerserver konnte die Ziele für den Anbieter "NULL" nicht aus der Datenbank auflisten. Name der in einem Pool zusammengefassten virtuellen Desktopsammlung: NULL Fehler: Die Anmeldung bei der Datenbank ist fehlgeschlagen." Things i tried so far: Configuring Connection Broker HA, WID got successfull migrated to dedicated VM with SQL Server But cause the connection Broker is not available i couldnt add a second connection broker. Restoring Connection Broker VM from Backup, after restore i could see and manage the deployment again but had to reboot the VM after Domain Trust reset. Update got installed with that and Problem is the same again. Update that got installed at that time: Edge Stable 103 x64 Build 103.0.1264.49 2022-07 Cumulative Update for Windows Server 2019 for x64 based Systems KB5015811 I guess something broke the connection to the WID and its no longer able to load the information. But why is it able to show the deployment on other servers? First pic Broken CB second pic other Server Any Ideas how to fix that? Thx!Windows Server / hyper-V VDI Question
I inherited this issue and didn't setup it up. From what the person who design and deployed it tells me I can't update the gold Image without affecting all the currently deployed and active VDIs but the gold image that we use is very out of date and logically it doesn't make any sense to me that if i update the gold image it will screw up all the active users. We are running thins clients that use MS connection broker to connect to hyper-v on two Active / Active Windows 2K16 servers for load balancing. We pre-assign the user to a newly deployed VDI based on the gold image. That gold image is really out of date with a lot of software that we don't use anymore, I want to update that gold image but the person who deployed this over a year ago tells me it will screw up the other active VDIs. Is there a way to update the image without screwing up existing users?
