Anyone partake in Adobe RUM now that final version is out?

donmontalvo
Esteemed Contributor II

Final is out...anyone using it? Care to share strategy? Are you using with or without AUSST? Self Service? TIA

http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html

http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/AdobeRemoteU...

PS, I added "Adobe Renote Update Manager (RUM)" to the Third-Party Products page, but doesn't show up yet so I set this post to "AAMEE".

Don

--
https://donmontalvo.com
9 ACCEPTED SOLUTIONS

taugust04
Valued Contributor

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

View solution in original post

acdesigntech
Contributor II

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.

View solution in original post

cbrewer
Valued Contributor II

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

View solution in original post

taugust04
Valued Contributor

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.

View solution in original post

taugust04
Valued Contributor

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 :-).

View solution in original post

bentoms
Release Candidate Programs Tester

mscottblake
Valued Contributor

My computers are in a lab type of environment. I have updates turned off in AAMEE since the users are not admins and use RUM to maintain updates. I don't use an Adobe update server, so they are all pulling straight from Adobe.

Setting a policy to run RUM is actually quite easy. Once you download the binary, place it where you want it to be on your target systems, drag that file into Composer, and package it up. Then in the advanced tab of the policy you create, you just enter "/path/to/RemoteUpdateManager". Scope it and trigger it however you like and it works like a charm.

As far as I can tell, I'll never have to worry about repackaging an update to my CS packages. It's the easiest thing Adobe has created to date.

View solution in original post

tkimpton
Valued Contributor II

@Don. Yes we are in a better place. Just feel a little push is needed for the whole solution to work smoothly with updated clear documentation.

View solution in original post

tfriedm
New Contributor III

Thanks for all the input and youtube videos.

I also want to thank Karl Gibson, Product Manager Enterprise IT tools, Adobe Systems Europe Ltd and he helped me figure out my install issues for RUM. It's actually quite simple once we went through my install doc. Here's an updated process that works for me.

Running Adobe Remote Update Manager without AUSST packaged with the Jamf Suite

“NOTE: Adobe Remote Update Manager is only for a subsection of Adobe Desktop products. It can not be used for browser plug-ins such as Flash Player and for Adobe Reader, Acrobat Professional, and Adobe AIR application updates.”

From: http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html, download the RemoteUpdateManager.dmg. The RUM files are also installed in the Utilities folder under: /Applications/Utilities/Adobe Application Manager/Enterprise/Utilities/ when you download AAMEE 3.1.

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

Start Composer

Place only the RemoteUpdateManager file onto the client, (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. Next, go to the Exclusion List tab and scroll down until you find /private/var/tmp/, click on it, and then hit the - or remove button. Save the changes and proceed with the packaging. When you are all done, reset the exclusions to the defaults.

Take a snapshot. (I called it: Adobe Remote Update Manager.pkg) and place the .pkg into Casper Admin.

Then, 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/
/remoteupdatemanager

You can break this up into two Policies. One just places the Adobe Remote Update Manager.pkg on clients with Adobe applications installed and the Self Service Package is just the command line for the users to be able to run updates as needed.

Local install Test:

On the client run the following from a command line: Sudo /private/var/tmp/remoteupdatemanager

Verify that it’s running by monitoring the log files at: /Users/(user account)/Library/Logs/
Select: RemoteUpdateManager.log

An online tutorial showing how to configure AUSST and package RUM can be viewed on Adobe TV at: http://adobe.ly/NsxrY1

View solution in original post

42 REPLIES 42

chris_kemp
Contributor III

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

taugust04
Valued Contributor

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

donmontalvo
Esteemed Contributor II

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

--
https://donmontalvo.com

acdesigntech
Contributor II

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.

donmontalvo
Esteemed Contributor II

@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

--
https://donmontalvo.com

cbrewer
Valued Contributor II

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

donmontalvo
Esteemed Contributor II

@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

--
https://donmontalvo.com

cbrewer
Valued Contributor II

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

donmontalvo
Esteemed Contributor II

[color=red]Blaspheme!!![/color]

@cbrewer wrote:

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

[color=blue]<ducking for cover>[/color]

Don

--
https://donmontalvo.com

taugust04
Valued Contributor

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.

donmontalvo
Esteemed Contributor II

@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
--
https://donmontalvo.com

taugust04
Valued Contributor

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 :-).

