However when trying to add the 2nd connection broker, I get this error I have followed this article step by step, tested the connection to the sql database through ODBC and that works. I cannot seem to add a second connection broker to my HA setup. They have helped me a great deal with my RDS VDI deployment. To allow the connection brokers to communicate with SQL you need to configure the SQL Native Client using ODBC. Configuring SQL Native Client on Connection Brokers Once you have changed the TCP setting from dynamic to Static you need to create a inbound firewall rule for TCP 1433 allow. Remove 0 from the TCP Dynamic Ports and add 1433 to the TCP port for all IP address’s. Open the SQL Server Configuration Manager, open the TCP/IP Properties under SQL Network Configuration and set the listen all option to NO. Once you have configured the RDS Connection Broker login, you will see it appear under logins in the security folder for the SQL instance. In the Server Roles page select DBCreator, Sysadmin and public.

Configure security permissionsĬreate a security group and add the RDCB servers as members.Īdd all connection brokers into the security GroupĬreate a new user and add the Group name to the login name. Select default settings for the reporting services. You can set a Service account, for this example i have used the defaults.Įnter the User names that can access SQL administrator and a SA password. For this example i am using SQL Express 2012 and a single instance.įor more information on high available SQL Solutions please see the following link:

Visionapp remote desktop 2017