Creative Cloud Packager 1.10 & Creative Cloud 2017 are 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*

The age old question. Buffet or set menu ?

Hi All,

Let me set the scene for a moment. We are in casa Gibson. Now I know that you are probably picturing  some picturesque castle or thatched cottage on the foothills of some rolling green Irish mountain. Perhaps your vision is temporarily interrupted by the livestock crossing your field of vision. But alas my attempts to convince Adobe to allow me to work from such a scenic remote location (using a 56k modem) have not come to fruition.

In casa Gibson I am quite happy to cook and serve dinner to my family most nights. I try and predict what everyone would like to eat on any given night, i give them the portion size I think is correct, apply the right amount of seasoning, you see where I am going with this right. However when I bring the dinner to the table, It is invariably only a matter of time before somebody says ” I didn’t want that” , “you forgot my drink” , “can I have the blue cup instead of the red cup” or “My friend said her family eat a new type of synthetic cheese, why can’t we have that ?”.

So I gleefully look forward to the nights when I can make Tex-Mex . You know why ? Because I can just put everything on the table, the cheese, the salsa, the guacamole, the fajitas etc.. I can sit down knowing I don’t need to get back up again. Everybody can choose what they want/need and get on with enjoying their lovely food while I relax with a nice cold bottle of beer (insert your favourite beer here). You see sometimes it is nice if you just lay out the options and let people help themselves. Perhaps they want cheese today but maybe tomorrow they don’t.

Now I know what you are thinking. That guys family sound awful and can you tell me why this is in any way relevant to me.

Well, we have heard consistently from many IT admins that while Named Licensing benefits their creative end users it also introduces a potential issue for IT. The Creative Cloud Desktop app has an “Apps” panel which allows end users to install applications, apply updates as soon as they come out and un-install applications when they are either finished with it or wish to update to the latest version. Many IT admins choose to disable the apps panel because their end users do not have administrative privileges of their own system. This can be for a myriad of reasons.

We have now introduced the capability for the IT admin to allow the Creative Cloud Desktop application to run with elevated privileges. So if you choose, you can change the setting in either Creative Cloud Packager or the deployment section of the Enterprise Console and allow end user’s who are not admins on their system to install, update or remove the Creative Cloud Applications that have been conferred to them via the Enterprise console. This option will be visible in Creative Cloud Packager the next time you re-launch.

This has the capability to really empower end user’s and at the same time remove much of the overhead from the IT administrator. I know this option will not be appealing to all organisations but it is just that, an option.

Below is some screen grabs of the option in Creative Cloud Packager & the Enterprise Console.


Elevated Privileges

Dashboard Elevated

You can configure this for new packages or if you wish to deploy to existing clients you can create a package that just includes the Creative Cloud Desktop app. More details on how to do this can be found here.


Karl Gibson | Senior Product Manager | Creative Cloud Enterprise

Creative Cloud Package 1.9.5 is live – Redesigned installer technology plus much more

Hi All,

As Staind once said “It’s been awhile”. The last update had some exciting information regarding support for multi language packages and Acrobat workflow improvements. This update is also quite exciting, of course context is everything and so when I say exciting I mean as exciting as a post about a redesigned installer technology can possibly be, so put down that big inflatable party finger.

We have today released a number of updates for the Enterprise IT Tools. For a quick summary please have a look at the video below (monotone is for life not just videos)

Alternative Video Link:

If you are more of a text person then this bit is for you

Creative Cloud Packager (1.9.5) (Release Notes)

The main focus for this release was to support a completely redesigned version of Adobe’s proprietary installer technology. We are really excited about the capabilities that can be seen in this first phase of the redesign but also the long term capabilities we can provide to customers. For today however the headline feature for this change is that we have

  • Cut the install time of the Creative Cloud applications by roughly 50%.

In most cases it is actually more the 50% which is quite an astonishing improvement.

  • Updates for these products will now also be full installers.

Meaning when you package an update for a product you will now see a new icon updater icon. When you see this icon it means the installer can be used to install the update on a system that has the software already but also on a system that does not already have the base version. The installer redesign means smaller packages so the difference between the previous patch versions and new full installers is negligible but it does mean you no longer need to have both update packages and base version installs.

Over the next little while you will see the Creative Cloud products adopting the installer changes and we have a list documented on our help page.

  • Added support for Adobe Experience design in CCP

