Adobe Acrobat DC CC Automatic Updates

[acjuelich]

Hello,

I created an Adobe Acrobat DC Creative Cloud installer (Device licensing).  In that process I specified to disable updates.  I tried to use the Customization Wizard to modify the created MSI (as I've done for previous Acrobat Pro installs) but it does not open and says it isn't supported.  From there I deployed the installer via 'setup.exe --silent' and all seemed well.  Adobe Acrobat appears to be automatically installing updates, though.

I have downloaded the Group Policy Templates and specified to disable updates but that does not work.  I can modify the registry setting via the Group Policy Preference information they gave but I'd like to avoid this if possible.

Any thoughts?

These were the URL's I was referencing:

Windows Updates

Group Policy-Active Directory — Enterprise Administration Guide

[Kanikas]

Moving to Installing, Updating, & Subscribing to Acrobat​

[Steve Cordero · Accepted solution]

In order of appearance of the post.

The MSI file that needs to be used when modifying the package with the Adobe Customization Wizard is NOT the MSI file that the Creative Cloud Packager creates.  It is the one within the folder path the would be something like this:

"C:\Users\[USERNAME]\Desktop\Adobe Acrobat Pro DC - CC\Build\Setup\APRO15.0\Adobe Acrobat\AcroPro.msi"

The "bUpdater" registry entry or the Disable Updates setting in the Creative Cloud Packager "should" both work.

[acjuelich]

So I grab the MSI from that location after I create the package in Creative Cloud Packager?  So I just ignore what the Packager creates?

[Steve Cordero]

No,  not necessarily.  You can make the modifications to the AcroPro.msi and still use the Creative Cloud packager installer.

[acjuelich]

So I can modify that AcroPro.msi and then deploy using the Creative Cloud Packager Project MSI?

[Steve Cordero]

Yes,  of course. It’s not hard at all.  Just remember to keep the Package and MST names the same for the CCP created package as it's already expecting the names it packaged not a modified one.

[acjuelich]

I just specify the MST in the 'setup.ini' correct?  This is how I've done it with Reader in the past, but that is deployed with 'setup.exe'.  Then deploy using the 'creativecloud_package.msi'?

[Steve Cordero]

I am going to send you a private link in a few minutes that will help explain the details.

[acjuelich]

That helped me out a ton.  I'm trying with the MST instead of 'saving' the MSI as was shown in the video.  I will test and see how it goes.

Thanks for your assistance!

[acjuelich]

Got it figured out thanks to Steve.  Here are the steps, in order, that I followed to complete this:

1. Create your Package with Creative Cloud Packager.  Let's say it was called 'AcrobatDC_CC'
2. After that is created, navigate within that folder to 'AcroPro.msi.'  This will be within 'Build\Setup\APRO17.0\Adobe Acrobat'
3. Open 'AcroPro.msi' with the Acrobat DC Customization Wizard and customize to your liking.  Save this customization as an MST (Transform File).  Let's called it 'AcrobatDC_CC.mst'
4. Within the same directory, open up 'setup.ini'
5. Under the 'Startup' heading ensure you have the following: CmdLine=/sall /rs
6. Under the 'Product' heading ensure you have the following, under 'msi=AcroPro.msi:' cmdline=TRANSFORMS="AcrobatDC_CC.mst"
7. Go back to your 'Build' folder and run the following script: "Setup.exe /sall /rs"
8. Done