Adobe Remote Update Manager overview

Adobe Remote Update Manager (RUM) provides a command-line interface that administrators can use to remotely install updates for Adobe applications across multiple client machines. Using RUM eliminates the need for administrators to log in to individual computers to apply updates manually, making update management more efficient in enterprise environments.

RUM is commonly used in organizations where manual updates are disabled on client machines. In these environments, end users typically do not have administrative privileges and cannot install updates themselves. RUM allows administrators to deploy updates remotely while maintaining centralized control over update distribution.

How RUM works

RUM is included as part of the Adobe package deployment workflow. When you create a package in the Admin Console, the option to enable RUM is selected by default. After the package is deployed, RUM is installed on the client machine and can be run locally or remotely using enterprise deployment tools.

Once started, RUM checks for available updates from either:

• Adobe Update Server
• A local update server configured using Adobe Update Server Setup Tool (AUSST)

RUM then identifies applicable updates for installed Adobe applications and deploys those updates to the client machine.

RUM supports updates for installed applications but does not support major application upgrades. To deploy major upgrades, create a new package from the Admin Console or allow upgrades through the Creative Cloud desktop app. 

Running RUM without AUSST

If an AUSST server is not configured, each client machine connects directly to Adobe Update Server over HTTPS through port 443 when RUM runs. The client machine checks for available updates and installs the applicable updates locally.

This model is commonly used in environments where client machines have direct internet access to Adobe services.

Running RUM with AUSST

Organizations that want greater control over update deployment can configure Adobe Update Server Setup Tool (AUSST) to maintain a local update server.

With AUSST configured, updates are first downloaded from Adobe Update Server to the local update server. When RUM runs on client machines, those machines retrieve updates from the local server instead of connecting directly to Adobe servers.

Using AUSST helps organizations:

• Reduce internet bandwidth usage
• Centralize update management
• Control update availability across the organization

Enterprise update management with RUM

RUM supports centralized update workflows across managed enterprise environments. Organizations commonly use RUM in the following scenarios:

Suppressed manual updates

Many organizations suppress manual updates during package creation to maintain administrative control over software updates. In these deployments, users cannot view or install updates themselves. RUM enables administrators to remotely deploy updates while maintaining centralized control.

Scheduled maintenance windows

Administrators can schedule RUM execution during maintenance windows or off-hours to minimize disruption for end users.

Deployment tool integration

RUM integrates with enterprise deployment and device management tools such as:

• Microsoft Intune
• Microsoft Configuration Manager
• JAMF Pro
• Munki
• Apple Remote Desktop

These tools can remotely trigger RUM execution across managed devices.

Bandwidth and timing control

When used with AUSST, RUM allows organizations to control when updates are downloaded and when they are deployed to client machines. This approach helps manage bandwidth consumption and maintain consistent update timing across the organization.

Prerequisites and considerations

Before using RUM, review the following considerations:

• Adobe applications targeted for updates should not be running when RUM starts.
• RUM must run with elevated administrative privileges.
• On macOS, RUM commands must be run using sudo.
• RUM works regardless of whether manual updates are suppressed on client machines.
• Client machines require network access either to Adobe Update Server or to the AUSST server.

RUM installation locations

When you deploy a package with RUM enabled, the tool is installed in the following default locations.

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

macOS: /usr/local/bin

Administrators can run RUM directly from these locations or execute it remotely using enterprise deployment and device management tools.

Update scope and limitations

By default, RUM updates all installed Adobe applications on the target machine, including required dependencies and components. Administrators can also choose to deploy updates only for specific Adobe applications and versions.

RUM supports updates for installed applications, including patches and minor revisions. However, RUM does not support major application upgrades.

Currently, RUM does not support updating Adobe XD.

For Acrobat and Reader, RUM downloads and installs updates as part of the same operation. The ability to separate download and installation phases applies only to Creative Cloud applications.

Acrobat and Reader support

RUM supports updates for Acrobat and Reader in enterprise deployments.

Acrobat and Reader updates can be deployed even if the Creative Cloud desktop app isn't installed on the client machine.

To support RUM updates successfully:

• On macOS, the Acrobat Updater version must be 1.0.14 or later.
• On Windows, supported versions include:
  • Classic track: 15.006.30279 or later
  • Continuous track: 15.023.20053 or later

These version requirements ensure compatibility with the Acrobat update workflow.

For information about command syntax, parameters, return values, and log files, check the RUM syntax and log reference.