Platform
Adobe Remote Update Manager (RUM) installs updates for Adobe apps on managed computers. Run it locally or through your deployment tool with administrator privileges.
RUM installs updates, including patches and minor revisions. It doesn't install major application upgrades. To deploy a major upgrade, create a new package from the Admin Console or allow upgrades through the Creative Cloud desktop app.
Prerequisites
Before you run RUM, make sure that:
- An Adobe package is deployed on the client machine, and RUM is installed on it. See RUM download and installation options.
- You run RUM with elevated administrative privileges.
- On macOS, you run RUM commands using sudo.
- The Adobe apps you want to update aren't running when RUM starts.
- The client machine can reach the Adobe Update Server or your AUSST server.
RUM works whether or not manual updates are suppressed on client machines.
RUM download and installation options
You can get RUM in either of these ways:
- Deploy it with a package. When you create a package in the Admin Console, the Enable Remote Update Manager option is selected by default. After you deploy the package, RUM is installed on the client machine. See Create Managed packages.
- Download it from the Admin Console. Sign in to the Admin Console, then select Packages > Tools. See Packaging overview and tools.
When you deploy a package with RUM enabled, the tool is installed in these default locations:
|
|
Default location |
|---|---|
|
Windows |
C:\Program Files (x86)\Common Files\Adobe\OOBE_Enterprise\RemoteUpdateManager |
|
macOS |
/usr/local/bin |
You can run RUM directly from these locations or remotely through your deployment and device management tools.
Run RUM from the command line
Open Command Prompt (Windows) or Terminal (macOS) as an administrator, go to the RUM installation location, and run:
- Windows: RemoteUpdateManager
- macOS: sudo RemoteUpdateManager
By default, RUM downloads and installs all applicable updates for the installed Adobe apps. To update specific apps, download updates for later, or use a proxy server, see Deploy and manage updates with RUM.
For command syntax, return values, and log files, see RUM syntax and log reference.
Update sources for RUM
When RUM starts, it checks for available updates from one of these sources:
- Adobe Update Server
- A local update server that you configure with the Adobe Update Server Setup Tool (AUSST)
RUM then identifies the updates that apply to the installed Adobe apps and deploys them to the client machine.
Running RUM without AUSST
If you don't configure an AUSST server, each client machine connects directly to the Adobe Update Server over HTTPS on port 443 when RUM runs. The client machine checks for updates and installs them locally. This model works well when client machines have direct internet access to Adobe services.
Running RUM with AUSST
To control update deployment more closely, configure AUSST to maintain a local update server. AUSST downloads updates from Adobe Update Server to your local server first. When RUM runs, client machines retrieve updates from the local server instead of connecting to Adobe servers.
With AUSST, you can:
- Reduce internet bandwidth usage
- Centralize update management
- Control update availability across your organization
- Control when updates download and when they deploy to client machines
For more information, see the Adobe Update Server Setup Tool overview.
Enterprise update management with RUM
Organizations commonly use RUM to:
- Deploy updates when users can't. Many organizations suppress manual updates when they create packages. Users then can't view or install updates, and RUM lets you deploy them remotely.
- Update during maintenance windows. Schedule RUM to run during off-hours to limit disruption for users.
- Trigger updates from deployment tools. These tools can run RUM across managed devices:
Supported products
By default, RUM updates all installed Adobe apps on the client machine, including required dependencies and components. You can also deploy updates for specific apps and versions.
|
Product |
Run updates it |
Notes |
|---|---|---|
|
Creative Cloud apps |
Yes |
Updates include patches and minor revisions. You can run the download and install phases separately. |
|
Adobe Acrobat |
Yes |
RUM downloads and installs updates in one operation. |
|
Adobe Acrobat Reader |
Yes |
RUM downloads and installs updates in one operation. |
Acrobat and Reader requirements
RUM supports updates for Acrobat and Reader in enterprise deployments. You can deploy these updates even if the Creative Cloud desktop app isn't installed on the client machine.
To update Acrobat and Reader successfully:
- On macOS, the Acrobat Updater version must be 1.0.14 or later.
- On Windows, use one of these supported versions:
- Classic track: 15.006.30279 or later
- Continuous track: 15.023.20053 or later