Use Adobe Remote Update Manager

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.

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.

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.

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.

Using RUM to automatically keep the updates current

In the section:

• Setting up your environment before using RUM
• Downloading and installing updates in separate instances
  
• Applying updates for Acrobat and Reader
  
• RUM syntax and description
• Examples
• Return values
• Download and installation status of updates
  
• RUM log file

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:

• Named User Licensing packages.
• Shared Device Licensing packages.

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.

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.

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.

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.

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, JAMF Pro, Munki, or Microsoft Intune 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 

Examples

Return values

After execution, RUM returns one of the following values:

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. 

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