Remove Web Application Proxy Server From Cluster ((new))
Before initiating the removal, perform these essential steps:
Ensure the remaining WAP servers are properly communicating and that their configuration is consistent.
If you are completely retiring the server, follow these steps to ensure a clean removal:
This guide outlines the standard procedures to gracefully decommission a WAP node using PowerShell and Server Manager. 1. Removing the WAP Node via PowerShell remove web application proxy server from cluster
Open the on your primary AD FS server. Navigate to Trust Relationships or check the proxy monitoring views to verify that the active proxies are checking in normally and the removed server is no longer expected by the federation service. 4. Cleanup DNS Records
Log into one of your remaining production WAP servers and run a manual configuration sync to ensure the cluster database updated correctly: powershell Update-WebApplicationProxyDeviceRegistration Use code with caution.
On the WAP server you want to remove, open an elevated PowerShell window (Run as Administrator). Execute the deployment removal command: powershell Uninstall-WebApplicationProxy Use code with caution. What This Command Does: Unpublishes all web applications from this specific node. Deletes the local operational settings. Removing the WAP Node via PowerShell Open the
Reload NGINX gracefully: nginx -s reload . Existing persistent connections will finish; new ones bypass it.
: Export the current WAP configuration via PowerShell.
In Kubernetes-based platforms, proxy configuration is often managed through cluster-wide settings or proxy manifests. The standard approach is to clear the proxy settings, not to delete the cluster object, as the object itself cannot be deleted. Cleanup DNS Records Log into one of your
Set-WebApplicationProxyConfiguration -ConnectedServersName ((Get-WebApplicationProxyConfiguration).ConnectedServersName -ne 'ServerToRemove.domain.local') Verify the update: Get-WebApplicationProxyConfiguration WordPress.com Method 2: Decommission the Server Node
Once you confirm 24–48 hours of error-free operation, you can safely delete the virtual machine or repurpose the physical hardware from your environment. To help tailor any further cleanup steps, tell me:
To ensure long-term environment health, complete these final maintenance steps across your network infrastructure: 1. Active Directory and DNS Clean Up
The most direct way to remove a specific server from the WAP cluster list is through PowerShell. This method updates the ConnectedServersName property across the entire cluster. Log into a different, active WAP server in the cluster. Open PowerShell as an Administrator.
From an external client (not internal corporate network), test your primary application URLs: