Cluster has vSphere Configuration Profiles (VCP) enabled on a non-supported vCenter version or non-supported ESXi host versions for HOST. Please make sure cluster has vSphere Configuration Profiles (VCP) enabled on a supported vCenter version, or ESXi hosts with supported version, or disabled vSphere Configuration Profiles (VCP) on the cluster.
vSphere Configuration Profiles (VCP) is an architectural state that, once enabled on a cluster, cannot be deactivated. The cluster's metadata is permanently updated to use the configuration-as-code (JSON) model for host settings.
VCF 9.0 enforces strict validation during the import process. If a cluster has the VCP flag enabled but the hosts do not meet the minimum versioning requirements for VCP orchestration within SDDC Manager, the import is blocked. Because the feature is non-reversible on the existing cluster object, the validation failure persists.
Create a New Target Cluster
In the vSphere Client, right-click the Datacenter and select New Cluster.
Provide a temporary name (e.g., Cluster-NonVCP).
Enable vSphere Lifecycle Manager (Manage all hosts in the cluster with a single image).
Note: Leave the checkbox for vSphere Configuration Profiles unchecked.
Select the ESXi image version that matches your current hosts.
Migrate ESX Hosts
Place the hosts in the original cluster into Maintenance Mode.
Drag and drop the hosts from the VCP-enabled cluster into the new Cluster-NonVCP.
Perform a compliance check and remediate if necessary to ensure the image is applied.
Finalize Inventory and Retry
Delete the now-empty VCP-enabled cluster.
Rename the new cluster to the original production name.