You can now use CCP to package the Adobe Experience design Preview


It is great to be able to release a few new features for AUSST our beloved tool for hosting an internal update server.

  • Added support for application binaries.

As I mentioned above updates now have a dual purpose and so we have leveraged this to also allow AUSST to support application binaries. In the context of a workflow, if your end users are using the Creative Cloud desktop application for self service then when they go to install let’s say the latest version of Photoshop and you have an internal server then the application will actually install via your internal server versus going out to Adobe every time to download the application bits. We have plans to allow more granularity with AUSST so you can specify just the application you want to sync versus all applications so look out for this soon.

  • Support for Acrobat DC updates (Windows only)

This has been a feature requested for quite some time so we are delighted that AUSST now allows you to host updates for both Creative Cloud and Acrobat. We are working hard to add support for Mac updates so expect this is the not too distant future.

Deployment dashboard

As you hopefully know, within the Enterprise Dashboard we have a deployment section that facilitates the download of pre-created packages.

  • Pre-Created packages for all applications

We have now tweaked the logic so you see not just the applications you purchased but all applications. Previously if you just purchased Creative Cloud complete but only wanted a Photoshop package you would need to use CCP. Now we show you all packages so you can choose the ones you specifically want.

  • Cut the time it takes for customisation by up to 30%


Actually….. I take it back. This is something to get excited about.  Pick up that big inflatable party finger and wave it like you just don’t care.

party finger

Finally (told you that you should have watched the video) we are really excited to be sponsoring the 2016 MacAdmins conference at Penn State and so I look forward to seeing you all there.


Karl Gibson | Senior Product Manager | Creative Cloud Enterprise

CCP 1.9.3 is live – Hola multi language, adiós Acrobat exception workflow

Hi Folks,

I am happy to announce that CCP 1.9.3  is live. This release brings some significant features that IT admins have been asking for. This functionality is also available in the Enterprise Dashboard.

Multi Language Packages

Yes you have read that right. A significant issue for IT admins who support multiple locales is the requirement to create one package per language. This release of CCP and the Deployment tab (in the enterprise dashboard) will offer the ability to “Match the OS language” and the ability to specify at deployment time what language you want the package to be installed in. This in a nutshell means one package regardless of the language you wish to deploy in. This hopefully solves a significant pain point for IT admins.

match os language

Acrobat (I am not Exceptional)

All too familiar to folks will be the fact that Acrobat when included in a Windows package is considered an exception and as such needs to be deployed separately with various nuances that are a pain. With this release of CCP and the deployment tab we will now no longer include Acrobat as an exception. The new workflow is that the IT admin will now simply deploy or double click the setup.exe file that is created. This file will then invoke both installers in one seamless step.



Before the holiday period we released a new version of Remote Update Manager (RUM) This update allowed for downloading and caching of updates as well as some other features. While we released this as a standalone download the new version will now be included in CCP and all subsequently created packages.

We have updated all our help documentation to reflect these changes


Karl Gibson | Senior Product Manager | Creative Cloud Enterprise

Want to know when Creative Cloud product updates get released ?

Hi All,

IT admins have mentioned on several occasions that there is no consistent method for them to be notified when updates are released for the Creative Cloud Products. In many circumstances this puts IT admins on the back foot and user’s sometimes become aware of the updates before IT. We (you) of course don’t like when user’s know something first it makes us look bad and it makes user’s think they just got one up on us. We cannot allow this, so inevitably this leads to deleting their profile, changing their password or deleting some required startup files. As someone who likes peace and harmony I felt it was my duty to remove this potential source of conflict.

Today we have released a new feature in the Deployment section of the Enterprise dashboard. It is now possible to subscribe to e-mail notifications. When you subscribe we will e-mail you on a weekly basis and let you know what updates have been released in the preceding week for the Creative Cloud and what those updates contain. The idea is that this will allow you to be more informed and more prepared. If you would like to implement your own patch day and you get a weekly e-mail let’s say every Tuesday then you could potentially have a patch day on Wednesday knowing what has been released and what was contained in those updates.


We made a cognisant decision to do this weekly rather than every time a product releases an update. If this needs to be changed then this is something we can revisit but we did not want your inbox’s to be overloaded or for the e-mails to carry less significance.

