All servers on your companys network run Windows Server 2008 R2. You deploy Remote
Desktop Services (RDS). The company has a load-balanced Remote Desktop Connection
Broker (RD Connection Broker) cluster. You are adding a Remote Desktop Session Host
(RD Session Host) server to the cluster. You need to ensure that the RD Session Host
server will receive only half of the RDS sessions. What should you do?
A.
Enable IP redirection on the RD Session Host server.
B.
Enable token redirection on the RD Session Host server.
C.
Configure the server weight for the RD Session Host server.
D.
Configure the DNS weight priority for the RD Session Host server.
Explanation:
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 relative weight value, you can help to distribute the load
between more powerful and less powerful servers in the farm. Additionally, a new “server
draining” mechanism is provided that enables you to prevent new users from logging on to a
terminal server that is scheduled to be taken down for maintenance. This mechanism
provides for the ability to take a server offline without disrupting the user experience. If new
logons are denied on a terminal server in the farm, TS Session Broker will allow users with
existing sessions to reconnect, but will redirect new users to terminal servers that are
configured to allow new logons