Configure extranet access for AD FS on Windows Server 2012 R2

Artikkeli
11/09/2015

Applies To: Azure, Office 365, Power BI, Windows Intune

This topic describes how to install the Remote Access role with the Web Application Proxy role service and how to configure the Web Application Proxy server to connect to an Active Directory Federation Services (AD FS) server.

2.2. Install the Remote Access role

To deploy Web Application Proxy, you must install the Remote Access role with the Web Application Proxy role service on a server that will act as the Web Application Proxy server.

Repeat this procedure for all of the servers that you want to deploy as Web Application Proxy servers.

To install the Web Application Proxy role service via the User Interface

On the Web Application Proxy server, in the Server Manager console, in the Dashboard, click Add roles and features.
In the Add Roles and Features Wizard, click Next three times to get to the server role selection screen.
On the Select server roles dialog, select Remote Access, and then click Next.
Click Next twice.
On the Select role services dialog, select Web Application Proxy, click Add Features, and then click Next.
On the Confirm installation selections dialog, click Install.
On the Installation progress dialog, verify that the installation was successful, and then click Close.

To install the Web Application Proxy role service via Windows PowerShel

The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.

The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.
```
  Install-WindowsFeature Web-Application-Proxy -IncludeManagementTools
```

2.3. Configure Web Application Proxy

You must configure Web Application Proxy to connect to an AD FS server.

Repeat this procedure for all of the servers that you want to deploy as Web Application Proxy servers.

To configure Web Application Proxy via the User Interface

On the Web Application Proxy server, open the Remote Access Management console: RAMgmtUI.exe, and then press ENTER. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
In the navigation pane, click Web Application Proxy.
In the Remote Access Management console, in the middle pane, click Run the Web Application Proxy Configuration Wizard.
On the Web Application Proxy Configuration Wizard, on the Welcome dialog, click Next.
On the Federation Server dialog, do the following, and then click Next:
- In the Federation service name box, enter the fully qualified domain name (FQDN) of the AD FS server; for example, fs.fabrikam.com.
- In the User name and Password boxes, enter the credentials of a local administrator account on the AD FS servers.
On the AD FS Proxy Certificate dialog, in the list of certificates currently installed on the Web Application Proxy server, select a certificate to be used by Web Application Proxy for AD FS proxy functionality, and then click Next.

The certificate you choose here should be the one that whose subject is the Federation Service name, for example, fs.fabrikam.com.
On the Confirmation dialog, review the settings. If required, you can copy the PowerShell cmdlet to automate additional installations. Click Configure.
On the Results dialog, verify that the configuration was successful, and then click Close.

To configure Web Application Proxy via Windows PowerShell

The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.

The following command will prompt you to enter credentials of a local administrator account on the AD FS servers.
```
Install-WebApplicationProxy –CertificateThumprint '1a2b3c4d5e6f1a2b3c4d5e6f1a2b3c4d5e6f1a2b' -FederationServiceName fs.fabrikam.com
```

Optimize congestion control settings between Web Application Proxy and the AD FS servers – optional step

The extranet facing Web Application Proxy is able to throttle requests from the extranet if the latency between the Web Application Proxy and the federation server increases beyond a certain threshold. Based on this feature, the Web Application Proxy will reject external client authentication requests if the federation server is overloaded as detected by the latency between the Web Application Proxy and the federation server to service authentication requests. It is closely related to a similar algorithm employed for congestion control in TCP known as Additive Increase Multiplicative Decrease (AIMD). The solution works by using a congestion window represented by a pool of tokens that it leases out to each incoming request to the Web Application Proxy.

In a high latency DMZ network or a highly loaded Web Application Proxy, it is possible for authentication requests to be rejected even if the federation server can satisfy these requests successfully based on the default settings that control this algorithm. In such an environment, we strongly recommend modifying the settings to be less aggressive by performing the following steps.

On your Web Application Proxy computer, start an elevated command window.
Navigate to the ADFS directory, at %WINDIR%\adfs\config.
Change the congestion control settings from its default values to ‘<congestionControl latencyThresholdInMSec="8000" minCongestionWindowSize="64" enabled="true" />’.
Save and close the file.
Restart the AD FS service by running ‘net stop adfssrv’ and then ‘net start adfssrv’.

Next step

Now that you have verified that you have configured Web Application Proxy computers, the next step is to Install Windows PowerShell for single sign-on with AD FS.

Jaa