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

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?

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/AdobeExceptionsDeployer.pdf

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

Don

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

@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

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.

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

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.

Great

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

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

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

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

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

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.

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

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.

Hi @tfriedm @mscottblake @donmontalvo @taugust04 , Please help with RUM deployment. My case is - We have many users who has installed multiple adobe apps from different sources. We use jamf pro to manage all our mac systems. Now as part of app updates we need to update all the adobe apps" supported by RUM". I am new to composer and adobe deployments 1st question is - does RUM work in my scanrio ? if yes, how can i silently/forcefully install RUM on all managed mac's by jamf. I saw your above instructions for the package the RUM, honestly i am new to composer. I see below file when I run the dmg file. AdobeRemoteUpdateManager.pdf
InstallRUMManPage.sh
RemoteUpdateManager
RemoteUpdateManager.1
When I double click on sh file just a script open up does nothing, when click on exec file it just give "zsh:bad cpu type in exceutable/volume/RUM/Remote update manager/Remoteupdatemanager" and does nothing Because i am new your steps are not clear to me how to create package. I used the snapshot method in composer by running the sh and exce file nothing captured. I haven't tried with just drang and drop method.

Hello sk8559, I'm afraid that I have not be actively supporting Adobe packaging for a few years. Also, at the time when I wrote my suggested fix, Adobe apps were managed as individual licensed apps and not part of their current cloud suite, so I don't know if the steps that I listed will still apply. I'll review your post and if I find any information, I'll post a response. Todd

I also placed this info in your other post: I think this link should answer your question: https://helpx.adobe.com/enterprise/using/applications.html. If you go down to Manage updates remotely, you'll see that RUM only works on Managed Packages. Users that are downloading the apps directly are not supported by RUM.