none
RDS 2019 deployment - unable to add second RD Broker - RRS feed

  • Question

  • We are running a seperate RDS deployment for our 2019 servers. We had 2 brokers, gateways and RDWeb, with the three roles on one machine each. On our SQL cluster we have a database, where the nodes connect to. One of the brokers started acting up after some Windows updates, and finally it refused to work anymore. Do I just removed it from the deployment, updated our load balancers and currently we are running on one broker/gateway/rdweb just fine. But I want to add a second node again.

    When I do so I get the following error:

    The list of joined nodes could not be retrieved on <the machine I try to add as second broker>. Privilege not held.



    So far I've tried:

    - With the broker-dns entry with and without the second node in;

    - after removing the old node (new one has the same name) I verified in the SQL database, the old server is NOT in there anymore;

    - Firewalls all wide open while adding the node; even if no blocks were logged at al;

    - Added the computer account of the new node to SQL and allowed it access to the DB, even we use username/pass as seems to be required in a HA setup.

    The SQL connection string is fine by the way, for one the remaining node works fine and until recently it worked fine for the seconde node as well.

    How to fix this? Any clue?

    Monday, June 17, 2019 12:29 PM

All replies

  • hi,
    about "The list of joined nodes could not be retrieved"
    there is a thread
    https://social.technet.microsoft.com/Forums/en-US/004af6d1-9621-41aa-ab0e-cb4dd5390608/rds-2012-certificate-mistmatch?forum=winserverTS

    other document for your reference
    Troubles with Removing RD Connection Broker High Availability
    https://ryanmangansitblog.com/2013/04/14/troubles-with-removing-rd-connection-broker-high-availability/

    Please Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

     


    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    Wednesday, June 19, 2019 3:41 AM
    Moderator
  • hi,
    Is there any progress on your question?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Sunday, June 23, 2019 3:44 PM
    Moderator
  • Hi,

    sorry for not responding, seems I didn't enable alerts for this post. Unfortunately, no. I wasn't able to join the host as a broker. The post linked to above is refering to certificate issues initially and later a powershell command which gave that user the same error I have, to which I don't see a solution.

    In the end I just reinstalled the machine, ran the very same scripts to install everything and now it's just fine. So it must have been something in the OS itself, not the RDS deployment as a whole. So it's not fixed, but I worked around it.

    Thanks!

    Monday, June 24, 2019 7:58 AM
  • Hi
    Thanks for your reply I. I hope everything goes well.

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 2, 2019 10:23 AM
    Moderator