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.
Open the Remote Access Management Console and delete any web applications published specifically through this node. Uninstall the Role:
We will execute removal in a specific order: . remove web application proxy server from cluster
Once traffic has bypassed the server, you can officially dissolve its relationship with the AD FS federation service. WAP removal is handled entirely via PowerShell. Log into the WAP server you want to remove. Open with elevated administrator privileges. Execute the deployment removal command: powershell Uninstall-WebApplicationProxy Use code with caution. What Happens During This Step? The local remote access configuration is deleted.
Run a synchronization check via PowerShell to guarantee configuration alignment with AD FS: powershell Update-WebApplicationProxyDeviceRegistration Use code with caution. Step 5: Post-Removal Cleanup Removing a web application proxy server from a
Assuming you have an active-passive or active-active cluster managed via a configuration management tool (Ansible, Puppet) or shared storage.
To ensure the cluster successfully updated its topology, verify the status from one of the WAP servers that will remain active. Log into a remaining WAP server in the cluster. Open as an Administrator. Execute the connection status command: powershell Get-WebApplicationProxyConfiguration Use code with caution. Open the Remote Access Management Console and delete
The process is not always smooth. Here are some of the most common issues and how to address them:
: Navigate to Manage > Remove Roles and Features , then uncheck Web Application Proxy and RAS Connection Manager Administration Kit (CMAK) . PowerShell : powershell