![hp vmware esxi 6.7 hp vmware esxi 6.7](https://www.hex64.net/wp-content/uploads/2018/12/Download-custom-upgrade-bundle-for-the-server-from-VMware-official-site.png)
So, once that’s all done mount the ISO however you like, I use iLO and go through the install as per normal, continue through the warning about CPUs of this socket being depreciated. You should now have ‘ESXI65CUST.iso’ in your working folder.
![hp vmware esxi 6.7 hp vmware esxi 6.7](https://networklessons.com/wp-content/uploads/2013/07/vmware-esxi-configuration-security-profile.png)
So what now? I didn’t want to settle for the standard image, so I did the following to bundle the U2 hpe-smx-provider into the 6.5 image.įor the lazy: There is a link at the end of this post with a download to the compiled ISO. Installing the standard ESXI 6.5 ISO does allow the server to boot, but is missing a lot of drivers and does not give the pretty all-inclusive system stats that the HPE ISO does.
![hp vmware esxi 6.7 hp vmware esxi 6.7](http://www.vmwarearena.com/wp-content/uploads/2017/08/Upgrade-ESXi-6.0-to-ESXi-6.5-using-ISO_1.jpg)
It would appear that one driver is causing this in the 6.5 image, “hpe-smx-provider” (650.03.11.00.17-4240417). After some digging, it would appear this is actually a known issue with most G7 servers (unsure about G6).