Please pardon the dumb question, but I'm new to using MSI files to deploy apps.
I have some apps that I deploy using an extracted MSI from the vendor's install.exe file, occasionally with transforms, as well as a few captured installs using Wininstall LE. Every so often, I need to modify a file or files that are contained within these packages, usually a config file. I'm wondering what the best method is to update these files?
Tools available to me at the moment are Wininstall LE and Orca.

I can easily create a new package, but that leaves a lot of custom installs sitting in the add/remove apps list.

In the Zenworks captured package days, we'd just replace, or add the file, update the version number and it would install.


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


We would generally create a new package like you say, and manage the upgrade process as a 'major upgrade'. This works well for our own repackaged MSI's but isn't so easy for vendor packages. Because the default sequence for a major upgrade is to install the new package and then uninstall the old one, it is quite efficient if you are only updating one file as the install of the new package just overwrites the single file and the uninstall of the old package will leave behind any files that haven't changed.

Alternatively, if it's a config file that we know is going to be updated frequently then we take it out of the main package altogether and manage it as an independant supplementory package.

Answered 03/14/2006 by: ab2cv
Orange Senior Belt

Please log in to comment