Certificate error after Server Replacement. (Rebuilding Broker)

Dominique Beaulieu 1 Reputation point

Long story short We wanted to remove the HA on the broker on a TS Farm so I uninstall all role and decomissione the both RDBroker. I build a new VM and reinstall all the role.

If my new VM Name are the same name as the Old Cluster name was, I got a this error : "The connection was terminated because an unexpected server authentication certificate was received from the remote computer" (With certificate from my cert server with that name)

If I Give any name with certificate according to that name, It work well. Is there a better solution then renaming the Farm? Thanks

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
3,442 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,646 Reputation points Microsoft Vendor


    When creating RD Broker HA, you will need to create DNS records for HA farm. Since you wanted to remove the HA, have you confirmed that you also modified the DNS records on DC? The issue might be caused by the DNS resloution.



    If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

    0 comments No comments

  2. Dominique Beaulieu 1 Reputation point

    Yes I did I have reuse the same name so before to do that I have remove all the static DNS entry for the round robin to be sure the Automatic entry will be correctly created when I join the new server with the same name.

    That been said I also double check before writing that answer. And I confirm I is correct. One foward and one reverse both matching with the Server name and IP. And both with a time stamp so they are not static.

    0 comments No comments

  3. Dominique Beaulieu 1 Reputation point

    I finaly decide to keep the server I create with a new name, and keep it not in cluster. After adding the 4 server and tuning a few ting and clone one to recreate one of the not working server. The Same problem appear on that new setup.

    Dont know where to look to solve this issue. :(

    0 comments No comments