Environment: Session Based
RDSGW1 - Roles: RD Connection Broker (High-Availability Configured), RD Gateway, RD Web Access
RDS1 - Roles: RD Session Host
RDS2 - Roles: RD Session Host
DNS Configured to remoteapp.domain.com (pointing to IP of RDSGW1)
Scenario:
User 1: Connects fine to remoteapp.domain.com. User 1 is authenticated and launches a remoteapp. User 1 connects to the application hosted on RDS1 and all is fine and well. User 1 logs out ofremoteapp.domain.com
I open up RDSGW01 and disallow new connections to RDS1.
User 1: Connects fine to remoteapp.domain.com. User 1 is authenticated, but is still trying to launch a connection to apps onRDS1.
I shutdown RDS1 as a test to see if RDSGW01 would redirect that client toRDS2 but same result. The application hangs as it is unavailable onRDS1.
Is there a configuration change that needs to be done in order for that clients connection to fail over toRDS2?
As an aside, it does seem to balance users across both RDS1 andRDS2 remote applications fairly evenly. I would assume that denying new connections to servers would have done the trick, but not in my experience thus far.
Any takers?