Quoted from Jody Rodgers’s
You are at your holiday party. You have had one, okay, more than one, glass of spiked eggnog. You are singing along to Wham!’s “Last Christmas” off key. Let’s face it, your judgement might be slightly impaired. And of course, as an IT admin, your goal is to avoid talking to your production manager at these type of events. Too late. He’s cornered you. Oh, that tie! Does he think he is being ironic wearing that Santa tie?
And the next day when you awake you have a slight flashback. What did I promise? Something about telling the production manager I would deploy Adobe’s Creative Cloud for teams before I left for my break. How can you package up and deploy the “cloud?” That doesn’t even make any sense. Oh my head. The nog!
Well I hope this blog will be your Rockstar Recovery drink to get you through this. First, let’s clarify a few things. First, the Creative Cloud for teams offering is different the Enterprise offering. We’ll have a few blog posts going into the Enterprise offering in 2013. This post is simply focused on what an IT admin who has to help roll out the Creative Cloud for teams can do with the existing Adobe IT tools like AAMEE and RUM to make things easier. We’ll be rolling out comprehensive documentation in January on this topic but want to give a quick overview.
Let’s say you are rolling out 50 seats of Creative Cloud for teams in your office. You may be involved with the actual administration of sending out invites. This is done through the admin portion of the Creative Cloud site. From the Invite Multiple option you can either copy and paste user’s email addresses (ouch! carpal tunnel) or import a .txt or .csv file of the user’s email address. Then you can send them an invite and they’ll login with or create an Adobe ID.
Then they’ll download and install the Creative Cloud version of the Adobe Application Manager and begin downloading and installing the full offering of Adobe’s Creative Cloud applications and updates. All of them. All of the apps. All at once. All 50 of the users. What? This is in your Portland office? The only office that hasn’t had the network upgrade yet. Better turn off your mobile stat and hide.
Now that scenario of course could be avoided if you used your existing deployment infrastructure by pushing out packages of the apps rather than using your office’s internet connection for all 50 users. But how do you package up a set of apps that come from the cloud? Ah, you need a work-a-round, a hack. Well my friend, as a former IT admin I am all about the hack. Here’s how you do it: The bulk of the applications they are downloading from the Creative Cloud are the CS6 installers and to be frank, are not exactly what I’d call svelte in the MB/GB department. So you could download them yourself from our FTP site as the CS6 Master Collection and then use AAMEE 3.1, our CS6 packager, to package them out and distribute them.
But wait, AAMEE requires a volume serial number, right? Well remember we also have a Trial workflow in AAMEE 3.1. And the Trial workflow is really an unlicensed version of the CS6 app, just waiting for licensing via a serial number or an Adobe ID login associated with a subscription or Creative Cloud membership. Get it? So once it is packaged up you can distribute using your deployment infrastructure and then have them log in after you send the invites. This turns the unlicensed CS6 app into a Creative Cloud app. Magic. More like magic hack.
A few caveats about this plan/hack are:
1) apps such as the Edge tools, Muse and Lightroom aren’t part of CS6 so the end-users will have to download those apps on their own. The Edge tools and Muse are quite lightweight in size though.
2) the updates that you package with AAMEE 3.1 will not fully get the applications up to date. Why? Because the Creative Cloud have their own special feature updates that are not part of CS6. Therefore they can’t be seen in the Updates screen with the CS6-based AAMEE 3.1. You could execute the Remote Update Manager (RUM) once the end user has signed into the application with a valid Creative Cloud account. Then when you run RUM it will recognize the install as a Creative Cloud app and then pull that Creative Cloud-specific update down and install it.
(There is obviously a joke opportunity in there with RUM and spiked eggnog but I am going to refrain. Not because I am opposed to stupid jokes. Anyone who has read this blog in the past knows that. But this is out of principal. And that is because I am in the camp that firmly believes eggnog only has one true friend. And that friend is from Loretto, Kentucky. I’ll say no more.)
If you have read through this blog post cursing me and saying things aloud saying things like “Don’t you know my end-users aren’t admins?” or “There is no way we would give our users access to whatever apps they want.” or “I don’t want my users to have to have Adobe IDs.” If that is the case, then we have an Enterprise version of the Creative Cloud that can accommodate your organization. Lots more info on this topic coming early 2013 including us previewing some cool new stuff at the Mac IT event in San Francisco which we are are a sponsor.
If you are not familiar with our FTP site, you can get to the CS6 installers by going here:
And if you are unfamiliar with AAMEE you can download it here along with the tome that is the Enterprise Deployment Guide that covers AAMEE, RUM, and more:
Hope this hack helps. That is a lot of ‘h’ action. Here’s two more: Happy holidays!