Software Deployment

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

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup" 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.