Software Deployment

I don't think that it really is necessary to clean up all the msi stuff during packaging because I presume that a good exclusion list already filters out all these stuff...

ORIGINAL: rpfenninger

I don't think that it really is necessary to clean up all the msi stuff during packaging because I presume that a good exclusion list already filters out all these stuff...


Depends entirely on the quality of the packaging tool, the completeness of the exclusions list and the knowledge of the packager in being able to identify things that shouldn't be in the package, but for me, running MSIZAP seems like a catch-all solution. We use WinInstall and I have to admit that it still captures MSI specific information on occasion. Remember that developers of repackaging tools would surely expect the repackager to be following best practices and so may assume that they weren't ever going to try and recapture an MSI.

As an example, imagine you didn't realise that your installation setup was an MSI (wrapped in a setup exe), and you inadvertantly captured it. Sometimes it's only been after the capture that I have been able to spot that I've captured an MSI package in error. Having not so tight exclusions it would seem, has made this possible.

Ofcourse, now as a better method of checking for MSI installations I always have verbose logging turned on in the policy.

Alan