Custom Baseline Status Shows "Incompatible" on vCenter Server
search cancel

Custom Baseline Status Shows "Incompatible" on vCenter Server

book

Article ID: 410452

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • In VMware vCenter, when performing a compliance check under Updates > Baselines, the host displays an "Incompatible" status. This prevents remediation until the baseline aligns with the image profile used on the host.

  • A custom upgrade baseline always shows as Incompatible, even though the default patch baselines (Critical, Non-Critical, Security) might show compliant or non-compliant.

Environment

VMware vCenter Server

Cause

This incompatibility occurs because the ESXi host was originally built using a custom ESXi image, while the baseline being applied is based on a standard VMware ESXi ISO. The image profile of the host does not match the image profile defined in the custom upgrade baseline.

To verify the image used to build ESXi host, follow these steps:

  • Log in to the ESXi Host Client (https://<host-ip>/ui) or vSphere Client.
  • Navigate to the Host > Summary tab.
  • Check the "Image Profile / Build Information."
    • A standard ISO build show information similar to: VMware ESXi 8.0.2 build-22380479.

    • A custom ISO will have a different build string, including vendor-specific information.

Resolution

To resolve this, re-create the custom baseline using the custom ISO that was used to build the host, instead of a standard ISO. Follow these steps:

  • Re-create the Custom Baseline:
    • Obtain the desired version of a custom ESXi ISO image for the same vendor used to install the host.
    • In vCenter, navigate to Updates > Baselines.
    • Create a new Host Baseline (or modify the existing baseline)
    • When creating the baseline, ensure to select "Upgrade" as the baseline type and upload the correct custom ESXi ISO image.
    • Once the new baseline is created with the custom ISO, attach it to the affected host or cluster.
  • Perform a compliance check.

    • The host should now show as "Compliant" or "Non-Compliant" (if patches are missing), allowing for remediation if necessary.

Additional Information