I have created an mst for a vendor msi and afterwards I try to apply an msp file.
This is failing. How can I see which customisations in my mst are causing the patch to fail ?
0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer

The best way to handle patches IMV is to have an Administrative Installation Point and patch that (having backed it up first, of course - always have a fall-back!). Then you can apply whatever transform/command line you want to the new MSI. The additional bonus is that you have a single maintenance point, rather than 'x', where 'x' is the number of PCs on which the product is installed.

As usual, create a verbose log for your installs when testing. Without a log, it's pretty much quess-work as to what's gone wrong.
Answered 08/03/2009 by: VBScab
Red Belt

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.


Yes, I have also done it in the same way previously,
Answered 08/04/2009 by: abking99
Second Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity