Silently Install Adobe Creative Cloud

Deployment Examples, PDQ Deploy

You’ve got some users that need access to Adobe Photoshop or Dreamweaver perhaps…that’s where deploying Adobe Creative Cloud comes in. This post will have two parts. First you will make configurations using the Creative Cloud Packager, then you will create a deployment package to silently install Adobe Creative Cloud.

Note: These steps will ONLY work for Team, Enterprise, or Education plans of Creative Cloud, NOT individual.

Making Configurations with the Creative Cloud Packager

You’ll need to have administrator access to the Creative Cloud account. Log in at Adobe.com and select Manage team. From there you will be able to download the Creative Cloud Packager under Deployment Tools > Download Win.

creative cloud packager download

This will download the CCPLauncher.exe. Launch the executable and login, then you will be able to select Create Package.

create package adobe

Now you’ll need to give the package a name, a location where the package should be saved, architecture (32 or 64-bit), and the license type. License type will vary from plan to plan. Named License is available for the Teams plan. Serial Number License is available for the Enterprise plan, and Device License is available for the education plan. You should only see the license(s) applicable to your account.

adobe license type

In Package configurations, de-select the Applications & Updates via the Apps Panel options if the users are not also local administrators. This will keep your users from getting update notifications or otherwise being prompted to install updates.

silently install adobe creative cloud no update notifications

Next, select the applications and/or updates you wish to build into your installer.

installing adobe products

That’s it! Click build and the Creative Cloud Packager will create a directory containing your MSI installer.

Silently Install Adobe Creative Cloud Package

For these next steps you’ll need to have PDQ Deploy downloaded. The free version works great for deploying to either 32-bit or 64-bit architectures. However if you want to create a deployment package that will deploy to both the 64-bit installer and the 32-bit installer to the respective target computers, you’ll want a two-step package that allows you to specify which architecture each package is to be deployed.

For our example we will create a two step package to silently install Adobe Creative Cloud Package to both architecture types.



  1. In PDQ Deploy click New Package or select File > New Package.
  2. Name the Package and make sure you have your copy mode set to pull. Pull is recommended due to the size of this installation. Using the pull copy mode also requires that you place the Repository on an accessible file share. (Learn more about Push vs. Pull Deployments.) deploy adobe creative cloud
  3. Click on Step 1, give the step a title. For the Install File, navigate to the directory where you downloaded the Creative Cloud 32-bit installer. Make sure you select Include Entire Directory. If left unchecked your deployment WILL FAIL as you will be missing important pieces required for the installation. adding adobe msi
  4. Click on the Conditions tab and select the O/S Version. Since Adobe Creative Cloud products will only run on Windows 7 and above, exclude XP and Vista. Exclude servers unless required.

    Select the appropriate architecture. Since this step is installing the 32-bit Creative Cloud applications, select 32-bit from Architecture.architecture adobe cc

  5. If you have PDQ Deploy Pro or Enterprise mode and need to deploy another architecture type, add a new Install step. Repeat steps 1-4 with the new install file. If you are using the free version of PDQ Deploy or only need to deploy to one architecture type you’re ready to save and silently install Adobe Creative Cloud. install adobe cc

After you save the package you will find it in the Packages folder in the left side tree. Highlight the package, and click Deploy > Deploy Once in the right corner of the console.



IMPORTANT: While we make every effort to test on multiple platforms and architectures, it is highly recommended you test the deployment before a general release into production. Given the possibility of the package being substantially sized, testing will provide important information on bandwidth limitations and deployment times. In our tests, a single instance of Photoshop took anywhere from 15 – 20 minutes to deploy.

Troubleshooting Deployment Issues

If the package deployment fails and/or you receive a 1603 error, please try the following.

  • Machines should be fully patched and not in need of a reboot.
  • Check to ensure sufficient space is available on the drive where Adobe CC will be installed. Some Creative Cloud deployments can be several gigabytes in size, which includes the files copied to the target and the installed size.
  • Clear out %WINDIR%\Temp directory.
  • Review the troubleshooting steps in this article: http://support.adminarsenal.com/entries/448443

This post was adapted from a Knowledge Base article available at support.adminarsenal.com.

7 Comments

  • Hi Brigg, I just created the package following your instruction and it’s working like a charm. My package only contains Indesign 2015 and I deployed on a computer with Indesign 2014, so at the end I have both versions installed on that computer. According to you is there a way to automatically update the current version instead of installing the newer version next to the previous? If not, creating a package that first uninstall the previous version and then install the newer version could be a good idea?

    Thanks in advance.
    Ciao
    Massimo

    • Historically, Adobe has always allowed for side-by-side installations of its products, and will likely continue that practice since it has been the standard for the last 15+ years. This means in-place upgrades might never be the norm.

      If you want to uninstall the previous version, and you used the CCP to install the 2014 version, you can use the original MSI to initiate the uninstall as part of an uninstall/install package. The command line would be custom and look something like this:

      msiexec.exe /uninstall “<path_to_original_InDesign_CCP.msi" ALLUSERS=1 /qn /norestart /log output.log

      The difference from most uninstalls is the exclusion of the /x and the inclusion of the /uninstall parameter.

      Another option would be to use PDQ Inventory (Enterprise license required) to pull the uninstall string. This can be achieved by creating a report for the Adobe application and then creating a deployment based on the enumerated uninstall strings. You can also get this information direct from the registry, located in the SOFTWARE\[Wow6432Node\]Microsoft\Windows\CurrentVersion\Uninstall\{APP_GUID} registry path.

  • Hi guys
    While these steps will work most of the time, there seems to be an issue or bug with Acrobat package if you deploy it on its own with CC app.
    Basically, CC app is installed, but the Acrobat package exits with error code 19 (logs has a lot of return codes 1 in them, too). Despite the error code, PDQ will still receive code 0 and think it was a success.

    The workaround for this problem (and good alternative to above steps) is instead of using MSI file, use EXE file with –silent parameter.
    See Adobe documentation on how to specify language if required, not sure there are more switches though.

    As of today with latest CCPLauncher I can confirm that running exe silently installs both cloud and Acrobat nicely and it supports elevated installation where user is not required to be an admin for installs or updates from CC app.

    Cheerio.

  • Has anyone been able to deploy CC 2017 using the setup.exe with the silent install switch? I’ve tried this, but it appears to fail. I haven’t been including the entire directory as the setup.exe is suppose to support network based installations.

  • Hi Bryant,
    If you perform (in the build directory of the package you created with Adobe CCP) a setup.exe -help, you should see a usage statement:

    setup [--silent] [--ADOBEINSTALLDIR=] [--INSTALLLANGUAGE=] [{-h, -help, --help}]

    In this case, the silent switch would be --silent.

    If you do receive an exit code 19 (see the comment above), that typically means a, “Conflicting Process is Running” (it can also mean that a dependency failed if it’s a return code rather than an exit code.

    If you’re using the Adobe Acrobat or similar setup.exe (as found in ..\Build\Setup\APRO15.0\Adobe Acrobat\), the pertinent parts of the usage statement are as follows:

    /sAll = Silent mode for the product
    /rs = Reboot suppress
    /rps = Reboot prompt suppress
    /sl “LANG_ID” = Set Language; LANG_ID – Code in decimal digits

    So you would run the setup.exe with any of those switches in the deployment.

    If either of the above doesn’t help, please contact support: https://support.adminarsenal.com/hc/en-us

1 Trackback

Leave a Reply

Your email address will not be published. Required fields are marked *