WAP server to ensure the cluster no longer attempts to communicate with the decommissioned node. View current cluster members: powershell
Ensure the remaining WAP servers are healthy, synchronized, and capable of handling the redirected traffic.
Alternatively, you can remove the proxy trust via PowerShell on the AD FS server: powershell Remove-AdfsWebApplicationProxy -HostName "WAP-Server-FQDN" Use code with caution. Step 4: Update DNS and Load Balancer Settings
In the sub-features, ensure is selected for removal. Complete the wizard and restart the server if prompted. 3. Cleaning Up AD FS Relying Party Trusts remove web application proxy server from cluster
: Get-WebApplicationProxyConfiguration | Select-Object -ExpandProperty ConnectedServersName
: If the server name persists in the Remote Access Management console after uninstalling the role, it is because the "primary" node still has it in its configuration list. Re-running the Set-WebApplicationProxyConfiguration command from a healthy node usually fixes this.
How to Remove a Web Application Proxy Server from a Cluster Removing a Web Application Proxy (WAP) server from an Active Directory Federation Services (AD FS) farm deployment requires careful execution to avoid user downtime. This step-by-step guide explains how to cleanly decommission a WAP node, update your network infrastructure, and verify that your external access remains stable. 1. Pre-Removal Checklist WAP server to ensure the cluster no longer
This returns the fully qualified domain names (FQDNs) of all servers currently recognized as part of the WAP cluster. 2. Logical Removal from the Cluster
Remove-WebApplicationProxyServer
Every environment is unique, and the commands for your specific software stack may differ. Always refer to the official documentation for your platform and test the removal in a non-production environment first. If you run into issues, consult the vendor's support channels or their community forums for targeted assistance. Step 4: Update DNS and Load Balancer Settings
On an internal AD FS server, use PowerShell to forcibly remove the orphaned entry:
Before removing a WAP server from a cluster, consider the following: