Adobe Installation and Licensing

Blog to post all Installer and Licensing related info to users of Adobe products

Nov 2, 2016

Creative Cloud Packager 1.10 & Creative Cloud 2017 are live!

**Update 12/06/16- CCP 1.11 with the new uninstall workflow is now live**

Hi All,

Apologies for my tardiness on the announcement of CCP 1.10 but I didn’t want to make two announcements in a week and give you Gibson fatigue which is a real thing apparently*.

Last week we went live with CCP 1.10 which, to the delight of the team has broken the endless 1.9.x loop. This release includes various under the hood changes but most significantly also includes the below features

  • When you create a package, a packageInfo.txt is created inside the build package folder. This file contains the list of products and updates that you have included in the package. For more information see, Deploy packages.
  • When you create a package, a ConflictingProcessList.xml is created inside the build package folder. This file contains information about processes that will conflict with the installation process. For more information, see Deploy packages.
  • When you start the installer, it will check for the conflicting processes running on the host computer and exit the installation if any conflicting processes are found.
  • The latest version of Remote Update Manager will be downloaded and packaged during the package creation process. For more information, see Use Adobe Remote Update Manager.

Also by way of a sneak we will shortly be including a new workflow in CCP for un-installing previous versions of Creative Cloud applications. If you recall presently the best method to remove a previous version is to use the original CCP package, however if you no longer have that package or wanted to remove only a subset of the applications that were packaged then you are out of luck. This feature when released in November will provide granular control over what previous version of the Creative Cloud applications to remove. I normally don’t like to speak about a feature before it is released but considering our big announcement today I thought it would be useful to know this was on the horizon.


Speaking of the big announcement !

Today Adobe has announced the release of Creative Cloud 2017. As part of this release 15 products have been updated with lots of new features. For more information on the features you can visit here.

For a snapshot of the products and their new versions please see the below table.

Product Version Full Installer
After Effects CC (2017) 14.0.0 Yes
InCopy CC (2017) 12.0.0 Yes
Photoshop CC (2017) 18.0 Yes
Premiere Pro CC (2017) 11.0.0 Yes
Media Encoder CC (2017) 11.0.0 Yes
Audition CC (2017) 10.0.0 Yes
Dreamweaver CC (2017) 17.0.0 Yes
Animate CC (2017) 16.0 Yes
InDesign CC (2017) 12.0.0 Yes
Illustrator CC (2017) 21.0.0 Yes
Bridge CC (2017) 7.0 Yes
Muse CC (2017) 2017.0 Yes
Prelude CC (2017) 6.0 Yes
Experience Design CC (beta) 0.6.2 No
Character Animator CC (beta) 1.0.5 Yes

All the products are now live in both CCP and the deployment snap in of the Enterprise Dashboard. As usual as these products are full installers so you cannot use the Remote Update Manager to install them. They will also install side by side with the current versions unless you un-install first.

Finally just a reminder you now also have the ability to allow non admins to install products via the Creative Cloud Desktop app by selecting “Elevated Privileges” when creating a package.


Karl Gibson | Senior Product Manager | Creative Cloud Enterprise

