Creative Cloud Packager & SCCM - Acrobat DC - Package install starts but quits.

Report · Oct 17, 2017

Hello,

I have the task of packaging Adobe CC applications in my environment.

W10 64bit - v1606

SCCM - v1606

Adobe Acrobat Reader 2015 - Normally on machines by the time a CC user comes along.

All other packages have been created and installed successfully.

The Adobe DC application is proving to be challenging.

I have repeated the packing process twice with the same result.

The Job via SCCM completes. (Exit code 0) however no icons for the product show up.

I manually run the .MSI package and it attempts the install only getting so far... suddenly the install progress indicator goes backward and quits.

Any idea what is going on?

Thank you,Tony H.

Report · Oct 18, 2017

You will want to get a verbose installation log. Here is the Microsoft KB on enabling this Windows Installer feature.

https://support.microsoft.com/en-us/help/223300/how-to-enable-windows-installer-logging

After you have the log, then you can look at the error(s) that may be causing the installation problem.

Report · Oct 19, 2017

i have the exact same problem. Can't seem to find an answer anywhere. I guess my only solution is to try and bundle Acrobat DC alongside some of the other packages and hope that it works.

Report · Oct 19, 2017

I have the exact same problem.

I've narrowed it down to the Visual Studio 2013 C++ redistributable that Adobe is expecting.

I'm running Windows 10, and it auto installs version 12.0.406....

However Adobe doesn't recognise this as being installed and is prompting for an "ok" or "cancel" to continue installing.

You can't install the run bundled with Acrobat, as it's an older version.

So we're stuck being unable to deploy the application as it's expecting a response so throws an error.

Report · Oct 19, 2017

penishonc16073137 - Can you provide the verbose MSI logs for the installation that show this behavior to the Forum?

Report · Oct 19, 2017

Hi Steve

Please find see the appropriate lines from the logs:

Property(S): UnsupportedOS_HotFix = Acrobat requires an update for this 64-Bit operating system. The update can be found at http://www.adobe.com/go/ms_kb930627. Please update your system and run setup again. Setup will now terminate.

Property(S): UpgradeTagFile = instmsiw.exe

Property(S): VCRTFailureHeader = Visual C++ 2013 (x64) Runtime Missing

Property(S): VCRTFailureMsg1 = Installing Acrobat via MSI will not install Microsoft Visual C++ 2013 (x64) runtime. Without this, some application functionality will not work.

Property(S): VCRTFailureMsg2 = You can try installing using setup.exe if not already done. Press 'Ok' to ignore and proceed anyway or 'Cancel' to stop the installation.

Property(S): VCRTx64FileName = msvcr120.dll

Property(S): VCRTx64FileVersion = 12.0.21005.1

Property(S): ValueImportAction = Import Action

Property(S): WebRscProductCodeString = {291AA914-A987-4CE9-BD63-0C0A92D435E5}

Property(S): WIA_Service = ServiceNotRunning

I can find somewhere to upload the whole log file if needed.

The KB it refers to is one for Vista, not Windows 10.

We are running Windows 10 1703.

Report · Oct 19, 2017

You could try using this install PROPERTY to get around installing the MS C++ Redistributatables in the Acrobat installer.

Adobe Properties — Enterprise Administration Guide

Installation

DC and later

IGNOREVCRT64

Since Acrobat looks for Visual C++ x64 2013 Runtime (VC) by default, set IGNOREVCRT64 to 1 if it is not present AND not needed. IGNOREVCRT64 need only be used when all of the following are true:

During Acrobat installs on 64-bit machines
When Visual C++ x64 2010 SP1 Runtime is not installed
Installation is NOT done via setup.exe.
The following functionality is NOT needed: 1) Acrobat PDF Creation add-on (PDFMaker plugin) for Microsoft Office 64-bit applications (viz. Word, Excel, PowerPoint & Outlook) and 2) sending emails or resolving addresses via 64-bit Microsoft Outlook.

Since Acrobat looks for Visual C++ x64 2013 Runtime (VC) by default, set to 1 if it is not present AND not needed. During non-setup.exe installs when VC is not present, installation behavior is as follows:

Command line installs abort if IGNOREVCRT64=1 is not passed.
UI installs display a dialog asking the user whether they would like to continue or cancel.
Setup.exe installs succeed. Installs never abort as the property is passed while spawning the MSI.

