Update Manager reports incompatible compliance status after a successful remediation using a baseline group
search cancel

Update Manager reports incompatible compliance status after a successful remediation using a baseline group


Article ID: 309296


Updated On:


VMware vCenter Server


This article describes a specific issue. If you experience all of the above symptoms, consult the sections below. If you experience some but not all of these symptoms, your issue is not related to this article. Search for your symptoms in the Knowledge Base or Open a Support Request.

This issue occurs only under all these conditions:
  • When a host is upgraded and rescanned against a baseline group which consists of one host upgrade baseline and one or many host patch baselines.
  • When you have imported 4.0 to 4.1 host upgrade zip bundles.
  • After a successful remediation against a baseline group, the host gets marked as Incompatible.
  • When you click for details, you see the message:

    The upgrade has a missing package for host xxx.xxx.com of type embeddedEsx


VMware vCenter Server 4.1.x
VMware vCenter Update Manager 4.1.x


The incompatible message is being incorrectly reported by the system, so this message can be safely ignored.

However, to work around this issue:

  1. Connect to the vCenter Server using the vSphere Client.
  2. Click the Update Manager tab.
  3. Click the Admin view, then click the Host Upgrade releases tab.
  4. Using the Import upgrade release option, import the upgrade bundle which is used to upgrade 3.5 hosts to the current 4.1 release. For example, import the upgrade-from-ESXi3.5-to-4.1_update02.502767.zip bundle. The release and respective upgrade baseline is automatically updated. You do not have to update/create any baseline.
  5. Once the import is successful, go to the compliance view and start host scanning with the Upgrade and Patch scan options selected for the host. This corrects the compliance status of the host which is already upgraded.
  6. Use the same baseline group against the hosts which have not yet been upgraded to prevent the issue from occurring.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box