I'm in the process of setting up the free KEMP load balancer for a PoC of RDS set up in an HA/load-balanced fashion and am having a bit of trouble.
Currently my setup is as follows
2xWindows 2012 R2 servers for Gateway and Web Interface functions - they are running Windows NLB for each role. DNS Names of "rdsgw" and rdsweb"
2xWindows 2012 R2 servers for the Connection Broker role - they are running Windows NLB for the CB role. No DNS name pointing to the NLB VIP
2xWindows 2012 R2 servers for the Session Host role - these are behind the KEMP. DNS name of "rdsha" pointing to the KEMP VIP.
In the configuration above, things seem to be working (the Windows NLB portion was setup prior to me discovering the free KEMP load balancer to test with), but when users connect to the RDS farm the connection brokers are unable to see the sessions in the Server Manager. So in the event we want to manage user sessions that way, we are unable to, and have to log in to each session host to manage them instead.
Is anyone else experiencing this?
I should note we have made the necessary GPO changes mentioned here "https://support.kemptechnologies.com/hc/en-us/articles/205948506-Connection-Broker-and-changes-requested-for-RDS-Configuration".
I'm not sure if this is the expected behavior or not.
Any help is appreciated.