If you run VMware vSphere on HPE ProLiant servers, you probably already know the golden rule: Don’t just grab the vanilla ISO from VMware.
If you are in a hurry and trust the HPE add-on:
Identify the profiles available inside the downloaded offline bundle: hpe custom image for esxi patched
Navigating HPE Custom Images for ESXi: Deploying, Patching, and Version Control
Ensure your vCenter Server has internet connectivity to sync with the VMware Compatibility Guide and the HPE software delivery repository. If air-gapped, manually import the HPE Vendor Add-on ZIP file into the vLCM depot. If you run VMware vSphere on HPE ProLiant
If you apply a standard VMware patch to a host built with an HPE Custom Image, However, a best-practice approach ensures that both the hypervisor code and the hardware vibrants remain synchronized and supported. Methods to Patch an HPE Custom ESXi Host Depending on your vSp 1. vSphere Lifecycle Manager (vLCM) - The Modern Standard
If you prefer traditional baselines or are on older versions, you can still use vSphere Update Manager . Installing Updates and Patches on the ESXi Host If you apply a standard VMware patch to
for the first install or major version upgrades (e.g., ESXi 7.0 to 8.0) to ensure storage and network controllers are recognized. Applying Critical Patches
: This is the recommended tool for managing patches. You can import the HPE Custom ISO as a new image or add the HPE Add-on to an existing baseline.
esxcli software profile update -d /vmfs/volumes/DATASTORE_NAME/patch-bundle.zip -p PROFILE_NAME Use code with caution. Reboot the host: reboot Use code with caution. Best Practices for Post-Patch Verification
Maintaining a "patched" state requires balancing the VMware base update with the HPE-specific components. Patching ESXi Custom images (HPE) with Update Manager