Hi All,
Let me first explain what I have and what I'm trying to achieve.
I have 1x Microsoft RD Connection Broker Server
I also have 2x Microsoft Remote Desktop Session Host servers (one primary and one secondary)
I then have a Kemp hardware loadbalancer which contains the IPs of the Session Host servers
I have configured an RD Connection broker farm that includes the two aforementioned Session Host servers.
The plan is for clients to connect into the Session Host servers via the Kemp loadbalancer's virtual IP. As the Session Host servers are part of the RD Connection Broker Farm on the RD Connection broker sever I want there to be continuity for user sessions in the event of a primary Session Host server failure. The problem is that this is not happening!
To test I am logging into a user session on Session Host Server1 (I get server1 as I have weighted the real server IP on the Kemp device so it will always connect here unless it is down). I then simulate a Server1 failure (pulling power). The session crashes and I start a new session. The Kemp device does its job and directs me to Server2. All good so far. However once I put in the users login details I get the 'Server cannot be found' error. So the connection broker is kicking in as its trying to connect me to the existing session but on the wrong server! It is trying to reconnect me to the failed server. Does anyone have any ideas why this would be happening?
Any help appreciated!