The Many Uses Of RUM

*** Guest Blogger Karl Gibson, CS Enterprise Systems Engineer ***

A few weeks ago, Jody was kind enough to ask me to write a guest blog about RUM. Misunderstanding him and keen to impress so as to secure a permanent spot on this blog, I threw myself into the research I felt was required. I visited all 1,000 pubs in Dublin to sample there finest RUM, what I came to realize in pub 999 is that Ireland actually only imports 3 brands of rum, lesson learned!  Needless to say when I presented my findings to Jody he was not impressed and clarified he would actually like me to speak about the newest Enterprise IT Tool codenamed RUM (Remote Update Manager) So let’s get on with it.

Through my experience in speaking with IT Admins in the Enterprise and Education sectors, I have noticed the default behavior in most cases when building packages with AAMEE is that most people seem to select to have clients suppress updates. This I think is for 4 main reasons:

  1. Users are not Admins on there own machine, which means updates will fail.
  2. Bandwidth
  3. Control and validation of updates
  4. They use AAMEE to create update packages

I think everyone agrees that keeping software up to date is important for a number of reasons, chief among them security and bug fixes.

The RUM tool allows you to remotely initiate the Adobe Updater on client machines. It works as follows:

1. Admin creates package using AAMEE and selects update options, for example admin chooses to suppress updates.

2. Package is deployed and installed on clients

3. RUM file is copied to clients

4. Using a 3rd party deployment tool, admin sends a command to all clients telling them to invoke the Adobe Updater. Updater launches as admin and pulls down and installs all updates for CS products installed on the client from either Adobe.com or if you have set up your own internal Adobe Update Server using AUSST then updates (Mac or Win) will come from your internal server (saving bandwidth)

RUM will run when executed regardless of the update selection you have chosen in AAMEE and works with Creative Suite version 5 onwards.

We have already seen this tool being used to great effect and with people implementing it into there update schedule and having it execute automatically with designated frequency.

But don’t take my word for it, test it out today. If you have installed AAMEE 3.0 then you already have RUM, which is located in the “Adobe Application Manager/Enterprise/Utilities” folder.

If you just want the RUM tool, here is the direct link

http://labs.adobe.com/technologies/aameetools/

Now I am off to get Vitamin A for my liver.

Karl Gibson | CS Enterprise Systems Engineer

6 Responses to The Many Uses Of RUM

  1. Jody Rodgers says:

    Thanks Karl! But to be clear, you may need more than just Vitamin A, and be careful in taking too much Vitamin A as it can actually cause liver damage.

    http://www.livestrong.com/article/29091-vitamins-liver/

    Man am I helpful.

    Jody Rodgers | Sr. Product Manager | Enterprise + Volume | CS + CCM | Adobe

  2. Thanks for the RUM data. I have two questions I believe apply to many in the “education sector”:

    In our environment, we rebuild from a master image after every class. Currently (CS5.5), that process runs unattended because we create that image with all updates (and prefs., etc) in place. When the next class begins, a student fires up the computer and we’re good to go. Is there a workflow that approximates this with CS6?

    Second, and more generally, it seems odd that there isn’t an installer, created by Adobe, that an admin can use to install, serialize and update in one go, in preparation for imaging/deployment. I’m not trying to criticize–I know the tools you provide are handy for a broad range of enterprise users. But it seems that since you have these tools, Adobe should be able to build a more fool-proof installer than smaller (read, understaffed) businesses like mine can. Question: is this something we might look forward to?

    Thank you…

    new to these tools,
    Steve

    PS have you enjoyed El Presidente?
    http://www.nytimes.com/interactive/2012/06/12/dining/summer-drinks-generator.html

    • kagibson says:

      Steve,
      Regarding the first workflow. You would be able to do similar for CS6, when installing the software for the master image you would install CS6 in trial mode, configure it and update it. You could then create the image and schedule the serialization file AAMEE 3.0 creates to run on first boot. This would leave you with a fully functional, configured and updated machine.

      Second, AAMEE 3.0 does a build a package that is pre-serialized and ready to be deployed. I understand though as I mentioned above, the workflow for imaging requires some extra steps. Regarding updates in the case of AAMEE 2.1 it would also pull in the most recent updates and add them to the package. This unfortunately did not make AAMEE 3.0 but will be restored in AAMEE 3.1

      Cheers
      Karl Gibson
      CS Systems Engineer

      • Eric says:

        What happens if you install in trial mode and you want to make adjustments to say photoshop settings on the master image after 30 days? Does it still let you get in?

        • Jody Rodgers says:

          Nope. You can serialize the master image. It simply will not stick though once cloned.

          Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Digital Media | Adobe

          • Eric says:

            Cool, thanks. That is easy enough. So easy to make adobe serialization work after sysprep, dont see why so many people are offended of having to put another step in.

Leave a Reply

Your email address will not be published. Required fields are marked *


8 − = five

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>