Hi,

We are deploying MSI packages via SCCM 2007.  In SCCM, there is an option in the advertizements that « rerun if failed previous attempt ».  I understand that if the MSI return a 3010 (reboot required), SCCM will consider the installation as « failed » which is not exactly true.   Is there a way to tell SCCM NOT TO RERUN if the MSI return the exit code, 0, 3010 or 1641?

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

 

With SCCM, if the exit code is 0 it will not rerun.

 

With exit code 3010, unsure, I think SCCM waits for the reboot? I cant remember - stupid brain. Anyway, I do recall a 3010 as a werid one, since a 3010 is not really a fail, I think you can make it a (SCCM) success, but you need to do some custom vodoo (config) magic with SCCM (ask google about that).

 

With exit code 1641, reboot, that could be bad for users randomly rebooting? Avoid a reboot if you can with REBOOT=REALLYSUPPRESS, you can also put that in a property.

 

Answered 04/09/2013 by: rileyz
Red Belt

Please log in to comment
1

Next, investigate why the package requires a reboot. If, for example, it's because it's adding to the System path, a simple edit can change it so that it adds to the User path instead, which doesn't require a reboot.

Answered 04/09/2013 by: VBScab
Red Belt

Please log in to comment
1

Rather than calling msi directly through SCCM, You can call VBScript (with error control) which will call your msi/mst..

Answered 04/10/2013 by: jagadeish
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity