Remove Web Application Proxy Server From Cluster <Cross-Platform>

If the proxy node had a dedicated Virtual IP (VIP) using keepalived, handle the VRRP:

# For Windows WAP Get-WebApplicationProxyApplication | Select-Object ExternalURL, BackendServerURL, ExternalCertificateThumbprint If your cluster sits behind a hardware or software load balancer (F5, AWS NLB, HAProxy), verify the health probe settings. Does the balancer use a simple TCP handshake, or does it probe a specific URL ( /wap/health )? Removing the node before updating the LB will cause traffic to route to a black hole. Part 2: Graceful Quiescing – Draining the Traffic A hard shutdown is the enemy of production stability. You must "drain" the node. 2.1 Stop New Sessions (The "Drain" Step) Instruct the load balancer or the proxy itself to stop accepting new connections while finishing existing ones. remove web application proxy server from cluster

# Temporarily mark the server as down in the upstream block upstream backend_wan server 10.0.0.10:80; # Keep this server 10.0.0.11:80 down; # Mark removal node as down If the proxy node had a dedicated Virtual

Open PowerShell as Administrator on the target WAP server: Part 2: Graceful Quiescing – Draining the Traffic

Introduction: The Art of Surgical Infrastructure Removal