This feature is now live so feel free to subscribe.

Finally as a reminder this page gives an overview of the different update options available.


Karl Gibson | Product Manager | Creative Cloud Enterprise

Yo ho ho and an update to RUM

Hi All,

Remote Update Manager (RUM) is a tool conceived of at a JNUC many moons ago in a bar (most likely grumpies) when times were simpler and my beard was still for the most part ginger and not greying as it is now. Unfortunately since it’s inception we have not really expanded on RUM’s core functionality due to higher priority items in the backlog. When it was confirmed that we were once again sponsoring and presenting at JNUC, I was keen to showcase some new RUM functionality. The presentation , which can be found here, went well and we received great feedback on the new functionality and also some suggestions for tweaks which we promptly incorporated.

New Features

  • Ability to list what updates are available for client
  • Ability to download updates to be installed later
  • Increased vebosity in the logs. We show specifically what succeeds or fails.
  • Better support for console logging
  • Version information now displays in the terminal

We are not planning to do another release of CCP for a little while but I was keen to get this in the hands of IT admins and so I am taking the slightly unorthodox step of posting here. Once you download the binary you can deploy in the following ways

  • You can copy the RUM binary manually to your existing clients,
  • Inject the binary into an existing CCP package (Resources folder on mac and Build on windows)
  • Replace the binary on the machine you do your CCP packaging on (ccp\utilities\RemoteUpdateManager) This will ensure the latest version of RUM is added to all new packages you create.

When we do another revision of CCP we will of course incorporate this latest version. Hopefully these updates will prove useful for you and I am excited to see what IT admins do with it.

RUM documentation can be found here

Download links




Karl Gibson | Product Manager | Creative Cloud Enterprise

CCP 1.9.2 is now live and I am trying to recover from MacSysAdmin

Hi All,

I have my feet firmly back on Irish soil after a few great days at MacSysAdmin in Gothenburg. I must say it is a very unique and engaging conference. The level of knowledge on display is quite impressive and that very much extended to working with Adobe products. After my presentation in which I requested for IT admins to continue to engage and work with us there was several very engaging discussions which will hopefully lead to new functionality and fixes.

While I was presenting and playing pool in Gothenburg the team was hard at work and we released CCP 1.9.2 yesterday. The main focus of this release was on proxy support. Previously while Pac was supported there was some issues and we also did not support WPAD. Both of which are now fully supported and from our preliminary tests with customers this build looks to have solved all of the issues customers were experiencing with these network topologies.

CCP 1.9.2 now also includes the option of Auto-updating. This can be set from the preference menu and when there is a new update of CCP you will also see a screen requesting your preference.

Finally with the introduction of El-Capitan we were required to change the location of RUM on the client system to conform with Apples new guidelines. As such, when we deploy RUM now from a CCP package it will be located in “/usr/local/bin”



Karl Gibson | Product Manager | Enterprise IT Tools

Major Milestone- Cloud Packaging has arrived

Hi All,

Lately posts have been a little thin. This past year the team has been heads down, focused on a new initiative that I’m excited to share with you.


As many may know, Adobe has used its own installer technology called RIBS for the past several years. RIBS was created to bind the individual products together when we first released Creative Suite and the technology is still used in todays Creative Cloud products.

We realize RIBS is not ideal for enterprise workflows and in order to deploy the software you are required to use either Creative Cloud Packager or it’s predecessor AAMEE. While those products offer features beyond their core competency of converting from RIBS to native installer such as the ability to specify update behaviour, pre-serialise, create update packages and license files, it is still an additional step IT need to take.  Also in order to use CCP, you need both Mac and a Windows systems clean of other Adobe software and network connectivity, requiring IT to open firewall ports.

The Change

Now, Adobe will pre-populate packages for Creative Cloud for enterprise customers. When a user logs into the Adobe Enterprise Dashboard, they will go through the following process


Adobe entitlements are detected and packages will be created automatically,

created automatically

When you select packages you can filter by “created automatically

These Pre-Created packages will leverage the default and most common settings. Users can change certain settings such as language, update behaviour and for Windows, bit architecture,

Once satisfied with the packages and settings select “build”



The system will start building and downloading packages

download copy

It’s as simple as that !

Users can also, delete packages and can filter by package creator.