*No instances of Gibson fatigue have been confirmed to date*



  • By marco - 7:54 AM on November 3, 2016   Reply

    Hi, what about OS version needed to run these apps? (OsX in my case…)

  • By Mick Conners - 10:39 AM on November 3, 2016   Reply

    Quick question on this, so if we have CC2015, latest apps deployed and run Remote Update Manager command on these remotely, the existing apps won’t update to CC2017 will they? If they don’t, can we install the new apps along side of the CC2015 apps without conflicts?


  • By Adam Ealovega - 4:59 PM on November 4, 2016   Reply

    Hi Karl, Excited for the 2017 roll out. Great news. From a CCP standpoint, however, for the 2017 release I’ve been having a persistent “Failed to Initialize …. The Setup base path does not exist.” error on all custom Enterprise deployment packages I’ve built on Windows yesterday and today. I’ve not had this issue before CC 2017 so wanted to run it by you in case this could be a bug (would be equally thrilled if it was user error on my part). The “Setup Base Path” is equal to the location of the setup.exe and .msi I’m running in all cases so that is the confusing part. I’ve tried builds for AE and PS and tried on multiple client systems. Please reach out by e-mail and I can provide additional info if needed. Thanks, Adam.

  • By Frank Schöne - 6:42 AM on November 9, 2016   Reply

    Hi Karl, just one question. I want to deploy serialized so can I create a package for Experience Design CC (beta)? Best Frank

  • By Don W. - 9:34 AM on November 10, 2016   Reply

    We are running into issues with the new “Elevated Privileges” feature. User’s are still getting prompted for admin credentials on OSX machines even after they relaunch the Creative Cloud Desktop app.

  • By Don Montalvo - 3:33 PM on November 10, 2016   Reply

    Hi Karl,

    Thanks for the FYI, haven’t seen any requests for CC 2017 yet but this gives us a chance to get ramped up.


  • By Dawesi - 1:55 PM on November 12, 2016   Reply

    stuck in signin loop… CC 2017 is dead… wow… now I can’t code at all… oh well off to visual studio code until you fix it in 6 months time… #nothingchanges…

  • By sebus - 7:33 AM on November 19, 2016   Reply

    And where is CCP 1.10?
    Still can not find it…

  • By Calum Hunter - 2:42 AM on November 22, 2016   Reply

    hows that built in uninstaller coming along?

  • By Shane Palmer - 11:09 AM on January 4, 2017   Reply

    Karl, just a few points of feedback.

    As I mentioned in the MacAdmins #adobeinstalls Slack channel it would be nice if the ConflictingProcessList.xml file was in a human readable form so it makes easier for Admins to read and find out what conflicting processes to look out for. When opening this file in TextWrangler I can see that the entire XML file is ONE line. At the very least this needs to be formatted with each XML start tag, and possibly end tags (depending on the number of elements and type of element(s) contained), on a new line to make it easier for humans to read and to allow for XML aware tools like TextWrangler to be able to correctly present it in a readable form.

    Also, after doing my first build for 2017 that includes a bunch of recent updates I also noticed that the PackageInfo.txt is not very informative about the exact update versions that were included in the package. This is very important to have so that when I go back to look at this file months later I can tell how out of date my packages are. As you can see in the example below it does not show you what the exact update version is for CC2017 applications:

    This package contains following products
    SpeedGrade CC (2015) (9.0)
    Lightroom CC (2015) (6.0)
    Extendscript Toolkit CC (4.0)
    Fireworks CS6 (12.0.0)
    Extension Manager CC (7.0)
    Prelude CC (2017) (6.0.0)
    Muse CC (2017) (2017.0.0)
    Animate CC and Mobile Device Packaging (2017) (16.0)
    InCopy CC (2017) (12.0.0)
    Audition CC (2017) (10.0.0)
    After Effects CC (2017) (14.0.0)
    Dreamweaver CC (2017) (17.0.0)
    Premiere Pro CC (2017) (11.0.0)
    Media Encoder CC (2017) (11.0.0)
    Illustrator CC (2017) (21.0.0)
    InDesign CC (2017) (12.0.0)
    Photoshop CC (2017) (18.0)
    Bridge CC (2017) (7.0)

    This package contains following updates
    Adobe CSXS InfrastructureCS6
    Fireworks CS6 update to improve Mac 10.8 platform compatibility and resolve usability bugs.
    Extension Manager 6.0.8 Update
    Extension Manager CC Update
    Adobe Application Manager
    Adobe SpeedGrade CC 2015.1 Update
    Lightroom CC (2015.8) / 6.8
    Prelude CC (2017) (Full installer)
    Muse CC (2017) (Full installer)
    Adobe Preview CC (Full installer)
    Animate CC and Mobile Device Packaging (2017) (Full installer)
    Audition CC (2017) (Full installer)
    After Effects CC (2017) (Full installer)
    Dreamweaver CC (2017) (Full installer)
    Camera Raw CC (Full installer)
    Premiere Pro CC (2017) (Full installer)
    Photoshop CC (2017) (Full installer)

    • By Shane Palmer - 11:24 AM on January 4, 2017   Reply

      I also just noticed that it is not remembering the Advanced Settings>Adobe Update Manager Behavior between package builds. It keeps defaulting back to “Adobe Update Manager is disabled (IT manages update distribution)”.

      And as a related feature I would like to see it remember whether or not you have the Creative Cloud Desktop Application option checked. We use serialized installers and prefer not to have the CCDA installed so it would be nice not to have to uncheck this every time I build a package.

Add a comment