You need to ensure that the users connecting to the RD Connection Broker farm can establish sessions on Server3

Your network contains three servers that run Windows Server 2008 R2. The servers are
configured as shown in the following table. Server1 has Remote Desktop Services Per
Device client access licenses (RDS Per Device CALs) installed. Server2 and Server3 are
members of a Remote Desktop Connection Broker (RD Connection Broker) farm. Four
months after Server2 and Server3 are deployed, you discover that users can no longer
establish Remote Desktop sessions on Server3. You verify that Server3 is online and that
all required services on Server3 run properly. You verify that the users can establish
Remote Desktop sessions on Server2. You need to ensure that the users connecting to the
RD Connection Broker farm can establish sessions on Server3. What should you do?

Your network contains three servers that run Windows Server 2008 R2. The servers are
configured as shown in the following table. Server1 has Remote Desktop Services Per
Device client access licenses (RDS Per Device CALs) installed. Server2 and Server3 are
members of a Remote Desktop Connection Broker (RD Connection Broker) farm. Four
months after Server2 and Server3 are deployed, you discover that users can no longer
establish Remote Desktop sessions on Server3. You verify that Server3 is online and that
all required services on Server3 run properly. You verify that the users can establish
Remote Desktop sessions on Server2. You need to ensure that the users connecting to the
RD Connection Broker farm can establish sessions on Server3. What should you do?

A.
On Server3, enable dedicated farm redirection.

B.
On Server3, configure the Remote Desktop licensing settings.

C.
On Server1, install additional RDS Per Device CALs.

D.
On Server1, run the Manage RDS CALs wizard and click the Migrate action.



Leave a Reply 0

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