If the server is domain-joined and will never return:
On a remaining WAP node, run this command to ensure the cluster recognizes the change: powershell Get-WebApplicationProxyConfiguration Use code with caution. Monitor Event Logs
If using the native Windows NLB feature, open PowerShell as an Administrator on any cluster node and run: powershell Stop-NlbClusterNode -NodeName "WAP-Server-To-Remove" Use code with caution.
Remove-AdfsWebApplicationProxy -TargetWebApplicationProxy <ProxyObject> remove web application proxy server from cluster
Set-WebApplicationProxyConfiguration -ConnectedServersName "://domain.com" Use code with caution. Copied to clipboard
Simply uninstalling the role from the server does not automatically remove it from the cluster's configuration list, which often leads to orphaned entries in the management console. 🛠️ Removal Process 1. Identify Current Nodes
Complete these final operational hygiene steps to finish decommissioning the asset: If the server is domain-joined and will never
Run the following deployment command to remove the role and its management tools: powershell
From an external device outside your corporate network, navigate to your AD FS sign-in page (e.g., https://domain.com ) to ensure the remaining proxy servers handle authentication successfully.
Before initiating the removal, ensure the following steps are taken to mitigate risk: Copied to clipboard Simply uninstalling the role from
: Execute the following, replacing '://domain.com' with the target FQDN: powershell
Leo pulled up the admin console. A simple command stared back at him: Remove-WAPServer -ClusterNode WAP-03 . His finger hovered over the Enter key.
Once the server is no longer handling traffic, remove the role. Open . Click Manage > Remove Roles and Features . Uncheck Web Application Proxy . Complete the wizard and restart the server. 4. Post-Removal Verification
Step 2: Uninstall the Web Application Proxy Role via PowerShell
The removed server should not appear.