Comments on: Customize and Deploy Adobe Acrobat Reader using SCCM

By: GC

The patch does not install using the provided example.

Tested on
Reader DC 2022.003.20322 MUI for Windows-64bit
Reader DC 2022.003.20322 MUI for Windows-32bit

after install the 32 bit version is 15.007.20033 the 64 bit version is 2021.001.20135
I will try playing with Christopher Ireland’s suggestion to see if I can get the patches to install.

By: DT

The AcroRead file that is extracted is from 2015. How do you extract a more recent file?

By: Mohammed Younis

Mohammed Younis

Hi,

I have deployed Adobe reader DC to the firm. I need to enable Adobe to automatically update without any intervention from me.

What is the best way to do this?

Any advice is appreciated, thanks

By: John

John

In reply to Prajwal Desai.

This is happened when we deploy Adobe Reader DC version 2022.002.20212.

At the end, there is 2 version found at PC (Adobe Acrobat Reader DC 15.007.20033 and Adobe Reader DC version 2022.002.20212).

Is there any missing steps or way to prevent this?

By: Prajwal Desai

Prajwal Desai

In reply to John. This can happen if you have deployed the application as required.

By: John

John

Adobe Acrobat Reder DC 15.007.20033 installed by itself with this method.

By: Vitaly

Vitaly

Hello,

First i would like to thank you for everything, whitout your blog i don’t know where would i be: D

With this manual I’ve created the application in SCCM, until this day everything was perfect.

Today if i click on the install button in the Software Center the next version will be installed:

2015.007.20033

If i download the latest msi file what is 2022.001.20117 the problem is the same.

Do you have any ideas why is this happening?

Thanks in advance.

Best regards, Vitaly

By: majel

majel

for me is better using setup.exe with *.cmd START /WAIT “%~d0” “Setup.exe” /sAll /rs /sl “1029”
(/sl “1029” is my language)
first, there is no new package for my language (it always downloads the old version 19.0.** or 21.0.**) so I download the MUI version and the second is that this is the initial installation of adobe via sccm so I set in the installation that I want to uninstall all previous installations of the reader (currently we only use 64bit, but historically there are a lot of machines with 32bit versions) and this function only works when you run setup.exe. (see note under this option)

By: Matt Nicholson

Matt Nicholson

It’s worth noting that when installing Adobe Acrobat DC, the standard detection method of using the MSI ID doesn’t work because Adobe have used the same MSI ID for every version of Adobe DC since at least 2015. I’ve managed to get it working using the MSI ID *and* the specific version number:

Setting Type: File System
Type: File
Path: %ProgramFiles(x86)%\Adobe\Acrobat DC\Acrobat
File of folder name: Acrobat.exe

• The file system setting must satisfy the following rule to indicate the presence of this application
Property: Version
Operator: Greater than or equal to
Value: 22.1.20117.0

Note: You must ensure any older versions of Adobe DC are set to use the “Equals” operator, otherwise SCCM will not be able to tell the difference between the new and old versions and will repeatedly uninstall your application.

I’ve twinned this with another detection method (using the Or connector) looking for a specific registry entry. Possibly redundant, but I wanted to nail it down tight after having a *lot* of trouble with this deployment:

Setting Type: Registry
Hive: HKEY_LOCAL_MACHINE
Key: SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-1033-FFFF-7760-0C0F074E4100}
Value: DisplayVersion
Data Type: String

• This registry setting setting must satisfy the following rule to indicate the presence of this application
Operator: Equals
Value: 22.001.20117

Hope that’s of use.

By: Christopher Ireland

Christopher Ireland

There are several way to do this.

The straight MSI command requires the actual patch path to be included, which will be difficult considering the ccmcache folder will be different every time:
msiexec /i AcroRead.msi /qn TRANSFORMS=AcroRead.mst PATCH=C:\

The PowerShell method could handle it like this:
$args = "/i $PSScriptRoot\AcroRead.msi /qn TRANSFORMS=$PSScriptRoot\AcroRead.mst PATCH=$PSScriptRoot\AcroRdrDCUpd2200120085.msp"
Start-Process -FilePath msiexec.exe -ArgumentList $args -Wait -WindowStyle Hidden

But of course the easiest way to install after running the customization wizard is to simply run Setup.exe by itself. It will find the setup.ini file in the same directory and will install the MSI, the transform, and the patch automatically.