Menu
Customizing Packages in HP SPP ISO and Offline Firmware Update in ProLiant Servers This is a quick guide showing how to include/slipstream custom packages (rpm, exe, etc.) in HP/HPE SPP (Service Pack for ProLiant) ISO images for updating of system software or firmware of components within HPE/HP servers. HP Service Pack for ProLiant (SPP) is a comprehensive systems software and firmware update solution, which is delivered as a single ISO image. This solution uses HP Smart Update Manager (HP SUM) as the deployment tool and is tested on all HP ProLiant Gen9, Gen8 and earlier servers as defined in the Service Pack for ProLiant Server Support Guide. The Service Pack for ProLiant (SPP) is a comprehensive systems software and firmware update solution, which is delivered as a single ISO image.
If you’ve ever worked with HP ProLiant servers before, you’re probably familiar with the HP Service Pack for ProLiant https://renewrate240.weebly.com/blog/kabali-telugu-movie-download-torrent. (HP SPP). As I’ve only worked with Dell servers before (it’s kind of fun that I’ve not come in contact with HP servers managed with ConfigMgr up until now), I’m used to use the DRM (Dell Repository Manager). Seagate data recovery software free download.
Overview
- Get your hands on the HP SPP
- Cleanup HP SPP
- Copy HP SPP to the Content Library
- Create a wrapper script
- Create a Package
- Add HP SPP to a Task Sequence
Get your hands on the HP SPP
As of writing this post, the latest version of HP SPP is 2014.02 and can be downloaded from the link below.
You’d need to login to be able to download the ISO. If you don’t have an account yet, it’s a pretty fast sign-up process.
Cleanup HP SPP
As in this post I’ll be focusing on using the HP SPP for Windows Server deployments, and for that we don’t need all the linux-based files that comes along as well. Since the servers that will be deployed with ConfigMgr needs to download all the content in the package that we’ll create later, it would be wise to keep the data to a minimum. Once you have downloaded the ISO, mount it and copy the folder below and all of its contents to a folder of your liking. I’ll be copying the files to G:HP.
<driveletter>hpswpackages
Open an elevated PowerShell console and run the following command:
When you run the command above, you’ll remove all of the unnecessary files that we won’t be needing when deploying the HP SPP for Windows servers. The orginal size of 3GB+ has now been decreased to about 1.2GB instead. It’s still a lot of data, and perhaps there could be some more cleaning done, but I’ll leave that up to each of you to decide on that.
Copy HP SPP to the Content Library
Now that we have the files we need, it’s time to move them to the Content Library on your Primary Site server (or wherever your Content Library is located). In my lab environment, I’ll be using the following location for the HP SPP files:
CM01ContentLibrary$PackagesHPHPSPP2014.02
Move all of the contents of G:HPswpackages to the location in the Content Library.
Create a wrapper script
Since HP has decided to go their own way when it comes to exit codes, we need to have a wrapper interpreting the return codes from the installation. This can be accomplished by using the following script:
If you take a look at the script, we have a variable called sSetupCommand that contains the actual setup command that will be executed. Here you’re able to specify the command line parameters that are supported by the HP SPP. I would encourage you to look them up so that you use the correct ones that suites your environment.
Save this script as InstallHPSPP.vbs and copy it to the same location that you copied the HP SPP files in your Content Library.
Create a Package
I’ll assume that you know how to create a Package in ConfigMgr, so that process will not be described here in this post. What’s important though when you create the package is to specify the content source and not to create a Program. You could of course create a Program if you wish, but I’ll be leveraging the Run Command Line step in the task sequence instead of the Install Package. Also, remember to distribute the package to your Distribution Points.
Add HP SPP to a Task Sequence
When editing the task sequence, it’s important that we add the Run Command Line step during the Online phase. That means that we have to add it after the Setup Windows and Configuration Manager step at some point. Here in my lab environment I’ve edited my Windows Server 2012 R2 Standard – Install task sequence and added a Run Command Line step with the following command line:
cscript.exe InstallHPSPP.vbs
In addition to that I’ve also selected to use the package that we created earlier.
Now when you go and deploy this task sequence to one of your servers, the HP SPP installation will take care of all your driver installations and additional software that it finds suitable for your server.
Jojo bizarre adventure wallpaper hd. (3685)
Chief Technical Architect and Enterprise Mobility MVP since 2016. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation. Awarded as PowerShell Hero in 2015 by the community for his script and tools contributions. Creator of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService to name a few. Frequent speaker at conferences and user groups.
Related
tl;dr rant avoiding summary: HP SPP downloads may be broken for you, call them for a direct link
HP has recently started charging for firmware.
Part of the new procedure for downloading the Service Pack for Proliant is checking whether you have a valid support contract or HP Care Pack associated with your account.
HP has one of the world’s worst websites so you can imagine the convoluted process you need to follow to achieve anything. I managed to add a valid Care Pack to my account and thought I was ready to go. Nope, I somehow descended into the 7 circles of hell going round and round logging on numerous times, selecting one of various ways to get to the SPP download, clicking on “Obtain Software” to head straight back to a notice saying I needed a valid entitlement with either a support contract or Care Pack and try again and again.
I then tried to run a chat session with someone from HP, had to enter all my details again as it must be too hard to read these from my account and click the Submit button which went nowhere.
I didn’t want to log a support ticket as it being a low priority I would probably get a reply when Gen700 servers are available.
Hp Proliant Service Pack Download 1
Hp Proliant Service Pack 2016 Download
I called phone support, spoke to a very friendly guy who took my server serial number, confirmed I should have access to download the SPP and then said he could see the entitlement was not linked correctly to the support side for downloading the SPP.
He said many HP customers are having the same issue and they are apparently working on sorting out all this linking and with the large number of accounts they have this is taking some time.
He then emailed me with a download link and username and password to get the SPP.
If you are having any issues downloading the SPP with your login, call HP and ask for the download link, don’t try to fight it yourself.
HP, please sort your house out. We want to believe you’ve turned a corner and are heading in the right direction but don’t force your customers to pay for downloading firmware and then not have the back end processes worked out so they can actually do this.
Hp Spp Iso Download
The other infrastructure vendors are laughing at you when they have simple, often free. software downloads and can update software and firmware with a single click and no downtime.