cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not applicable

commandline install doesn't check conditions?

I have an .msi install that has install conditions, system searches, etc. All of these things work great when the install is run normally. However, if I run the install from the commandline none of these checks get performed and the install just installs iteself and that's it. Do I need to set something somewhere or what am I doing wrong?
Labels (1)
0 Kudos
(2) Replies
RobertDickau
Flexera Alumni

That doesn't seem right (LaunchConditions and AppSearch should appear in both the UI and Execute sequences). Does a log file tell you anything more?
0 Kudos
Not applicable

I figured out what my problem was - I had created a few custom actions to check for certain requirements that were triggered off of the 'next' button I had (doActions on the InstallWelcome Screen). I didn't add these actions to the Execute sequence however. Once I did that everything was fine. J
0 Kudos