i have been tasked with producing our default apps in msi and deploying via GPO, how can i get around the problem of removing the old app and re-installing it via GPO, i use winstall le to create the packages
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


One way to do that would be to create tranform files for the MSI packages. I know it's easy with Office, but not sure how difficult it is with apps that don't have their own custom install wizards.

With Office transforms, you can have it remove all previous versions before installing the new version. That's all done in one shot so it's simple.

Custom transforms is the way to go if you can figure them out for each package. If not, I don't think there's an easy route.

Answered 04/16/2004 by: A-Baum
Senior Yellow Belt

Please log in to comment
Got the same problem to resolve!

My first idea is to create a batch file with uninstall strings of installshield installation (got from registry), uninstall.exe or whatever else I can find, to uninstall like all apps I will deploy.

As applications were always installed in the default directory, the user settings should stay the same for most of all apps.

Putting that on the test bench ASAP!

Any1 got a better idea?
Answered 04/16/2004 by: in4matik
Senior Yellow Belt

Please log in to comment
Well it really depends on how you deployed the old app. It will also depend on how you deploy the new apps. Workstation or user deployed. If they are workstation deployed then its simple.

If the old app is an msi then you just create a custom action to remove it during the install of the new one by calling the msiexec.exe /u <msiname.msi> /qr. If you want to get fancy then set a launch condition to remove the old app if found.

If the old app is a setup.exe then do a capture of the setup.exe and create a Wisescript with the files and registry keys to remove. Create a custom action call the Wisescript in your new msi to remove the old app first then install the new msi.

If the old app is an SMS script then you can call the SMS uninstall script from within your new msi during install. Do it as a custom action.

If the app is user based/installed by user then it might be trickier because your users will have to remove the old app prior to installing the new one. Users may not have the rights to remove HKCR keys etc depending on your environment...so take that into consideration as well.

If you deploy the new app to the workstation as workstation deployed then your custom actions will remove the old app and registry keys in the system context without a worry......but it wont remove any HKCU data concerning that app. Remember to set a unique key and then you will be able to set a condition on the msi to help remove any user registry settings once the app is first run.

I really should diagram this one day to help explain it better. Beware HKCU keys in old apps.....they can cause lots of injuries.
Answered 04/19/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment