Sophos Client Install - how to detect failure
This question seems half package development and half SCCM, but I'll start it off in the Package Development forum.
I created a package in Wise Package Studio 8 to install the Sophos Safeguard (formerly Utimaco) encryption client. The package installs 3 MSIs: one does some pre-install actions, one installs the actual client, and one does configures the client.
Here's my challenge: if a PC has installed another program that requires a reboot, but the PC hasn't rebooted, the Sophos install will fail at the 2nd MSI. The first MSI (the pre-install) is successful, but the 2nd and 3rd MSIs fail due to the pending reboot. The log file for the 2nd MSI states "Error 5002. Some pending file operations were detected."
But even though the 2nd and 3rd MSIs don't really install, SCCM reports the package install as Successful.
Another thing I tried was separating each MSI into its own package and running them sequentially in SCCM, but that netted me the same end result: even though MSIs 2 and 3 failed, SCCM reports the install as Successful.
Seems I need a way to evaluate whether MSI #2 failed or not, and if it did, do something so that SCCM reports the install as a failure, but I'm not exactly sure what to do.
I created a package in Wise Package Studio 8 to install the Sophos Safeguard (formerly Utimaco) encryption client. The package installs 3 MSIs: one does some pre-install actions, one installs the actual client, and one does configures the client.
Here's my challenge: if a PC has installed another program that requires a reboot, but the PC hasn't rebooted, the Sophos install will fail at the 2nd MSI. The first MSI (the pre-install) is successful, but the 2nd and 3rd MSIs fail due to the pending reboot. The log file for the 2nd MSI states "Error 5002. Some pending file operations were detected."
But even though the 2nd and 3rd MSIs don't really install, SCCM reports the package install as Successful.
Another thing I tried was separating each MSI into its own package and running them sequentially in SCCM, but that netted me the same end result: even though MSIs 2 and 3 failed, SCCM reports the install as Successful.
Seems I need a way to evaluate whether MSI #2 failed or not, and if it did, do something so that SCCM reports the install as a failure, but I'm not exactly sure what to do.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
dunnpy
13 years ago
Ron,
Just thinking off the top of my head here...
You could put a system search in the package (or launching VB Script) to check for pending file operations (registry), so that it fails gracefully if there is something pending. SCCM should then report as a 'proper' failure so you can mop-up accordingly.
There is a tool called WhyReboot that will help you work out where those pesky pending operations are.
The other possible option is to set SCCM to only run the package 'Only When User Is Logged Off', based on the thinking that this will catch the machine when it has first been booted and before logon - meaning no pending file operations. This assumes that your users shutdown every evening or shutdown rather than logoff when finished.
Hope that helps,
Dunnpy
Just thinking off the top of my head here...
You could put a system search in the package (or launching VB Script) to check for pending file operations (registry), so that it fails gracefully if there is something pending. SCCM should then report as a 'proper' failure so you can mop-up accordingly.
There is a tool called WhyReboot that will help you work out where those pesky pending operations are.
The other possible option is to set SCCM to only run the package 'Only When User Is Logged Off', based on the thinking that this will catch the machine when it has first been booted and before logon - meaning no pending file operations. This assumes that your users shutdown every evening or shutdown rather than logoff when finished.
Hope that helps,
Dunnpy
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
