To make sure that correct load balancing is carried out when using Connection Broker based persistence, some changes are required on the Session Hosts.
Please note that these changes are only required when Load Balancing your Session Hosts, and Not required if you are Load Balancing your Connection Brokers.
Changes Needed on the Session Hosts
First, disable the following two options:
- Go to gpedit.msc > administrtive Templates > Windows Components > Remote Desktop Session Host > RD Connection Broker.
- 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 Session Hosts.
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: