Before you install a package created with Adobe Creative Cloud Packager, read this article. Follow the instructions in this article to ensure that the exception payloads are installed and configured correctly. If you are installing Adobe Acrobat, refer to the instructions in the article Deploying Adobe Acrobat.

Installation packages

When creating an installation package, Creative Cloud Packager presents you with a list of applications and components that can be installed, from which you make your choices. All of these choices are recorded in the package.

When you create a package for enterprise deployment, two folders are created:

  • The Build folder contains the MSI (Windows) or the PKG (Mac OS) file for deployment with enterprise deployment tools such as Microsoft SCCM, Apple ARD, or JAMF Casper Suite.
  • The Exceptions folder contains the payloads that must be installed separately.

If you are installing Adobe Lightroom 5 or prior

On Windows, Adobe Lightroom 5 and prior versions are packaged in the Exceptions folder.

If the only exception is Lightroom 5 or a prior version, use the following steps:

  1. Deploy and run the Adobe Lightroom MSI file using the following command:
    msiexec /i Lightroom.msi TARGETDIR="C:\Program Files\Adobe"
  2. Run the main MSI file to license the application.

If the exceptions are Lightroom 5 or a prior version and Acrobat, run XDA in pre mode, before you deploy Adobe Lightroom as outlined above.

If your package exceptions include, Acrobat XI or prior, Lightroom 5 or prior, and another app such as Edge reflow, do the following:

  1. Run XDA in pre mode.
  2. Run the main MSI.
  3. Run XDA in post mode.
  4. To supress the EULA, run the following command:
    • adobe_prtk --tool=EULA --leid=V7{}Lightroom-55-Win-GM --eulasuppress
  5. To supress the Sign in screen, run the following command. This step is not applicable in the case of named licenses.
    • adobe_prtk --tool=Register --leid=V7{}Lightroom-55-Win-GM --regsuppress=ss

For information on adobe_prtk, see Adobe Provisioning Toolkit Enterprise Edition.

If Muse fails to launch after installing

Muse CC requires .NET Framework 4.5.2 or later to function. If Muse is installed on a machine and is failing to launch, you may need to deploy .NET Framework separately. For Adobe® Muse™ CC (2015.2) and onwards, the exceptions (such as .NET) are copied in the following location and the you need to install them separately:

Program Files (x86)\Common Files\Adobe\Installers\Third Party\<Sapcode_Of_App>\<package_name>\

For Muse versions prior to CC (2015.2), you need to install the .NET framework from the exceptions folder.

After you deploy a package with Muse, use the following step to deploy the .NET Framework:

  • Run exception deployer in post mode.

    .NET gets installed on the client machine. Muse should now launch when you try to.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy