Is there a tool that can register all msiexec command lines that are run by a wrapper.

If we have to deploy a vendor setup, we disassemble the wrapper and deploy the msi's .
It is sometimes a challenge to know all command lines that are run by the wrapper.

A collegue told be a vague story about being able to log these entries in the setupapi.log.
Is this possibble ?
Do you know of any other tools that can register this information.

Procmon allows for msiexec to be monitored but it does not give an easy overview in my opinion.
0 Comments   [ + ] Show Comments

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.

Answers

0
Usually wrappers launch the MSI through a single command line with multiple arguments. After the MSI is launched by a wrapper, you can try using Process Explorer to see what command line was used for the msiexec process.
Answered 06/12/2010 by: john.pirvu
Senior Yellow Belt

Please log in to comment
0
Regarding setupapi.log you can specify to log all applications or a specific application (ex. setup.exe), search google for "Setting SetupAPI Logging Levels"
Answered 06/12/2010 by: AngelD
Red Belt

Please log in to comment
0
I usually use a vbscript called wmiprocessmonitor.vbs (search appdeploy for it) (to find out execution of external commands) in combination with windows installer logging policy (verbose logging) and debugview with the windows installer debug policy to fetch property changes during dialog option selections.
Answered 06/12/2010 by: AngelD
Red Belt

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