Adobe Systems Incorporated

Adobe Installation and Licensing

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

Dec 8, 2015

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.

Notifications

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.

Cheers

Karl Gibson | Product Manager | Creative Cloud Enterprise

Uncategorized

Comments

  • By Shane Palmer - 1:06 PM on December 18, 2015   Reply

    Karl,

    Thanks for adding the notification feature. Even though we deal with Serialized Licensing and can’t use the Enterprise Dashboard for much yet I was eager to receive these notifications so I signed up right away. As an IT admin this will be handy to be notified of updates rather than needing to discover them on the Creative Cloud for enterprise Updates: CCE Updates _for IT Admins_ blog (http://blogs.adobe.com/creativecloudenterpriseupdates/) or when another IT admin asks me why we haven’t packaged up a new update.

    However, after getting my first notification email I see a few things lacking in the notification email and many other places (on the update blog _for IT Admins_ mentioned above, on the Enterprise Dashboard, in the Creative Cloud Packager, and in the Adobe Update Manager/RemoteUpdateManager).

    The first thing that needs to be addressed is that the precise version of the update needs to be displayed everywhere possible, and not just the marketing version. For example, the latest email notification I received was for the Photoshop CC 2015.1.1 release. This equates to Photoshop CC version 16.1.1. All communications about updates need to include both version numbers because 2015.1.1 alone is meaningless to me when I look at the version information in the Finder Get Info window to compare what I currently have to what was released.

    The second thing that is lacking is that it is hard to understand when to judge whether I need to package up these new updates with CCP and push them out vs. when I can just push out a command to all my client Macs to run RemoteUpdateManager. For example starting with CC2014 I would see that some “major” updates with new features could be installed via RemoteUpdateManager where some could not, especially those that changed the name of the application (like from /Applications/Adobe Dreamweaver CC 2014/Adobe Dreamweaver CC 2014.app to /Applications/Adobe Dreamweaver CC 2014.1/Adobe Dreamweaver CC 2104.1.app). This time around I saw that the new Photoshop CC 2015.1 update release in early December was described as a “major” new update so I was expecting the application name would change and that I needed to update the package but discovered that I did not need to.

    These two things are very necessary for an IT admin to make a judgement call about whether or not they need to spend time (which many have very little of) packaging updates. With these December updates I had to use Creative Cloud Packager to package these applications along with their updates, install them and compare them to what is installed with the previous packages created (and RUM run on them) to get the versions for comparison and to figure out if new applications were going to be created alongside existing versions. So to put it another way I had to spend a few hours to package the updates and install them so that I could determine whether or not I needed to package the updates and install them. In this case I discovered that I did not need to package them and wasted a few hours when I could have just run RUM to get these same updates.

    I hope you take this as constructive criticism and use it to continue to improve communications regarding Adobe’s confusing versioning methods of madness to make it easier for IT admins who are strapped for time to quickly judge where there time needs to be spent when it comes to dealing with packaging up Creative Cloud.

    Thanks,
    Shane

    • By Karl Gibson - 8:49 AM on January 15, 2016   Reply

      Hi Shane,
      That’s great feedback. I will look at the version numbers and see if we can pull them. The issue is the Product team owns the update details so we are at there mercy to a degree. Saying that this is not something customers should need to be concerned with so I will look at what can be done to improve the usefulness of the E-mails.

      Regarding RUM. RUM can be used for all updates of CC. When we do a major release however this is considered a new application version versus an update so RUM will not for instance update from Photoshop 2014 – 2015.

      Cheers
      Karl Gibson | Product Manager | Enterprise IT Tools

Add a comment