Skip to main content

Steps to Setup a vLCM with offline image on vCenter server

 

✅ Steps to Set Up vLCM Using an Offline Image

Step 1: Download Required Offline Files (From a Computer With Internet)

🧩 What You Need:

  • ESXi Offline Bundle ZIP
    Example: VMware-ESXi-8.0U3-xxxxxx-depot.zip

  • Vendor Add-ons (optional but recommended for Dell, HPE, Lenovo, etc.)
    Example: HPE-Custom-AddOn_802.0.0.10.2-1OEM.802.0.0.24938291_231208.zip

🔗 Sources:

Download the relevant files and transfer them to your vCenter environment, ideally to a machine that can access the vCenter UI.


Step 2: Upload Offline Bundle to vLCM

  1. Login to vCenter Web Client.

  2. Go to Menu > Lifecycle Manager.

  3. Go to "Image Depot".

  4. Click "Import Updates" (top right).

  5. Upload your .zip file(s):

    • Base ESXi Offline Bundle ZIP

    • (Optional) Vendor Add-on ZIP


Step 3: Create or Update vLCM Image for Cluster

  1. Go to Hosts and Clusters view.

  2. Select your Cluster → Click "Updates" tab.

  3. Under "Image" section, click "Manage with a Single Image" (if not done yet).

  4. Click Edit to configure image:

    • ESXi Version → Choose from uploaded ZIP

    • Vendor Addon (optional)

    • Firmware and Drivers Addon → Set to None if not using HSM/HPM

  5. Save changes.


Step 4: Check Compliance

  • Once the image is set, run Check Compliance to verify cluster hosts match.

  • If any hosts are out of compliance, remediate them using the Remediate option.

Comments

Popular posts from this blog

Deploy OVF fails Issues detected with selected template. Details: VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].

 Error: While deploy using OVF file ,getting error as : Issues detected with selected template. Details: - -1:-1:VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19]. Solution: Open .OVF file and edit       <Info>Virtual hardware requirements for a virtual machine</Info>       <System>         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>         <vssd:InstanceID>0</vssd:InstanceID>         <vssd:VirtualSystemIdentifier>zabbix_appliance-6.2.7</vssd:VirtualSystemIdentifier>         <vssd:VirtualSystemType> virtualbox-2.2 </vssd:VirtualSystemType>       </System> to  vmx-19       <Info>Virtual hardware requireme...

Change ESXi acceptane level of VIBs to community Supported

-When you install VIB bundles you may see issue like:               'Could not find a trusted signer: self signed certificate  For resolving this issue, we have to convert the ESXi to community supported acceptance level. -To do that: if  ESXI is a VM :      Edit settings ->boot option ->disable secure boot. if Physical ESXi:      Edit  UEFI Now ssh to ESXi: - Move the ESX machine to community-support esxcli software acceptance set --level=CommunitySupported - Install the bundle with no-sign-check esxcli software vib install -d  VMware_bootbank_vmware-fdm_7.0.1-16478307.vib --no-sig-check -  Set back PartnerSupported esxcli software acceptance set --level=PartnerSupported