/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


Superseding Adobe Reader DC1501020056 with DC1701220093 using SCCM/Configmgr

09/12/2017 3537 views
Hi,
I wondering if anyone knows how to upgrade or replace Adobe Reader DC 2015 with DC 2017 using SCCM?
I have downloaded AcroRdrDC1701220093_en_US.exe and extracted the msi and generated the mst using the Adobe Customisation Wizard tool. However the GUID and ProductVersion is the same as the msi (AcroRead.msi) contained in AcroRdrDC1501020056_en_US.exe which I have installed currently and would like to remove and replace. I have just noticed that the AcroRead.msi is the same file in both versions, but there is a different msp with it that upgrades it. AcroRdrDCUpd1501020056.msp

Both the msi's contained in the two versions have the same properties as shown below:
ProductName: Adobe Acrobat Reader DC
ProductCode: {AC76BA86-7AD7-1033-7B44-AC0F074E4100}
UpgradeCode: {A6EADE66-0000-0000-484E-7E8A45000000}

I usually add another application to SCCM and set it to supersede. But as detection methods are using the GUID which are the same for both products it's not going to work.

If I install AcroRead and then apply the msp and obtain the GUID from the machine it is install on it is still the same as mentioned above 

How do I get the msp applied to bring the machines from 2015 to 2017?

Any help would greatly appreciated.



Answer Summary:
1 Comment   [ + ] Show comment

Comments

  • Thank you for the great advice. I had initially an application with a deployment type containing the base acroread.msi with a mst I generated. I'm wondering if I can now do the following: I would now need to supersede this application (and uninstall) with another but use setup.exe, add the latest msp and update setup.ini. As for detection I could use the guid with version since once the msp is installed the version will be incremented. Pls I could use additional checks such as setup.exe file size.

Answer Chosen by the Author

0
Sorry I misread your post.  What I mentioned would be for initial install.  For upgrade you can try this...

http://www.74k.org/updating-adobe-reader-with-a-msp-file


Answered 09/12/2017 by: DaBXRoMeO
Senior White Belt

All Answers

0
You have to use a MSP.  The MSP is the patch that will update the original version.  I did it by downloading the newest version of Reader.  Extracting the files.  Placing the .MSP file in the source directory of my package.  Updating the Setup.INI file (as seen below).  Then, I just created the Application using the Setup.exe.  The installation will recognize the patch and install it with the update.

It should look something like this in the Setup.INI: 

[Startup]RequireMSI=3.0CmdLine=/sall /rs[Product]PATCH=AcroRdrDCUpd1700920044.mspmsi=AcroRead.msiCmdLine=TRANSFORMS="AcroRead.mst"[MSI Updater]Path=http://ardownload.adobe.com/pub/adobe/reader/win/8.x/8.0/misc/WindowsInstaller-KB893803-v2-x86.exe

Reference to solution.


Answered 09/12/2017 by: DaBXRoMeO
Senior White Belt

0
I add application size as a check. I select the main .exe and check if the file size matches.

Please check my tip for Adobe Captivate CC edition. The images were reduced in size by ITninja but it may still help you.

http://www.itninja.com/software/adobe/captivate-1/11-1691
Answered 09/14/2017 by: nagendrasingh
Black Belt

0
Thank you for the great advice. I had initially an application with a deployment type containing the base acroread.msi with a mst I generated. I'm wondering if I can now do the following: I would now need to supersede this application (and uninstall) with another but use setup.exe, add the latest msp and update setup.ini. As for detection I could use the guid with version since once the msp is installed the version will be incremented. Plus I could use additional checks such as setup.exe file size.

And presumably when another update comes out I update setup.ini and replace the msp with the latest and supersede again. Would I best best to let the supersede uninstall the old version or update?
Answered 09/14/2017 by: edgefield
White Belt

0
If you take a few minutes to review the Acrobat Reader DC installs, you will find that the base MSI has remained unchanged from the time the program was initially released. EVERY update since then, including the 2015 to 2017 "upgrade" still uses the same base MSI but always with an updated MSP.
So all you have to do is deploy the latest MSP. That is ALL you have to do - no rocket science or deep thinking involved.
Answered 09/15/2017 by: EdT
Red Belt

  • Hi,
    But just one question when I only use the MSP file afterwards. How do I configure new settings which come with the MSP file. How do you set the reg key after updating? As far as I can see it, Adobe release new features, new wizards and these I would like to supress by default.
    Thanks
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