vivalageek

"Relative weight" of Session Hosts, which is set in the Session Host RDP-Tcp properties under the RD Connection Broker tab, allows you to shift the majority of connections onto a host when you set the weight of the preferred host to '100' and the secondary host to '1'. However this still means there is a very slight chance that TS02 will allow at least one client connection. Since you don't need a Connection Broker in this case (which is normally used for load-balancing), you could use MS NLB, which would allow TS02 to only be used if TS01 fails. You can either set it up with no load-balancing at all (in your case), or load-balance traffic arriving on specific TCP/UDP ports. All it needs is a single virtual IP on the existing network connections on the RD Session Hosts, mapped in DNS eg. TSFARM, and NLB can failover your server connections in seconds. This creates High Availability for your Session Hosts, better than a Connection Broker that uses Round Robin DNS (which still allows client connections to failed servers, causing connection errors). In this scenario you should be able to install the same software licenses on both Session Hosts because only one of them is being used at any one time. Also, if frequently-updated data is being stored on TS01, then as long as the data is being replicated (DFS?) from TS01 to TS02 you don't need to worry about staff losing their data if TS01 fails.