For MSI installs, use Require64BitVC10RT in the Setup.ini file under the Startup section.

Installation

11.x only

IGNOREVC10RT

IGNOREVC10RT need only be used when all of the following are true:

During Acrobat installs on 64-bit machines
When Visual C++ x64 2010 SP1 Runtime is not installed
Installation is NOT done via setup.exe.
The following functionality is NOT needed: 1) Acrobat PDF Creation add-on (PDFMaker plugin) for Microsoft Office 64-bit applications (viz. Word, Excel, PowerPoint & Outlook) and 2) sending emails or resolving addresses via 64-bit Microsoft Outlook.

Since Acrobat looks for Visual C++ x64 2010 SP1 Runtime (VC) by default, set IGNOREVC10RT to 1 if it is not present AND not needed. During non-setup.exe installs when VC is not present, installation behavior is as follows:

Command line installs abort if IGNOREVC10RT=1 is not passed.
UI installs display a dialog asking the user whether they would like to continue or cancel.
Setup.exe installs succeed. Installs never abort as the property is passed while spawning the MSI.

For MSI installs, use Require64BitVC10RT in the Setup.ini file under the Startup section.

Report · Oct 19, 2017

Hi Steve

Thanks - should've looked there. That works for me, hopefully it resolves the OP's issue too.

Report · Oct 19, 2017

This is still not working for me, using SCCM to distribute. My command line looks like this, what am I doing wrong?

msiexec command is running on the msi located in the Build folder that was created by the Creative Cloud Packager

msiexec.exe /i "AcroPro.msi" IGNOREVCRT64=1 /qn

If I run setup.exe manually, it installs fine. However, if I try to run the setup.exe from SCCM, it also fails.

Please advise. All other products created from CC Packager distribute and install fine, it is only Acrobat.

Report · Oct 19, 2017

OK, first the Creative Cloud Packager's MSI is NOT the file that needs to take the PROPERTY command. It's the MSI file (AcroPro.msi) that is next to the entire Acrobat install files and Setup.ini.

Report · Oct 19, 2017

Ok, well since you seem to know the proper procedure, perhaps you could outline the entire process for me since I don't seem to be able to follow what you're telling me.

My process is as follows, please correct me where I'm incorrect:

I build my packages, per what Adobe told me to do, using Creative Cloud Packager, device licensing.

I then use SCCM to create an application, pointing at the MSI file that is created in the build folder of the Creative Cloud Packager's files.

This process has worked for Lightroom, After Effects, Illustrator, InDesign, Photoshop, and Premiere Pro.

Please tell me how to correctly build and package Acrobat for SCCM distribution, using the PROPERTY command to ignore the Visual C++ check.

Thanks,

Report · Oct 19, 2017

If you are going to use the Windows installer via the Acrobat MSI, then you can use the line that you have but just in a different directory.

So here is the path on my test system to the Creative Cloud Packager's setup.exe and MSI file. This is essentially a bootstrap to the actual Acrobat installer MSI/Setup.

C:\Users\Labuser\Desktop\Subscription Acrobat\Build\[filename].MSI

Here is the path on my test system to the AcroPro.msi with the actual installer files. Note, your path to the file may be slightly different:

C:\Users\Labuser\Desktop\Subscription Acrobat\Build\Setup\APRO17.0\AcroPro.msi

This KB might help tailor it to your installation.

Deploy Adobe Acrobat XI or DC

Report · Oct 19, 2017

I've tried your suggestions, including downloading the Acrobat Customization Wizard. Unfortunately none of this works. This is the most painful process I've ever experienced trying to deploy a piece of software, particularly an MSI file. I've literally spent the entire part of my last two days unsuccessfully attempting to install this software.

Since my company has a software agreement, is there some method of contacting tech support in hopes that they can assist in deploying Acrobat?

Report · Oct 19, 2017

Yes, they can start a case through the Admin Console.

Report · Feb 06, 2018

Did you ever get this to work?

I completely agree with your statement of "This is the most painful process I've ever experienced trying to deploy a piece of software". I've been at it for 6 weeks, and short of logging in to each computer with an admin account, and running "Setup.exe .sAll", I don't see any way of installing this software.