Skip to main content
J
jonh70769409
Participating Frequently
April 21, 2015
Answered

Deploying Acrobat DC with SCCM

  • April 21, 2015
  • 3 replies
  • 26121 views

My understanding is you no longer have to use a preinstall and can just run setup.exe from the command line (which there are 2 Btw, but this example implies use of the setup.exe from the exceptions folder, in which case why is there even another folder? I have tried both and neither work.

This is the information I can find about installing Acrobat DC in SCCM using the CCP.

Setup.exe /sALL /extUI /sl "[installLanguage]" /msi INSTALLDIR="" EULA_ACCEPT="NO" SUITEMODE=1 OWNERSHIP_STATE=1 LANG_LIST="[installLanguage]" INSTALLLEVEL=101 AS_DISABLE_LEGACY_COLOR=1 IGNOREAAM=1

Path of setup.exe:


<Package Location>\Exceptions\APRO12.0.0en_US\Adobe Acrobat\Setup.exe

So...

1. I create the 64- bit package in CCP and have two folders -  build and exceptions

2. I create a package in SCCM as usual and run setup.exe from the command line from this path: Exceptions\APRO15.0en_US\Adobe Acrobat

When I run a test from the command line my application install stops and asks for a serial number. ( I already entered that when I created the package). Moreover, the number it is asking for is different than the CCP serial number I use to create the package. Do I need two serial numbers, one to use in CCP and put one in the Abcpy.ini file?

So, this procedure appears not to work and I am stumped.

Can someone correct me if I am doing it wrong? Also, where are the variables from the setup.exe command above documented?

    This topic has been closed for replies.
    Correct answer ___Dom___

    Dominic,

    That made the install work!

    But on launch, Acrobat prompted for a user login. The instructions here: Creative Cloud Help | Deploying Adobe Acrobat mentioned that I should not put our CC license key in the wizard so I was not able to use the "Grant Offline Exceptions..." option. Putting the CC license key in the Wizard gives me a "[license-key-string] Error"], so I believe that's correct.


    I do have my ccp file at the root directory of the package and that did seem to suppress the login request if I didn't reference the mst with a TRANSFORMS= paraemter. Is there a way I can make the msi aware of the ccp? I didn't see that in the available properties in the document you referenced.

    Many, many thanks!

    Ric


    Hi Ric,

    the licensing information is installed by the setup.exe or the MSI in the "build" directory, so you need to execute that as well, e.g.

    cd Exceptions\APRO15.0en_US\Adobe Acrobat\

    start /wait msiexec /i "AcroPro.msi" /qn /lv* %TEMP%\AcrobatInstall.log

    cd ..\..\..\Build

    start /wait msiexec /i "PackageName.msi" /qn /lv* %TEMP%\PackageName.log

    cd ..\Exceptions

    ExceptionDeployer --workflow=install --mode=post


    Note that if you choose to use the msiexec method to install Acrobat, the default language will be determined by the operating system language.


    The ExceptionDeployer is necessary for the possibility there are other applications in the package (e.g. Edge Code, Scout) which need to be installed after the main "build" directory's packages.


    Hope that helps,


    Dominic

    3 replies

    ___Dom___
    Community Manager
    ___Dom___Community Manager
    Community Manager
    May 1, 2015

    As pointed out, the Acrobat DC setup.exe and the setup.exe or MSI from the "Build" directory are both necessary when installing a package containing Acrobat DC (the latter installs the licensing information).

    You can either run the setup.exe in the "Build" directory, or use msiexec with the MSI file in the "Build" directory, both will achieve the same result.

    Ric5
    Ric5
    Inspiring
    May 6, 2015

    People,

    I'm, trying to do the install with a batch script (we use deployment tools other than SCCM) and am trying to turn off the EULA window on first launch. I have this working with an msi and a ccp file I created with Creative Cloud Packager (serial number license under our ETLA). After a good deal of work (I'm mostly a Mac guy building Windows installers) I got it working with the line:

         msiexec.exe /i "Exceptions\APRO15.0en_US\Adobe Acrobat\AcroPro.msi" /qb

    But if I try to use the TRANSFORMS=[mytransform].mst switch to call the mst I created with the Customization Wizard (it's located in the same folder as the batch file and I have a copy in the same folder as the msi just to see if that helps) I get the dreaded "This installation package could not be opened..." error. With the Customization Wizard, I prepped the mst to turn off the EULA but, as Adobe said, I didn't enter the serial number in the C-Wiz as suggested in the help for CCP. Also, I could not get the script to run if I called the MSI in Build folder. It only seems to work with the one in Exceptions.

    Any ideas on what I'm doing wrong?

    ___Dom___
    Community Manager
    ___Dom___Community Manager
    Community Manager
    May 6, 2015

    The default transforms file used is AcroPro.mst, but you're referencing the installer from a directory several levels above. I suggest putting yourself in the directory itself before calling msiexec since you're using a relative path for the transforms file.

    e.g.

    cd Exceptions\APRO15.0en_US\Adobe Acrobat\

    msiexec /i "AcroPro.msi" /qb

    reference:

    Adobe Properties — Enterprise Administration Guide

    J
    jonh70769409Author
    Participating Frequently
    April 22, 2015

    Thanks Ashish

    Ashubijalwan1
    Adobe Employee
    Ashubijalwan1
    Adobe Employee
    April 22, 2015

    Hi Jon,

    If I understood the scenario correctly, you have created a package for Acrobat using CC enterprise serial key starting with 1591. In this case, you will need to run Acrobat from exception folder first which installs the app however in this case licensing remains with build folder hence after installing Acrobat from exception folder, you also need to run setup.exe under build folder to serialize acrobat.

    I think below batch script can help.

    i.e : I have created an Acrobat package only naming AcrobatDC

    Start /w Msiexec.exe /i “C:\Users\user name\Desktop\AcrobatDC\Exceptions\AcrobatProfessional12.0-mul\AcroPro.msi” /qn

    Msiexec.exe /i “C:\Users\user name\Desktop\AcrobatDC\Build\AcrobatDC.msi” /qn

    Hope this helps.

    Thanks,

    Ashish

      J
      jonh70769409Author
      Participating Frequently
      April 22, 2015

      When I try to run the MSI  from \Exceptions\APRO15.0en_US\Adobe Acrobat\ with msiexec.exe /i “AcroPro.msi” /qn ( I take the qn off to see what's going on), the installer stops and asks me for a serial number (a different number than I used in CCP to make the package)

      I am wondering if CCP is making the right package

      kbrister
      kbrister
      New Participant
      April 27, 2015

      It's sounds like the package is being created correctly. When installing Acrobat DC via command line, all I used was "Setup.exe /sALL /rs /msi EULA_ACCEPT=YES" . That sample syntax they give you on that support page just doesn't seem to work at all. That page is out of date anyways, looks like all they did was slap "DC" over anything that said "12".

      Once Acrobat DC is fully installed, make sure to then install the Creative Cloud Package installer from the build folder.

      You shouldn't be prompted for serial number.

      Regards,

      Kenton

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices