Locate the backend pool for your web application proxy cluster. Set the target WAP server status to or Disabled . Monitor active connections until they drop to zero. Step 2: Uninstall Web Application Proxy via PowerShell
server from a cluster involves both logical removal from the configuration and physical uninstallation of the server role. Whether you are decommissioning an old server or troubleshooting a duplicate entry, following a clean removal process ensures your Active Directory Federation Services (AD FS) farm remains healthy. 1. Identify the Server to Remove
Get-EventLog -LogName "Web Application Proxy" -Newest 10
Confirm the server is removed from the backend pool and the load balancer shows "Healthy" for remaining nodes. remove web application proxy server from cluster
Select . This allows existing connections to finish while blocking new requests. For Hardware Load Balancers (F5, Citrix ADC, Kemp) Log into your load balancer management console. Mark the target WAP server as Disabled or Drain . Monitor active connections until they reach zero. Step 2: Remove the Server via PowerShell
To guarantee that your infrastructure remains stable and fully functional after the removal, perform the following validation checks:
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. Locate the backend pool for your web application
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.
Delete the or AAAA records pointing to the IP address of the removed WAP server. Revoke or Reclaim SSL Certificates If the WAP server is being permanently decommissioned: Open certlm.msc (Local Computer Certificates).
Change the status of the target WAP node to or Disabled . Monitor active connections until they drop to zero. Step 2: Uninstall Web Application Proxy via PowerShell
You must have Local Administrator permissions on the WAP server and sufficient privileges on the AD FS server to modify the configuration.
simply reinstall Windows on the same hostname and rejoin it to the cluster without first removing the trust. A reused hostname with an orphaned trust will cause a “duplicate proxy” error during reconfiguration.
To ensure no "ghost" settings remain, perform these final checks: DNS Entries