Use Adobe Remote Update Manager

  1. Adobe Enterprise & Teams: Administration guide
  2. Plan your deployment
    1. Basic concepts
      1. Licensing
      2. Identity
      3. User management
      4. App deployment
      5. Admin roles
    2. Deployment Guides
      1. Named User deployment guide
      2. SDL deployment guide
    3. Deploy Creative Cloud for education
      1. Deployment guide
      2. Integration with Canvas LMS
      3. Integration with Blackboard Learn
      4. Configuring SSO for District Portals and LMSs
      5. Kivuto FAQ
      6. Primary and Secondary institution eligibility guidelines
  3. Set up your organization
    1. Set up identity
      1. Identity types | overview
      2. Set up organization with Enterprise ID
      3. Set up organization with Federated ID
        1. SSO overview
        2. Setup Azure Connector and sync
          1. Set up SSO with Microsoft via Azure OIDC
          2. Add Azure Sync to your directory
          3. Azure Connector FAQ
        3. Set up Google Federation and sync
          1. Set up SSO with Google Federation
          2. Add Google Sync to your directory
          3. Google federation FAQ
        4. Generic SAML
          1. Set up SSO with other SAML providers
          2. Set up SSO with Microsoft Azure ADFS
          3. SSO Common questions
          4. SSO Troubleshooting
        5. Education SSO
          1. Configure SSO for District Portals and LMS
          2. Common questions
          3. Dovetail
      4. Verify ownership of a domain
      5. Add and manage domains
      6. Link domains to directories
      7. Use directory trust to add pre-claimed domains
      8. Migrate to new authentication provider
    2. Asset settings
    3. Authentication settings
    4. Privacy and security contacts
    5. Console settings
    6. Manage encryption
  4. Manage products and entitlements
    1. Manage users
      1. Overview
      2. Administrative roles
      3. User management techniques
        1. Manage users individually   
        2. Manage multiple users (Bulk CSV)
        3. User Sync tool (UST)
        4. User management API (UMAPI)
        5. Microsoft Azure Sync
        6. Google Federation Sync
      4. Change user's identity type
      5. Manage user groups
      6. Manage directory users
      7. Manage developers
      8. Migrate existing users to the Adobe Admin Console
      9. Migrate user management to the Adobe Admin Console
    2. Manage products and product profiles
      1. Manage products
      2. Manage product profiles for enterprise users
      3. Manage self-service policies
      4. Manage app integrations
      5. Manage product permissions in the Admin Console  
      6. Enable/disable services for a product profile
      7. Single App | Creative Cloud for enterprise
      8. Optional services
    3. Manage Shared Device licenses
      1. What's new
      2. Deployment guide
      3. Create packages
      4. Recover licenses
      5. Migrate from Device Licensing
      6. Manage profiles
      7. Licensing toolkit
      8. Shared Device Licensing FAQ
  5. Manage storage and assets
    1. Storage
      1. Manage enterprise storage
      2. Adobe Creative Cloud: Update to storage
      3. Manage Adobe storage
    2. Asset migration
      1. Automated Asset Migration
      2. Automated Asset Migration FAQ  
      3. Manage transferred assets
    3. Reclaim assets from a user
    4. Student asset migration | EDU only
      1. Automatic student asset migration
      2. Migrate your assets
  6. Manage services
    1. Adobe Stock
      1. Adobe Stock credit packs for teams
      2. Adobe Stock for enterprise
      3. Use Adobe Stock for enterprise
      4. Adobe Stock License Approval
    2. Custom fonts
    3. Adobe Asset Link
      1. Overview
      2. Create user group
      3. Configure Adobe Experience Manager 6.x Assets
      4. Configure and install Adobe Asset Link
      5. Manage assets
      6. Adobe Asset Link for XD
    4. Adobe Sign
      1. Set up Adobe Sign for enterprise or Teams
      2. Adobe Sign - Team feature Administrator
      3. Manage Adobe Sign on the Admin Console
    5. Creative Cloud for enterprise - free membership
      1. Overview
      2. Getting started
  7. Deploy apps and updates
    1. Overview
      1. Deploy and deliver apps and updates
      2. Plan to deploy
      3. Prepare to deploy
    2. Create packages
      1. Package apps via the Admin Console
      2. Create Named User Licensing Packages
      3. Adobe templates for packages
      4. Manage packages
      5. Manage device licenses
      6. Serial number licensing
    3. Customize packages
      1. Customize the Creative Cloud desktop app
      2. Include extensions in your package
    4. Deploy Packages 
      1. Deploy packages
      2. Deploy Adobe packages with SCCM
      3. Deploy Adobe packages with ARD
      4. Install products in the Exceptions folder
      5. Uninstall Creative Cloud products
      6. Use Adobe provisioning toolkit enterprise edition
      7. Adobe Creative Cloud licensing identifiers
    5. Manage updates
      1. Change management for Adobe enterprise and teams customers
      2. Deploy updates
    6. Adobe Update Server Setup Tool (AUSST)
      1. AUSST Overview
      2. Set up the internal update server
      3. Maintain the internal update server
      4. Common use cases of AUSST   
      5. Troubleshoot the internal update server
    7. Adobe Remote Update Manager (RUM)
      1. Use Adobe Remote Update Manager
      2. Channel IDs for use with Adobe Remote Update Manager
      3. Resolve RUM errors
    8. Troubleshoot
      1. Troubleshoot Creative Cloud apps installation and uninstallation errors
      2. Query client machines to check if a package is deployed
      3. Creative Cloud package "Installation Failed" error message
    9. Create packages using Creative Cloud Packager (CC 2018 or earlier apps)
      1. About Creative Cloud Packager
      2. Creative Cloud Packager release notes
      3. Application packaging
      4. Create packages using Creative Cloud Packager
      5. Create named license packages
      6. Create packages with device licenses
      7. Create a license package
      8. Create packages with serial number licenses
      9. Packager automation
      10. Package non-Creative Cloud products
      11. Edit and save configurations
      12. Set locale at system level
  8. Manage your account
    1. Manage your Teams account
      1. Overview
      2. Update payment details
      3. Manage invoices
      4. Change contract owner
    2. Assign licenses to a Teams user
    3. Add products and licenses
    4. Renewals
      1. Teams membership: Renewals
      2. Enterprise in VIP: Renewals and compliance
    5. Purchase Request compliance
    6. Value Incentive Plan (VIP) in China
    7. VIP Select help
  9. Reports & logs
    1. Audit Log
    2. Assignment reports
    3. Content Logs
  10. Get help
    1. Contact Adobe Customer Care
    2. Support options for teams accounts
    3. Support options for enterprise accounts
    4. Support options for Experience Cloud

