MS Terminal Services
Kemp leads the industry in driving the price/performance value proposition for application delivery and load balancing to levels that our customers can afford. Our products' versatile and powerful architecture provide the highest value, while enabling our customers to optimize their businesses that rely on Internet-based infrastructure to conduct business with their customers, employees and partners.
Kemp products optimize web and application infrastructure as defined by high-availability, high-performance, flexible scalability, security and ease of management. They maximize the total cost-of-ownership for web infrastructure, while enabling flexible and comprehensive deployment options.
This document describes various aspects of configuring the Kemp LoadMaster for use with Microsoft Terminal Services. It describes in detail how to configure the LoadMaster using the LoadMaster Web User Interface (WUI).
This document is intended to help anyone who wishes to learn about or implement load balancing on Microsoft Terminal Services using the Kemp LoadMaster.
Published with LMOS version 220.127.116.11 LTS. This document has not required substantial changes since 18.104.22.168 LTS. However, the content is in sync with the latest LoadMaster LTS firmware.
Setting up a Virtual Service to balance Microsoft Terminal Servers is very similar to setting up any other Virtual Service. The system tries to automatically detect the type of Virtual Service based on the port of the Virtual Service.If the Virtual Service uses port 80, 8080 or 443, then it will be configured as a HTTP/HTTPS service. If it uses port 3389 then it will be configured for terminal services. If the port is set to anything else, the service will be configured as "Generic".
The type of the service can always be changed manually if needed.
This configuration is intended to allow the LoadMaster to balance Microsoft Terminal Services across multiple servers. Upon first connection, a server is allocated using the standard scheduling methods, i.e. Round Robin, Least Connection, Adaptive, etc.
If a user disconnects from his/her session without logging out, it is preferable to maintain persistence with the server that he/she originally connected to. This allows that user to come back to the screen they were working on, with all the same windows open and applications running where they had left off.
This is where the Persistence Mode of Terminal Service comes in. If this persistence mode is enabled, when a user reconnects, the LoadMaster will try to connect the session to the same server. It does this in one of three ways:
If the terminal servers support a RD Connection Broker, the LoadMaster will use the "routing token" supplied by the RD Connection Broker to determine the correct host to connect to. The LoadMaster persistency timeout value is irrelevant here - it is a feature of the RD Connection Broker.
The IP address redirection option in the RD Connection Broker configuration must be unchecked for this to work.
Using RD Connection Broker with the LoadMaster is optional in terms of persistence. If the client pre-populates the username and password fields in the initial request, then this value is stored on the LoadMaster. As long as these fields are still populated upon reconnect, the LoadMaster will look up the name and reconnect to the same server as the original connection. The persistence timeout is used to limit the time the information is kept on the LoadMaster.
If using Terminal-Service or source IP mode, then if neither of these two modes succeeds, the source IP address will be used for persistency.
Web User Interface (WUI), Configuration Guide
Kemp LoadMaster, Product Overview
This document was last updated on 22 March 2021.