Software Deployment

As ever, use MSI logging to see what's going on. Run both installs with a verbose log and then compare the two. My guess is that a Custom Action is being run in the UI sequence but not in EI/ED. A log will give you that information.

Hi Ramesh,

U can also trobuleshoot capturing the registry information when manual installation and when not manual [command lind /qb /qn ] , so u can compare both , probably u may get the difference......!!


Thanks,
Sourav

ORIGINAL: sourav
U can also trobuleshoot capturing the registry information when manual installation and when not manual [command lind /qb /qn ] , so u can compare both , probably u may get the difference......!! Capturing the registry would be pointless in determining why a dialog box is presented or not since the registry isn't involved in that decision tree: that process is conducted 'internally' between the MSI and the Windows Installer engine.

I am guessing that what ever triggers to ask for a Username and Password runs in UI, and when you use /qb or /qr does not get executed. Check your CA's and which ones run in InstallExecuteSequence and InstallUISequence.

Hi Ramesh,
do you have Wise Install Taylor at hand?
If yes try to generate a MST for the app.
If you don't have Wise, you could try to log the installation and see, if you can find the properties which hold the values after they are put into the dialog.
An other way would be to open the MSI in ORCA and go to the control table. Remember the dialogs title and order the table after the first column and scroll to the entries for the dialog in question. Have a look at the entries in the 'Property' column.
Regards, Nick