acdesigntech
Contributor II
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 :P Spent my entire afternoo fighting with Adobe garbage errors "Photoshop can't initialize [for no @)#^(#^_ reason] because you don't have the necessary permissions"

tkimpton
Valued Contributor II

@don ROLF you crack me up lol!

dpertschi
Valued Contributor

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).

donmontalvo
Esteemed Contributor II

@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.

--
https://donmontalvo.com

tkimpton
Valued Contributor II

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

The documentation really has to be better.

donmontalvo
Esteemed Contributor II

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

--
https://donmontalvo.com

tkimpton
Valued Contributor II

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.

tkimpton
Valued Contributor II

Oh and showing examples of real life work flows!

bentoms
Release Candidate Programs Tester

tkimpton
Valued Contributor II

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

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

donmontalvo
Esteemed Contributor II
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...

--
https://donmontalvo.com

tkimpton
Valued Contributor II

Oh right

Thanks, I really appreciate it

tfriedm
New Contributor III

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.

tkimpton
Valued Contributor II

That would just install the man page and not the actual files. Don't worry it's Adobes fault for very very poor documentation.

The pkg Don sent me has a very nifty python script to install everything :)

Maybe one day....AAMEE will do it automatically..

Don anyway to load the file to the community or at least the script?

donmontalvo
Esteemed Contributor II

The script is actually provided by Adobe. All you need to do is download [edit]Greg Neagle's[/edit] ZIP'd wrapper package, then drop a couple files into it...done:

http://managingosx.wordpress.com/2011/05/02/more-help-from-adobe/

external image link

It's really pretty simple. But you're right, the documentation is very badly written.

Have a look:

http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/AdobeExcepti...

Hmmm....I wonder if Greg Neagle helped Adobe whip the wrapper together. :)

Don

--
https://donmontalvo.com

tkimpton
Valued Contributor II

No excuse fog them now not to just include that mechanism in AAMEE by default!!!

Thanks Don

I can never ever ever find anything on Adobe. I have to hunt so many places and still nothing. Documentation is poorly written and trails of Jody Roger jokes and sifting through blog crud makes me loose patience.

Come here and find Adobe solutions immediately ;)

I'll check out the Adobe dev forums further

donmontalvo
Esteemed Contributor II

@tkimpton Trust that Jody is directing his team to build more functionality into AAMEE, but no matter how robust and usable they make it, Jody admits Adobe has nothing on Nerf...now those guys know how to Deploy CS-6.... :)

external image link

