Help with Flash 10 uninstaller and vendor MSI


I'm new to Wise and have only had a brief overview and am struggling with a package I am trying. I need to get the adobe flash uninstaller to run, uninstall previous versions, the run the Flash 10 vendor MSI.

I have created a transform file to include mms.cfg which seems ok. I have re-used an older script that looks for older versions, runs the uninstaller if found, then runs the vendor MSI, and have included this script in a blank msi, the idea being > run the msi > this starts the uninstaller > Flash 10 MSI runs and installs. This all needsto happen silently and be deployed over AD.

The MSI runs, the installer starts but it errors and won't complete. Can anyone tell me if this is the right way to do, or is there an easier way? Does this even make sense!? Like I say I'm new to this and it's very trial and error.

0 Comments   [ + ] Show comments

Answers (1)

Posted by: anonymous_9363 13 years ago
Red Belt
It sounds like you're running your script - which eventually executes an MSI - from within another MSI. You cannot do that: the engine only allows one installation to run at a time. You would best be advised to just have the uninstall part in its own MSI (although I dislike that kind of thing, preferring to capture such activity). You can then set up your GPO to run that MSI first, followed by the Flash MSI and your transform. Remember to add MSIs to the GPO in the order you want them to execute.

BTW, FFR, saying "it errors and won't complete" doesn't really help. Stating the actual error or, even better, posting the relevant section of a verbose log (remembering to use the CODE tag, accessed using the button marked '<%'), means you'll get a more targetted response. You get a verbose log from the command line by using the '/L*V' switch:MSIEXEC /I foobar.msi /L*V %TEMP%\foobar.log For GPO targets, you can set a policy (Computer Configuration/Administrative Templates/Windows Components/Windows Installer/Logging/Enabled, replace 'iweap' with 'voicewarmup') or, more quickly, create a .REG file from this:REGEDIT4

and merge it into the target's registry. In either case for policy-based logging, logs end up in %SystemRoot%\TEMP, prefixed 'MSI' and with a '.LOG' extension. You'll need to search the logs for the particular product. I normally use the ProductCode, as it's unique.

Lastly, remember to turn the policy off/delete the 'Logging' entry, as it's an "all or nothing" policy - it logs GP advertisements as well as installs at every log-in - and will therefore quickly fill the folder with files.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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