Your company has an Active Directory domain. The company has a server named Server1 that has
the Remote Desktop Services server role and the RD Web Access role service installed. The company
has a server named Server2 that runs ISA Server 2006. The company deploys the Remote Desktop
Gateway (RD Gateway) role on a new server named Server3. The company wants to use ISA as the
SSL endpoint for Remote Desktop connections. You need to configure the RD Gateway role on
Server3 to use ISA 2006 on Server2. What should you do?
A.
Configure the RD Gateway to use SSL HTTPS-HTTP bridging.
B.
Configure the Remote Desktop Connection Authorization Policy Store on Server3 to use Server2 as
the Central Network Policy Server.
C.
Export the SSL certificate from Server2 and install the SSL certificate on Server3. Configure the RD
Gateway to use the SSL certificate from Server2.
D.
Export a self-signed SSL certificate from Server3 and install the SSL certificate on Server2.
Configure the ISA service on Server2 to use the SSL certificate from Server3.
Explanation:
To enhance security for an RD Gateway server, you can configure Microsoft Internet Security and
Acceleration (ISA) Server or a non-Microsoft product to function as a Secure Sockets Layer (SSL)
bridging device. The SSL bridging device can enhance security by terminating SSL sessions, inspecting
packets, and re-establishing SSL sessions. You can configure ISA Server communication with the RD
Gateway server in either of the two following ways:
HTTPS-HTTPS bridging. In this configuration, the RD Gateway client initiates an SSL (HTTPS) request
to the SSL bridging device. The SSL bridging device initiates a new HTTPS request to the RD Gateway
server, for maximum security. HTTPS-HTTP bridging. In this configuration, the RD Gateway client
initiates an SSL (HTTPS) request to the SSL bridging device. The SSL bridging device initiates a new
HTTP request to the RD Gateway server. To use HTTPS-HTTPS or HTTPS-HTTP bridging, you must
enable the Use SSL Bridging setting on the RD Gateway server. Source:
http://technet.microsoft.com/en-us/library/cc772387.aspx