To use config.xml for silent deployments, must you have the volume license version?

The package KB refers to paths and files that don't exist on the media that I have, and the setup.exe doesn't like that /config switch

If I install manually, I am never prompted for a product key, and the application is licensed.

If I run setup -q, I can get the installation to run silently, but I lose the ability to install to a custom location, and if run the app for the first time, I am prompted for a product key, which I never had to specify in the first place.

Can anyone assist?
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


It seems that the Custom Action is UI based which means that it will execute only at the time of non-silent installation. Try moving that CA to Execute Immediate sequence and if CA uses any dialog based property make sure that you declare it on the property table or by passing argument at command-line installation.

Answered 10/07/2008 by: zipsantro
Purple Belt

Please log in to comment
The MSI is buried inside a cab file.

I don't think it'd be wise to touch the MSI, and repackage the cab.

You can't create a transform on it, because it's called via the setup.exe

It's a true chicken and egg scenario. You can't use the msi on its own, nor can you avoid using the setup.exe
Answered 10/07/2008 by: AaronTan
Senior Yellow Belt

Please log in to comment