I have an captured MSI, which contains HKCU and HKLM entries.
The package works fine when tested manually, however it is creating issue when installed through SCCM. It doesn't contain any advertised shortcuts.
I have included active setup, however it doesn't solve the problem.
It always needs a repair after installation from user account to properly launch the application.

Can you please provide me starting pointers for troubleshooting this?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Are you sure that the installer didn't already contain an MSI? This sounds like classic "captured MSI" behaviour to me...
Answered 02/03/2012 by: VBScab
Red Belt

Please log in to comment
The first place to look is your source. Check if it's an MSI that you captured (yes, I'm repeating what VBScan said above). If it's not, check that the setup.exe doesn't kick off an MSI inside the setup or launch an MSI from within the media folder; that's an error that a lot of new packagers make. (It's not an MSI, so I captured it. True, the file wasn't an MSI, but it launched one.) So look there. Anytime a capture doesn't behave like an MSI should - stuff not working, transforms not being applied, properties not being accepted - that's the first place to start looking and 90% of the time that will be your problem.
Answered 02/03/2012 by: Arminius
Second Degree Green Belt

Please log in to comment
Look in the entries for 'MsiInstaller' in the Application log in Event Viewer and see which component(s) are not present. Then look at the MSI and check out what's in the component.
Answered 02/04/2012 by: andys0123
Orange Senior Belt

Please log in to comment