I need to update the firmware on a HP Proliant Microserver Remote Access Card installed in my N40L.
Can someone please explain what I need to do to create a boot device that will update the firmware on the Remote Access Card?
after checking my ILo4, version2.61 on my Gen8 hp microservet, i saw an exclamation mark at cpld-pal0. It is now version 0x06.
i have read that there is an version 0x32.
anybody who has this version, and can provide me with a download link?
Attached my firmware configuration. Any suggestions for any updating? Think most is up to date?
Sorry can’t upload photo, error 200.
Newbie here, so please be gentle with me!
I have an 18 month old Gen8 server bought new but now out of warranty, so limited access to HPE updates. My Gen8 has 8Gb memory, Recently added Xeon 1220v2, standard disk controller (122i ) and 4 off 3.5” drives giving 6Tb of storage under storage spaces. OS on SATA HDD sitting in ODD space as recommended on here. I was running Win10 Pro, but after upgrading processor and trying to update drivers with Intelligent Provisioning, I fell foul of the expired warranty. I also lost my printer driver for HP laser jet and my sound drivers (usb connected sound card).
To cut a long and painful journey a bit shorter, I am re-installing Win10 Pro from DVD, with licence key under IP. My question as someone without warranty, but with a copy of the SPP download (ISO?), how do I install the various drivers needed from the SPP and do I need to update the firmware for the Xeon processor, if so how? I read on here that the original 2014 J06 firmware does not have a thermal solution for Xeon processor and ILO shows high temps for some components.
I am reasonable knowledgeable in Windows of old and have Rufus to create bootable usb sticks, but unsure how to get from SPP ISO image as downloaded (871795_001_spp-2017.04.0-SPP2017040.2017_0420.14).
Any help from experienced gurus much appreciated!
I installed a BU50N Blu-ray 4K drive in my HPE ProLiant Gen8 MicroServer. Worked out well, I'm using PowerDVD13 -- I had to restart the "Machine" several times before it saw the ODD but "Machine" finally figured it out.