Web Application Proxy: This server is not included in the ConnectedServersName list
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 |
Warning |
Category |
Configuration |
Issue
This server is not included in the ConnectedServersName list.
Impact
The Remote Access Management console may not work as expected.
Resolution
Use the Set-WebApplicationProxyConfiguration cmdlet to add this server to the ConnectedServersName list.
All Web Application Proxy servers must be included in the ConnectedServersName list, otherwise they will not appear in the Remote Access Management console and attempts to change or configure published applications may result in unexpected behavior. You can manually configure the ConnectedServersName list only using Windows PowerShell.
Membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.
To add a server to the ConnectedServersName list
On the Web Application Proxy server, open a Windows PowerShell window.
Use the following command to view the current ConnectedServersName list:
Get-WebApplicationProxyConfiguration
Copy the current ConnectedServersName list to the clipboard.
Run the following command to add a server to the ConnectedServersName list:
Set-WebApplicationProxyConfiguration –ConnectedServersName <paste-existing-list-here>,<new_server_name>.<domain_name>
Note
You must provide the existing list of connected servers, and then add each new server as a comma-separated list for this command to be effective.