We have a small farm of 3 RDS servers and one separate RDCB server using Windows 2012 R2. We have decided not to use the RDCB server to handle to load balancing due to limitations and complexity, but instead work with a 3rd party load balancer(Snapt) that is agentless.
When someone first logs onto an RDS server, session is balanced across the farm appropriately. Things change though when a session becomes disconnected and the user wants to re-logon. At this point the user enters their credentials for the RDS session, the RDP screen goes black and then the logon screen appears again. I believe this is due to the second RDP session hitting a different server, CB realizing an active session exists on a different server, and moving the user to the appropriate server.
I believe the issue lies in our load balancer and not the connection broker but I wanted to see if I could get some feedback on this as my team and I might be missing something entirely.
Thanks,
Joe