The 2.0 version of Adobe Application Manager Enterprise Edition (or AAMEE so that I do not get carpal tunnel from typing the full name) is available directly for downloading for the Adobe DevNet site. http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html In addition to this release the 2.0 version of the Adobe Update Server Setup Tool (AUSST) is now available for download as well. More about AUSST in a bit.
The team has been hard at work to create a new version of AAMEE that supports the new CS 5.5 release but also supports CS 5.0 media and 5.0 updates. The two big new features of AAMEE are: 1) in-app updates and 2) support for Acrobat X with CS 5.5 media.
I am really excited about the in-app updating, so excited that I already blogged about it, basically stealing my own thunder as it were. But seriously, it was a pain to leave AAMEE and go then go to the CS Updates blog and download the updates and then manually add them. Right? Right. And how on earth could you possibly know if all those updates were interrelated to the applications you were deploying? Do you a PHD in Adobe Updateology? Me neither, and I work here. This is why the team delivered the ability in this new version to have AAMEE query Adobe’s external update server for you. You pick the applications you are creating the package for on the Updates screen and then it shows you the updates related to that update. Then you can download them from within AAMEE and build your core application package with the latest updates or if you are creating just an update package of CS applications it is up to date. What if you are creating more than one package? AAMEE caches the updates so they can be repurposed.
Also on the topic of updates, if you have been deploying the video products you will want to check out the section of the Deployment Guide called “Difference between Product Update Names for DVD and Electronic Software Distribution—Combination Package” to explain why you might be seeing updates labeled Trial even if you did not download a trial CS installer or even if your software was serialized. This involves esoteric things such as licensed content, templates, ESDs, and other things you might know if you had that PHD in Adobe Updateology or if you were Todd Kopriva.
A great aspect of working with the CS 5.5 media is that it comes with Acrobat Pro X on the same disc or disc image. And AAMEE 2.0 supports it. Progress! Before I get carried away with my exclamation marks I should sober myself with visualizing the long series of asterisk marks this topic deserves as there are indeed a decent amount of caveats with deploying and updating Acrobat Pro X as part of CS 5.5. Please check out the “Deploying Adobe Acrobat” section of the Deployment Guide and ESPECIALLY the “Handling Feature Lockdown on Mac OS after Applying Updates” subsection if you are deploying Acrobat X out to Macs as part of an AAMEE package. I know it isn’t pretty. What is not in the doc, specific to Acrobat Pro X, is that on the Mac you also need to mac sure you are deploying the package out to the right OS. For instance, if you are using a North American English CS 5.5 serial you will run into trouble deploying this out to a Mac that has their OS language set to Swedish. That is a bit of an edge case, but if you run into this let us know and we’ll have some workarounds.
AUSST allows you setup a local update server to house your Adobe CS updates on your own server. If your users are admins you can save a lot of bandwidth from having them pull the updates locally instead of from Adobe’s servers. I pronounce AUSST similar to “cost” sans the “c” of course, or like saying the city of Austin without the “in” part. Trust me, saying the full names or even the five letters of these five name IT tools in full gets old real fast.
Now that we got the pronunciation out of the way, let’s talk about what’s new with AUSST 2.0. Primarily and most importantly it provides support for the forthcoming CS 5.5 updates. So if you are an organization using the current version of AUSST and are about to migrate to 5.5 or will have a mixed environment of 5.0 and 5.5 users you will want to upgrade right away. For clarification, if you are running an update server setup with AUSST 2.0 it will support both 5.0 and 5.5 updates.
Along with the release we have a completely new documentation for AUSST. We heard your feedback loud and clear about the documentation and have effectively rebooted the documentation. We’d love to hear your thoughts on the new documentation as a lot of time was spent on re-visioning it. We want to continually improve these docs so that getting started with an update server is straightforward.
What does AUSST 2.0 not do? Well the biggie that is not yet implemented is the ability to send out command line requests to the AUSST server to push out updates to end users. We are looking into this and other feature requests for a future version of AUSST.
Note: AUSST 2.0 is part of the AAMEE 2.0 install. The location for the various operating systems is on Page 15 of the Deployment Guide. It is also available as a separate download on the Adobe DevNet site
Please keep in touch. We read every single comment. Even the spam comments.
Jody Rodgers | Senior Product Manager | Enterprise & Volume | Creative Suite