Remove Web - Application Proxy Server From Cluster Hot!

Before running any removal commands, complete these preparatory steps to avoid downtime and administrative errors.

Run the following command to remove the Remote Access and Web Application Proxy features, followed by a deployment-safe restart: powershell

Open an elevated PowerShell console on the server to be removed. Execute the following command to remove the server from the Web Application Proxy configuration:

If you prefer a visual interface, use the standard Windows Server utility. Open . remove web application proxy server from cluster

If you are using Windows Network Load Balancing (NLB), open the Network Load Balancing Manager and delete the host from the cluster. If you use a dedicated hardware load balancer, permanently delete the node from the pool/VIP configuration. 2. Verify Remaining Node Synchronization

Ensure the remaining nodes in the WAP cluster are healthy and synchronized. You can check the current deployment status by running this PowerShell command on any operational WAP node: powershell Get-WebApplicationProxyConfiguration Use code with caution. Update Load Balancer Configurations

Sometimes, the Remote Access management database retains metadata about the removed server. Clean this up from a remaining cluster node. Log into a WAP server in the cluster. Open PowerShell as an Administrator. undergoes hardware retirement

Event ID 374, 381 Cause: A load balancer or DNS still points to the removed WAP IP. Fix: Remove A/PTR records from DNS. Flush ARP cache on the load balancer. Use netsh int ipv4 show neighbors to verify ARP entries.

If the Uninstall-WebApplicationProxy command fails or hangs, the local synchronization database might be corrupted, or communication with the AD FS server may be blocked.

Ungraceful removal can cause connection resets for users and load balancer errors. Update Load Balancer Configurations Sometimes

Check active connections every 60 seconds:

How to Remove a Web Application Proxy Server from a Cluster Web Application Proxy (WAP) servers provide secure remote access to internal web applications and Active Directory Federation Services (ADFS). When a WAP server becomes unhealthy, undergoes hardware retirement, or requires a clean operating system reinstall, you must safely remove it from the load-balancing cluster.

Ensure network ports 443 and 49443 are open between the WAP server and the AD FS servers. If network paths are already dead, you can force-uninstall the Remote Access role via Server Manager or use PowerShell to remove the deployment feature directly: Remove-WindowsFeature RemoteAccess -IncludeManagementTools . Issue: Remaining Nodes Report Sync Failures