Adobe Installation and Licensing

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

Jun 24, 2014

I love the smell of a new release in the morning – CCP 1.6 is Live

Hi All,

What a lovely morning it is and you know what makes a morning even better? coffee and you know what else? a croissant. But after your coffee and croissant, that’s right a new product release! Fresh on the heals of the awesome 2014 product announcements + Ink and slide. We have also gone and released a new version of Creative Cloud Packager.

Features of this version include

The ability for Enterprise and Education Device License customers to create a license file.

Enterprise folks will remember this from the AAMEE days but it is also now possible to use CCP to create a license file. This is useful for enterprise customers if they wish to go from trial to serialised deployment or they wish to change from one license key to another.

For Education Device License customers this is especially important if you are trying to migrate from one license type to another for example going from a Team Named license to Device license.

CCP 1.6 copy

We have also added a nifty feature whereby when you create a license file we also produce a Un-License file that can be used to remove the Creative Cloud License from an existing machine.

The ability to create a package with just the Creative Cloud for desktop app

In the past it was not possible to create a package with just the Creative Cloud for Desktop app. This made things a little difficult if you wanted to deploy an update to the app across your environment. You can now create a CCP package containing just the desktop App.


InDesign CC 2014 & InCopy CC 2014 (32 Bit Windows) Issue

With the release of InDesign & InCopy CC 2014 we noticed an issue whereby when you select a 32 bit package in CCP an error is encountered during the build process. This is due to the maximum file path being exceeded during extraction. We are working on a long term fix however in the interim we have documented the required workaround here.

Adobe Muse CC 2014

On Mac, Muse CC 2014 is bundled in the main payload and it no longer requires an Adobe ID upon launch.

On Windows, Muse CC 2014 is still treated as an exception furthermore there is some nuances to how it is deployed. More information can be found here

Again we are working with the relevant teams to try and improve the process and make it as painless as possible to deploy.


