Interesting...haven't done this myself, but I'll be watching this.

I've been using the beta version since earlier this summer, and recently updated the version installed in our environment to the final 3.1 version. I'm using it in conjunction with an AUSST. I have a shell script stored in Casper that runs RUM. We have a normal policy in place that checks for Apple software updates weekly at login. I amended that policy to run the RUM if Adobe CS6 is installed.

I've seen some issues with updates getting hung-up if the system is at the loginwindow, but I believe that has to do more with how Adobe is writing and packaging their updates than the RUM software itself. Overall, I would say it works well in conjunction with an AUSST.

We don't have self-service implemented, so we're not using it via that methodology...

~Ted

We were thinking of using RUM on a monthly basis, trigger all updates via policy, requirement being computer is logged off (else policy won't run). We'd also provide via Self Service, would show update available if you missed the monthly policy. :D

when I was building our CS6 packages, I did a VERY quick test with AUSST and RUM and it all went swimmingly.

Haven't done much use case testing, just a few simple tests while I was packaging.

@acdesigntech That's great to hear! Our original plan to date our PKG and then create monthly update PKGs fell flat, as AAMEE 3.1 still can't use the PKG as a starting point for creating "all updates since last package" package. :(

Adobe RUM...delicious...

Don

Where are you guys choosing to store the RemoteUpdateManager binary on client machines?

@cbrewer I hope this doesn't start a religious war (like vi vs pico vs etc...). We put it in /usr/sbin although it can be put in a number of places that are part of the standard path.

Don

I went with /usr/local/bin for no particular reason.

Blaspheme!!!

@cbrewer wrote:

I went with /usr/local/bin for no particular reason.

<ducking for cover>

Don

Since this was an Adobe product, I decided to add it to:

/Library/Application Support/Adobe/

...and created a directory called RUM, and installed the binary there.

@taugust04 The only problem in that isn't part of the standard path.

$ echo $PATH

/opt/local/bin:/opt/local/sbin:/Developer/usr/bin:/Developer/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin

That's true. My shell script is coded to run it from the directory I created. I'm still a novice in terms of my scripting skills and best practices. Although it's not a standard path for UNIX binaries, I like to keep Adobe products isolated from the rest of the system as much as possible .

I like to keep Adobe products isolated from the rest of the system as much as possible .

heh, I'd like to isolate them all the way off the system Spent my entire afternoo fighting with Adobe garbage errors "Photoshop can't initialize [for no @)#^(#^_ reason] because you don't have the necessary permissions"

@don ROLF you crack me up lol!

I would like to enjoy RUM also.

When I build my AAMEE pkg, in the Configuration options for Adobe updater, is the first option Adobe Update Manager is disabled the appropriate choice? (no internal update server yet).

@dpertschi If you're using RUM, and have no update server, disabling that option means only you can update CS using RUM, and the updates would come from Adobe. We let users update, and we've got them all pointing to internal servers.

Thanks for the clarification. Jody Rogers if your reading please twat the document writer.

The documentation really has to be better.

@tkimpton I'm guessing you meant "swat the document writer". :)

This is what I found with cs6

If I use AAMEE and disable updates, point to an internal server, use self service to launch the Update Manager then it shows like trial installation options of say After effects etc instead of showing no updates available etc.

Documentation should be clear. This is causing mass confusion!

So Documentation should say in and Enterprise the recommended options using AAMEE is to NOT disable updates, point to an internal Adobe software update set using AUSST, generate and generate the override file required for AMMEE.

The outcome is then possible to update the suite with RUM AND update manually if required.

Oh and showing examples of real life work flows!

@Don, nope Tim meant http://onlineslangdictionary.com/meaning-definition-of/to-twat-someone

Sorry Don forgot its just British slang for hitting someone very hard lol

Thanks for the file. How did you get my email?

Thanks for the file. How did you get my email?

@tkimpton Well, you didn't make it easy...I remembered your old posts included your email in the sig. ;)

If you open the Exclusions PKG in Pacifist you'll see how it's put together...

Oh right

Thanks, I really appreciate it

I've been trying to package RUM with the help from my account manager without success. Could anyone provide the steps on how that they've created the package and then how it's setup in Self-Service?

Here's what I've done so far with the help from Jamf:

Package and Deploy Adobe Remote Update Manager (RUM)

From: http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html, download RemoteUpdateManager.dmg

Once you open the .dmg file, you’ll see the following:
AdobeRemoteUpdateManager.pdf
InstallRUMManPage.sh
RemotUpdateManager
RemoteUpdateManager.1

Place all those files, even the script, into a hidden location on a machine, (we used: /private/var/tmp).

In order to package /private/var/tmp, you need to temporarily allow composer to see this location. By default, Composer will ignore this location. In Composer, go to the Composer menu and click on Preferences, then go to the Exclusion List tab, then scroll down and find /private/var/tmp/, click on it, and then hit the - or remove button. Save the changes, and then try to package the files again. When you are all done, reset the exclusions to the defaults.

I saved the completed file as a .pkg and added to Casper Admin.

Then, I create a Self Service policy called: Adobe Remote Update Manager (RUM).
In the Packages tab, selected the Adobe Remote Update Manager.pkg

In the Advanced tab, I entered the following command: /private/var/tmp/InstallRUMManPage.sh

Results:
I ran the policy on a 10.7.5 computer running Adobe Master Collection CS6 – job completed, but no updates to Master Collection and I couldn’t find a ~/Library/Logs/RemoteUpdateManager.log as noted in the Adobe documentation.

I also tested on a 10.6.8 computer running Adobe Master Collection CS5.5. This time the job ran but hung in Self Service without completing.

Thanks for any help or clarification.