Remove Web Application Proxy Server From Cluster _best_ Jun 2026

Removing a Web Application Proxy from a cluster is straightforward but requires careful sequencing to avoid service disruption. The key steps are:

On any AD FS server (or using AD FS management tools):

WAP relies on SSL certificates. Ensure the node you are removing does not hold a unique, non-exportable private key that isn’t stored elsewhere. Check the thumbprint:

Click in the top right corner and select Remove Roles and Features . Click Next until you reach the Server Roles page. Uncheck Remote Access . remove web application proxy server from cluster

If the server has already been decommissioned or if you just want to remove its entry from the management console's cluster list, use the following commands on a remaining healthy WAP server:

On the remaining WAP servers, open Event Viewer > Applications and Services Logs > Microsoft > Windows > WebApplicationProxy > Admin . Watch for Event ID 12006 or synchronization errors that indicate the cluster is looking for the missing node.

Uninstall-WindowsFeature Web-Application-Proxy, CMAK, RSAT-RemoteAccess ``` Use code with caution. Copied to clipboard Via Server Manager (GUI) Server Manager and select Remove Roles and Features Select the server and uncheck the Remote Access Confirm the removal of features and click 3. Post-Removal Cleanup Load Balancers Removing a Web Application Proxy from a cluster

Uninstall-WindowsFeature -Name Web-Application-Proxy, DirectAccess-VPN -IncludeManagementTools -Restart Use code with caution.

To remove a Web Application Proxy (WAP) server from a cluster, you can use PowerShell to update the ConnectedServersName

Removing a web application proxy server from a cluster is not merely a matter of turning off a switch. It is a process of . The difference between a professional team and an amateur one is visible in the post-removal state. Check the thumbprint: Click in the top right

For native WAP clustering without external LB, use Windows Network Load Balancing (NLB) or DNS round-robin:

# On the node being removed systemctl stop keepalived systemctl disable keepalived