Adobe Systems Incorporated

Adobe Installation and Licensing

Blog to post all Installer and Licensing related info to users of Adobe products

Sep 24, 2011

Top Ten Awesomeness of AAMEE 2.1

I’ve wanted to do a top ten list on this blog for sometime. I am sucker for those top ten articles on the internet. You know the ones “Top Ten Best Places For Real Estate In Places You Would Never Move To,” “Top Ten Worst Places For Real Estate Including Where You Live,” or “Top Ten Best Android Apps Released Between 8-10 AM This Morning.” And then you click on them and then the site annoyingly makes you click through ten separate pages so you can see ten ads. By the time you get to the 8th one you have lost interest and feel your carpal tunnel kicking in.

This is not that type of top ten. Nope. Just a list of ten awesome things about the free IT packaging tool Adobe Application Manager Enterprise Edition (AAMEE) 2.1. Once you get to the 8th item on this list you’ll say “I can’t stand it, I have to have it now” and you’ll stop reading and click on the download links. But wait, how can a dot release that has TEN awesome things in it? That is a lot of stuff for a dot release. Right? Well the AAMEE team is pretty much obsessed with packing in as much goodness as they can. We’ve been focused on saving IT admins time and I think this release has a lot to offer on that front.

So without further ado I bring you…
Top Ten Awesomeness of AAMEE 2.1:

1) Existing packages can be updated!
We now have a new workflow that allows you to update packages that are created with AAMEE 2.1 so that they are always up to date. If you create a package in October, you can go back and refresh the updates in that package in December. Awesome.

2) AAMEE now supports more than just the Creative Suite!
Sweet, more suites. AAMEE 2.1 fully supports Technical Communication Suite 3.5 and has limited support for eLearning Suite 2.5 and Acrobat X Suite. Awesome.

3) No more merging of DVD images!
Some folks download the Creative Suite from the Adobe Licensing Website (LWS) as one single large image. Others get it other ways including from resellers and have to take the physical discs and then create images of them and then go through a convoluted and time consuming process of merging them. Merge no more my friends as we now support multiple disc inputs, both physical or iso/dmg. Awesome.

4) Preferences!
Those who have never used AAMEE or have created lots of packages with AAMEE may not think that preferences as a category are not worthy of my gratuitous and carefree use of exclamation marks, but trust me. Prior to 2.1 there were no saved preferences. Now AAMEE automatically remembers your preferences for things including the package name, save to location, Installer location and best yet all the options you select on the Configure Package screen are now all saved after you quit and reopen AAMEE. A big time saver if you have to create multiple packages in a row. Awesome.

5) Never quit AAMEE again!
Another time saver for sure. Now after you are finished building a package you will see a New Package button that takes you back to the start of the workflow process. It is kind of an infinitive loop. Why would you need this? Well let’s say you had to break down the Master Collection into 14 separate application packages. Before, you would have to open AAMEE 14 times. Combined with the fact that we now have preferences this dreadfully laborious task would be, well, still dreadfully laborious. But overall, quicker. Awesome.

6) Support for Apple Mac OS 10.7 Lion!
You can now happily use AAMEE 2.1 to create packages on your 10.7 system knowing it has been tested and vetted by the AAMEE crew. Awesome.*
*See the Known Issues with Adobe products on Mac OS 10.7 Lion doc for the latest on compatibly with the products and 10.7.

7) Support for Apple Remote Desktop 3.5!
Want to create packages with AAMEE 2.1 and then push them out to systems using ARD 3.5? Of course you do. And you can sleep well at night knowing it is supported. Awesome.

8 ) Filter updates by name!
We’ve added a Search by Product option in the Updates section of AAMEE 2.1. There are a ton of updates and sifting through them can be a little daunting. Now in the Updates screen simply type in the Product name and get instant results of what updates are available for that product. Awesome.

9) AAMEE 2.1 is thinking about its demise!
“Ever since the XP-38 came out, they just aren’t in demand.” Wether its landspeeders or packaging tools eventually things become obsolete. As exciting and shiny as AAMEE 2.1 is today, we have to come to grips that one day there will be an AAMEE 2.2 or an AAMEE 3.0. And AAMEE 2.1 has come to terms with this and starting with this version it will do a search at launch to see if a new version is available and announce its own redundancy. Awesome.

10) ExceptionInfo.txt file now includes commands!
Okay, so maybe I front loaded this list a bit and now the end of the list is looking rather thin. There maybe there is some truth to that. But if you are a Mac admin and having to deploy items from the Exceptions folder you probably don’t want to have to go to a website just to get the command line text for deployment, right? Why not put it in the doc that is in the Exceptions folder? We did. See? Even this last one falls under the category of: Awesome.

So there you go, ten solid reasons to click on the links below and start using AAMEE 2.1. We also have a new Read Me that includes more on these new features and a list of known issues. And we are continually updating and revising the CS5/CS5.5 Enterprise Deployment Guide that explains how to use AAMEE, APTEE, AUSST and more.

Adobe Application Manager, Enterprise Edition 2.1 (Windows)

Adobe Application Manager, Enterprise Edition 2.1 (Mac)

Jody Rodgers | Senior Product Manager | Enterprise & Volume | Creative Suite | Adobe Systems

