OPERATIONAL DEFECT DATABASE
...
...
Sometimes, instant clone provisioning leads to the creation of cp-parent VMs on all hosts in the selected cluster. The cp-parent VMs are tied to the host they are on and cannot be migrated through the vSphere client. This prevents the host from entering maintenance mode if initiated from the vSphere client.If your environment does not rely on VUM (VMware Update Manager) to upgrade your ESXi hosts, this issue does not occur if you have deployed Horizon 7.1 or later. On those versions, when you put the host in maintenance mode, vSphere will automatically remove the instant clone cp-parent VMs. If your environment does rely on VUM to upgrade your ESXi hosts and you are using Horizon 7.13 or Horizon 8 (all versions), you can globally disable all of the instant clone cp-parent VMs in a vCenter so that VUM can update the ESXi hosts in that vCenter. For steps on how to globally disable, see https://docs.vmware.com/en/VMware-Horizon/2106/virtual-desktops/GUID-7C5BB17B-D239-4779-B2CA-B9AD9C72CDB7.html . If you use VMware Update Manager, we recommend that you always keep the instant clone cp-parent VMs disabled for your vCenter to simplify your ESXi maintenance. Disabling cp-parent VMs for you vCenter instructs Horizon to choose to deploy instant clone pools without cp-parentVMs (and to delete any cp-parentVMs that already exist). It might slow down the provisioning speed of instant clones a bit, but does not impact the functionality of instant clones. If you use VUM and you are on an older Horizon release, follow the remainder of this KB for manual steps.
You can use either of the following methods to put a host in and out of maintenance mode.Method 1. From vSphere Client Select the host that you want to put in maintenance mode. If you are using the vSphere web client, make sure that the plug-in to edit Annotations is installed.Look up Annotations in the host's Summary tab and set InstantClone.Maintenance to 1.Wait up to 3 minutes and the cp-parent VMs on this host will be deleted. Also, the value for InstantClone.Maintenance will change to 2.Put the host in maintenance mode. This host will no longer be used for provisioning.Perform maintenance.Take the host out of maintenance mode.Clear the InstantClone.Maintenance annotation value.As new provisioning happens, cp-parent VMs and then instant clones will be created on this host. Method 2. From Connection Server From the Connection Server, run IcMaint.cmd to delete the cp-parent VMs and put the host in maintenance mode. See The syntax is: -vc host name or IP address of vCenter Server -uid vCenter Server user ID-hostname ESXi host name-maintenance ON|OFF IcMaint.cmd -vc <VC host name or IP> -uid <user ID> -password <user password> -hostName <ESXi host name> -maintenance ON Note: This command deletes the cp-parent VMs from the host. The host is not automatically put into maintenance mode. To perform maintenance on the host, the vCenter server administrator must manually put the host into maintenance mode.Wait up to 3 minutes and the cp-parent VMs on this host will be deleted.Perform maintenance.Run IcMaint.cmd again to take the host out of maintenance mode. The syntax is: IcMaint.cmd -vc <VC host name or IP> -uid <user ID> -password <user password> -hostName <ESXi host name> -maintenance OFFAs new provisioning happens, cp-parent VMs and then instant clones will be created on this host. For translated versions of this article, see: 日本語: Horizon インスタント クローンを持つ ESXi ホストのメンテナンス モードの切り替え (2145513) 简体中文: 进入和退出具有 Horizon 即时克隆的 ESXi 主机的维护模式 (2145530)
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
