In the February 2014 release of Smart Update Manager (SUM), part of HP Service Pack for ProLiant, HP decided to change the setup behavior, and of course breaking my existing sequences for server deployments. The new SUM is available here: http://h17007.www1.hp.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx and as part of their new strategy for server downloads (which sucks beyond belief), you need to register before you can download the ISO.
Changes
Prior to version 6.2.0 you run the hpsum.exe with a few command line switches. That file is now gone and replaced by hpsum.bat (!). Excuse me HP, this is 2014, not 1994.
Anyway, the hpsum.bat is just a wrapper for the new setup named hpsum_bin_x64.exe, which you find in the x64 folder of SUM.
The /express_install switch is gone and replaced by /s (or /silent), and to prevent the target server from writing back to the MDT deployment share, I recommend copying the repository to the local drive, and then use the /use_location switch. As with previous SUM version, HP don’t follow any standards for exit codes either. In the HP world, exit code 1 means successful, but requires a reboot.
Shorthand, you need a wrapper, and below is one:
Ps. If you wonder why I’m using VBScript instead of my usual PowerShell scripting, it’s because MDT 2013 still uses VBScript, and being able to tap into their functions is more important than re-writing everything in PowerShell.
The wrapper
This wrapper copies the HP SUM to the local machine, runs the setup, and takes care of the non-standard exit codes.
The Application
Simply download the HP SUM 6.2.0, mount the ISO, and copy the content of the \hp\swpackages folder to a folder named Source in your application folder.
Then copy the wrapper to the root of your application, and configure the application to run the wrapper.
My HP SUM 6.2.0 application.
The root folder of the HP SUM 6.2.0 application.
The Source folder of the HP SUM 6.2.0 application.
The HP SUM 6.2.0 in the task sequence.
Happy Deployment, Johan
More ...