Creative Cloud Packager 1.5 is Live

ccp copyccp copyCCP Segment screen

Hi All,

It has been a little while since my last post. That does not mean that I have embraced the dream to retire to some remote island off Fiji or at least spend 6 months out of the year there. A place with no internet connectivity, and just a small shop to get supplies from and make a long distance phone call across a crackled line once a month to touch base with the outside world. I guess this would also mean I would have no need for my pedometer, smart watch, tech glasses, Bluetooth headphones, smart thermostat, smart smoke detector and most distressingly my smart crockpot. On reflection, it seems as though I have invested way too much in technology to ever lead a life of solitude and so with that settled, let’s get on to business.

Some of you will already have noticed that Creative Cloud Packager 1.5 is live and available to download. This release includes several under the hood changes as well as customer facing features.

  • Creative Cloud Packager now supports Value Incentive Program (VIP) for education customers.
  • You can now deploy specific version updates, rather than just the latest updates.

-If a newer update is present in CCP and you wish to deploy and older version of it from some physical media you may do so via the offline media workflow.

  • Creative Cloud Packager also supports packaging non-Creative Cloud apps.

-Creative Cloud Packager will allow customers also entitled to Premiere Elements for Mac, Photoshop Elements for Mac and Technical Communication Suite to package and deploy using Creative Cloud Packager. This is accomplished when you enter a license key for the relevant product in to the packager and we will fetch the product and present it for packaging.

  • Adobe Update Server Setup Tool (AUSST) now supports secure connections (https).

-The product update binaries, however, are still transferred over http.

  • New customer segment Identification screen (as above)
  • Trial License workflow for enterprise renamed to Named License (can still be used for trial)

If you have not updated yet then all you need to do is launch CCP and you will be prompted to update.

Cheers

Karl Gibson | Product Manager | Enterprise IT Tools

