Remove Web Application Proxy Server From Cluster Official

How to Remove a Web Application Proxy Server from a Cluster Managing a Remote Access deployment often requires scaling your infrastructure down or replacing aging nodes. When using Web Application Proxy (WAP) in a cluster, simply shutting down a server isn't enough; you must gracefully remove it to maintain the integrity of your AD FS (Active Directory Federation Services) publishing environment.

WAP, particularly in Microsoft-centric environments (acting as a reverse proxy for Active Directory Federation Services - ADFS), is not a stateless load balancer. It holds specific configuration ties, certificate dependencies, and publishing rules. This guide provides a comprehensive, vendor-agnostic approach with specific emphasis on ADFS/WAP, NGINX, and HAProxy clusters.

Troubleshooting if the server still appears in the console after running the commands remove web application proxy server from cluster

Once the node is removed from the cluster's configuration, you must officially uninstall the role from the server itself to clean up local binaries and services. Using Server Manager:

Also, on the load balancer, confirm which VIP (Virtual IP) the target WAP serves. Remove the target from the load balancer’s pool now – but leave the server running. This redirects all live traffic to other cluster members. How to Remove a Web Application Proxy Server

Alternatively, you can remove it using the AD FS management console under Service > Web Application Proxies.

Connectivity to the other nodes in the cluster to ensure the configuration update propagates. Using Server Manager: Also, on the load balancer

: If using an external load balancer, remove the server's IP address from the backend pool. Certificates