Any other errors apart from 1603 in log files ?.

Did the application method work? I have tried but the keep getting a failed install with an exit code of 1636.

I noticed that the working directory is C:\Windows\System32 and not ccmchace folder.

Any ideas why?

1. Create an application (not a package) that installs the base unpatched Acrobat Reader from the .msi (Current base version of Acrobat Reader 2015 is 15.006.30033)

2. Create the an application to apply updates
2a. Download the latest .msp patch for the same track from the FTP site (current patch is 15.006.30201)
2b. Put the .msp file in the same directory as the .msi file
2c. Copy the SCCM Software Library application created in step 1
2c. Open the properties of the copied application. Rename it! (e.g. Acrobat Reader DC Updates)
2d. Select ‘Deployment Types’ tab, click the item in the list and choose edit
2e. Select ‘Programs’ tab and update Installation Program to:
msiexec /p “AcroRdr2015Upd1500630201_MUI.msp” REINSTALLMODE=vomus REINSTALL=ALL /qn
NOTE: change the .msp file to match the one downloaded
2f. Select ‘Detection Method’ tab and select the detection rule and edit item
2h. Select the second radio button (MSI product must exist and the following condition must be met)
2i. Select MSI Property: “Version”, “Greater than or Equal to”, 15.006.30201
2j. Select the ‘Dependencies’, click ‘Add’ and then ‘Add’ again: select the base application created in step 3 and select auto install
2h. Distribute the application
2j. Deploy the application to a collection that detects if the base software is installed. I’m using a collection query on SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode = {GUID} taking the GUID from the Detection Method of the application. In this way you can require the installation and it will only target machines that need the update on already installed software.

In the future: download a new .msp. Update the Installation Program value and update the Detection Method Version Number property. The new update should then get pushed to everyone.

-I set up mine as an Application vs. Packages because install detection is better (Wasn’t sure it would work, but I had no issues)
-In the application I edited the Deployment Type’s ‘Detection Method’ to also look for version and the ‘Dependencies’ to look for the original Acrobat Reader install. The update can then auto-install the base application.
-On the update command I used: “msiexec /p “[currentpatchfile].msp” REINSTALLMODE=vomus REINSTALL=ALL /qn” My understanding is that if you don’t so this the client machine’s cached .msi will not be updated

Agreed.