Jody has done a lot in the past 2 years...remember what a mess it was when Adobe distributed its installer development to different pockets of marginally capable developers who made the Adobe Creative Suite (etc.) installers a collective mess. Adobe probably saved a ton of money since we ended up subsidising their development team (joke's on us, ey?). :)

AAMEE is Jody's baby (thank you Victoria!), it's part of the solution. We're slowly crawling our way out of the hole Adobe put us in. We're soooo much better off now than we were back then. Hopefully Adobe will take care of Jody and give him even more authority and control, who knows we may even see proper PKG/MPKG installers that don't need to be re-engineered.

I'm hoping to see a Nerf Cluster Bomb Deploy Everything Adobe gun, this way we won't have to (re)package anything.

Don

--
https://donmontalvo.com

mscottblake
Valued Contributor

My computers are in a lab type of environment. I have updates turned off in AAMEE since the users are not admins and use RUM to maintain updates. I don't use an Adobe update server, so they are all pulling straight from Adobe.

Setting a policy to run RUM is actually quite easy. Once you download the binary, place it where you want it to be on your target systems, drag that file into Composer, and package it up. Then in the advanced tab of the policy you create, you just enter "/path/to/RemoteUpdateManager". Scope it and trigger it however you like and it works like a charm.

As far as I can tell, I'll never have to worry about repackaging an update to my CS packages. It's the easiest thing Adobe has created to date.

tkimpton
Valued Contributor II

@Don. Yes we are in a better place. Just feel a little push is needed for the whole solution to work smoothly with updated clear documentation.

tfriedm
New Contributor III

Thanks for everyone's input. I'm working with an Engineer from Adobe tomorrow to review the process and all the suggested methods of deployment. I'll share the results when complete.

tkimpton
Valued Contributor II

Great

Please get him to twat whom ever wrote the AUSST tech notes!

donmontalvo
Esteemed Contributor II

Maybe @tfriedm will go all 'Gladys Ormphby' on Adobe...LOL...

https://www.youtube.com/watch?v=IBczl5p5ySk

--
https://donmontalvo.com

tfriedm
New Contributor III

Thanks for all the input and youtube videos.

I also want to thank Karl Gibson, Product Manager Enterprise IT tools, Adobe Systems Europe Ltd and he helped me figure out my install issues for RUM. It's actually quite simple once we went through my install doc. Here's an updated process that works for me.

Running Adobe Remote Update Manager without AUSST packaged with the Jamf Suite

“NOTE: Adobe Remote Update Manager is only for a subsection of Adobe Desktop products. It can not be used for browser plug-ins such as Flash Player and for Adobe Reader, Acrobat Professional, and Adobe AIR application updates.”

From: http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html, download the RemoteUpdateManager.dmg. The RUM files are also installed in the Utilities folder under: /Applications/Utilities/Adobe Application Manager/Enterprise/Utilities/ when you download AAMEE 3.1.

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

Start Composer

Place only the RemoteUpdateManager file onto the client, (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. Next, go to the Exclusion List tab and scroll down until you find /private/var/tmp/, click on it, and then hit the - or remove button. Save the changes and proceed with the packaging. When you are all done, reset the exclusions to the defaults.

Take a snapshot. (I called it: Adobe Remote Update Manager.pkg) and place the .pkg into Casper Admin.

Then, 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/
/remoteupdatemanager

You can break this up into two Policies. One just places the Adobe Remote Update Manager.pkg on clients with Adobe applications installed and the Self Service Package is just the command line for the users to be able to run updates as needed.

Local install Test:

On the client run the following from a command line: Sudo /private/var/tmp/remoteupdatemanager

Verify that it’s running by monitoring the log files at: /Users/(user account)/Library/Logs/
Select: RemoteUpdateManager.log

An online tutorial showing how to configure AUSST and package RUM can be viewed on Adobe TV at: http://adobe.ly/NsxrY1

jwojda
Valued Contributor II

@tfriedm - Thank you, this helped tremendously. I've managed to get a basic setup through Self Service with your help.

I do have a question though, Adobe seemed a little vague in their doc about what it will update vs not update. Is there a more comprehensive list or are those 4 or 5 apps the listed the only things it wont update?
Is there a separate update procedure for Acrobat Apps?

tfriedm
New Contributor III

Thanks for your response John. Here's a link that should help answer your question: http://helpx.adobe.com/creative-cloud/packager/using-remote-update-manager.html

This information comes from Karl Gibson, the person that helped me put together the RUM deployment and he has also recently replaced Jody Rodgers as the Product Manager for the Enterprise IT Tools.

Specifically, the document calls out the non-supported apps.
"Note: Remote Update Manager is meant only for a subsection of Adobe Desktop products. It cannot be used for browser plug-ins such as Flash Player and for Adobe Reader, Acrobat Professional, and Adobe AIR application updates."

Checkout this link for Acrobat Pro updates: http://www.jamfsoftware.com/solutions/adobe-acrobat-pro-and-the-casper-suite. If you do a search on each of the other apps that you mentioned within jamf nation, there's tons of good advice to manage them. Unfortunately, Adobe has products in the company that are not part of the Creative group's patch schedule and are done independently.

jwojda
Valued Contributor II

I ran a test on a cs5.5 design std install, verified the CS.5.5 package installed and ran as expected, exited out of it, then I ran the RUM and watched the the RUM.log file while everything completed. But when I launched PS5.1, it prompted for a SN. Do I need to re-send a SN after running RUM?

the CS6 test did not have the same issues, just 5.5...

tfriedm
New Contributor III

RUM only applies available updates. There may be a problem with your Photoshop install package. It shouldn't break the Photoshop serial number. I'd suggest re-packaging CS5.5 with AAMEE V2.1 with the latest updates and running RUM again. If it still causes issues, then you'll want to contact Adobe support or talk with Jamf support and get a ticket started.