![installing server 2016 remote desktop services installing server 2016 remote desktop services](https://content.spiceworksstatic.com/service.community/p/post_images/0000333596/5bde47e6/attached_image/IMG_0320.JPG_2.jpg)
- Installing server 2016 remote desktop services update#
- Installing server 2016 remote desktop services windows#
So I started the backup restore, installed Windows Updates and after the restart the same initial error condition: The role Remote Desktop Connection Broker is completely missing. To avoid spending more time on a possibly unrecoverable system, I restored the VM from a backup before the Windows updates. Reinstalling the Remote Desktop Gateway role did not change the error pattern. Although the role was installed according to the server manager. The result was that our system had lost the role RDS-GATEWAY. Unfortunately, this didn't help us much, because I then used "Get-RDServer" in Powershell to output the status of the systems involved in the RDS infrastructure. But then Sebastian made the following experience: After that, the management of the Remote Desktop structure via UI and Powershell was available again and thus visible. The next step was to reinstall the Windows Remote Desktop Connection Broker role. Remote Desktop Connection Broker Role broken The Windows event log for this is not very informative, Sebastian wrote. So he checked the installed Windows roles and it turned out that the Remote Desktop Connection Broker role is not installed at all, or is detected as no longer installed.
Installing server 2016 remote desktop services update#
Sebastian writes about the error pattern that was noticed quickly after the update installation, that Windows services belonging to the roles mentioned above were missing on the two systems. These are probably included in the January 2022 update KB5009608 (see here). I have not found any KB articles for the latter two updates KB5009639 and KB5010523.
![installing server 2016 remote desktop services installing server 2016 remote desktop services](https://i.ytimg.com/vi/pnscjO1QAmU/maxresdefault.jpg)
Two of these systems run Windows Server 2022, all others Windows Server 2019.Īfter automatically installing the Windows updates (KB5011497, KB5009639 and KB5010523 were installed) after release on these two Windows Server 2022 systems, remote connections through these systems stopped working.One VM per customer is used here, providing the roles of Remote Desktop Gateway, Remote Desktop Connection Broker and Web Access for Remote Desktop.Sebastian works for an IT service provider as an administrator, and his employer runs remote desktop (gateway) infrastructures for its own purposes as well as for customers. just reported via email that he encountered issues with two Windows Server 2022 systems earlier today due to Windows updates released on March 8, 2022. However, this does not affect the error described below. The Known Issues section of the update support article states that when connecting to devices in an untrusted domain with Remote Desktop, authentication fails when using smart card authentication. The update raises the OS build to 20348.587 and makes internal, unspecified, security fixes to the operating system. I had covered it in the blog post Patchday: Windows 11/Server 2022 updates (March 8, 2022): As of March 8, 2022, Microsoft has released cumulative update KB5011497 for Windows Server 2022.