Creative Cloud Packager 1.1 – A big week for CC Team & Enterprise customers

Hi All,

There has been many big days in my life but very few big weeks. Perhaps the week I got married and the week I went to Disneyland (not the same week) but this week must also be up there. On Monday 17/06 Adobe released it’s brand new Creative Cloud branded applications. Which I must say are extremely impressive with lots and lots of new features. On Tuesday 18/06 we realised that as a result of the changes on Monday there was an issue with Creative Cloud Packager 1.0 which was preventing package creation.  Ooops this was obviously not intended. However stay with me we have a fix.

We are now on Wednesday ,  which also happens to be my favourite day of the week, just in case that comes up in the Karl Gibson trivia quiz at your local bar. Today we are going to release Creative Cloud Packager 1.1. for our Creative Cloud Team customers.

Fear not Creative Cloud Enterprise customers we have not forgotten you. The great and really exciting news is that Creative Cloud Packager 1.1 will also be available for you. Since we released Creative Cloud Packager 1.0 in April for Creative Cloud Team customers the feedback has been overwhelmingly favourable. With this in mind it was really important to us that Creative Cloud Enterprise customers also have this this experience when it came time to packaging the new Creative Cloud applications & updates. Here is the breakdown of Creative Cloud Packager Features

 

  • Downloads applications & updates directly from Adobe’s Creative Cloud- No physical media/ LWS downloads
  • Create customised packages containing just the applications you wish to deploy.
  • Support for Feature Bearing updates- Updates are broken up in to Feature bearing & regular updates. IT admin can choose which they want to package.
  • Creative Cloud allows you to select the locale you wish to create packages with
  • Ability to modify update behaviour of client applications
  • Ability to disable or enable Creative Cloud Desktop Application.
  • Caching of Applications and updates to save bandwidth- Ability to change where cache is located.
  • CCP offers in app updating. When a new version is detected you are asked if you want to update.

 

CCP 1.1 Sign In

CCP 1.1 Application Screen

 

How do you get Creative Cloud Packager 1.1 ?

Creative Cloud Team customers

CCP 1.1 is now live. if you already have CCP 1.0 then when you next open or launch the application you will be prompted to install an update.

CCP Update screen

 

If you do not already have CCP then you can go to the Team admin portal creative.adobe.com and sign in with your Team admin ID and you will see a deployment section on the right hand side. You can download CCP 1.1 from here.

CCP admin portal link

 

Creative Cloud Enterprise Customers

On June 21st we will be making Creative Cloud Packager 1.1 available on Adobe’s Licensing Website (LWS) licensing.adobe.com In the past when you have signed in to LWS you would see a list of all the applications. This has now been replaced and you will see only Creative Cloud Packager 1.1,  your License Key and a handful of applications CCP cannot currently package. These include Edge Code, Reflow, Scout and Gaming SDK.

Note although we are making CCP 1.1 live on LWS on the 21st it does take time to replicate on peoples LWS account.

 

The Roadmap

I am incredibly proud of the work the Team has done on Creative Cloud Packager. By downloading the applications & updates directly from the cloud we are removing a massive headache from the IT admin and also as you can see from the above there is lots of other great features. This is just the beginning however. We have lots of plans in store for CCP. As the Creative Cloud evolves the Creative Cloud Packager will also evolve and offer greater customisation of the services the Creative Cloud offers. Also top of our To Do list is to add support for packing of archived versions. As of right now if the IT admin for a Team or Enterprise need to package previous versions i.e CS6 they need to use AAMEE 3.1. This is something we are looking to remedy.

One more thing

Yes I did the one more thing……..thing

With Creative Cloud Packager we have included a new version of the Adobe Update Server Setup Tool (AUSST 3.0) the new version offers significant performance improvement and we have also made AUSST proxy aware and so you can now use AUSST even if you are behind a proxy. AUSST is included in the Creative Cloud Packager build.  We are also making AUSST 3.0 available on the Devnet site for those who are still pondering the Creative Cloud but want to take advantage of the new features, please keep an eye out over the next few days.

Help Page

The Creative Cloud Packager Help Page is located here

http://helpx.adobe.com/creative-cloud/packager.html

 

Cheers

Karl Gibson

Product Manager | Enterprise IT Tools

10 Responses to Creative Cloud Packager 1.1 – A big week for CC Team & Enterprise customers

  1. Great news – and referencing here your previous post on CCP 1.0 for more background and details:

    http://blogs.adobe.com/oobe/2013/04/somebody-new-brings-you-something-new-introducing-the-creative-cloud-packager.html

  2. Don Montalvo says:

    Thanks for the Adobe Creative Cloud For Enterprise demo in Dallas this morning, it was very informative and well done.
    PS, our licensing.adobe.com logins appear to not work…did something change?
    Don

  3. Jason Bush says:

    Guys you have some bugs you may want to take care of quickly.

    1. Ignore conflicting process doesn’t work. Tested on a few machines and rebuilt the packages. Major hassle to get all apps closed prior to install.

    2.Apps save the Creative Cloud login info and password for your main account even if you disable the creative cloud. Essentially I was able to login and could change the master account password etc.

    3. Where do the apps download prior to creating packages? Looks like some go to /tmp? It would be good to know since they eat up a lot of space.

    • Karl Gibson says:

      Jason,
      Thank you for giving us the heads up. Regarding the issues you are seeing

      Point 3. -Creative Cloud Packager does cache applications to save bandwidth and speed up package creation. The cache location can be changed and viewed when you go to preferences on the “Create Package” screen.

      Point 2. Can i ask if you created and installed the resulting package on the same system ? If so then yes this is the behaviour we expect because your machine is picking up the same token from CCP. We always advise not to create and test on the same system. This however will not be the behaviour on client systems they will not see any credentials from the IT admin that created the package.

      Point 1. The team is looking into issues with “Ignore Conflicting Process” not taking affect and we have logged a bug.

      Cheers
      Karl Gibson | Product Manager | Enterprise IT Tools

  4. Jason Bush says:

    files downloaded/cached by the installer end up here:
    /Users/your_user/Library/Application\ Support/Adobe/CCP/AdobeCCPCache
    About 7GB worth of data for what would be web premium or design premium

  5. Corey George says:

    Our Adobe rep has led us to believe that CC Enterprise is not yet shipping. Has anyone else received it for Enterprise?

    • Karl Gibson says:

      Hi Corey,
      Creative Cloud for Enterprise has been out since last December this is a common misconception, however I would expect an Adobe Rep to be aware of this. Apologies if this is not the information you have been getting.

      Cheers
      Karl Gibson | Product Manager | Enterprise IT Tools

  6. Brian Pelletier says:

    We’ve had requests by users to use the Digital Publishing Suite. We’ve just begun creating our builds with the creative cloud packager (having updates turned off for us to do with AUUST). Is there anything extra I need to do to enable DPS functionality? In reading the quick start guide for DPS you recommend going to “Update” under the Help tab from within InDesign to download the DPS functionality. As we have turned off updates, this option is greyed out. What do you recommend and is this needed? Sorry if this is an obvious question, my knowledge of DPS is pretty limited.

    • Karl Gibson says:

      Hi Brian,
      Unfortunately DPS updates are not supported in Creative Cloud Packager. The reason for this is that there inclusion results in a much higher rate of failure of the deployment package. We continue to try and work with the DPS team to come up with a solution as I am well aware this is something our customers really want.

      Cheers
      Karl Gibson | Product Manager | Enterprise IT Tools

Leave a Reply

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


seven − = 5

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>