Remove ESXi host from vCenter greyed out

[tmdv]

Environment:

VMware ESXi, 6.7.0, 15160138

vCenter: 6.7.0.41000 build number: 14836122

We cannot remove one crashed VMware host from our datacenter. We do not have any clusters configured. We do have a vDS. Other hosts are working fine and in production. Remove from inventory is greyed out in vCenter.

The following action I already tried:

Disconnect the host (succesfully)

Remove host from vDS (succesfully)

Remove from inventory is greyed out

Used PowerCLI but came with this error:

Remove-VMHost : 21-4-2020 08:23:16      Remove-VMHost           The method is disabled by 'com.vmware.vcIntegrity'

At line:1 char:1

+ Remove-VMHost ESXVN0XX.FQDN

Any ideas?

[IRIX201110141]

What was the solution?

The "com.vmware.vcIntegrity" referrers to VMware Update Manager.

Regards,

Joerg

[tmdv · Accepted solution]

Well the solution was to reboot vcenter. After this I was able to remove the ESX host from the inventory. However I do think it is a bug.

[tpman]

Same problem, same solution, same opinion...this is a bug.  Thanks tmdv​

[Jeff_CH]

Hi,

I had the same issue and was able to remove the host without rebooting the vCenter:

- Disconnect the host

- Create a new cluster

- Move the disconnected host to the newly created cluster

- Delete newly created cluster

Cheers

[FernandesSelwyn]

I had this issue as well when performing some migration with moving hosts in between clusters. I used the following with powershell after you connect to your vCenter

$vDC = get-datacenter

#Move to offending host to the root datacenter so it's not part of a cluster

get-vmhost esx01* | move-vmhost -destination $vDC

#Remove it from inventory with no wait... or remove the confirm flag to get prompted. 

get-vmhost esx01* | remove-vmhost -confirm:$false

As i had to do this to a number of hosts, you can either pass a comma separated list of host

[HostaHost]

Just ran into this same issue on a VCSA 7.0.2 HA cluster; host that had been in maint mode went down for retirement, could not remove.  I had to HA fail VCSA over to the passive to get it to let me remove it.

Good quality stuff...

[MCollauto]

Like other people said: Same problem, same solution, same opinion...this is a bug. 😉

[SysadminCFch]

SameSame -> Same problem, same solution, same opinion...this is a bug.

[zwy123]

I quite agree with you on this point. Thank you

[RuslanPRO]

not necessarily new cluster, it could be new or some exist folder. - its work to.

[mtaylor_lfcu]

This worked well for me. Thanks!

[filipe_dias]

Yes!
That´s the solution!