From Cluster [exclusive] | Remove Web Application Proxy Server

Verify that your infrastructure continues to work seamlessly without the removed node. Check Remaining WAP Nodes

By the end of this article, you will understand the prerequisites, the dismantling process, and the post-removal validation steps required to keep your cluster healthy.

"Sorry, old friend."

: Remove any host (A) records or service (SRV) records in your private and public DNS that point to the decommissioned server. Common Issues

Step 3: Remove the WAP Configuration (Optional but Recommended) remove web application proxy server from cluster

Ensure the remaining nodes in the cluster have sufficient capacity to handle the load of the removed server.

If your WAP server had a dedicated DNS record (e.g., wap2.contoso.com ), remove or archive it: Verify that your infrastructure continues to work seamlessly

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-WindowsFeature RemoteAccess, RSAT-RemoteAccess -Restart Use code with caution. Common Issues Step 3: Remove the WAP Configuration

Leo leaned back. Three years. The cluster didn't mourn. It adapted. That was its nature.

echo "disable server wap_cluster/wap_node_02" | socat stdio /var/run/haproxy.sock