/build/static/layout/Breadcrumb_cap_w.png

MSIs, Custom Actions, Repair, and frustration

I'm building a couple of MSIs that need to run a .vbs after all the files are installed/copied.

When the MSI is run normally, it works fine.

If I do a:
msiexec -i "\\server\apps\winstall\dat\Messaging Client(s)\gaim\2.0B3\gaim.msi" /qn REINSTALLMODE=vamus

when theres an older version of Gaim (in this case) on the machine, the Custom Action fails to run.
I have it set to run in the Install Exec sequence, After InstallFinalize
Install Exec Condition is "NOT Installed OR MaintenanceMode="Modify""

I also have this problem with another MSI

I'm probably missing something obvious, but is there a way to get the Custom Actions to run when the MSI is run in Modify mode?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: viswakar 18 years ago
Senior Yellow Belt
0
Hi ,

For a custom action to run at both installation and during maintenance you can use " NOT REMOVE " as condition .
" Action that runs during install and reinstall only ".

NB: Do not use 'v' in vamus option for the first installation of an application or feature .

Cheers !!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