Adobe Remote Update Manager (also referred to as RUM) provides a command-line interface that admins can use to remotely install updates of Adobe apps. Therefore admins do not need to log in to each client machine to install updates.

Hoiatus.
Märkus.
  • Remote Update Manager only detects updates but not upgrades. To install Creative Cloud app upgrades, either create a package from the Admin Console, or install the upgrades from the Creative Cloud desktop app.
  • RUM should be launched with elevated privileges.
  • If you are running RUM on a macOS machine, you must run the commands using sudo. Using the sudo command in Terminal requires an administrator password.

The latest versions of RUM ill are downloaded and packaged during the package creation process.

When you create a package, the Management Options screen on admin console has an option for enabling the use of RUM. If this option is selected (which is the default), RUM is included in the package. When the package is deployed, RUM is copied to the following locations on the client machine:

Windows:
C:\Program Files (x86)\Common Files\Adobe\OOBE_Enterprise\RemoteUpdateManager

macOS:
/usr/local/bin

RUM can then be run from the client machines.

Overview

Once you have deployed the Adobe apps on client machines, you want the subsequent updates for the packages to be available on the client machines. You can create an update package and deploy it manually on the client machines.
Instead of deploying the updates manually, you can use RUM. It polls Adobe Update server or the local Adobe Update Server if set up using the Adobe Update Server Setup Tool (AUSST). RUM deploys the latest updates available on update server to each client machine on which it is run. You need not manually push updates to the client machines.
The default setting when creating a package from the Admin Console is to have the Adobe updates turned off. Most enterprise environments do not provide their end users with admin privileges. With the updates turned off, the end users will not see the availability of updates; nor could they apply them if downloaded. RUM can be used to have those updates applied remotely even if updates have been disabled through the Options screen in the package creation workflow.
Once you have installed RUM on each client machine, you can run it remotely through command line or from remote management tools.

