== An Overview of the Terminal Services Session Broker ==
The TS Session Broker is positioned on the front line in front of two or more servers running terminal servers and is responsible for balancing terminal service load requests between authorized servers such that a single server does not become overloaded. TS Session Broker can be run on a serser server specifically designated for the task, or, since the broker itself does not require significant resources, on one of the terminal servers in the group.
Load balancing may be configured using a concept known as ''relative weighting'' or using ''round-robin DNS''. Under relative weighting, an administrator specifies assigns each server a weight value (based on percentages) which, relative to the weights assigned to other servers, governs the load levels on that server. For example, a server with a weight of 30 will have a load of 30% of the load of another server in the farm with a weight of 100. it It is important to understand that loading is based on number of sessions on each server, and not any knowledge of the total resource load on a particular server at a given time. For example, one server with small 'resource light' application applications will be viewed by the TS Session Broker as being at the same load level as a server with a large, resource intensive applicationapplications.
Round-robin DNS, as the name suggest, passes the load balancing responsibility onto a DNS server.
== Prerequisites for Implementing TS Session Broker ==
Before deplaying deploying a Terminal Server farm there a few key prerequisites that should be taken into consideration. Firstly, the server designated to run the TS Session Broker service must be a member of a domain.