Karl Gibson | Product Manager | Enterprise IT Tools



  • By Paul Benham - 5:47 AM on June 25, 2014   Reply

    There doesn’t seem to be a way in the new 1.6 version to unselect the Adobe Creative Cloud desktop app! This will be annoying for our lab deployments as the students will play around with the menu item extra on the machines.

    Also the Creative Cloud Packager automatically updated itself so that now it ONLY offers to download and package the CC14 versions of the Creative Cloud apps. This is a major issue for us as we were in the process of building and testing images for our labs (it’s the summer break here in the US) and the curriculums that the instructors have been working on use the CC versions, not the CC14 versions.

    Finally, it seems that if a lab machine already has the CC version installed, a new package created with the CCP1.6 will install the CC14 version ALONGSIDE the existing version and not just update it.

    This is a real mess.

    • By Karl Gibson - 6:21 AM on June 25, 2014   Reply

      Hi Paul,
      Thanks for the post. Regarding the first query.The option to include or exclude the CC desktop app on the configuration screen of CCP is still applicable. What is included by default is what we call “Adobe Creative Cloud” this is not the desktop app rather it is the underlying Adobe Application Manager components that are required for install and licensing. The reason we have done this is that if there was for some reason a fix required for licensing etc then we would be providing you with the ability to create a package that just contains the require fix for those underlying components versus what you would have had to do in the past which is to push out a new application or an update for an application just to provide a fix for those underlying components. I do take your point however that this might be confusing and lead to IT thinking the Creative Cloud Desktop app is mandatory which it is not.

      To your second point, the Creative Cloud applications such as Adobe Photoshop CC (2014) are actually essentially new applications versus updates to the previous versions and so as such they can be installed alongside the previous versions which has historically been the case. If you wish to remove the previous version first you may do so by using the CCP uninstall file.

      I hope this make sense ?

      Karl Gibson | Product Manager | Enterprise IT Tools

      • By Paul Benham - 7:09 AM on June 25, 2014   Reply

        Thanks for your reply Karl.
        So am I right in thinking that there is no way to make installation packages for the ‘original’ versions of the CC apps anymore. I know that our Macs on campus have already been re-imaged this summer with the CC versions of the Suite, but our Windows labs have not, so they will have to deploy the CC 14 versions using v1.6 of the Creative Cloud Packager. We definitely do not want to be installing/running 2 different versions of Photoshop/InDesgin/Illustrator etc on our lab machines.



        • By Karl Gibson - 7:21 AM on June 25, 2014   Reply

          Hi Paul,
          The Creative Cloud provides you with access to the latest versions plus the previous versions. If you select the “show Archive Versions” checkbox on the CCP Applications and Updates screen and scroll down you will see the previous versions which in this instance will be the CC versions and also the CS6 versions. I hope this makes sense. We are certainly not trying to force any versions on you and the idea is that you the IT admin retain the choice as is consistent with your labs/images.

          Karl Gibson | Product Manager | Enterprise IT Tools

          • By Paul Benham - 7:25 AM on June 25, 2014  

            I hadn’t noticed the “Archive Versions” checkbox. Thanks for pointing that out to me. That will make our lives easier this summer : )



  • By TGB - 11:50 PM on June 29, 2014   Reply

    The “Disable all Adobe AIR installers, including Community Help Client” does not stop AIR from being deployed as part of the Digital Publishing components. Installation has currently stalled on my test machine due to the AIR installer not working while nobody is logged in at the Console (I’m sshed into the box).

    7848 ?? Ss 0:00.25 /Library/Application Support/Adobe/Installers/AdobeDigitalPublishingCC2014/ContentViewer/Adobe AIR AIR Installer -silent -eulaAccepted

    Please fix CCP so that “disable AIR installers” actually DOES disable all AIR installers.

    • By TGB - 11:55 PM on June 29, 2014   Reply

      From /Library/Logs/Adobe/Installers/DPS Desktop Tools CC2014 31.0.0 06-30-2014.log:

      06/30/14 16:38:57:321 | [INFO] | | OOBE | DE | | | | 25003 | Calling the custom action code for post-install for payload DPS Desktop Tools CC2014_31.0.0_AdobeDigitalPublishing-mul {B50A5328-440A-4DF9-99AC-35F5A6F73C55}
      06/30/14 16:38:57:321 | [INFO] | | OOBE | DE | | | | 25003 | ::START TIMER:: [Post payload :{B50A5328-440A-4DF9-99AC-35F5A6F73C55}]
      06/30/14 16:38:57:321 | [INFO] | | OOBE | DE | | | | 25003 | CustomHooks.dylib: In PostPayloadInstallProc
      06/30/14 16:38:57:321 | [INFO] | | OOBE | DE | | | | 25003 | CustomHooks.dylib: In InstallAirApp()
      06/30/14 16:38:57:321 | [INFO] | | OOBE | DE | | | | 25003 | CustomHooks.dylib: DPS App Builder installer files are located:
      06/30/14 16:38:57:321 | [INFO] | | OOBE | DE | | | | 25003 | /Library/Application Support/Adobe/Installers/AdobeDigitalPublishingCC2014/ContentViewer/Adobe AIR AIR Installer
      06/30/14 16:51:00:342 | [INFO] | | OOBE | DE | | | | 25003 | CustomHooks.dylib: installation failed
      06/30/14 16:51:00:357 | [INFO] | | OOBE | DE | | | | 25003 | CustomHooks.dylib: About to delay, to allow previous installation to finish.
      06/30/14 16:51:25:357 | [INFO] | | OOBE | DE | | | | 25003 | CustomHooks.dylib: Delay complete.
      06/30/14 16:51:25:357 | [INFO] | | OOBE | DE | | | | 25003 | CustomHooks.dylib: In InstallAirApp()

      I killed the stuck “Adobe AiIR Installer” process – the one that was never supposed to be invoked at all, as far as the CCP configuration settings are concerned – at 16:51.

      • By TGB - 12:10 AM on June 30, 2014   Reply

        DPS App Builder and Adobe Content Viewer also cause the installation to stick.
        They got jammed into the InDesign CC 2014 section of CCP without any real indicator, they’re known to be a problem, and then the “disable AIR” option, which is intended to circumvent the limitations of the crap AIR installer technology in the first place, is just ignored.
        A big chunk of what CCP is designed to do is silent, unattended, no-user-logged-in installs – it’s probably the majority of how it’s used. I thought this had been drilled into the install/OOBE team.
        Guys, seriously… what is going on?

        • By Karl Gibson - 1:58 AM on July 1, 2014   Reply

          Hi TGB,
          The team had a look at the issue and it is something we have experienced before. Normally CCP blocks DPS updates because the failure rate is so high on account of Air runtime. Which is exactly the experience you are having. The way we block DPS is to hardcode there product code in to ours. What has happened in this instance is that the respective team have changed their product code and now CCP is not blocking anymore. The team and I are looking in to releasing a fix for this and we will have more information over the coming days. Thanks for flagging this with us and my apologies for the inconvenience it has caused.

          Karl Gibson | Product Manager | Enterprise IT Tools

  • By Art Vandelay - 4:47 PM on July 3, 2014   Reply

    Edge Animate CC 2014 is launching in trial mode even with a serialized package. This is with CCP 1.6 and OS X 10.9.3. I upgraded to CCP 1.6 before deploying CC 2014, so don’t know if this is a CCP 1.6 problem or a CC 2014 problem.

    • By Karl Gibson - 1:19 AM on July 4, 2014   Reply

      Hi Art,
      We just tested on our end and created a serialized package with CCP 1.6 and Edge Animate CC 2014 , which was successful and the product was licensed on launch. Can you please share the “oobelib.log” file from your machine so we can have a look to see what the issue is ? It can be found in ~/Library/Logs

      Karl Gibson | Product Manager | Enterprise IT Tools

      • By Art Vandelay - 8:19 AM on July 7, 2014   Reply

        Disregard. I realized over the weekend that I had never updated the serialization file. Created a new one and Animate CC 2014 is no longer opening in trial mode.


  • By Shane Palmer - 9:58 AM on July 15, 2014   Reply

    I am not sure if this is a function of the new Creative Cloud Packager 1.6, the new Creative Cloud 2014 or both, but when I install Creative Cloud 2014 (everything minus Edge Code, Edge Reflow, Scout and Adobe Gaming SDK) there is no SWID Tag installed at /Library/Application Support/

    I use this SWID Tag in Casper to track licenses so this makes it a bit harder to do without this file.

    • By Karl Gibson - 12:33 PM on July 16, 2014   Reply

      Hi Shane,
      It depends on the type of customer you are but if you use a serial then the SWID tag for CC will not be for an individual product rather it will be for Creative Cloud so it will show as something like “V7CreativeCloudEnt-1.0”

      Is that appearing ?

      Karl Gibson| Product Manager | Enterprise IT Tools

      • By Shane Palmer - 7:54 AM on July 17, 2014   Reply


        With the previous version of Creative Cloud it would create /Library/Application Support/{}CreativeCloudEnt-1.0-Mac-GM-MUL.swidtag. So far after building and installing Creative Cloud 2014 on a handful of machines none of them have any SWID tag at all. The /Library/Application Support/ folder is completely empty.

        On a side note based on your comment, does this imply that even if the tag was getting created correctly that it would be the same tag as for the previous version of Creative Cloud? If so how will I be able to track those that have Creative Cloud 2014 vs. those that have the previous version of Creative Cloud?


  • By Mark M - 10:06 AM on July 17, 2014   Reply

    I’m trying for the first time to serialize a trial version. I can create the license file (prov.xml) using the CCP tool. However, I can’t find the adobe_prtk tool on Mac or Windows- either the machine with the trial version, or the machine that I have CCP installed on. Am I looking for the wrong thing? These instructions seem rather vague.


    • By Karl Gibson - 5:05 PM on July 22, 2014   Reply

      You can just use the “Create License file” workflow in CCP to move from trial to licensed. No longer a need for APTEE or Prov.xml.

      Karl Gibson | Product Manager | Enterprise IT Tools

  • By BW~Merlin - 8:27 PM on October 13, 2014   Reply

    We recently updated our server that we do our packaging from and using Creative Cloud Packager 1.6 all my new packages are broken and do not install (Old server was Windows Server 2008 SP2 Enterprise 32bit and I have tried on both Windows Server 2003 SP2 Standard 32bit and Windows Server 2012 R2 x64 and packages made on either of them still fail).

    I am using the exact same method of installation (Microsoft Deployment Toolkit installing acrobat first using the exception deployer, then the adobe MSI and then post install) I have used in the past to install Creative Cloud Design and Web as well as Creative Cloud Master Collection but my new packages using CCP 1.6 all fail during the installation of the MSI (error code 1603). My old Master Collection package still installs fine and we would use that but we are removing applications we don’t actually use to speed up deployment.

    Where can I download an earlier version of the CCP as the new one is making broken MSI files.

    • By Karl Gibson - 2:48 AM on October 14, 2014   Reply

      I don’t believe the issue is related to the version of CCP you are using. I think we should look at what is going on in the log files of the client machine as part of the install to ascertain where the error is occurring. Can you advise if there is any other Adobe software on the server you are creating the packages from ? Did you install one of the packages to the server to test ? Also can you please send the log files from the client system where the package is failing. The location of the log files can be found here . If you can mail them to me we can have a look and try to figure out what is going wrong.

      Karl Gibson | Product Manager | Enterprise IT Tools

Add a comment