다음을 통해 공유

Web Application Proxy must be configured before it is used

  • 아티클

 

Applies To: Windows Server 2012 R2

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Web Application Proxy Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.

Operating System

Windows Server 2012 R2

Product/Feature

Web Application Proxy

Severity

Error

Category

Configuration

Issue

Web Application Proxy was installed but not configured for initial use.

Impact

If Web Application Proxy is not configured it cannot be used to publish applications.

Resolution

Use ‘Remote Access Management’ in Server Manager to start the configuration wizard or use the Install-WebApplicationProxy PowerShell command. 

After installing the Web Application Proxy role service on a server, you must also configure Web Application Proxy on the server. If you do not configure Web Application Proxy, you will be unable to publish applications and the Web Application Proxy server will not provide AD FS proxy functionality.

Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.

To configure Web Application Proxy

  1. On the Web Application Proxy server, open the Remote Access Management console: On the Start screen, click the Apps arrow. On the Apps screen, type 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.

  2. In the navigation pane, click Web Application Proxy.

  3. In the Remote Access Management console, in the middle pane, click Run the Web Application Proxy Configuration Wizard.

  4. On the Web Application Proxy Configuration Wizard, on the Welcome dialog, click Next.

  5. 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.contoso.com.

    • In the User name and Password boxes, enter the credentials of a local administrator account on the AD FS servers.

  6. 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.

  7. On the Confirmation dialog, review the settings. If required, you can copy the PowerShell cmdlet to automate additional installations. Click Configure.

  8. On the Results dialog, verify that the configuration was successful, and then click Close.