About the author

Related Articles

11 Comments

  1. 1

    hw_doc

    Hi,
    we used HP’s customized ESXi installation media, but HP is not visible as a patch vendor in our vUM instance. Has anyone the same issue?

    Reply
  2. 2

    viktorious

    Hi,

    You have to add patch repository yourself. See the PDF mentioned in the article, or check Ivo’s article on this:
    http://www.ivobeerens.nl/2012/07/17/add-hp-drivers-vib-to-vmware-update-manager-vum/

    Reply
    1. 2.1

      hw_doc

      Great – this worked for me – thanks a lot, viktorious!

      Reply
  3. 3

    sanderdaems

    Nice one, thanks Viktor

    Reply
  4. 4

    Eric van der Meer (vMeer-IT)

    Hi Viktor,

    Thanks for sharing this with us, but I would like to mention one thing in this configuration that you have to be aware of.

    In the default baseline: ‘Non-Critical Host Patches’, by default all patch vendors are in the criteria. This will include Hewlett-Packard patches, so when you periodically run Update Manager and install the ‘Non-Critical patches’ you will install the Hewlett-Packard patches with it. I manually choose the patch vendors in the Non-Critical baseline and unselect Hewlett-Packard as the associated patch vendor for this baseline. With this configuration I’m able to decide when I install the HP patches, this is only usefull when you do use the default baselines and run the Non-Criticals…

    Another advantage of this is that you can see the Host Compliance status separately between the Non-Critical and your Hewlett-Packard baseline, one can show you a compliant status and the HP baseline can show you non-compliant for example. This helps you keeping track on the compliant status of your environment.

    Regards,
    Eric van der Meer

    Reply
  5. 5

    viktorious

    Hi Eric, a good addition to the article! Thanks for the comment.

    Reply
  6. 6

    Christian van Barneveld

    Hi Viktor,

    Thanks for sharing this!
    Have you noticed that only the HP packages are updated, but not the device drivers? Everything is up to date, but the Emulex drivers are still on the old version and it seems that I have to import the VIB manually in VUM. When I import the HP custom image (depot.zip) in VUM the device drivers are updated succesfully.

    Do you know if this is by design or do I mis something?

    Regards,
    Christian

    Reply
  7. 7

    topuli

    if you want to update the device drivers too, just add an additional download source with the following source url
    http://vibsdepot.hp.com/index-drv.xml

    regards
    t.

    Reply
  8. 8

    Derek

    http://vibsdepot.hp.com/ says:

    New host name: On November 1, 2015, HP vibsdepot will switch to a new host name of vibsdepot.hpe.com.
    Please replace any use of vibsdepot.hp.com to the new vibsdepot.hpe.com after November 1, 2015. HP vibsdepot will be referred to as HPE vibsdepot as of November 1, 2015.

    Reply
  9. Pingback: Configure HP ILO directly on ESXi server - Virtual to the Core

  10. Pingback: Configurare una HP ILO direttamente da ESXi server - Virtual to the Core

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.