I'm managing an HPE ProLiant DL360 Gen10 running Windows Server 2019 Standard. Device Manager reports the Intel(R) Management Engine Interface driver as version 11.6.0.1026, dated January 2016, and signed by Microsoft Windows Hardware Compatibility Publisher. That seems old for this server, but the system is in production, so I don't want to update anything blindly.
Should I use HPE's Service Pack for ProLiant (SPP) and Smart Update Manager (SUM), or install a package directly from Intel? Are the Windows MEI driver and the server's SPS/ME firmware separate components? What's the correct place to check the actual firmware version—Device Manager, iLO, or HPE's inventory tools?
I'd also appreciate advice about reboot and downtime requirements, firmware upgrade sequencing, the risk of interrupting an update, and whether remote out-of-band updating through iLO is safe or requires physical access. I want to verify the HPE-recommended baseline and any applicable advisories before scheduling maintenance.
3 Answers
Use HPE’s SPP and SUM rather than downloading a generic Intel package. SUM can inventory the server, compare it with the HPE firmware and driver baseline, check dependencies, and show whether an update is actually recommended.
The Windows MEI driver and the SPS firmware are separate components. The version shown in Device Manager is only the Windows driver; it does not tell you the firmware version running on the board. Check the firmware inventory in iLO or SUM, where SPS should appear as its own component.
If HPE does not recommend a newer MEI driver and the server has no related issue, there’s usually no reason to force an update simply because the date looks old. Update firmware through HPE’s tools or iLO, not through Device Manager.
A 2016 date on the Windows driver is not automatically evidence of a problem. The driver may be the HPE-supported version for that operating system, while the actual management-engine firmware is tracked separately. Base the decision on HPE’s compatibility information and security advisories, not just the Device Manager timestamp.
If the server is far behind the current baseline or the documented upgrade path is unclear, pause and check the component release notes or contact HPE technical support. Do not rely on a generic Intel installer for a production ProLiant unless HPE specifically directs you to use it.
For a normal ProLiant maintenance cycle, run the appropriate HPE SPP with SUM in interactive mode, review the proposed changes, and apply the tested baseline. SUM does not eliminate the need to read release notes, especially if the server is several firmware generations behind, but it is the standard way to identify supported updates and dependencies.
SPS firmware updates generally require the host to be shut down or rebooted, so plan for downtime. If you perform the update through iLO, make sure iLO access and the remote console are working beforehand, and do not interrupt power or connectivity during the flash. Remote updating is supported, but have an out-of-band recovery plan and schedule it as carefully as an on-site update.
That makes sense. I’ll first capture the iLO firmware inventory, compare it with the matching SPP and advisories, and only then decide whether the MEI driver or SPS firmware needs attention.
It’s still worth checking the release notes before updating. A very old firmware level may require an intermediate version, so don’t assume you can jump directly to the newest release.