I have a Remote Desktop Session Host farm with a Remote Desktop Connection Broker (Server 2008 R2) arbitrating connections for this farm. The Connection Broker is configured as the RD Web Access RemoteApp source (with the Web Access role installed on the same machine):
and Windows 7 clients are connecting to the RD Web feed to receive the RemoteApp connection files. Everything works so far except for one major detail - the RDP files received from the RD Web Access server are directing users to a specific session host in the farm (the first one joined) instead of the farm itself, thus introducing a single point of failure and defeating the load balancing capabilities of a farm.
I obviously could enter the RD farm name as the "Source name" instead of the connection broker's, but since the RD connection broker is aggregating a number of farms and single RD servers and I would like to keep a single point of administration, I would rather not do this.
So can I change this behavior by reconfiguration or a hotfix? Would upgrading to a Server 2012 R2 connection broker help matters here?