34,333
edits
Changes
→Joining Terminal Servers to a TS Session Broker
* If the server is relying on the TS Session Broker to perform load balancing (as opposed to round-robin DNS) select the ''Participate in Session Broker load-balancing'' check box and specify a suitable weight value.
* Choose whether or not to use IP address redirection. When a user disconnects from a session wihtout logging off the session is maintained by the server so that the user can reconnect and resume where they left off. In a server farm it is important that the user be reconnected to the server on which the previous session is till running. By default the client queries the TS Session Broker and is redirected to their existing session by using the IP address of the server where the existing session resides. In order to use this default method, the client computers must be able to connect directly by IP address to terminal servers in the farm. That being the case, this is the recommended setting. If, on the other hand, Ip address redirection is not used, the IP address is instead embedded in a token. Under this configuration, when the client reconnects to the load balancer, the routing token is used to redirect to the existing terminal server on which the existing session is running. * Select the IP addresses to be used for reconnection. Note that Remote Desktop clients version 5.2 and older only support IPv4 addresses.
Repeat the above tasks for each server in the farm. Once completed the farm is ready for use.
