Hpe Custom Image For Esxi Patched | 2026 Update |
Manual patching doesn't scale. For 10+ hosts, use these tools to ensure every host has a HPE Custom Image for ESXi patched to the same level.
| ESXi Build | HPE Addon Version | Minimum SPP Version | iLO Firmware | | :--- | :--- | :--- | :--- | | ESXi 8.0 U2 (Build 22348879) | HPE 802.0.0.10.4.1 | SPP 2024.09.00.00 | iLO 6 v2.50 | | ESXi 7.0 U3 (Build 20345678) | HPE 703.0.0.10.3.2 | SPP 2024.06.00.00 | iLO 5 v2.82 |
If you patch ESXi without updating SPP, you may see: NMI: PCIe error or S.M.A.R.T. monitoring failed.
Add-EsxSoftwareDepot https://downloads.hpe.com/pub/softlib2/software1/sc-vmware-sw-pkg-prod/p123456789/vib20.zip
Clone the HPE baseline.
# Find the HPE profile name (e.g., "HPE-ESXi-8.0U2-xxx-no-tools")
Get-EsxImageProfile | Where-Object $_.Name -like "HPE*"
Before you patch your HPE ESXi hosts, ask yourself:
If you answered "Yes" to all four, go ahead and remediate. Your servers—and your Monday morning—will thank you. hpe custom image for esxi patched
Have a horror story from patching HPE servers with the wrong image? Or a clever PowerCLI one-liner? Drop it in the comments below.
Updating an HPE Custom Image for ESXi is generally handled through two main methods: using vSphere Lifecycle Manager (vLCM) for automated updates or the ESXCLI for manual, command-line patching. Method 1: vSphere Lifecycle Manager (Recommended)
This is the modern way to ensure your HPE drivers and the VMware base image remain in sync.
Check the Hardware Support Manager (HSM): Ensure your vCenter is integrated with the HPE OneView or HPE iLO Amplifier Pack. This allows vCenter to verify firmware and driver compatibility simultaneously.
Define a Desired State: In the vSphere Client, go to Lifecycle Manager > Image. Select the ESXi Version (the patch level).
Add the Vendor Add-on (Select the specific HPE Customization add-on). Manual patching doesn't scale
Remediate: Attach this image to your cluster or host. Click Check Compliance, then Remediate. vCenter will automatically put the host in maintenance mode, apply the patch + HPE drivers, and reboot. Method 2: Manual Patching via ESXCLI
If you don't use vCenter or need a quick manual fix, you can patch an existing HPE-customized host while preserving the HPE drivers.
Download the Patch: Get the latest ESXi Offline Bundle (.zip) from the VMware Patch Portal.
Upload to Datastore: Use the vSphere Client to upload the .zip file to a datastore accessible by the host. Enter Maintenance Mode: esxcli system maintenanceMode set --enable true Use code with caution. Copied to clipboard
Apply the Patch: Use the update command (which preserves existing drivers) rather than install (which overwrites them).
esxcli software vib update -d /vmfs/volumes/DATASTORE_NAME/patch-file-name.zip Use code with caution. Copied to clipboard Reboot & Exit Maintenance: reboot esxcli system maintenanceMode set --enable false Use code with caution. Copied to clipboard Important Considerations Reboot host and verify successful boot and hardware
HPE Drivers: Avoid using the standard VMware "Install" command, as it may replace HPE-specific high-performance drivers with generic VMware ones.
Compatibility: Always check the HPE Servers Support Matrix to ensure the ESXi patch version is supported by your specific ProLiant generation (e.g., Gen9, Gen10, Gen11).
HPE Custom ISOs: If you are doing a fresh install or a major version upgrade (e.g., 7.0 to 8.0), always download the pre-baked HPE Custom Image directly from the HPE Support Center. If you'd like to proceed, let me know:
What version of ESXi are you currently on (e.g., 6.7, 7.0, 8.0)?
What HPE ProLiant Generation are you using (Gen9, Gen10, Gen11)? Are you using vCenter to manage these hosts?