Change management for Adobe enterprise and teams customers

The products that are included in Adobe Creative Cloud and Document Cloud are released regularly with updates that provide new features and functionality. For enterprises, Adobe provides multiple ways in which you can create and deploy packages. As an admin in your enterprise, you will need to understand how to manage the deployment and applying of updates to the end users in your organization. And then you need to decide which method or combination of methods best suits your organization requirements.

This article gives you an overview of Adobe's release model, and helps you understand the different ways you can effectively manage the updates for the end users in your organization.

How to manage updates

With the transition to the Creative Cloud and Document Cloud, Adobe has adopted a service model for customer updates. This means that new features, feature enhancements, and bug fixes are released regularly. And so your users can have the latest and greatest functionality and improvements without having to wait for the next full release. This model also allows your organization to create packages that can be first tested and validated before releasing the new features and functionality to the end users.

Managing updates

With the latest Adobe installer technology, you only need to create a single package installer for all users with the same product requirements; irrespective of their current setup of Adobe CC apps, 

For example, say you have multiple categories of users in your organization; and you need to update all these users to Photoshop CC (2017.0.1):

  • One that has version 2015.5 previously installed
  • One that has version 2017 previously installed
  • And some users who have no previous version of Photoshop CC installed

You are not required to create a complex set of packages to handle:

  • Upgrades from 2017 to 2017.0.1
  • Fresh installations of 2017.0.1

Error management

We understand that installing products in an enterprise environment is not a simple task. You might often encounter errors during the deployment or installation process. However, with the single installer in place for all users (irrespective of their current setup), you will encounter a consistent set error codes and messages for all setups. You do not need to address different error scenarios for fresh installations versus updates.

How to deploy updates in an enterprise

We know each customer is different. And as an enterprise or teams customer, you have different needs and requirements. You want the most updated features in the products that you have purchased, but you also want to control how and when these features are made available to your end users.

The following sections outline the options that are available to you for applying or deploying updates to your end users:

Self service

If your end users have access to the Creative Cloud Desktop application, they are notified when new updates become available and are prompted to install. This method reduces the overhead for IT and gives users access to the latest updates as soon as they are released. 


Package updates via the Admin Console

The Packages tab in the Admin Console allows you to create the following types of packages:

Create Self-Service packages to give your users complete control of the updates that they can to download and install.

Create Managed packages to maintain greater control of the updates that your users can install.

Download Adobe Templates (pre-created packages) from the Packages tab in the Admin Console and then distribute these to your end users.

These packages are created and maintained for you in the Admin Console. This means that you don't create these packages at your location. You can download and deploy the created packages as you need them.

Package updates via Creative Cloud Packager

You can choose to use the Creative Cloud Packager, a desktop app, to create packages on computer at your site. When you launch Creative Cloud Packager you can select to create a new package. When you get to the Applications and Updates screen just select the updates you want to package. The result is a native installer package that can be deployed to all of your end users.

Packages created using the Creative Cloud Packager, are created and maintained at your location. You can deploy the created packages as you need them.

Remote Update Manager (RUM)

The Remote Update Manager (RUM) allows the administrator to remotely invoke the updater on the client system. You can update all applications or just the selected applications. You may also choose to list what is available for the client or to download and cache the updates to be installed later perhaps after a restart.

On premise update server

It is possible to host your own on-premise update server. Using the Adobe Update Server Setup Tool (AUSST), you can sync your own web server with Adobe’s. This allows you to host all updates on premise. To install the updates, you can either use RUM to install from your update server on demand or you can choose to have the clients update themselves either on schedule or via self-service with the Creative Cloud Desktop application.


How do I know if updates are available?

Admin Console Packages tab

If you have access to the Admin Console, you can check for updates in the packages tab for the packages that you have previously created.

Apps not up-to-date

Email notifications

In the Packages tab of the Admin Console, you can choose to receive email notifications once a week with the updates that have been released for the Creative Cloud products.

  1. In the Admin Console, choose Packages > Tools & Notifications.

  2. To enable notifications, select the checkbox in the Notifications section.

Also, remember that if you have downloaded a pre-created package or have access to the Admin Console then the Packages page shows you what updates are available for your package.

Apps not up-to-date

Using the Creative Cloud Desktop app

If you choose the Self service option to deploy updates, your users get notifications from the Creative Cloud Desktop app.

Updates in CCDA

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy