sql server connection string 2012 remote server

The end nodes (RD Virtualization Host, RD Session Host, and RD Web Access) are configured with the full list of all the fully qualified domain names (FQDNs) of the RD Connection Broker servers, and they can connect to any of the RD Connection Broker servers in the setup. The RD Connection Broker servers are using a SQL database for storing data, and RDP clients are connecting to the RD Connection Broker servers using DNS Round Robin. The following diagram shows an Active/Active Broker deployment with one RD Virtualization Host server and one RD Session Host server. This prevents the RD Connection Broker server from being a single point of failure and also allows “scale out” as load demands. The Active/Active Broker feature in Windows Server 2012 eliminates the need for clustering and provides a fully active/active model with this model two RD Connection Broker servers can be combined under a single DNS entry to provide both fault tolerance and load balancing. This provided high availability in the case of component failure, but it did not address high scale requirements.

In previous releases, the RD Connection Broker role service has supported an active/passive clustering model. This post is intended for administrators who are deploying virtual machine-based or session-based desktop deployments with RD Connection Broker and who want to have high availability and scalability in their deployment. This post provides an in-depth look into one of those features, the new high availability feature of RD Connection Broker known as the Active/Active Broker, and includes deployment steps and performance results. There have been a couple of posts recently about the new Remote Desktop Services features in Windows Server 2012. Hello, this is Jingyuan, Munindra, and Sriram from the Remote Desktop Virtualization team. First published on CloudBlogs on Jun, 27 2012

Sql server connection string 2012 remote server