HP PowerShell Cmdlets

HP has introduced another batch of over 90 PowerShell cmdlets with a focus on BIOS management.  The new batch of cmdlets joins two previous batches of cmdlets that allow management of iLO, the onboard IP management interface on ProLiant servers,  and for Onboard Administrator, the primary management interface on HP’s BladeSystem hardware.

OneView introduced the ability to set BIOS settings during the provisioning of systems and these BIOS cmdlets put the same level of control into more system admins and engineer’s hands, even if the environment has not adopted HP OneView.

When I read this news, the first thing that popped into mind was using this to ensure that my Windows cluster hosts are set to the correct Power Management mode and easily enough, that is the example that is found in the HP documentation that shipped with the toolkit.   For my Windows clusters running things like Exchange or SQL, we follow the best practice to set the Power Management to Static High Performance mode and this toolkit gives me an easy way to write a script to collect this information from multiple hosts and send an email alert for hosts where this is set incorrectly.

Use Scenarios

The HP BIOS Cmdlets are compatible with both WinPE and standard Windows installations meaning that the BIOS cmdlets can be used during system deployment to adjust and set BIOS settings on a host.  This is useful if an enterprising admin wants to ensure the BIOS settings of the hardware during an System Center Config Management installation or with third party imaging systems like Altiris. Interestingly, there is a cmdlet that create an HP customized WinPE image that is deployed with the BIOS cmdlet distribution.

The bulk of the cmdlets are Get- and Set- verb cmdlets, as you would expect.  These cmdlets allow you to retrieve and set specific settings with each cmdlet.  All of the BIOS cmdlets are listed at the end of this post as an overview.

Getting Started

There are some pre-requisites, but anyone using PowerShell will likely already have the pre-requisites installed.  The pre-req’s are:

• Microsoft .Net Framework 4 or Microsoft .Net Framework 4.5
• Windows Management Framework 3.0 or Windows Management Framework 4.0
• For WinPE, Windows Assessment and Development Kit is needed.

The installation for the HP BIOS PowerShell cmdlets is found at www.hp.com/go/powershell.  The download is an MSI and the installation is simple and straight forward.  The QuickSpecs are found here for easy reference.

Connecting & Disconnecting

Connecting to a host is simple.  According to the documentation, the syntax for a connection is very similar to connecting to vCenter Server using PowerCLI.

[code lang=”PowerShell”] $variable = Connect-HPBIOS 192.168.0.100 -Username "username" -Password "password"[/code]

All of the documentation and examples show using a connection variable with the Get- and Set- cmdlets, so that may be a best practice, but it is entirely possible to perform a connection in a single line if you only need to adjust a single setting.  Connecting takes a bit of time, so using an establish connection will save you a lot of time.

Storing the connection in a variable for reference also allows you the benefit of establishing multiple sessions to different hosts.  This could be useful for setting settings across multiple hosts with a simple For loop in PowerShell.

Disconnecting is just as simple.

[code lang=”PowerShell”]Disconnect-HPBIOS $variable[/code]

Receiving Updates

Like the previous version of HP cmdlets for iLO and Onboard Administrator, HP has packaged an Update-HPBIOSModuleVersion cmdlet that checks the HP website and automatically pulls down the newer versions of HP BIOS cmdlets when they are available.

What do you connect to?

So, it begs the question – when you do a Connect-HPBIOS cmdlet, what are you connecting to?  The answer is the Windows OS.  You are not connecting to the iLO, as I first thought.  So, this means, only targets running the Windows OS are going to be viable to you.  I had hoped that maybe the PowerShell toolkit was talking to iLO and its RESTful API, but this is not the case. Connected to the RESTful API would have meant you could use PowerShell to script against Linux and VMware hosts in addition to Windows hosts, but perhaps this will come in future versions.

Quick References of the BIOS Cmdlets