The new TS Session Broker Load Balancing feature, you can distribute the load between servers in a session load balancing terminal server farm. With TS Session Broker Load Balancing, new user sessions are redirected to the terminal server with the fewest sessions.
With TS Session Broker to load balance sessions involves two phases. In the first phase, the first compounds by a preliminary load-balancing mechanism that distributes such as domain name system (DNS) round robin. After a user authenticates, asks the terminal server that accepted the initial connection to determine the TS Session Broker server, where the user should be redirected.
In the second phase leads to the terminal server, where the first connection is established the user on a terminal server that was specified by TS Session Broker. The redirection behavior is as follows:
A user with an existing session is at the server to connect to the session.
A user without an existing session with the terminal server that connects 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 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 relative weight value, you can help distribute the load between more powerful and less powerful servers in the farm. For more information, see Configure TS Session Broker settings by using Terminal Services Configuration.
In addition, a new "server draining" mechanism is provided that can prevent new users from logging onto a terminal server, which is expected to be put in maintenance mode. This mechanism provides the possibility to a server offline without having to take the user experience. If new logons are denied on a terminal server in the farm, TS Session Broker allows users to connect to existing sessions, while new users to terminal servers that are configured to allow new registrations to be diverted. For more information, see Deny logons to a terminal server in a load-balanced farm.
You can enable TS Session Broker Load Balancing Using Terminal Services Configuration, Group Policy or Windows Management Instrumentation (WMI). If you distribute DNS round-robin on the initial values of connections, you must also configure DNS entries for each terminal server in the farm.
Kaydol:
Kayıt Yorumları (Atom)
bari türkçe anlatım olsaydı bişede anlamıyorum :(
YanıtlaSil