- DOWNLOAD VMWARE ESXI 5.5 ISO HP INSTALL
- DOWNLOAD VMWARE ESXI 5.5 ISO HP DRIVERS
- DOWNLOAD VMWARE ESXI 5.5 ISO HP DRIVER
- DOWNLOAD VMWARE ESXI 5.5 ISO HP DOWNLOAD
On a side note – generally, which is considered “better”: 6.5 U3 (if it works) or plain 6.7? What does 6.7 bring to the table – features we can honestly make use of on a HP G7-era server, in a homelab (as in, no vSphere)? Having more support lifetime is useless here. Nope no good with all those packages swapped out, it still boots and runs but all the health information is borked.įor now I’m going back to plain 6.7, swapping smx-provider for the 6.0 latest release of hpe-smx-provider, I think that is the latest version we can get working nicely at the moment unless a ESXi guy can dig into this a bit. Starting to think this may be a wild goose chase… Other differences I’ve spotted with “lsu-” packages: Tried 6.7U3 HPE, removed “smx-provider” and added/replace all other packages with following: I noticed while experimenting with this that there are additional “lsu-xyz” packages in 6.7U3, not present in 6.7, provided by VMware – lsu-smartpqi-plugin is new, and there was already “smartpqi” by vendor HPE… Those are storage related, maybe removing them or downgrading some others is worth a go next but I’ve run out of time tonight.įor the record and if anyone else wants to pick up where I’ve left off for now: I’ve tried to mimic all the same versions in the working 6.7 image for the HPE, Microsemi and MSCC packages on a custom build of HPE 6.7U3 using this guide/PowerCLI, it boots and versions are what I want them to be, but with no fix for the dodgy CIM results with 6.7U3 on at least my D元60 G7 (ilo3 1.91, SPP G7.1-3).
DOWNLOAD VMWARE ESXI 5.5 ISO HP INSTALL
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.
DOWNLOAD VMWARE ESXI 5.5 ISO HP DRIVER
Add the good driver into the custom image.Īdd-esxsoftwarepackage -imageprofile ESXICUST -softwarepackage "hpe-smx-provider 600.03.11.00.9-2768847"Įxport-EsxImageProfile -ImageProfile ESXICUST -ExportToIso -filepath "c:\HPE\ESXI65CUST.iso".
Now we can see both driver versions from the bundles.Remove-EsxSoftwarePackage ESXICUST hpe-smx-providerĪdd-EsxSoftwareDepot -DepotUrl C:\HPE\ESXIHP6U2.zip New-EsxImageProfile -CloneProfile HPE-ESXi-6.5.0-OS-Release-6* -Name "ESXICUST" Clone the profile so we can work on the clone.Once that is done, fire up PowerCLI, and do the following commands:Īdd-EsxSoftwareDepot -DepotUrl C:\HPE\ESXIHP65.zip I also renamed them to make it easier for myself, “ESXIHP65” “ESXIHP6U2”. Once that is all installed, grab both of the following files and put it somewhere easy, I just shoved them in C:\HPE.
DOWNLOAD VMWARE ESXI 5.5 ISO HP DOWNLOAD
The first thing you want to do is download PowerCLI for Windows. 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.
DOWNLOAD VMWARE ESXI 5.5 ISO HP DRIVERS
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. 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).