HP SSM with /noreboot parameter causes reboot when SP87463 is installed on ZBook 15 G3

[Stan_0]

When applying softpaqs using HP System Software Manager during a system deployment, the system unexpectedly reboots when SP87463 is installed.  Respecting the /NOREBOOT switch is a requirement for a softpaq to be SSM enabled and so this is a bug in the softpaq installer.

Investigating the cause of the reboot, I note that the .cva file specifies the command to install the Softpaq:

[Install Execution]

Install="n/a"

SilentInstall="CallInst.exe" /app Update.bat /hide

Reviewing the Softpaq contents, it is seen that the Update.bat file calls Insta64.bat on a 64-bit installation of Windows.  Reviewing the Insta64.bat file from the FW64 folder within the Softpaq shows that the last 3 lines of this called script are:

echo System will restart in 10 sec

rem Shutdown -r -t 10

del *.log

I've logged a case with support regarding this issue and have been frustrated by their suggestions (e.g. format the harddrive as GPT and boot in UEFI mode).  In the past, I've had some success getting Softpaqs repackaged for SSM compliance by posting in the forums so I'm hoping an HP employee will see this post and address the issue in this Softpaq installer.

Regards,

Stan

[Joel_R]

Stan,

I will pass along your issue with SP87463 to the appropriate team within HP.

Joel

[Stan_0]

Excellent, thank you Joel.

[Stan_0]

I've discovered that Softpaq sp82739 (Intel USB 3.1 eXtensible Host Controller Driver for HP Thunderbolt Dock G2 v17.2.70.3 REV: A PASS: 2) also contains a hard-coded reboot:

CVA Snippet showing install instructions:

[Install Execution]
Install="setup.exe"
SilentInstall="CallInst.exe" /app install.cmd /hide

install.cmd:

@echo off

wmic datafile where "name='C:\\Windows\\System32\\drivers\\USB3Ver.dll'" get version /value| find /I "Version=5" >nul
if not errorlevel 1 goto Ins 
goto RMV

:RMV
echo Remove and Install
.\15\Setup.exe /quiet /uninstall
Timeout 5
.\3.x\Setup.exe -s -overwrite
Timeout 5
.\17\Setup.exe /qn
Timeout 5
Shutdown -r -t 15
goto end

:Ins
echo Install
.\17\Setup.exe /qn
Timeout 10
Shutdown -r -t 15
goto end 

:end

And I've found the documentation indicating that an SSM compliant Softpaq must provide for a controlled reboot HP SSM User Guide (page 8).  Snippet for convenience:

Additional requirements for software packages

● Post-operating system silent installation—All drivers supported by SSM must have post-operating system installation mechanisms. This means that they must have a self-contained executable setup program such as an InstallShield program, a batch file, or Microsoft Installer. If the deliverable requires changes to INF files, then they need to be included in an executable that can be run by SSM. The only function of SSM is to detect the hardware and software and run a single command specified by the CVA file.

● Detectable deliverable version—To allow SSM to determine if a specific deliverable version is installed on a system, the deliverable must have a significant file. The significant file is used to determine if the software is already installed and, if so, which version is installed. The significant file must have the correct version in its resource header. Any time a deliverable’s version and revision change, the value in the resource header of this significant file must change too.

● Controlled reboot of system—All packages must support a controlled reboot of the system. This means that they cannot reboot the system by default. If the vendor delivers an installation mechanism that requires a reboot, use the /reboot option for SSM. This allows multiple packages to be installed with a single reboot at the end of the process. If the application reboots the system, SSM might not complete successfully while waiting for the application to finish and might leave temporary files on the client system.

● Installation mechanism—Any installation mechanism provided must be able to gracefully recover from a failed installation by exiting without requiring user interaction. HP recommends using a mechanism that can log errors. The installation mechanism must support upgrading from previous versions.

● Customized packages structure—Each customized package supported through SSM must reside in its own separate folder within the File Store. Its associated CVA file must have a unique name and must reside in the root of this unique subfolder. See File Store on page 13 for additional information about the structure of the File Store.

This is becoming a disturbing trend and has me wondering if HP intends to retire HP SSM as a deployment tool.  Controlled reboots are essential to the proper use of HP SSM and if HP's direction is to provide Softpaqs without controlled reboots the use of SSM as a deployment tool becomes extremely marginalized. 

Can a new version of sp82739 be created without the hard-coded reboot and are there any assurances that HP SSM will continue to be supported as it has in the past for the foreseeable future?

[Joel_R · Accepted solution]

FYI

SP91809 was released on 9/18/18 fixing the forced reboot issue.

ftp://ftp-boi.external.hp.com/pub/softpaq/sp91501-92000/sp91809.exe

Joel