If you are completely dismantling the WAP infrastructure rather than just removing one node, you may need to remove the proxy trust on the AD FS side. Remove-AdfsWebApplicationProxyRelyingPartyTrust .
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.
Only do this if you intend to block all external access through proxies or are rebuilding the trust from scratch. Summary Checklist Update Cluster List PowerShell ( Set-WAPConfig ) Prevents "Server Down" errors in the management console. Uninstall Role Server Manager Frees up system resources and removes the WAP service. Cleanup DNS DNS Manager remove web application proxy server from cluster
Use the following command to filter out the decommissioned server (replace 'ServerToRemove' with the FQDN of the node you are removing): powershell
Managing a high-availability environment often requires scaling back or replacing aging infrastructure. When you need to , simply turning off the machine isn't enough; the configuration will still exist in the AD FS database, leading to management errors and synchronization issues. If you are completely dismantling the WAP infrastructure
This guide outlines the standard procedures to gracefully decommission a WAP node using PowerShell and Server Manager. 1. Removing the WAP Node via PowerShell
Open Server Manager and click > Remove Roles and Features . Select the target server and uncheck Remote Access . Only do this if you intend to block
In the sub-features, ensure is selected for removal. Complete the wizard and restart the server if prompted. 3. Cleaning Up AD FS Relying Party Trusts