Change High Availability Database connection string on Windows Server 2016

J Parmar 22 Reputation points
2021-07-05T09:48:37.49+00:00

Hello
Does anyone know how to change or if its even possible to Availability Database connection string on Windows Server 2016

We have copied the database to another server and now need to redirect the connection string to a new server.
The only thing that is different is the Folder to store the database file.

I ran this but get a communication error - the ODB test works and also added a ANY ANY firewall rule between the 2 servers.

Set-RDDatabaseConnectionString -ConnectionBroker "Connedtionbroker.local" -DatabaseConnectionString "DRIVER=SQL Server Native Client 11.0;SERVER=NEWSERVERNAME;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;DATABASE=RDS_Databasename"

111845-image.png

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,134 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,573 questions
0 comments No comments
{count} votes

Accepted answer
  1. Leila Kong 3,701 Reputation points
    2021-07-06T02:53:23.61+00:00

    Hello @J Parmar ,

    Thanks for your query.

    1.Is there any screenshot for the error message?
    2.How did you configure the RD Connection Broker High Availability?
    https://nedimmehic.org/2017/05/16/remote-desktop-services-2016-connection-broker-high-availability/
    3.It is possible to move the Connection Broker SQL database. Please check the following document for reference:

    (1) Move the RDCB HA database for RDS 2012/R2: http://blog.justinsnair.com/move-the-rdcb-ha-database-for-rds-2012r2/
    Set-RDDatabaseConnectionString -ConnectionBroker -DatabaseConnectionString “DRIVER=SQL Server Native Client 10.0;SERVER=;Trusted_Connection=YES;APP=Remote Desktop Services Connection Broker;DATABASE=”
    Armed with my new command, I followed this procedure:
    Stopped new connections to RDSH servers
    Created the appropriate firewall rules to allow the RDCB servers to contact the new MSSQL Server
    Backed up database on old MSSQL Server
    Restored database on new MSSQL Server
    Used the PowerShell command above to set the new connection string
    Restored connections to RDSH servers

    (2) Moving the Connection Broker SQL database: https://social.technet.microsoft.com/Forums/office/en-US/04f2beae-1b35-41dc-aa22-3281e55461c2/moving-the-connection-broker-sql-database?forum=winserverTS
    Copy the old DB to the new SQL server. Database file location was same on old and new server
    Apply the permissions same as old SQL server
    Logon to RDGATEWAY
    Get/save the current settings by
    Open PowerShell on RDgateway
    Type ipmo remotedesktop
    Type Get-RDConnectionBrokerHighAvailability. Save results
    Used the following commandSet-RDDatabaseConnectionString -ConnectionBroker "RDGATEWAYSERVERFQDN" -DatabaseConnectionString "DRIVER=SQL Server Native Client 11.0;SERVER=NEWSQLSERVER;Trusted_Connection=Yes; APP=Remote Desktop Services Connection Broker;Database=NAMEOFSQLDATABASE"
    Detached old DB
    Restarted RDGATEWAY server

    Best regards,
    Leila


    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Leila Kong 3,701 Reputation points
    2021-07-16T01:18:56.193+00:00

    Hello @J Parmar ,

    We haven’t heard from you in a couple of days.
    Please post back at your convenience if we can assist further.

    0 comments No comments

  2. J Parmar 22 Reputation points
    2021-07-16T03:35:47.807+00:00

    It turned out to be a SQL permission issue. ;)


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.