question

DelaneyHorton-3511 avatar image
0 Votes"
DelaneyHorton-3511 asked DSPatrick commented

Windows Server 2019 Cannot Install RS Connection Broker

I have a brand new environment with three servers:
- One AD DC
- Two Hyper-V hosts on which I'm trying to deploy RDS

All three servers are running GUI-less Windows Server 2019.

When I try to deploy a Virtual Desktop Environment with this command on my second Hyper-V host (not the RDCB or RDWA):

 New-RDVirtualDesktopDeployment -ConnectionBroker "VDI-HOST01.DOMAIN.COM" -WebAccess "VDI-HOST01.DOMAIN.COM" -VirtualizationHost @("VDI-HOST01.DOMAIN.COM","VDI-HOST02.DOMAIN.COM")

I get this error:

 Unable to install RD Connection Broker role service on server VDI-HOST01.DOMAIN.COM
     + CategoryInfo          : InvalidResult: (:) [], RDManagementException
     + FullyQualifiedErrorId : JobStateFailed
     + PSComputerName        : localhost


All servers are a member of the same domain and in the same OU. The user account that I am using is a member of both Domain Admins and the local Adminstrators group on each server.

Each Hyper-V server is a member of the local "RDS Management Servers", "RDS Endpoint Servers", and "RDS Remote Access Servers" groups on each machine.

Uninstalling Windows Internal Database, renaming to WID_OLD, and reinstalling RDCB does not fix the issue.

I tried enabling and collecting logs as suggested here: https://docs.microsoft.com/en-US/troubleshoot/windows-server/remote/log-files-to-troubleshoot-rds-issues but no logs were created. As they both have UI in their names, maybe I can't properly enable them without a GUI.

WinRM connection settings are just fine. I'm able to PSRemote into each server from each server and run all commands except for this RDS deployment one.



Am I missing something here? Any help would be appreciated, because I am absolutely stumped.



remote-desktop-serviceswindows-server-2019
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick avatar image
0 Votes"
DSPatrick answered DSPatrick commented

Looks like remote desktop connection broker and remote desktop virtualization host are no longer supported on a core server.

https://docs.microsoft.com/en-us/windows-server/get-started-19/removed-features-19#features-we-removed-in-this-release

Remote Desktop Connection Broker and Remote Desktop Virtualization Host in a Server Core installation Most Remote Desktop Services deployments have these roles co-located with the Remote Desktop Session Host (RDSH), which requires Server with Desktop Experience; to be consistent with RDSH we're changing these roles to also require Server with Desktop Experience. These RDS roles are no longer available for use in a Server Core installation. If you need to deploy these roles as part of your Remote Desktop infrastructure, you can install them on Windows Server with Desktop Experience.

--please don't forget to upvote and Accept as answer if the reply is helpful--



· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DSPatrick

Well that is extremely unfortunate.
We were using Server 2019 with Desktop Experience before (which is why we weren't having these issues), and we decided to shift to Server 2019 Core under the assumption that we would have better performance and wanted to test. I did not see these release notes about making RDCB and RDVH require Desktop Experience; I must've pulled up older documentation when I was researching compatibility.

Thanks for your prompt answer. It looks like we'll have no choice but to revert to Desktop Experience again.

0 Votes 0 ·

You're welcome.

0 Votes 0 ·
DSPatrick avatar image
0 Votes"
DSPatrick answered DSPatrick commented

Something here may help. Looks like the connection broker should go on a dedicated virtual machine.
https://infohub.delltechnologies.com/l/vdi-deployment-guide-microsoft-rds-for-dell-emc-microsoft-storage-spaces-direct-ready-nodes-1/installing-remote-desktop-services

--please don't forget to upvote and Accept as answer if the reply is helpful--






· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DSPatrick

I have created several deployments before where the connection broker has been on the physical machine acting as a virtualization host and have not run into this problem. However, the link you provided mentions adding all servers to Server Manager. I do not have this program while using the 2019 Server Core, like I did with previous deployments that worked. I also do not have a Server with Desktop Experience on this domain or network, so I am not sure how to incorporate Server Manager for managing these servers.
That might be the issue here. Do you have any suggestions?

0 Votes 0 ·

mentions adding all servers to Server Manager

More than likely the only advantage with Server Manager is so you can add the roles to them remotely. Another option might be WAC
https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/understand/faq

Back to the issue it may be the core install is a problem?
https://social.technet.microsoft.com/Forums/ie/en-US/b5c2bae3-0e3b-4d22-b64d-a51d27f0b0e4/deploying-rds-2012-r2-quotquotunable-to-install-rd-web-access-role-service-on-serverquot?forum=winserverTS



--please don't forget to upvote and Accept as answer if the reply is helpful--










0 Votes 0 ·