Märkus.

To set up a local update server (AUSST) in your enterprise setup, see Adobe Update Server Setup Tool.

Running RUM without AUSST

If an AUSST server isn't set up, each client machine polls Adobe Update Sever through port 443 over HTTPS to receive updates when you run RUM.

Remote Update Manager - Without AUSST

Running RUM with AUSST

If you have set up an AUSST server, the updates are downloaded from the Adobe Update Server onto the local update server. When you start RUM, each client machine polls the local update server to get updates.

Remote Update Manager - With AUSST

Using RUM to automatically keep the updates current

Setting up your environment before using RUM

If you do not want the products/components on client machines to directly download the updates without admin intervention, suppress manual updates while creating the package. For more information, see how to create:

Märkus.

RUM works irrespective of whether you have suppressed manual updates on client machines.

To store updates locally on a server for clients to access when you start RUM, use the Adobe Update Server Setup Tool (AUSST). See Running RUM with AUSST. For more information on how to set up AUSST, see Using Adobe Update Server Setup Tool.

Märkus.

Adobe Applications for which updates are to be installed should not be running when RUM is started.

Downloading and installing updates in separate instances

Using RUM, you can also remotely download and install updates on client machines. While passing the command for remote update, you can choose either to download and install the updates in the same or multiple lunches\runs of RUM. It enables you to download the applicable updates and then install them later. For more information on downloading and installing updates, see --action command-line option under RUM syntax and description.

Märkus.

The --action command-line option currently does not support the download of Acrobat and Reader.

Applying updates for Acrobat and Reader

The RUM supports Acrobat and Reader. However, before you run the Update Manager, you are recommended to check the following on the client machine:

On macOS, the Acrobat Updater version must be 1.0.14 or later.

  1. To check the updater version, run the following command in the terminal:

    defaults read "/Library/Application Support/Adobe/ARMDC/Application/Acrobat Update Helper.app/Contents/Info" CFBundleVersion

  2. If the updater version is older than 1.0.14, download the latest updater from:
    https://armmf.adobe.com/arm-updates/mac/ARMDC/ARM_update/ARMDC Agent Installer.pkg

  3. Install the downloaded updater package using the following command:

    sudo installer -pkg <path to the downloaded .pkg file> -target /

On Windows, the application versions should be as follows:

  • Classic track: 15.006.30279 or later
  • Continuous track: 15.023.20053 or later

For details latest updates for Acrobat/Reader, see Release Notes | Acrobat, Reader.

Märkus.

The above mentioned prerequisites are sufficient to apply updates for Acrobat and Adobe Reader. This means that the updates can be applied even if the Creative Cloud desktop app is not installed on the client computer.

RUM syntax and description

To start the update deployment remotely on each client machine, run RUM on each client machine. You might use enterprise deployment tools, such as SCCM, ARD, or JAMF Casper Suite for this. Alternatively, you can use a batch file that starts RUM on each client machine.
The syntax for RUM is as follows.

RemoteUpdateManager --proxyUserName= --proxyPassword= --channelIds= --productVersions= --action= --help 

Parameter

Description

--proxyUserName

The user name for the proxy server, if applicable

--proxyPassword

The password for the proxy server, if applicable

--channelIds

For the products listed in this page, use the --productVersion parameter, instead of --channelIds.

Specifies the id for the product for which updates are to be deployed remotely. You can specify one or more products by specifying their channel ids in a comma-separated list. Ensure that there is no space between the comma and the channel id that follows. For a list of products and the corresponding channel ids, see Channel IDs for use with RUM.
Default: If you do not specify this parameter, all available updates are deployed.

--productVersions

This parameter is optional and is applicable to the apps listed in this page.

Specifies a combination of SAP code of the product and the base version of the product for which the update is to be deployed. 

For example,--productVersions=ILST#25.0 deploys the update for Adobe Experience Designer (Preview) 0.5.0. 

If you do not specify a version (but only a product Id), updates for all the product versions installed on the client machine are deployed. If you do not provide this option, updates for all the products installed on the client machine are deployed.