The question I am sure that will arise is, why doesn’t Adobe just use native installers  ?. It is a very valid question. As i mentioned RIBS allows you to deploy multiple products in the same binary but other advantages are limited to Adobe itself. This is changing and in the not so distant future I will go in to more detail about the changes that are being made to the RIBS installers to increase the benefit to end users.

The Team

Finally (I know long post) I was in Noida nearly two years ago when we sat down as a team and discussed this new direction. We discussed the pain points and how we could remove the packaging step for IT admins. Since then the team have worked tirelessly to make this a reality. We have many features still to implement to get this where we want but as a 2.0 release this is a huge step and I want to publicly thank each member of the team who worked crazy hours and put up with my stress levels.

Now the real question is, if you have a big launch at 6am is it too early for a celebration beer ?

Video Walkthrough


Karl Gibson | Product Manager | Enterprise IT Tools

Major enhancements to Creative Cloud for enterprise

Guest Blogger: Amy Redell | Senior Product Marketing Manager

Last week, Adobe announced major enhancements to Creative Cloud for enterprise.

These enhancements include all the new features of Adobe Creative Cloud 2015 desktop and mobile apps, as well as new advanced security options and deep integration with Adobe Marketing Cloud and Adobe Digital Publishing Solution (DPS), both priced separately.

Advanced Security

Adobe now offers two hosting options to ensure protection of corporate assets, including customer-managed data encryption keys and a managed service hosting option that offers dedicated storage behind your organization’s firewall. Both hosting options meet critical IT demands and ensure at-rest data encryption, single sign-on, and the ability to granularly manage entitlements for users and groups.


Creative Cloud for enterprise with managed services continuously syncs with Adobe Experience Manager, a key component of Adobe Marketing Cloud, enabling creative and marketing teams to securely access, share and collaborate on content created with Adobe’s desktop and mobile CC apps, accelerating creative-to-marketing workflows.

In addition, Creative Cloud for enterprise will support an upcoming release of DPS. DPS continuously publishes content to mobile apps, allowing your organization to deeply engage with customers on digital devices. Upon release, DPS entitlements will be added to the Adobe Enterprise Dashboard, allowing IT admins to manage all Adobe enterprise products, including Creative Cloud, DPS, Marketing Cloud and Document Cloud, from one, central location.

Learn More

Contact your Adobe Account Executive today to discuss an extended trial of Creative Cloud for enterprise or learn more about the new hosting option.



Adobe Creative Cloud for enterprise now supports Single Sign-On

Edit 16/02/15: Survey is now closed and link has been removed.

Guest Blog: Laurel Hahn Zimmer | Product Manager | Creative Cloud for enterprise

Hi All,  

I am extremely pleased to announce that Adobe Creative Cloud for enterprise now supports Single Sign-On (SSO)!

Adobe has introduced Federated IDs which enable our enterprise customers to establish SSO between their identity management systems and Adobe products and services.

With SSO support, we’re delivering on our promise to provide IT administrators better security controls and allowing users to log in with a single credential to access Creative Cloud for enterprise desktop apps, services and mobile apps.

To learn more about the new Federated ID identity type and the other identity types available from Adobe, see Manage Identity Types. For detailed instructions on enabling SSO, see Configure Single Sign-On.

Important: For users who access the Creative Cloud for Desktop app, v1.9 is required which provides support for Federated IDs.

Finally, I’d like to highlight an upcoming IT-focused event: Live Webinar | Adobe Enterprise Dashboard: Single Sign-On and User Management on Feb 19th | View Event Info

Cheers, Laurel

Note from Karl.

Yesterday the Muse team went live with Muse 2014.3. What is significant for IT admins is on Windows Muse is now no longer considered an exception and so will now be part of the main payload. Anybody who has been deploying Muse will know that previously the process was a bit tedious so we are grateful to the Muse team for putting in the effort here to improve the process.

A short while back we introduced CCP 1.8, in the chaos to get it released in order to resolve an issue I did not have the chance to speak about one of it’s new features. As you know when you use CCP in conjunction with the Enterprise Dashboard we surface the package metadata to all admins in your org. We have now added a new field where we surface the GUID of the package. This is great if you want to remotely query systems in your environment and allows you to reconcile the package and it’s contents which are stored in the dashboard.

Package GUID


Karl Gibson | Product Manager | Enterprise IT Tools