Add HP or Dell drivers to VMware Update Manager (VUM)

HP has created a vSphere Installation Bundle (VIB) depot for all sort of important HP driver bundles for VMware vSphere 5 and higher. The VIP depot contains:

    • HP ESXi 5.0 Management Providers bundle – includes the latest HP Common Information Model (CIM) Providers, HP Integrated Lights-Out (iLO) driver, HP Compaq ROM Utility (CRU) driver, and the new HP Agentless Management Service (AMS).
    • HP ESXi 5.0 Utilities bundle – ESXCLI utilities such as HPBOOTCFG (boot order configuration),HPONCFG (remote iLO configuration) and HPACUCLI (Smart Array reporting and configuration)
    • HP ESXi 5.0 NMI bundle – Non Maskable Interrupt (NMI) driver used to write VMware® errors to the Insight Management Log (IML)
    • HP Agentless Management Service Offline Bundle – a service that provides support for Agentless Management and Active Health. Agentless Management Service provides a wider range of server information (e.g. OS type and version, installed applications, IP addresses) allowing customers to complement hardware management with OS information and alerting. Agentless Management provides Integrated Lights Out (iLO) based robust management without the complexity of OS-based agents. Active Health provides 24×7 mission control for servers, delivering maximum uptime through automated monitoring, diagnostics and alerting.
    • Device Drivers as used in the HP Customized VMware images
    • Latest ProLiant Server and option firmware and driver version recipe

The VIB depot can be used by the following tools:

  • VMware Update Manager (VUM)
  • ImageBuilder

With the HP VIB depot integration for example in VUM there is no need to download and install the bundles manually. In this blog post I explain how to add the HP VIB depot to VMware Update Manager (VUM) by using the following steps:

Add the VIB Depot to VUM

  • Open the vCenter Client
  • Select under Solution and Application in the main screen of the vCenter client – Update Manager
  • Select configuration
  • In the Download sources select – Add Download Source
  • In Source URL use:
    • For HP Updates:
    • For Dell Updates:
  • Press OK
  • Select – Download Now to update the baseline


Create a new Baseline

  • Select the Baselines and Groups tab
  • Create
  • Baseline Name  – HP Updates
  • Baseline Type – Host Extension
  • Extensions to Add – Select the extensions you need. In this example I selected the following extensions:
    • hpnmi for ESXi 5.0 v1.3
    • HP ESXi 5.0 Complete Bundle Update 1.3
    • HP ESXi 5.0 Management Bundle 1.2-26
    • HP Utility Bundle ESXi 5.0 v 1.2


  • Finish

Attach the baseline and remediate

  • Attach the baseline to the cluster


  • Select the baseline and scan for patches and extensions
  • The HP bundles that are missing are listed


  • Use Remediate to install the HP bundles

When the hosts are rebooted and the remediation is finished, the Host Compliance overview is 100%.



Using the  HP VIB depot is great way of keep your HP server up-to-date with the latest HP bundles.

More information can be found HP VIB bundle site found here.

Update July 20 2012 : Viktor van den Berg tested the above configuration and found out that this only works with new  installations. For existing installation you need to create an additional Host Patch Baseline. Viktor explains this on his cool blog found here here.

vCenter Operations Manager (vCOPS) resources

VMware vCenter Operations Manager (vCOPS) is an automated operations management solution that provides integrated performance, capacity, and configuration management for highly virtualized and cloud infrastructure. Deep VMware vSphere integration provides the most comprehensive management of VMware environments. VMware vCenter Operations Manager is purpose-built for VMware administrators to more effectively manage the performance of their VMware environments as they move to the private cloud.


Here is a list of vCOPS resources available:

Nest Windows Server 2012 Hyper-V in VMware ESXi 5

In this blog post I explain how you can install Windows 2012 Server Release Candidate (RC) in VMware ESXi and enable the Hyper-V role. It is possible to build a Hyper-V cluster LAB and live migrate VMs between the virtual Hyper-V nodes on one VMware ESXi 5 host. 

Before you begin make sure:

  • Windows 2012 Server RC ISO is place on a datastore
  • VMware ESXi 5 Update 1 is installed with the latest updates
  • To be able to boot 64bit guest OSes, make sure that on the VMware ESXi host the line below is added to the /etc/vmware/config file on your physical ESXi 5.x host (more information can be found on the blog from William Lam)
vhv.allow = TRUE

Create a new VM with the following settings (adjust the settings for your own need):

  • Configuration – Custom
  • Name – HV2012-02
  • Storage – Choose VMFS
  • Virtual Machine Version – Virtual Machine Version 8
  • Guest Operating System – Microsoft Windows Server 2008 R2 (64-bit)
  • CPUs – 2 Sockets, 2 Cores
  • Memory – 4 GB
  • Network – 4 NICs VMXNET 3
  • SCSI Controller – LSI logic SAS
  • Create a new virtual disk
  • Disk Size – 40 GB
  • Virtual Device Node – SCSI(0:0)
  • Finish

After the VM is created edit  the VM configuration and add or change the following settings:

  • Hardware – CD/DVD drive 1 – Datastore ISO file – browse to the Windows Server 2012 ISO
  • Options – General  Options – Guest Operating System – Microsoft Windows Server 8 (64-bit)
  • Options – CPUID Mask – Advanced – Level 1 ecx (add the mask below for Intel Hosts)
---- ---- ---- ---- ---- ---- --H- ----
  • Options – Boot Options – Specify the boot firmware – EFI
  • Options – General – Configuration Parameters – Add Row – Add the line below (without =)
hypervisor.cpuid.v0 = FALSE 
  • Start the VM and install Windows Server 2012 
  • Install VMware tools
  • Add the Hyper-V role

If you need to install more Windows Server 2012 Hyper-V VMs, create a template so that you only need to do the settings once.