RD Connection Broker role service is failing while trying to install on Azure Stack HCI

Shilpi Verma 20 Reputation points
2024-11-18T09:21:16.9166667+00:00

In Azure Stack HCI, I am having 5 nodes. I have created 2 clusters, one cluster with 3 nodes and other cluster with 2 nodes. Now I need to set up Azure Virtual Desktop on 2 nodes cluster.

I have used custom windows image while creating VM on any cluster.

I am following the MS document - https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-deploy-infrastructure

But it is failing on first step only. RD Connection Broker role service is failing while setting up it from Server Manager. Please help.

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
369 questions
Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,593 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Sai Krishna Katakam 1,090 Reputation points Microsoft Vendor
    2024-11-18T17:23:16.7033333+00:00

    Hi Shilpi Verma,

    Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

    It sounds like you're having trouble with the RD Connection Broker role service on Azure Stack HCI. Here are some steps to help:

    Uninstall the Windows Internal Database, rename the old WID folder (e.g., C:\Windows\WID to WID_old), and reinstall the RD Connection Broker role service. (External reference: Fixed: RD Connection Broker Role Service Fails to Install 2016 - AnyViewer)

    Note: Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.

    Review the known issues for your specific version of Azure Stack HCI in the release notes.
    https://learn.microsoft.com/en-us/azure-stack/hci/known-issues-2402

    Make sure that all nodes in your cluster have proper connectivity and that there are no network issues. You can use the Invoke-AzStackHciConnectivityValidation cmdlet from the AzStackHCI.EnvironmentChecker module to test connectivity

    Collect and review the PowerShell registration logs and hcisvc debug logs from each server in the cluster.

    If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.