22 Responses to Creative Cloud Packager 1.5 is Live

  1. Rob LaRose says:

    Hi Karl,

    When I attempt to edit a .ccp made with v1.4, I get an error saying the package is corrupt. Is this expected? Anything I can do besides re-create the package?

  2. Dave Green says:

    I’ve found that creative cloud products will work with a proxy pac file only when the pac file is located on a web site and not a local directory. Has anyone else found this and a workaround?

  3. Nicke says:

    Hello,
    When creating new pkgs with CC Packager 1.5, there are major issues installing the software on a virtual machine. It seems that the backup-phase of OOBE-folder fails either on IPC, core, UWA or other folders.
    Due to this – the entire installation fails.
    On a physical machine it seems to work without issues.

    • Karl Gibson says:

      Hi Nicke,
      Are you saying this is a new issue with 1.5 or this is the first time you have tried ? Are you creating a licensed package with CCP or unlicensed and what virtualization technology are you using ?

      Cheers
      Karl Gibson | Product Manager | Enterprise IT Tools

      • Karl Gibson says:

        This issue has been fixed and will be reflected in the next release of CCP. Thank you for brining our attention to it.

        Cheers
        Karl Gibson | Product Manager | Enterprise IT Tools

  4. Joel Bruner says:

    It’s be helpful if the packages created by Creative Cloud didn’t have static Created/Modified/Last Opened Dates. v1.5 Continues to build packages with the date stamp of 12/12/13 8:24am (and a package version of 1) the current date on the package would be quite nice. Let me know if there’s a better bug reporting avenue.

    Thanks!

    • Karl Gibson says:

      Hi Joel,
      Thank you for bringing our attention to this. I have asked the team to look in to it. Can I ask are you just using Mac ?

      Cheers
      Karl Gibson | Product Manager | Enterprise IT Tools

  5. Hey,

    CCP 1.5 should bring support for non-Creative Cloud applications, however Captivate 8 seems to not be possible to package using CCP – either by specifying the license key or adding the offline media?

    /Nicke

    • Karl Gibson says:

      Hi Nicke,
      You are correct , CCP should package up Captivate 8. However there was an issue with pushing it live. I am expecting it to go live this week. My apologies for the delay.

      Cheers
      Karl Gibson |Product Manager | Enterprise IT Tools

  6. Eddie says:

    Hi,
    We just purchased CC Enterprise license. Our IT team created a couple packages with CC Packager. When we tried to install the packages, we are getting error “Cannot open mediadb” in the Adobe Setup Error log file. Any advice would be appreciated.
    Thanks,
    Eddie

    • Karl Gibson says:

      Hi,
      We would need more details and the log PDApp.log file from the client system where the issue is occurring. You can send them to me directly at kagibson@adobe.com

      Cheers
      Karl Gibson | Product Manager | Enterprise IT Tools

  7. I have been trying to build packages all morning with 1.5 and every time I download a package it stops and says it lost connection or that the package got corrupted and it can’t continue. Any observations you can make?

  8. Bill Fix says:

    I’m doing a trial install/package build.

    I built a package for Lightroom (small app) and I want to do a trial install of the product on the machine I created the package on.

    Can I do a single install from the package I created ?

    If so where can I find out how to do this.

    Here is the long file from the package I built:

    6/17/2014 14:20:13[INFO] AdobePackageBuilder – Build Version – 1.5.0.83
    6/17/2014 14:20:13[INFO] AdobePackageBuilder – Logging Level verbosity Set to 4
    6/17/2014 14:20:57 [INFO] AdobePackageBuilder – Sucessfully extracted the product at C:\Users\bfix\AppData\Local\Temp\{C1427A09-314A-4BB8-AB36-14E5A4FEF0AD}\ACCCx2_6_0_393
    6/17/2014 14:20:57 [INFO] AdobePackageBuilder – Extraction completed with return code = 0
    6/17/2014 14:21:38 [WARN] AdobePackageBuilder – No file exist at (C:\Adob CC\Bills Desk 3\Build\ASU\Tools\CCC\Uninstall\deploy\remove.xml)

  9. Alex says:

    Hi
    I am using the mac version of creative cloud packager and i would like to install the applications to a custom location i.e. /Applications/AdobeCC this seems to work for most of the applications apart from Acrobat XI, Muse CC and Lightroom, these applications ignore the custom location and install directly to the applications folder.
    I have tried creative cloud packager 1.4 and 1.5 with adobe cc and adobe cc 2014.

    Second problem is some of the Adobe Edge applications are listed as (preview) applications, are they actually preview applications or should the (preview) have been removed and its just a bug??

    Are you aware of a fix for these issues and where do i file a bug report??

    Thanks
    Alex

    • Karl Gibson says:

      Hi Alex,
      Those applications you list are actually treated a little different in that they are native installers and as such CCP cannot pass the required variable to them. For Acrobat you can use the configuration wizard. For Muse I believe you can push out the Muse msi with the switch to specify location. I am not 100% sure on Lightroom but I will look in to this.

      Regarding the Edge Applications, this is not a bug in fact this is how those products are positioned. This is more of a product call but there is no problem in packaging them up and deploying them.

      Cheers
      Karl Gibson | Product Manager | Enterprise IT Tools

      • Alex says:

        Hi Karl
        Thanks for getting back to me. I thought that might be case with the applications, its just a little confusing when you have an option in the packager to deploy to a custom location and not all of the applications do. Maybe there should be some information dialog warning users of this.
        As i am using OSX there is no msi option so i am running a post install script as part of our munki install to move the applications to a custom folder, i haven’t noticed any problems when using the applications but it would be great to know if you are aware of any issues when doing this??

        The problem with the Edge applications being labelled as preview makes some people think they are still in beta and people won’t deploy them

        Thanks
        Alex

        • Karl Gibson says:

          Hi Alex,
          Absolutely I take your point on board. Let me see if we can tweak this in the UI in the future release. XDA should work for deploying those exceptions with Munki.

          Cheers
          Karl Gibson | Product Manager | Enterprise IT Tools

  10. John Welch says:

    So we’re seeing inconsistent errors with 1.5 packages. The latest one, a physical install (double-click in the Finder) died trying to install Edge 3. From PDAPP.log:

    07/01/14 10:06:19:525 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | deploymentFile = (/tmp/25902DEB-AE13-4824-933B-CBD6283956FD//AA7AC8FC-E17D-41D8-BE2B-30E998B7582D), installSourcePath = (/Users/Shared/Creative Cloud Full_Install.pkg/Contents/Resources//Setup/EDGE3.0en_US)
    07/01/14 10:06:19:525 | [INFO] | | ASU | DeploymentManager | AAMEEUtilities | | | 166502 | Launch Process With Task
    07/01/14 10:06:27:971 | [FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | The return code from the Adobe Installer Process is (7).Stopping the installation process.
    07/01/14 10:06:27:971 | [ERROR] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | Media Failed (EDGE3.0en_US)
    07/01/14 10:06:27:971 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | Starting to clean the partially installed payloads.

    Looked at that folder in the Package, nothing obvious seems wrong. But, the ownership of the package is our local admin, not the logged in user. Going to see if copying the package to the desktop from /Users/Shared, which will change ownership helps.

  11. John Welch says:

    Further data. From the PDAPP log:

    07/01/14 10:03:03:125 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | STEP 3: Starting to launch Bootstrapper of Media (EDGE4.0en_US).
    07/01/14 10:03:03:141 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | The Bootstrapper seems to be missing(/Users/Shared/Creative Cloud Full_Install.pkg/Contents/Resources//Setup/EDGE4.0en_US/Install.dylib/Contents/MacOS/Install). Skipping the installation process.
    07/01/14 10:03:03:141 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | deploymentFile = (/tmp/25902DEB-AE13-4824-933B-CBD6283956FD//CBB22B35-DCCB-45B8-BB11-261217BCD066), installSourcePath = (/Users/Shared/Creative Cloud Full_Install.pkg/Contents/Resources//Setup/EDGE4.0en_US)
    07/01/14 10:03:20:920 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | Media Successfully Installed (EDGE4.0en_US)
    07/01/14 10:06:19:524 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | STEP 3: Starting to launch Bootstrapper of Media (EDGE3.0en_US).
    07/01/14 10:06:19:525 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | The Bootstrapper seems to be missing(/Users/Shared/Creative Cloud Full_Install.pkg/Contents/Resources//Setup/EDGE3.0en_US/Install.dylib/Contents/MacOS/Install). Skipping the installation process.
    07/01/14 10:06:19:525 | [INFO] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | deploymentFile = (/tmp/25902DEB-AE13-4824-933B-CBD6283956FD//AA7AC8FC-E17D-41D8-BE2B-30E998B7582D), installSourcePath = (/Users/Shared/Creative Cloud Full_Install.pkg/Contents/Resources//Setup/EDGE3.0en_US)
    07/01/14 10:06:27:971 | [ERROR] | | ASU | DeploymentManager | DeploymentManager | | | 166502 | Media Failed (EDGE3.0en_US)

    Edge 4 (I’m assuming animate 2014) installed fine, but Edge 3 did not.

    • Karl Gibson says:

      Hi John,
      We were not able to replicate the error on our end. Can you can provide us with the installer logs at /Library/Logs/Adobe/Installers and an idea of how you are deploying ?

      Cheers
      Karl Gibson | Product Manager | Enterprise IT Tools
      kagibson@adobe.com

Leave a Reply

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


+ three = 8

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>