Note that there are some explanatory texts on larger screens.

plurals
  1. PONeed advice on installing an application silently with patches
    text
    copied!<p>What I want to do is install program X with patches silently. Program X has an installer that is an MSI package. Program X has quite a few MSP file patches (8+)that have been released that I also want to install silently. There are two ways that I've seen to approach this:</p> <p><strong>Method 1:</strong> Slip Streaming into "Network" installation</p> <pre><code>msiexec.exe /a "C:\ProgramX\ProgramX.msi" </code></pre> <p>When the GUI pops up, I choose a location to extract to, then after extraction apply each patch with:</p> <pre><code>msiexec.exe /a "C:\admin_install_location\ProgramX.msi" /p "C:\patches\update1.msp" </code></pre> <p>This method takes a long time to slip stream each patch and if possible I'd like to automate it somehow, perhaps using a /qb.</p> <p><strong>Method 2:</strong> Apply during installation</p> <pre><code>msiexec.exe /I "C:\ProgramX\ProgramX.msi" ADDLOCAL=ALL SOFTWARE_CLASS=Editor SEAT_PREFERENCE=Fixed /qb PATCH="C:\patches\update1.msp;C:\patches\update2.msp;C:\patches\update3.msp" </code></pre> <p>What I would like to get advice on is: </p> <ol> <li><p>Which one is better suited for patches? Should I just slip stream for big service packs which are released less frequently and use method 2 for patches?</p></li> <li><p>Will the slip streamed "network" install version install faster than method 2 (assume the patch list is > 8 msp files)?</p></li> <li><p>Can I create the network location silently somehow with something like this?</p> <p>msiexec.exe /a "C:\ProgramX\ProgramX.msi" /qb INSTALLDIR="C:\admin_install_location"</p></li> <li><p>Is there any way to apply the patches as I create the network install location such as this?</p> <p>msiexec.exe /a "C:\ProgramX\ProgramX.msi" PATCH="C:\patches\update1.msp;C:\patches\update2.msp;C:\patches\update3.msp"</p></li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload