Software Delivery Repository - vibsdepot
(aka HPE Online Depot)
compatible HPE bundles for VMware® Image Builder, Update Manager and ESXCLI
Software Delivery Repository | vibsdepot | Getting Started | HPE Downloads | HP Downloads
Welcome to HPE vibsdepot! This is a one-stop repository that provides access to HPE developed bundles along with device drivers that are part of the HPE Customized VMware images. These bundles and associated vibs can be used with VMware applications and tools like VMware Update Manager (VUM), ESXCLI and Image Builder. To learn more about these tools, refer to the VMware documentation
The "Getting Started" link on the top panel describes how to effectively use vibsdepot. The "Downloads" link on the top panel will allow you to directory browse and download from groupings that correspond to HPE Customized VMware image releases.
Getting Started with HPE Customized images
VMware ESXi is a "bare metal" full-function hypervisor solution from VMware. It is highly secure, has a small footprint, and is set to be the long-term hypervisor platform for future VMware releases. We are committed to continue making HPE ProLiant servers and the supported infrastructure the best platform for hosting VMware ESXi. As part of this commitment, we provide HPE Customized VMware images that integrate the VMware ESXi base image with support for advanced ProLiant features for a seamless deployment experience. HPE Customized VMware images simplify configuring and deploying the ESXi hypervisor.
Certain ProLiant servers require using a custom image to run the ESXi hypervisor. Using the custom images on other ProLiant servers is optional but highly recommended. To determine if your server requires the HPE Custom Image, refer to the HPE server support matrix.
To get started with the HPE Customized VMware image, see the HPE VMware ESXi and vSphere 5.X, 6.X and Updates Getting Started Guide (PDF 298KB) and the HPE custom ESXi images for ProLiant servers Technical White Paper (PDF 170KB).
For information on the contents of the HPE Customized VMware images use the HPE customized image contents
To download the HPE Customized VMware images, use the HPE customized VMware image downloads
For additional downloads, please refer to the HPE and VMware Image and HPE Application Downloads
For more information on the HPE and VMware Alliance Partner Solution, see the HPE and VMware Alliance Partner Solution
For more information on the HPE ProLiant Servers with VMware, see the HPE Proliant Servers with VMware
- HPE and VMware Alliance Partner Solution
- HPE Proliant Servers with VMware
- VMware vSphere overview
- HPE ProLiant server and option firmware and driver support recipe (Current) (PDF 1.2MB)
- All HPE Proliant server and option firmware and driver support recipes
- VMware documentation sets
- HPE Service Pack for Proliant Release Notes
- HPE Manuals - VMware Virtualization Software For HPE ProLiant Servers
HPE and VMware Image and HPE Application Downloads
- HPE customized VMware image downloads
- HPE customized image contents
- VMware downloads including base images
- HPE Service Pack for Proliant
- HPE One View for VMware vCenter Server
- HPE server support matrix
- HPE End User License Agreement
- Eclipse License
- Libcurl End User License Agreement
- Net-SNMP License
- SNIA License
- zlib End User License Agreement
Important information: The ProLiant Gen8 and newer servers require the use of the HPE Customized image for a successful installation. The drivers for the new network and storage controllers in the Gen8 and newer servers are integrated in the HPE Customized image and are not part of the generic ESXi image that is distributed by VMware. ESXi requires drivers for these key controllers to be integrated in the base image. You will not be prompted to install key drivers during the installation process for ESXi.
New domain name: With the launch of the new company, Hewlett Packard Enterprise, please refer to this host as vibsdepot.hpe.com. If you access this system using VMware Update Manager, VMware Image Builder or VMware vSphereCLI, please update your repository configuration files accordingly.