Remove Web Application Proxy Server From Cluster Jun 2026

Instantly, the average response time for the payment API dropped from 340ms to 190ms. A 44% improvement. The error rate fell to 0.001%.

That's when I saw it. For the last 72 hours, wap-03 had been silently receiving packets from an old, forgotten monitoring script on a decommissioned jump box. Every five seconds, the script sent a malformed health check: GET / HTTP/1.1\r\nHost: \x00\x00 . wap-03 was spending 30% of its CPU trying to parse null bytes.

A cluster is only as strong as its weakest node. Redundancy isn't about keeping every machine breathing; it's about keeping the right machines healthy. Sometimes, removing a server isn't a loss of capacity—it's an amputation of a chronic disease. remove web application proxy server from cluster

Delete any A records or CNAMEs specific to this individual node’s IP address if they were used for management or direct routing.

If the server is "dead" and cannot run the uninstall command, you must manually remove the stale entry from the AD FS configuration. This is typically done on the AD FS primary server using the Remove-AdfsWebApplicationProxy cmdlet followed by the name of the defunct server. Instantly, the average response time for the payment

Remove-Item -Path "C:\ProgramData\Microsoft\Web Application Proxy\Configuration" -Recurse -Force

In the realm of modern IT infrastructure, high availability and redundancy are paramount. Web Application Proxy (WAP) servers, often deployed in conjunction with Active Directory Federation Services (AD FS), serve as the critical gatekeepers between the external internet and your internal corporate resources. That's when I saw it

Test-WebApplicationProxyApplication -ExternalUrl "https://mail.yourdomain.com" -Verbose

Removing a node without prepping these dependencies is like pulling a card from a house of cards.

The business didn't see 0.5%. They saw "99.95% uptime." But I saw the angry tweets. I saw the support tickets: "Card declined. Please try again." Those weren't bank declines. Those were wap-03 swallowing the requests whole.

The most reliable method to remove a "ghost" or decommissioned server from the cluster list is to manually update the ConnectedServersName property on an active node.