SCCM 2007/ Packaging issue...
I have an application which has setup.exe as a source media. I can run silently with switches /S /v/qn manually but when I am trying to install it through sccm 2007 it does not install the application. no short cuts on desktop, start programs or in add/ remove programe or no where.I can see sccm logs are fine giving result code as o.
trying to find work around. After installing through SCCM 2007 MSI logs looks like
"MSI (c) (44:58) [14:24:49:947]: MainEngineThread is returning 3"
=== Verbose logging stopped: 7/31/2015 14:24:49 ===
Any permission issue.?
Ensuring you set the ALLUSERS property to '1' is also good advice. It should be in all your MST templates.
BTW, I'd certainly NOT let a vendor EXE loose Without knowing *exactly* what it's doing. Sure, it's extracting and executing an MSI but are you sure it's not doing other stuff once the MSI's done with?
Examine the logs that are created and it should identify which MSIs were run, from where and with what command line parameters passed to them.
Grab the MSIs and create an MST for each one and incorporate the relevant settings, plus your usual standards.
Test locally and if working ok, test through SCCM individually, deploying one by one.
If that works, then create an installation chain and retest the deployment.
Anyway, all user = true and under system account still fails, right?
Does the application require any network access?
Did play around with Program Properties of the package?
Perhaps enable "allow users to interact with this program" can help, some setup somehow require a GUI.
Even if setup is unattended.
Last options are to debug the MSI and find out what is causing this block or repackage the MSI...(yes, very ugly).