To remove a Web Application Proxy (WAP) server from a cluster, you must update the ConnectedServers list in the proxy configuration and then decommission the role from the physical server. 1. Remove the Server from the Cluster List
This guide provides a step-by-step walkthrough on how to properly remove a Web Application Proxy server from a cluster using both the graphical interface and PowerShell. Prerequisites Before you begin, ensure you have:
This method ensures the trust relationship between the WAP server and the internal AD FS farm is cleanly revoked before the server is taken offline. remove web application proxy server from cluster
Removing a Web Application Proxy (WAP) server from a cluster involves both decommissioning the role on the specific server and ensuring the remaining cluster "forgets" the removed node. If a server is simply shut down or the role is uninstalled without updating the cluster configuration, it may still appear as a "ghost" entry in management consoles. 1. Remove the Server from the Cluster List
Watch the logs in real-time to confirm traffic has stopped. To remove a Web Application Proxy (WAP) server
View current servers:Get-WebApplicationProxyConfiguration | Select-Object -ExpandProperty ConnectedServersName
Even after role removal, some artifacts persist. Delete manually: Prerequisites Before you begin, ensure you have: Method
Update the cluster list:Run this command to keep only the servers you want. Replace the names in the list with your actual healthy servers. powershell
If you are completely retiring the server, follow these steps to ensure a clean removal: