Hi all,
Our Remote Desktop Gateways are configured to receive their remote apps from the connection broker. On our connection broker ,in it's remote App sources in Remote Desktop Connection Manager there is "farm.local".
Farm.local is a RRDNS entry comprised of 5 separate NLB Clusters, the TTL of Farm.Local is only 3 minutes. Meaning the DNS entry should rotate every 3 minutes.
When people connect VIA the gateway, they get directed to one NLB cluster and the connection broker never rotates after that. If I take farm.local out of the RemoteApp Sources in Remote Desktop Connection Manager on our connection broker, then re-add farm.local they are directed to a different NLB cluster.
It seems Remote Desktop Connection Manager gets the initial IP that the RRDNS is currently on and never updates past that.
Our Remote Desktop Gateways are configured to receive their remote apps from the connection broker. On our connection broker ,in it's remote App sources in Remote Desktop Connection Manager there is "farm.local".
Farm.local is a RRDNS entry comprised of 5 separate NLB Clusters, the TTL of Farm.Local is only 3 minutes. Meaning the DNS entry should rotate every 3 minutes.
When people connect VIA the gateway, they get directed to one NLB cluster and the connection broker never rotates after that. If I take farm.local out of the RemoteApp Sources in Remote Desktop Connection Manager on our connection broker, then re-add farm.local they are directed to a different NLB cluster.
It seems Remote Desktop Connection Manager gets the initial IP that the RRDNS is currently on and never updates past that.