The package contains msi and msp file. I have tried using the administrative Install but fails in a network. So I decided to go with the separate packages. I have sucessfully Installed the msi file without a patch and another package with a patch. When I try to deploy it in a network it fails but using the command line it works fine.

Command line: msiexec.exe /p "path of the Patch file" /qn (works fine)

I need to deploy the package via network which command I have to use?

I need to use the parameters in 'ini file' section to deploy.

Answer Summary:
create separate installers for msi and msp. run the msi first and then msp
0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


Why don't you apply patch (.msp) on your base msi in your local machine itself and then try to install the patched msi..

msiexec /a <Local Drive>\MyMSI.msi /p <Local Drive>\MyPatch.msp TARGETDIR=<Local Drive>\MyFolder


msiexec /a <Local Drive>\MyMSI.msi TARGETDIR=<Local Drive>\MyFolder

and then

msiexec /p <Local Drive>\MyPatch.msp /a <Local Drive>\MyFolder\MyMSI.msi


Answered 06/14/2012 by: jagadeish
Red Belt

  • this doesn't work good with Acrobat and it is difficult to patch later MSPs
  • piyushnasa, I wonder how you handle the customizations for this kind? like, adding some registries some settings, change of shortcuts, etc? Do you use MST to make changes to the base MSI or you have another MSI for the customization thingy?
    By the way, if you need to run this patch to install to users, you may need to use this:
    msiexec /p patch.msp REINSTALL=ALL REINSTALLMODE=omus
    Running the patch without the 2 extra properties will not patch an existing installation. It will only update the locally cached copy of the MSI database. That is what I think.
    • I need to install the patch through the network please find the details below
      INI file section
  • EXEFile=msiexec.exe
    AddCommand= /p "path of the Patch file" REINSTALL=ALL REINSTALLMODE=omus /qn
  • Please find the error details below
    'This patch package could not be opened contact the application vendor to verify that is a valid windows installer package'
  • 'This patch package could not be opened contact the application vendor to verify that is a valid windows installer package' - This error could be related to a path or wrong syntax or very long path. Always add a log syntax to verify what is going on of course.
    Can you try a batch file and see if its going to work? Put this line in the batch file on the same location with your msp.

    msiexec.exe /p "yourpatch.msp" REINSTALL=ALL REINSTALLMODE=omus /qn
Please log in to comment



I want to reiterate what has jagadeish said. That is also what I do and customize it using the Adobe Customization Wizard X. For a complete information on how to do that and manage your patches, you can take some time reading some stuffs from Adobe website itself.

Answered 06/14/2012 by: dj_xest
Fifth Degree Black Belt

Please log in to comment

Ask the deployment guys to create 2 separate packages in the tool like in SCCM we can create 2 different packages. One will install the MSI and the other will install the MSP with the command line as you have mentioned above.

They would then have to chain these installs.

Answered 06/15/2012 by: piyushnasa
Red Belt

Please log in to comment
Answered 06/15/2012 by: jagadeish
Red Belt

Please log in to comment

How do you deploy it in your network when it fails? Do you get any error message?

Answered 06/15/2012 by: henrik80
Second Degree Blue Belt

Please log in to comment

Are you using any deployment tool like SCCM, KACE or Altiris to deploy this patch?


Answered 06/14/2012 by: adilrathore
Fourth Degree Black Belt

  • I am using the vendor Installer and using Wise tool
Please log in to comment
Answer this question or Comment on this question for clarity
Nine Simple (but Critical) Tips for Effective Patch Management
This paper reviews nine simple tips that can make patch management simpler, more effective and less expensive.