I just went through this creating an install package for Adobe Reader DC. I used Powershell App Deploy Toolkit (I love that thing), but essentially, what is happening is two different command lines. First run your regular msiexec /I , then run another command to install the MSP separately. In my case, I have a transform file, and the whole line looks like this:
Execute-MSI -Action Install -Path 'AcroRdrDC1500720033_en_US.msi' -Transform 'AcroRdrDC1500720033_en_US.mst' -Parameters '/qn /norestart' Then right after that, I install the MSP separately: Execute-MSI -Action Patch -Path 'AcroRdrDCUpd1500920077.msp' -Parameters '/qn /norestart' If you don’t use PSADT, the patch install itself looks like: msiexec /update "AcroRdrDCUpd1500920077.msp" /qn /norestart From: [email protected] [mailto:[email protected]] On Behalf Of ccollins9 Sent: Wednesday, November 4, 2015 2:04 PM To: mssms <[email protected]> Subject: [External] [mssms] Installing MSI and MSP a same time Anyone have experience doing this with SCCM 2012? I'm not trying to use a patch file on this, but will if I need to. Example command line: msiexec.exe /i appname.msi PATCH=patch.msp /q. Apparently the PATCH= needs a full path. How can I identify the temp path that the file will run from c:\windows\ccmcache\x? I've tried: msiexec.exe /i appname.msi PATCH=.\patch.msp /q and msiexec.exe /i appname.msi PATCH=~%dp0patch.msp /q None seem to be working. Any help would be appreciated. Thanks!
