KEMP as RDS load balancer

0

Hi all, 

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. 

Thanks!

Jared

1 comment

Avatar
0
Mark Deegan

Hello Jared,

in the instance of the LM doing the load balance for the RDS, the Connection broker is not required as the LM directs the traffic. Please see the following

To make sure that correct load balancing is carried out when using Connection Broker based persistence, some changes on the connection broker itself are needed.

Changes Needed on the Connection Broker

First, disable the following two options:

  1. Go to gpedit.msc > administrtive Templates > Windows Components > Remote Desktop Session Host > RD Connection Broker.

  2. The following two options need to be disabled:
    • Use IP Address Redirection
    • Use RD Connection Broker load balancing

Note: These changes only need to be implemented on the Connection Broker.

 Next, enable Session Time Limit:

Go to gpedit.msc > administrtive Templates > Windows Components > Remote Desktop Session Host > Session Time Limit.

Session Time Limit must be enabled - the value of the limit depends on the customer's requirements.

Note: These changes only need to be implemented on the Connection Broker.

 

Remote Desktop Connection Limit

If requested by the customer, it is recommended to set the limit of connections on the Real Server itself, not on the LoadMaster. To do this, go to gpedit.msc > administrtive Templates > Windows Components > Remote Desktop Session Host > Connections.

This additional setting may be requested if Connection Broker Persistence is selected. In this case, all the incoming connections marked as persistent will be still sent to the same Real Server, even if the maximum number of connections have already been reached at LoadMaster level. This may be a problem if the Connection Limit is set at LoadMaster level only and the customer is requesting a hard limit on the number of incoming connections to the Real Server.

Note: This has to be implemented on all the host servers.

 

Additional Information on Connection Brokers

Refer to the following Microsoft TechNet article for further information on Connection Brokers: https://technet.microsoft.com/en-us/library/cc772245.aspx

When Connection Broker persistence is selected on the LoadMaster, the RD Connection Broker keeps track of user sessions. The RD Connection Broker database stores session information, including the:

  • Name of the RD Session Host server where each session resides
  • Session state for each session
  • Session ID for each session
  • User name associated with each session

The LoadMaster will then use this information to redirect a user who has an existing session to the RD Session Host server where the user’s session resides.

For further information, refer to the Remote Desktop Services Deployment Guide:

https://support.kemptechnologies.com/hc/en-us/articles/203858115-Remote-Desktop-Services