Set-WebApplicationProxyConfiguration -ConnectedServersName ((Get-WebApplicationProxyConfiguration).ConnectedServersName -ne 'ServerToRemove.domain.local') Verify the update: Get-WebApplicationProxyConfiguration WordPress.com Method 2: Decommission the Server Node
$updatedServers = (Get-WebApplicationProxyConfiguration).ConnectedServersName | Where-Object $_ -ne "://domain.com"
Get-WebApplicationProxyConfiguration
Perform the following checks:
In IBM WebSphere environments, you can use the administrative console of the job manager or the deployment manager to delete a proxy server from managed targets. The steps involve choosing the "Delete proxy server" job, specifying the job targets (like a specific node name), naming the proxy server to delete (e.g., proxy_server_2 ), and scheduling the job. The job stops the proxy server, if running, and removes it from the flexible management environment. Additionally, the "Proxy server cluster member collection" page allows you to view and manage proxy cluster members, including the option to delete a member. remove web application proxy server from cluster
Remove-ADFSWebApplicationProxy -Name "WAP-Server-01"
Do you plan to this server or delete the VM entirely? Share public link
# Temporarily mark the server as down in the upstream block upstream backend_wan server 10.0.0.10:80; # Keep this server 10.0.0.11:80 down; # Mark removal node as down
Retrieve the list of connected proxy servers to find the exact name: powershell Get-AdfsWebApplicationProxyRelyingPartyTrust Use code with caution. %windir%\system32\inetsrv\appcmd
%windir%\system32\inetsrv\appcmd.exe list config /section:webFarms > C:\Backup\webfarm.txt
This section varies significantly by technology stack. Follow the instructions that match your infrastructure.
A Web Application Proxy cluster enhances scalability and fault tolerance. By using a load balancer (such as Azure Load Balancer, F5, or Kemp) in front of multiple WAP servers, traffic is distributed, ensuring that if one server fails, others continue to handle requests.
Always document and export your current publishing rules before making infrastructure shifts. Run the following PowerShell command on the WAP node you plan to remove to log its unique configuration: powershell traffic is distributed
: Force the local cleanup by adding the force parameter if available in your environment, or manually strip the registry keys located under HKLM\Software\Microsoft\Windows NT\CurrentVersion\RemoteAccess\ . High CPU or Error Spikes on Remaining Nodes
After completing the removal, verify that the proxy has been removed and that the cluster is healthy.
If you used Round-Robin DNS instead of a dedicated load balancer, open your DNS Manager ( dnsmgmt.msc ) and delete the A or AAAA records pointing the external federation service URL (e.g., ://company.com ) to the IP address of the removed WAP server.
netstat -an | find ":443" | find /c "ESTABLISHED"
: Run the following PowerShell command to remove the WAP role and related features: powershell