I had already written some blog posts on the new Active-Active High Availability (HA) option in the past like RDS in WIN8 Feature highlight no. 1 Better High Availability of the RD Connection Broker and How to configure High Availability for RD Connection Broker on Windows 8 and RD Connection Broker HA – SQL Permissions and most recently RD Connection Broker HA and the RDP properties on the client.
But The Microsoft Remote Desktop Virtualization team released a nice blog post on MSDN on this subject as well. The details are show below.
“…In previous releases, the RD Connection Broker role service has supported an active/passive clustering model. This provided high availability in the case of component failure, but it did not address high scale requirements. 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 or more RD Connection Broker servers can be combined under a single DNS entry to provide both fault tolerance and load balancing. This prevents the RD Connection Broker server from being a single point of failure and also allows “scale out” as load demands.
The following diagram shows an Active/Active Broker deployment with one RD Virtualization Host server and one RD Session Host server. 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 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…”