Runs the firmware update utility to stage the update.Checks if a BIOS password has been set, if so creates an encrypted password file as required by the firmware update utility.If a BIOS update is available, downloads and extracts the softpaq.Extracts and runs the HPIA to identify the latest applicable BIOS update (if any).Checks the HP Image Assistant (HPIA) web page for the latest version and downloads it.Disables the IE first run wizard which causes a problem for the Invoke-WebRequest cmdlet when running in a context where IE hasn’t been initialised.Creates a working directory under ProgramData.I published a version of this script in Github here. I considered using the HP Client Management Script Library which seems purpose-built for this kind of task and is a great resource, but I preferred not to have the dependency of an external PowerShell module and its requirements. I know other equally handsome community members have shared some great scripts and solutions for doing BIOS updates, but I decided to create my own in this instance to meet our particular requirements and afford a bit more control over the update process. For us, good user experience is critical but finding the balance between keeping devices secure and up-to-date without being too disruptive to the user can be a challenge!įirst off was to create a script that could update the BIOS on any supported HP workstation, without needing to package and distribute BIOS update content. In this post I’m just going to share how we did that. To be honest, until now we’ve never pushed out BIOS updates to anyone, but to get these devices updated to 20H2 we now had no choice. Since we were getting ready to rollout 20H2 we encountered some affected models in piloting, which prompted me to find that advisory and then get the BIOS updated on affected devices. Not so long ago HP published a customer advisory listing a number of their models that need to be on the latest BIOS release to be upgraded to Windows 10 2004.

Hp elitebook update bios