Installing a Web Application Proxy (WAP) server consists of two distinct actions. The first is installing the Remote Access role, and the second is to then configure the role. The act of configuring Remote Access enables WAP to function as an AD FS proxy, and optionally enables you to also publish other applications.
Over time some of those servers may have been replaced without fully uninstalling them, for example if the server failed and was rebuilt. Or new nodes were added and the old ones just powered off. You may end up with a list that looks like the screenshot below.
Note that some servers are duplicated as they were rebuilt. Time to tidy that up!
This is straightforward. Once you know the server(s) that you have to remove, the below command will help.
In newer builds of AD FS, we can list the WAP servers using PowerShell.
(Get-WebApplicationProxyConfiguration).ConnectedServersName
This lists all of the known servers. Time to clean up the list!
Update WAP Server List
Only two WAP servers are actually meant to be in the list, so we specify them in using Set-WebApplicationProxyConfiguration.
Set-WebApplicationProxyConfiguration –ConnectedServersName Tail-CA-WAP-19.tailspintoys.ca, Tail-CA-STS-P.Tailspintoys.ca
Note that we then enumerate the list, and only two are now present.
Cheers,
Rhoderick
