Home | Troubleshooting |  Quick Setup  |  Cisco How to  |  Wireless  |  Forums   | Site Map | Services  | About Us | Chicagotech MVP  | Search  | Contact Us  |              

 

 

How does TS Session Broker work

The terminal server where the initial connection is made redirects the user to the terminal server that is specified by TS Session Broker. The redirection behavior is as follows:
=====================================
1. A user with an existing session will connect to the server where their
session exists.
2. A user without an existing session will connect to the terminal server
that has the fewest sessions.

TS Session Broker Load Balancing sets a limit of 16 for the maximum number
of pending logon requests to a particular terminal server. This helps to
prevent the scenario where a single server is overwhelmed by new logon
requests; for example, if you add a new server to the farm, or if you
enable user logons on a server where they were previously denied.

The TS Session Broker Load Balancing feature also enables you to assign a
relative weight value to each server. By assigning a server weight value,
you can help to distribute the load between more powerful and less powerful
servers in the farm.

Note: To configure a server to participate in TS Session Broker Load
Balancing, and to assign a server weight value, you can use the Terminal
Services Configuration tool.

If you want to use the TS Session Broker Load Balancing feature, both the
TS Session Broker server and the terminal servers in the same farm must be
running Windows Server 2008.

If you want to use DNS round-robin as the load balancer for initial
connections, you must create a host resource record for each terminal
server in the farm that maps to the terminal server farm name in DNS. (The
farm name is the virtual name that clients will use to connect to the
terminal server farm.) DNS uses round robin to rotate the order of the
resource records that are returned to the client. This functionality helps
to distribute initial connections across servers in the farm.

Also there is a Group Policy added for TS Session Broker:
=====================================
Computer Configuration\Administrative Templates\Windows Components\Terminal
Services\Terminal Server\TS Session Broker\Use TS Session Broker load
balancing

The possible values are:

1) Enabled: If you enable this policy setting, TS Session Broker will
redirect users who do not have an existing session to the terminal server
in the farm with the fewest sessions. Redirection behavior for users with
existing sessions will not be affected. If the server is configured to use
TS Session Broker, users who have an existing session will be redirected to
the terminal server where their session exists.

2) Disabled: If you disable this policy setting, users who do not have an
existing session will log on to the terminal server that they first connect
to.

3) Not configured: If you do not configure this policy setting, TS Session
Broker Load Balancing is not specified at the Group Policy level. In this
case, you can configure the terminal server to participate in TS Session
Broker Load Balancing by using the Terminal Services Configuration tool or
the Terminal Services WMI provider. By default, this policy setting is not
configured.

 

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics


 

 


 

 

Hit Counter   This web is provided "AS IS" with no warranties.
Copyright 2002-2015 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.