Adobe Remote Update Manager provides a command-line interface that you can use to remotely invoke the Adobe Update Manager and install updates with administrative privileges. Therefore you do not need to log in to each client machine to install updates.
Remote Update Manager should be launched with elevated privileges.
The latest version of Remote Update Manager will be downloaded and packaged during package creation process.
When you create a package with Creative Cloud Packager, the configuration screen has an option for enabling the use of Remote Update Manager. If this option is selected (which is the default), Remote Update Manager is included in the package. When the package is deployed, Remote Update Manager is copied to the following locations on the client machine:
C:\Program Files (x86)\Common Files\Adobe\OOBE_Enterprise\RemoteUpdateManager
Remote Update Manager can then be run from the client machines.
Once you have deployed the Adobe applications on client machines, you will typically 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 Remote Update Manager, which polls Adobe Update server—or the local Adobe Update Server if setup using the Adobe Update Server Setup Tool (AUSST) —and deploys the latest updates available on update server to each client machine on which it is run. Thus you do not have to manually push updates to the client machines.
The default setting when creating an installation package with Creative Cloud Packager is to have the Adobe updates turned off because the majority of enterprise environments do not provide their end-users admin rights. With the updates turned off, the end users will not see the availability of updates; nor could they apply them if downloaded. Remote Update Manager can be used to have those updates applied remotely even if updates have been disabled through the Creative Cloud Packager configuration options.
Once you have installed Remote Update Manager on each client machine, you can invoke it remotely through command line or from remote management tools.
Remote Update Manager is meant only for a subsection of Adobe Desktop products. It cannot be used for some native installer applications such as Adobe Edge Code, Edge Reflow, and Gaming SDK. Browser plug-ins such as Flash Player and for Adobe Reader, Acrobat Professional, and Adobe AIR application updates are also not supported.
To set up a local update server (AUSST) in your enterprise setup, see “Adobe Update Server Setup Tool”
If you do not have an AUSST server set up in your enterprise environment, each client machine polls the Adobe Update Sever directly to get the updates when you invoke Remote Update Manager.
If you have set up an AUSST server, the updates are downloaded from the Adobe Update Server onto the local update server. When you invoke Remote Update Manager, each client machine polls the local update server to get updates.
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 on how to do this, see the description of the Configure Package screen in the “Creating Deployment Packages” article.
Remote Update Manager works whether you have suppressed manual updates on client machines.
If you want all the updates to be stored locally on a server from where the client machines will access it when you invoke Remote Update Manager, use the Adobe Update Server Setup Tool (AUSST). See Running Remote Update Manager with AUSST. For more information on how to set up AUSST, see Using Adobe Update Server Setup Tool.
Adobe Applications for which updates are to be installed should not be running when Remote Update Manager is invoked.
Using Remote Update Manager, 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. This 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 Remote Update Manager syntax and description.
To invoke the update deployment remotely on each client machine, run Remote Update Manager on each client machine. You might use an enterprise deployment tool such as SCCM, ARD, or JAMF Casper Suite for this, or use a batch file that invokes Remote Update Manager on each client machine.
The syntax for Remote Update Manager is as follows
RemoteUpdateManager --proxyUserName= --proxyPassword= --channelIds= --productVersions= --action= --help
||The user name for the proxy server, if applicable
||The password for the proxy server, if applicable
For the products listed in this page, use the
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 it). For a list of products and the corresponding channel ids, see Channel IDs for use with Adobe Remote Update Manager.
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 baseversion of the product for which the update is to be deployed.
For example,--productVersions=SPRK#0.5.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 prod-uct versions installed on the client machine are deployed. Ifyou do not provide this option, updates for all the productsinstalled on the client machine are deployed.
The comma separated entries in --productVersions update/deploy:
The products, however, are updated by RUM 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.
Specifies the action to be performed: list, download, or install.
||Lists the usage of the tool.
- The following command invokes Remote Update Manager on the client machine for a scenario where there is no proxy server
- The following command invokes Remote Update Manager 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 updates only for the products corresponding to the channel id AdobePhotoshopCS6-13.0 and the channel id AdobeInDesignCS6-8.0. Note that there is no space between the comma (,) and “AdobeInDesignCS6-8.0”.
- The following command deploys latest updates only for Illustrator 19.0.
- The following command deploys latest updates only for all versions of Illustrator:
- 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
||Updates deployed successfully, or machine is already up-to-date.|
||Generic error, for example an internal error. For example, this might be the case where Adobe Application Manager installation is corrupted or network is not present. 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 Remote Update Manager Log file, explained in the next section.
The Remote Update Manager log file provides detailed information about the events that occur during deployment of exception payloads with Remote Update Manager.
The log file is named RemoteUpdateManager.log and is located as follows:
- In Windows, the log file is in the %temp% location.
- In Mac OS, the log file is in the folder ~/Library/Logs/.