Reader DC via Group Policy deploying 2015 version

Explorer ,
Oct 22, 2021 Oct 22, 2021

Copy link to clipboard

Copied

I'm trying to get Reader DC to deploy to a test machine, but it keeps installing the 2015 version.

Steps I've taken so far:

- Apply for the Distribution License, Get approved, and download the .exe file (Windows 10).

 

-Extract the .exe into it's files (cab, ini(2), msi, exe, msp) into a network share: "\\SHARE\Deployables\AcroRD21007\"

 

-Download/Install the same version of Acrobat Customization Wizard as the installer

 

-Within the Wizard: File>Open Package>\\SHARE\Depolyables\AcroRD21007\AcroRead.msi

 

-Configured using this as a guide: (https://www.pdq.com/blog/adobe-customization-wizard-xi-tutorial/)

 

-Transform>Generate Transform

 

-Verified Setup.ini was changed:

---------------

[Startup]
RequireMSI=3.1
Require64BitVC10RT=1
CmdLine=/sall /rs

[Product]
PATCH=AcroRdrDCUpd2100720099.msp
msi=AcroRead.msi

---------------

-Configured GPO using this as a guide: (https://www.adobe.com/devnet-docs/acrobatetk/tools/DesktopDeployment/gpo.html). Ensuring to select the .mst from the Wizard in the rule.

 

-Assigned the software to a machine in a test OU, ran gpupdate on target machine.

 

Initially, I was trying to just extract the .msi and and I was having the same issue. When trying to update, I was given "Error: 111100" which I am unable to find documentation for. 

Now, after doing all of this, I'm back where I started. 2015 version, with no ability to update.

Each new attempt at installing on test machine is done with a clean OS (No previous Adobe installations)

What am I missing?

TOPICS
Download and install , How to , Windows

Views

64

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Explorer , Oct 22, 2021 Oct 22, 2021

I researched slipstreaming updates and was able to patch the .msi to include the .msp and this solved it.

Likes

Translate

Translate
Explorer ,
Oct 22, 2021 Oct 22, 2021

Copy link to clipboard

Copied

LATEST

I researched slipstreaming updates and was able to patch the .msi to include the .msp and this solved it.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines