I've been asked to try and solve a problem with regards deploying an MSP and MSI together. What I need to do is 'import' an MSP into an MSI so that the MSI is then deployable without the need to deploy the MSP over the top afterwards.

Everything I have read seems to suggest that I can slipstream the MSP into an administrative install of the MSI, this appears to work in that I can see the uncompressed source files have been patched correctly but when I then deploy the MSI it carries on using the files that are compressed within the MSI. As a side note I can see that the MSI has had something done to it (after the admin install) as the time/date on it has changed although it is still the same size.

So is there any way to somehow 'force' the MSI to use the patched uncompressed files or am I going to have to repackage the MSI using the updated files which somehow seems overly complicated for what I'm trying to achieve...

Thanks in advance.

Answer Summary:
3 Comments   [ - ] Hide Comments


  • Are you using the correct MSI, i.e. the one which appears in the root of the AIP? The source MSI should remain untouched and, if the source MSI had the files compressed in it, the 2 MSIs should certainly be much different in size.

    I wonder if you might be trying to patch the source MSI, i.e. running ther patch but pointing the AIP's location when prompted to be the same path?
  • have you first uncompressed the MSI with the /a option, after that apply the Patch with the /p ...msp /a locationofuncompressed.msi ?
  • Thanks for the replies. After VBScabs reply I investigated further and this time did the admin install first of all, this in turn did then give me a 'new' msi very much cut down in size from the original one. I was then able to patch this using the patch and performing 'another' admin install but this time pointing it at the 'new ' msi.
    I realised that I was trying to do the patching and admin install all in one go (as this was the way I was reading it at various sites) when it seems you need to do it in 2 stages.
    Thanks for the help and have a good Christmas!
Please log in to comment

Answer this question or Comment on this question for clarity



The best thing you can do is run the MSI install and specify the MSP on the command line.  This saves you from messing with the admin install process.  You'll have to specify the specific path to the MSP, so I use %~dp0 on the commandline. One note; if you're using SCCM 2012, you can not specify the MSI with a MSP and a transform within a task sequence.  It's a bug.  You'll have to run the MSI with the MST, then follow it up with the MSP.

Answered 12/23/2013 by: vjaneczko
Eighth Degree Black Belt

  • Unfortunately thats not an option. The original vendor MSI breaks another app already installed on the machines if it's installed first without being patched
Please log in to comment

If the end rusult absolutely has to be one single msi file and you are not in any way required to keep the vendor msi/msp's create a new msi with snapshot/repackaging.

Another way would be to open your msi in admin studio and convert to ism, open up the msp as well and apply the changes to the ism. Generate a new msi from there. Both options will kill your vendor productcode. That;s fine as the vendor is not responsible for what you have created now. 

Best is however to go with the commandline solution from the previous answer. As wel as being standard functionality it keeps the installlation in such a state that you can  keep applying standard vendor updates and releases without having to de extra repackaging.


Answered 12/24/2013 by: EVEEN
Green Belt

Please log in to comment