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?

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.

Explanation:
You must configure RD Licensing correctly in order for your RD Session Host server to accept
connections from clients. To allow ample time for you to deploy a license server, Remote Desktop
Services provides a licensing grace period for the RD Session Host server during which no license
server is required. During this grace period, an RD Session Host server can accept connections from

unlicensed clients without contacting a license server. The grace period begins the first time the RD
Session Host server accepts a client connection.
A permanent RDS CAL is issued by a license server to a client connecting to the RD Session Host
server.
The number of days in the grace period is exceeded.
The length of the grace period is based on the operating system running on the RD Session Host
server.
The grace periods are as follows:
Source: http://technet.microsoft.com/en-us/library/cc725933.aspx