I have a deployment of two Windows Server 2012 R2 hosts, each running the RDCB service in an HA arrangement (the SQL database is on a separate server). In addition each host is also running the RDSH service.
The RDCB address is load balanced via DNS round Robin.
If a user creates an RDP session on a host, then disconnects, and then the host with the "disconnected" session becomes unavailable (i.e. disconnected from the network), the broker will continue to attempt to redirect the user to the existing disconnected session even though the server is unavailable.
I have tried adjusting the Registry settings as per this post:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/050ed3c2-1356-4c69-8337-1be735494670/session-broker-heartbeat-solution?forum=winserverTS
But the problem persists.
New RDP connections work fine, with the remaining broker creating new sessions on the remaining host.
This post:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/757c747f-b390-4f0a-aeb2-493400f6029a/windows-server-2012-r2-session-broker-offline-server-detection?forum=winserverTS
mentions that co-locating the RDCB and RDSH roles may be problematic, but this seemed related to new sessions. My new sessions are working fine.
Can anyone shine a light on the problem?
Surely the Connection Broker should be able to detect failed Session Hosts ?!