You need to ensure that all servers that have the Remote Desktop Session Host (RD Session Host) role service …

Your network contains an Active Directory domain. You deploy a server named Server1 that has the
Remote Desktop Connection Broker (RD Connection Broker) role service installed. You need to
ensure that all servers that have the Remote Desktop Session Host (RD Session Host) role service
installed are automatically configured to use Server1 as an RD Connection Broker. What should you
do?

Your network contains an Active Directory domain. You deploy a server named Server1 that has the
Remote Desktop Connection Broker (RD Connection Broker) role service installed. You need to
ensure that all servers that have the Remote Desktop Session Host (RD Session Host) role service
installed are automatically configured to use Server1 as an RD Connection Broker. What should you
do?

A.
Register a service principal name (SPN) for Server1.

B.
Register a service location (SRV) record for Server1.

C.
Use a Group Policy to configure the Restricted Groups settings.

D.
Use a Group Policy to configure the Remote Desktop Services settings.

Explanation:
RD Connection Broker Policy settings in this node control configuration of a Remote Desktop Session
Host server that is a member of a load-balanced Remote Desktop Session Host server farm. The full
path of this node in the Group Policy Management Console is Computer
Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop
Services\Remote Desktop Session Host\RD Connection Broker. Available policy settings Join RD
Connection Broker This policy setting allows you to specify whether the RD Session Host server
should join a farm in RD Connection Broker. RD Connection Broker tracks user sessions and allows a
user to reconnect to their existing session in a load-balanced RD Session Host server farm. To

participate in RD Connection Broker, the Remote Desktop Session Host role service must be installed
on the server. If the policy setting is enabled, the RD Session Host server joins the farm that is
specified in the Configure RD Connection Broker Farm Name setting. The farm exists on the RD
Connection Broker server that is specified in the Configure RD Connection Broker Server name policy
setting. If you disable this policy setting, the server does not join a farm in RD Connection Broker,
and user session tracking is not performed. If the setting is disabled, you cannot use either the
Remote Desktop Session Host Configuration tool or the Terminal Services WMI provider to join the
server to RD Connection Broker. If the policy setting is not configured, the setting is not specified at
the Group Policy level. In this case, you can configure the server to join RD Connection Broker by
using the Remote Desktop Session Host Configuration tool or the Terminal Services WMI provider. If
you enable this setting, you must also enable the “Configure RD Connection Broker Farm Name” and
Configure RD Connection Broker Server name policy settings, or configure these settings by using
either the Remote Desktop Session Host Configuration tool or the Terminal Services WMI provider.
Configure RD Connection Broker farm name This policy setting allows you to specify the name of a
farm to join in RD Connection Broker. RD Connection Broker uses the farm name to determine which
RD Session Host servers are in the same RD Session Host server farm. Therefore, you must use the
same farm name for all RD Session Host servers in the same load-balanced farm. The farm name
does not have to correspond to a name in Active Directory Domain Services. If you specify a new
farm name, a new farm is created in RD Connection Broker. If you specify an existing farm name, the
server joins that farm in RD Connection Broker. If you enable this policy setting, you must specify the
name of a farm in RD Connection Broker.
If you disable or do not configure this policy setting, the farm name is not specified by Group Policy.
In this case, you can adjust the farm name by using the Remote Desktop Session Host Configuration
tool or the Terminal Services WMI provider. This setting is not effective unless both the Join RD
Connection Broker and the Configure RD Connection Broker server name settings are enabled and
configured by using Group Policy, the Remote Desktop Session Host Configuration tool, or the
Terminal Services WMI provider. Configure RD Connection Broker server name This policy setting
allows you to specify the RD Connection Broker server that the RD Session Host server uses to track
and redirect user sessions for a load-balanced RD Session Host server farm. The specified server
must be running the Remote Desktop Connection Broker service. All RD Session Host servers in a
load-balanced farm should use the same RD Connection Broker server. If you enable this policy
setting, you must specify the RD Connection Broker server, using either its host name, IP address, or
fully qualified domain name. If you specify a name or IP address for the RD Connection Broker server
that is not valid, an error message is logged in Event Viewer on the RD Session Host server. If you
disable or do not configure this policy setting, you can adjust the RD Connection Broker server name
or IP address by usin the Remote Desktop Session Host Configuration tool or the Terminal Services
WMI provider.
This policy setting is not effective unless the Join RD Connection Broker policy setting is enabled or
the RD Session Host server is configured to join RD Connection Broker by using the Remote Desktop
Session Host Configuration tool or the Terminal Services WMI provider.
To be an active member of an RD Connection Broker-enabled RD Session Host server farm, the
computer account for each RD Session Host server in the farm must be a member of the Session
Directory Computers local group on the RD Connection Broker server.
Use RD Connection Broker load balancing This policy setting allows you to specify whether to use the
RD Connection Broker load balancing feature to balance the load between servers in an RD Session
Host server farm.
If you enable this policy setting, RD Connection Broker redirects users who do not have an existing
session to the RD Session Host server in the farm with the fewest sessions. Redirection behavior for

users with existing sessions is not affected. If the server is configured to use RD Connection Broker,
users who have an existing session are redirected to the RD Session Host server where their session
exists.
If you disable this policy setting, users who do not have an existing session log on to the first RD
Session Host server to which they connect.
If you do not configure this policy setting, you can configure the RD Session Host server to
participate in RD Connection Broker load balancing by using the Remote Desktop Session Host
Configuration tool or the Terminal Services WMI provider.
If you enable this policy setting, you must also enable the Join RD Connection Broker, the Configure
RD Connection Broker farm name, and the Configure RD Connection Broker server name policy
settings.
Source: http://technet.microsoft.com/en-us/library/ee791821.aspx



Leave a Reply 0

Your email address will not be published. Required fields are marked *