And that, Leo thought, was the highest praise a guardian could receive. WAP-03 had served its purpose. And in the end, the greatest act of service was knowing when to gracefully step aside—even if stepping aside meant being unceremoniously unplugged at 2:00 AM.
# On the target WAP server Uninstall-WindowsFeature Web-Application-Proxy -Restart
Note: The -Restart switch will automatically reboot your server to finalize the uninstallation process. Method B: Via Server Manager GUI remove web application proxy server from cluster
Removing a Web Application Proxy server from a cluster is a straightforward process, but it requires precision to avoid service interruptions. Whether you use the or the Uninstall-WebApplicationProxy PowerShell cmdlet, always remember to update your external networking components (Load Balancers and DNS) to reflect the change.
echo "disable server wap_cluster/wap_node_02" | socat stdio /var/run/haproxy.sock And that, Leo thought, was the highest praise
Now, log in locally (or via iLO/iDRAC) to the WAP server being decommissioned.
Removing a Web Application Proxy server from a cluster is not a “click and forget” operation. It requires reverence for the identity pipeline that runs your business-critical SSO. By following this guide – draining traffic, revoking trust, removing the role, and validating the cluster – you ensure zero downtime and zero security regressions. Successfully removed server 'WAP-03'.
(If the cmdlet does not apply to your specific functional level, the WAP server will simply time out and drop off from active sync monitors without affecting operation.) 6. Step 5: Post-Removal Verification and Troubleshooting
Before removing any node, complete the following assessment to understand the impact.
Successfully removed server 'WAP-03'.