This is kind of a dual-purpose Mac tutorial—how to automate Adobe Remote Update Manager and how to create an installation package using a point-and-click graphical interface.
Automating Adobe Remote Update Manager
You can find the Adobe Remote Update Manager on Adobe’s Creative Suite Enterprise Deployment page. Just scroll down a bit until you find it.
For our purposes here, the only file that matters is RemoteUpdateManager. That is the actual executable binary that initiates the updates. You don’t really need to install the RUM man(ual) page. If you want to find the update options (including how to use a proxy instead of getting updates directly from Adobe), you can find those on Adobe’s website.
Remember where the RemoteUpdateManager file is. We’ll need that file later.
Then create a text file called local.rum.plist and put in the following contents:
<!DOCTYPE plist PUBLIC “-//Apple//DTD PLIST 1.0//EN”
The text file you just created is the launch daemon that will run the Adobe Remote Update Manager (RUM) once a day at 18:15 (or with whatever frequency you set up).
Creating the distributable package
If there are multiple machines you want to set this up for, you don’t want to be manually copying files to two different locations on each computer. We’re going to set it up so you can install a .pkg file on each computer, or distribute the .pkg file to each computer using something like Munki.
Apple provides its own official documentation on how to build a .pkg file. If you can use those instructions, good on you.
I found it much easier to use a program called Packages to do it the point-and-click way.
When you go to the Packages website, click the Download link.
For this situation (Adobe RUM), we’re just going to select Raw Package and then click Next.
By default, the project will be a subdirectory of your /Users/username folder, so you may want to pick a different directory. If you’re fine with the default, just go with it.
Then go find the RemoteUpdateManager binary you downloaded from Adobe earlier.
Then select your local.rum.plist file you created earlier.
These permissions should be fine. It just means any user will be able to run RemoteUpdateManager, which is fine. Only the script will probably run it, but there’s no harm in the users being able to invoke it manually, too, if they want.