Posts tagged "Adobe Update Server Setup Tool"

Somebody new brings you something new- Introducing the Creative Cloud Packager

Hi All,

Some of you awesome IT administrators will already be familiar with who I am, some of you may not but for the last few years I have been the Systems Engineer working with our customers on Enterprise Deployment Issues. You may also recognise me from such blogs as “The Many Uses of RUM”. What you may not know is that I am and have been for the last 4-5 months the Product Manager for the Enterprise IT Tools such as AAMEE, AUSST, RUM ,XDA & APTEE.

 

What happened to Jody Rodgers you may be asking ?

Has Adobe tried to silence him ?

Stop him in his tracks before he makes deploying Adobe software too easy for IT admins ?

Has he tried one last time to grow his hair, become cool and join Sigur Ros ?

No !  in fact he has been promoted to Senior Product Manager for Creative Cloud for Enterprise.

 

So with that said there is going to be some exciting times ahead and some great new tools. So let’s get started.

 

Adobe Creative Cloud for Team is a pretty awesome offering.  You get all of Adobe’s applications, you get new feature bearing updates, shared storage, folder syncing & lots of other cool stuff.

However before now there was no great way to deploy the products to systems where users were not administrators. Our workaround was that you should download CS6 Master Collection from our FTP Server and package with AAMEE 3.1 but this was certainly not ideal and not what AAMEE was designed for. So the team who brought you AAMEE is bringing you The Creative Cloud Packager a brand new tool which will in it’s first iteration allow you, as an administrator for a CC Team to download directly from the application all of the Creative Cloud Products & Updates (regular and feature), define custom installation behaviour and at the end have a native MSI or PKG that you use with your deployment tool to install on all machines you manage. Now just in case you missed that, this means no separate media download. WHOOOO

 

Some key points

If you have used the AAMEE workaround up till now you can still use CCP from now on.

CCP caches to a location of your choice and so if the applications and updates have not changed then you do not need to download the same bits again and again thus saving you some time.

CCP can be used to create an update only package by just selecting updates.

CCP produces an msi file for Windows which is also accompanied with a Setup.exe that can be used for manual execution on a single system basis, rather than deployment. The Mac pkg can also be double clicked.

There is a new version of Adobe Update Server Setup Tool 3.0 (AUSST) included with CCP. This has been changed from python to C++ and has significant benefits such as

-Reduced the amount of time it takes to perform initial and subsequent syncs

-Ability to set up cron jobs for automatic syncing and updating of repository

Remote Update Manager (RUM) is also now included in the package and copied to the client by default although this can be changed if you wish

 

This tool is live today and will be available to Creative Cloud Team administrators from the Team admin portal.

Documentation is live and can be viewed here

You can catch a video I created on our Adobe TV site here

 

Here is a screen shot (not a mockup) of Creative Cloud Packager.  CCP is something that will be evolving and we have some pretty awesome plans for it, so stay tuned !!

ccp copy

 

*Update 09/04/13 Included image of where you will find Creative Cloud Packager on the admin portal when you sign in with admin account*

ccp live

Karl Gibson | Product Manager | Enterprise IT Tools

AAMEE 2.0 and AUSST 2.0 Live!

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.

AAMEE 2.0

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 2.0

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

Adobe Enterprise Deployment Tools Upgraded & Expanded

I am happy to announce the release of the much anticipated Adobe Application Manager Enterprise Edition (AAMEE) 1.1. This release has the ability to turn our CS updates that come down from Adobe.com in the format of .zip files on Windows and .dmg files on Macs into MSI and PKG files for easy deployment. You can do this singularly or better yet combine them into a big bundle of updates into one MSI or PKG. Want to deploy your CS5 applications and our updates at the same time? AAMEE 1.1 can do that too. Create your own “über-package” of CS applications with their updates and deploy them at the same time with one MSI or PKG. Cool, right?

And if that weren’t enough, we have released two new deployment tools for IT admins: Adobe Provisioning Toolkit Enterprise Edition (APTEE) and Adobe Update Server Setup Tool (AUSST.) Yes, we are continuing our 5 letter acronym spree! Put the three tools names together and you almost have enough letters to play Boggle™. Both new tools are command line based and I believe you’ll find them quite helpful. The Adobe Provisioning Toolkit Enterprise Edition (APTEE) tool allows you to serialize, unserialize or reserialize installed CS applications. The Adobe Update Server Setup Tool (AUSST) allows you to configure a server on your network to become the local location for acquiring CS updates.

We’ll have blog postings that dig further into each of these tools coming soon but I wanted to let you know right away about the three tools so you can download them and their documentation.

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

NOTE: The Adobe Developer Connection website and new tools on them may be unavailable for a brief time in the near future for a site-based update. So…get ‘em quick! Don’t worry, they will return once the revamped site goes online. The tools should be available on LWS as well.

9/13/10 6:43 PM PST UPDATE: The new Adobe Developer Connection website is up and the new tools are once again available. Sorry for anyone who was inconvenienced during the down time.

Jody Rodgers
Product Manager, Enterprise & Volume Customers
Creative Suite