Microsoft Terminal Services, a precursor to Microsoft Remote Desktop Services or ‘RDS’, allows users to remotely access a graphical desktop and associated applications running on a terminal services server.
Active server health checking by our load balancer detects non-responsive servers and removes them from the real server pool. This ensures that new connections only hit healthy terminal services servers.
Maintenance is made easy, as servers can be gracefully drained of client connections over time. Once a server has no clients connected it can be taken offline for maintenance, without any impact to services.
Server CPU and RAM usage can inform load balancing decisions with the use of our open source Windows feedback agent. A small number of users performing computationally or memory intensive tasks can quickly consume a server’s resources. Our feedback agent reports server resource use to the load balancer, allowing for server weights to be dynamically changed so that busy servers receive either fewer or no new connections.
Microsoft Terminal Services existed up until Windows Server 2008 R2, when Microsoft changed the nomenclature. For reference and comparison with Remote Desktop Services, details of how the naming of components changed can be found here.
Example deployment showing load balanced Terminal Servers.
Protocols and load balancing methods for Microsoft Terminal Services
|Protocol||Role||Default Ports||Supported load balancing methods|
|TCP||Remote Desktop Protocol (RDP)||3389||Layer 4 DR, Layer 4 NAT and Layer 7 SNAT|