The comma-separated entries in --productVersions update/deploy:

  • --productVersions=ILST#25.0: Deploys updates of Adobe Experience Designer (Preview) 0.5.0.
  • --productVersions=PHSP: Deploys updates of all the (full-installer apps) versions of Photoshop, as the version of product is not specified. 
  • --productVersions=ACR#12.0.0: Deploys updates of Adobe Camera Raw 12.0.
  • --productVersions=APRO#15.0: Deploys updates of Adobe Acrobat DC with major version 15 on Win32, Win64 and OSX10-64. For Acrobat installations with major version other than 15, appropriate major version must be used in place of 15.0.
  • --productVersions=RDR#15.0: Deploys updates of Adobe Acrobat Reader DC with major version 15 on Win32, Win64 and OSX10-64. For Reader installations with major version other than 15, appropriate major version needs to be used in place of 15.0.

RUM updates the products only if they are installed on the target system.  

All dependent/required components of the specified apps are also updated.

This parameter is optional. If not passed, all the updates are listed, downloaded, or installed as specified in the --action parameter. 

--action

Specifies the action to be performed: list, download, or install.

  • --action=list: Displays a list of applicable updates for the products installed on the machine. 
  • --action=download: Downloads the applicable updates.
  • --action=install: Installs updates if they are downloaded already. If the updates are not already downloaded, this command first downloads the updates and then installs them.
  • If --action is not specified, the command performs the default action and just downloads and installs the applicable updates.

Note: The --action command-line option currently does not support the download of updates for Acrobat and Reader.

--help

Lists the usage of the tool.

Examples

  • The following command starts RUM on the client machine for a scenario where there is no proxy server.

    RemoteUpdateManager

  • The following command starts RUM on the client machine that requires a proxy server user name TestUser and the proxy server password _27Dtpras?!

    RemoteUpdateManager --proxyUserName=TestUser --proxyPassword=_27Dtpras?!

  • The following command deploys latest updates only for all versions of Illustrator:

    RemoteUpdateManager --productVersions=ILST

  • The following command deploys latest updates only for Illustrator 19.0.

    RemoteUpdateManager --productVersions=ILST#25.0

  • The following command deploys latest updates for all versions of Illustrator and applicable updates for Photoshop CS6-13.0:

    RemoteUpdateManager –-productVersions=ILST --channelIds=AdobePhotoshopCS6-13.0

  • The following command deploys updates only for the products corresponding to the channel id AdobePhotoshopCS6-13.0 and the channel id AdobeInDesignCS6-8.0. There is no space between the comma (,) and “AdobeInDesignCS6-8.0”.

    RemoteUpdateManager --channelIds=AdobePhotoshopCS6-13.0,AdobeInDesignCS6-8.0

Return values

After execution, RUM returns one of the following values:

0

 Updates deployed successfully, or machine is already up to date.

1

Generic error, for example an internal error. For example,  the Adobe Application Manager installation may be corrupted or network is not available. In this case, typically, the process of downloading or installing updates cannot be started at all.

2

One or more updates could not be installed. For example, only two out of three updates might have been installed successfully.
Consider a case where updates are to be installed for Photoshop, Illustrator, and Dreamweaver. However, Photoshop is running on the client machine and so the updates were installed only for Illustrator and Dreamweaver. In this scenario, error 2 will be returned.

Detailed information is available in the RUM Log file, explained in the next section.

Download and installation status of updates

The console displays the status of downloading and installation of app updates. 

Status of download and installation of remote update of apps

RUM log file

The RUM log file provides detailed information about the events that occur during deployment of exception payloads with RUM.
The log file is named RemoteUpdateManager.log and is located as follows:

  • In Windows, the log file is in the %temp% location.
  • In macOS, the log file is in the folder ~/Library/Logs/.

Checking for Errors

The errors that RUM encounters are marked with the [ERROR] tag in the log file.

Log file data format

The RUM runs the complete Acrobat workflow (list and install) before running the Creative Cloud product workflows. The Acrobat logs will appear before Creative Cloud product workflows.

Also, the logs for all Creative Cloud products display in the following format:

SAPCode_version_platform. For example: PHSP_21.2.10.118_osx10-64.

However, the Acrobat and Reader logging information on Windows will be displayed as:

ProductName-BaseVersion. For example: AdobeAcrobatDC-15.0

Adobe logo

Logige oma kontole sisse