
Despite careful removal, issues can arise. Here’s how to handle them:
Note: You can also use a filter to remove a specific name from the current list automatically: powershell
Verify the hostname of the specific WAP server you want to remove and confirm the status of the remaining nodes.
Run the following command to uninstall the Remote Access feature: powershell
In modern enterprise architecture, Web Application Proxy (WAP) servers are critical components for providing secure, reverse-proxy access to internal applications. Often deployed in clusters for high availability, there comes a time when a server needs to be removed—whether for decommissioning, hardware upgrades, or maintenance. remove web application proxy server from cluster
How to Remove a Web Application Proxy Server from a Cluster Removing a Web Application Proxy (WAP) server from a deployment cluster requires careful execution. A clean removal prevents configuration sync errors and maintains active directory federation services (AD FS) stability. Pre-Removal Checklist
He typed the command. The screen flickered.
Navigate to the pool or virtual server handling external AD FS traffic. Locate the node matching the WAP server you want to remove.
Once traffic drops to zero, remove the node entirely from the pool. For Windows Network Load Balancing (NLB) Despite careful removal, issues can arise
Alternatively, use PowerShell on the AD FS server to verify active proxy connections: powershell Get-AdfsProxyProperties Use code with caution. Step 4: Post-Removal Verification
When removing a WAP server from a cluster, follow these best practices:
In the Microsoft identity ecosystem, the serves as the reverse proxy and security gateway for Active Directory Federation Services (AD FS) . It sits in the perimeter network (DMZ), protecting on-premises AD FS servers from direct exposure to the internet.
Set-WebApplicationProxyConfiguration -ConnectedServersName "HealthyServer1.domain.com", "HealthyServer2.domain.com" Use code with caution. Copied to clipboard Often deployed in clusters for high availability, there
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.
Permanently delete the removed server's IP address from your load balancer pools or Windows NLB cluster configuration. Leaving it in place can cause intermittent connection errors if the load balancer attempts health checks on a dead node. Clean Up AD FS Trust Relationships
You must have Local Administrator permissions on the WAP server and sufficient privileges on the AD FS server to modify the configuration.
Set-WebApplicationProxyConfiguration -ConnectedServersName ((Get-WebApplicationProxyConfiguration).ConnectedServersName -ne 'ServerToRemove.domain.local') Use code with caution. Copied to clipboard Option 2: Using Server Manager (Full Role Uninstallation)