Deployment Tips, Updates


  • By Don Montalvo - 4:48 AM on September 24, 2011   Reply

    This is a great update!

    If we have a 13 GB package for Adobe CS 5.5 Master Collection that was created in October, can we use AAMEE 2.1 in December to package only the updates released since then? Or do we need to push another 13 GB package only to get the updates deployed?

    You guys are awesome…you’ve made our jobs SOOOOOOO much easier!!!

    Don Montalvo, TX

    • By Jody Rodgers - 10:04 AM on September 24, 2011   Reply

      Thanks so much Don!

      In your example you can simply create and push out a small Update-only package in December that has the updates that were released during the duration between Oct-Dec. I think the best use of this feature is for a lab or school where once a quarter they refresh the systems. Or maybe in a location where an image gets refreshed on a scheduled basis.

      Again, thanks for the kind words!

      Jody Rodgers | Senior Product Manager | Enterprise & Volume | Creative Suite | Adobe Systems

      • By Don Montalvo - 11:51 AM on September 25, 2011   Reply

        Of course…there is the CREATE UPDATE PACKAGE on the very first window. Wow, you guys really did a sweet job with this baby!


  • By William Smith - 6:40 AM on September 24, 2011   Reply

    Thanks for this, Jody! Each AAMEE update really does make my work with Adobe products a much better experience. I have an upgrade from CS4 to CS5 for a few groups next weekend and I’m actually not dreading it like I would have with deployments a few years ago. (That’s a compliment.)

    I ask that you focus on the Adobe Air stuff next! Having to exclude AIR in AAMEE because of proxies but having Help dependent on it is one of my last pain points. After that we can bake cookies.

    • By Don Montalvo - 10:38 AM on September 24, 2011   Reply

      …if I may also ask for AAMEE to include Acrobat Pro X updates too? 🙂


  • By Asus A53U-XE1 - 12:09 PM on September 25, 2011   Reply

    I <3 number 2 on the list! Great to see we can finally integrate a lot more stuff, makes everything just a bit more cohesive!

  • By Sean Alexander - 7:02 AM on September 26, 2011   Reply

    I agree with William and Don on the request of AIR and Acrobat Pro X.
    From reading the release notes and the blog, I am looking forward to AAMEE 2.1.

  • By Kai Howells - 8:59 PM on October 13, 2011   Reply

    I’m liking all the options in the new AAMEE.
    I like that things like AIR can be excluded and am going to be testing a Design Premium package I’m building at the moment under an InstaDMG workflow.

    This product, whilst used by far less people than the Creative Suite as a whole, really makes our lives easier and I’m very happy to see that Adobe realises how important tools like this are and continues to improve them.

    I like it that in CS5.5 that Acrobat X is now able to be packaged with AAMEE, this is an improvement and all I ask on this front is that Acrobat updates are able to be rolled in for a future release.

    Thank you Jody and the team for listening to the feedback from all of us, down in the trenches, and building a better product.

  • By Lee Ramsay - 11:37 PM on October 13, 2011   Reply

    Has the issue where running acrobat first de-serialises the rest of the creative suite, in AAMEE 2.1? This was reported by many people on the AAMEE 2.0 blog post, and was not responded to.

  • By Jerry Silverman - 7:46 AM on November 21, 2011   Reply

    Dude, the XP-38 was basically the same machine. They just changed the plating, hoped no one noticed.

  • By Don Montalvo - 7:44 AM on December 19, 2011   Reply

    One of our clients just signed an EPP, good news for us on the management side.

    Now we just need a reliable way to purge old versions of CS (reliably) and pushing 5.5 (reliably).

    The AAMEE produced PKG for Master Collection 5.5 runs fine on a freshly imaged machine.

    However it fails on a Mac that has older versions installed. We’ve tried all these:

    1. Adobe cleaner tool (

    2. Running every Adobe uninstaller we could find in /Applications/Adobe* and /Applications/Utilities/Adobe*

    3. Manually purging Adobe folders from ~/Library/Adobe* and /Library/Adobe*

    Even using all these methods, we can’t get the AAMEE produced PKG for Master Collection 5.5 to work.

    PS, and yes the AAMEE produced PKG works fine on freshly imaged Macs. 🙂

    I wanted to check here before opening a ticket with Adobe (hoping EPP offers leverage).

    We have hundreds of users asking us go get them updated to 5.5…we need to get this resolved.


    • By Don Montalvo - 1:46 PM on December 19, 2011   Reply

      OK, turns out I had “Abort install” set in AAMEE prefs…I’m switching that and testing again.

      Oy, I can’t wait for AAMEE 3 to come out. It’s supposed to give the AAMEE user a 1000 volt shock if they don’t use the proper settings. 🙂


  • By Bob Reed - 11:19 AM on September 7, 2012   Reply

    I am using AAMEE 2.1 to repackage CS5.5 (Design Premium) with updates for Snow Leopard users. I have no problem incorporating Adobe updates, but have not figured out a way to incorporate rapid releases into packages. Our users use K4 along with InDesign and InCopy. And Vjoon periodically recommends us to install specific Adobe rapid releases beyond our current update level. We have not been able to get AAMEE to recognize and work with Adobe rapid releases.

    Imagine the chaos if every software maker developed their own proprietary installer mechanisms instead of using MSI on Windows or PKG on Mac. Adobe, what were you thinking?
    Bob Reed

    • By Jody Rodgers - 3:50 PM on September 7, 2012   Reply

      What were we thinking? No seriously!?!? Dealing with non-standard installers is a pain, I will give you that. That is why I was so glad to see Acrobat taking the lead and going to native OS installers. Now, onto your present issue. Have you experimented with the Remote Update Manager (RUM) tool pointing to a local AUSST server? You can get RUM here, and yes it works with CS5.x by design:

      BTW, this might be a better topic for our forum:

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

  • By Yuriy Vinokurov - 6:20 AM on March 22, 2014   Reply

    This AAMEE is a pain in an ass. I try to create deployment for native InCopy 5.5 installer and what do I see? “This version does not supported by this version of AAMEE ” Brilliant! AAMEE 2.1 support CS5.5, but it does not support CS 5.5. What a wonderful shitlication!!!

Add a comment