"No supported hosts found for remediate" error during an ESX/ESXi host remediation
search cancel

"No supported hosts found for remediate" error during an ESX/ESXi host remediation


Article ID: 308614


Updated On:


VMware vCenter Server VMware vSphere ESXi


  • The ESX/ESXi host remediation using VMware vCenter Update Manager fails.
  • You see the error:
No supported hosts found for remediate

The operation is not supported on the selected Inventory objects.
Check the events for the objects selected for the operation.
  • In the C:\Documents and Settings\All Users\Application Data\VMware\Update Manager or C:\Users\All Users\VMware\VMware Update Manager\Logs\vmware-vum-server-log4cpp.log file, you see an entry similar to:

    "[DATE'VciHostRemediateTask.VciHostRemediateTask{14}' 2276 INFO] [vciHostRemediateTask, 1313] Skipping [HostName] as it is part of HAC enabled cluster"
  • When trying to remediate an ESX host, it may fail with the error:

    There are errors during the remediation operation. Check the Tasks and Events tab and log files for details.
  • Remediate entry in Events, you see the error:

    Cannot remediate host "hostname" because it is a part of a HA admission control enabled cluster.


VMware vCenter Update Manager 6.0.x
VMware ESXi 4.1.x Installable
VMware ESXi 4.0.x Installable
VMware vCenter Update Manager 4.0.x
VMware vCenter Update Manager 5.5.x
VMware vSphere ESXi 6.0
VMware vCenter Update Manager 5.1.x
VMware vSphere ESXi 5.5
VMware ESXi 4.1.x Embedded
VMware vSphere ESXi 6.5
VMware vSphere ESXi 5.0
VMware vCenter Update Manager 6.5.x
VMware ESX 4.1.x
VMware vSphere ESXi 5.1
VMware ESX 4.0.x
VMware ESXi 4.0.x Embedded
VMware vCenter Update Manager 4.1.x
VMware vSphere ESXi 6.7
VMware vCenter Update Manager 5.0.x


This issue occurs because the admission control policy that is set is preventing vCenter Update Manager from remediating the host.

vCenter Server uses admission control to ensure that sufficient resources are available in a cluster to provide failover protection and to ensure that virtual machine resource reservations are respected. Admission control imposes constraints on resource usage and any action that would violate these constraints is not permitted. If an automated process needs to take actions, it may temporarily violate the failover constraints. For example, as part of an upgrade directed by VMware vCenter Update Manager.


To resolve this issue, you can either disable strict admission control or disable VMware HA altogether, put the ESX/ESXi host in the maintenance mode, and then continue with the upgrade.
To disable strict admission control:
  1. Right-click the cluster and click Edit Settings.
  2. Under Cluster Features, click VMware HA.
  3. Under Admission Control, select Disable: Power on VMs that violate availability constraints.
  4. Click OK.
To disable VMware HA:
  1. Right-click the cluster and click Edit Settings.
  2. Under Cluster Features, select Turn off VMware HA.
  3. Click OK.

After the ESX/ESXi host is successfully remediated, re-enable VMware HA on the cluster in the event of future host failovers.

Additional Information

Note: If you do not want to disable the strict admission control or HA at the cluster level, use this alternative workaround to resolve the issue.
  1. Create a new Test Cluster in the Datacenter.
  2. Move the ESX host being remediated into the new Cluster.
  3. Remediate the host.
  4. If the remediation completes successfully, the ESX host can now be moved back into the original HA cluster.
ESX/ESXi ホスト修正が次のエラーで失敗する: No supported hosts found for remediate(修正がサポートされているホストが見つかりません)
ESX/ESXi 主机修复失败,并显示以下错误:未找到用于修复的受支持主机