Posts tagged "RUM"

Creative Cloud Packager 1.3 is live

Great news, Creative Cloud Packager 1.3 is now live.

We are genuinely excited about this release. Not that CCP 1.2 was not exciting, actually who am I kidding it was important in that it had some bug fixes but that’s not exciting is it ? Though maybe I am being presumptuous and their are people out there who just love a good bug fix. CCP 1.3 on the other hand brings some pretty exciting features and just to keep those aforementioned people happy we also have some bug fixes.

Here are the new features in CCP 1.3

  • Support for archived versions of Products
  • Support for Native application Installers (Edge Code, Edge Reflow, Scout, Gaming SDK)
  • Support for Proxy Auto Configuration (PAC) files
  • RUM support for Feature Bearing updates
  • New Shortcut locations
  • New IT Tools Un-installer
  • Build information in Product UI

ccp 1.3 archive

 

Let’s start with

Support for archived versions: The Creative Cloud gives you access to the latest and greatest Adobe products but also access to previous or archived versions of products which is a very important aspect to many peoples workflows. CCP 1.3 now allows you to package the latest and greatest but also archived versions of applications beginning with CS6 era applications. They can be packaged together or separately depending on what your requirement is.

Support for Native application installers: In the past you would need to download separately from Adobe’s licensing website any applications that were native installers. In this release those applications are now downloaded directly from CCP.

Support for Proxy Auto Configuration (PAC) files: CCP will now honor PAC files that are used to provide proxy information.

RUM support for Feature Bearing Updates: This was a big one, you can now install FB updates by invoking RUM or by going to the “Help” menu of the product itself, this was not previously possible for Creative Cloud Enterprise customers.

As promised there are some important bug fixes in this release. Some customers where having issues with imaging when non Creative Cloud products where included in the image, this should now be fixed. Customers using AUSST where experiencing an intermittent issue whereby downloads where timing out. We have now updated the version of AUSST carried in the CCP 1.3 download and also on Devnet to resolve these issues.

What do you need to do to get this amazing new release you ask ? Why just re-launch CCP and you will be prompted to self update.

For more information on this release please visit the Creative Cloud Packager help page

Finally a special thank you to all the participants who helped test out the Pre Release version. Your input as always is incredibly valuable.

Cheers

Karl Gibson | Product Manager | Enterprise IT Tools

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

Using Adobe’s IT tools to deploy Creative Cloud for teams

3rd (and final) UPDATE 05/13/13
This article is now antiquated and should not be used. In April we released a brand new tool for our Team Customers called “Creative Cloud Packager” for more information please go here

 

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.

Screenshot of the admin portion of the Creative Cloud site

 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:

ftp://ftp.adobe.com/pub/adobe/cs6/downloads/

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:

http://www.adobe.com/products/creativesuite/technical-resources.html

Hope this hack helps. That is a lot of ‘h’ action. Here’s two more: Happy holidays!

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

 

UPDATE: The PDF of the white paper “Adobe Creative Cloud for teams IT Deployment Guide” is live:

http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/CCT_IT_Deployment_Guide.pdf

 

2nd UPDATE 3/6/13: Two issues with the workflow mentioned, both fairly major. First, the media that is on the FTP is not for North American English. We are working to get that posted on the FTP site. In the meantime, you can find the CS6 MC media from: http://www.adobe.com/downloads/

[Note: Getting media from that page requires the use of the Adobe Download Assistant which is very consumer focused. Sorry about that.]

Second, in order to have the ability to login properly with a Creative Cloud for Teams account the system needs to have the latest copy of Adobe Application Manager installed. Unfortunately the Adobe Application Manager can’t be packaged with AAMEE nor is it a native installer. I know, I know!  Here are the links to the Adobe Application Manager files:

Windows: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4773

Mac: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4774

It can be installed from command line by:

Win: <Path to Setup.exe>Set-up.exe –mode=silent –action=install
Mac: <path to ASU> /ASU/Install.app/Contents/MacOS/Install –mode=silent –action=install

AAMEE 3.1 Beta Live (Yes, Updates Have Returned!)

Update for Sep 13, 2012:  The release of AAMEE 3.1 is live and features 3 significant features not in the beta. See the blog post AAMEE 3.1…or why puffer fish is a delicacy for more info.

____________________

I was working on another draft of my acceptance speech for Software Industry’s Worst Product Manager of the Year 2012 award when I got the call: AAMEE 3.1 could be released as a beta. And this series of mudslinging and thinly veiled (and some not so veiled) insults will no hopefully come to a close. With the return of the Updates workflow we can now can dodge rotten tomatoes thrown our way for worthy reasons (like breaking imaging workflows) instead of taking out features everyone liked.

The beta of AAMEE 3.1 is now on Adobe Labs in the Enterprise IT Tools for Adobe Creative Suite section. We decided to go the route of releasing the beta on Adobe Labs instead of our traditional Prerelease program because we wanted to get this in the hands of as many people as possible, as soon as possible. This release is not 100% “feature complete” and I am hoping to get one more significant component into this release. In the meantime, here is the Top Ten of what is new with AAMEE 3.1 beta:

1)   Updates added to Installation Package workflow

2)   Updates added to Trial Package workflow

3)   Update Package workflow added

4)   Modify Existing Package workflow added

5)   Support for eLearning Suite 6

6)   Support for Technical Communication Suite 4

7)    New Welcome screen

8)   Display of build time now in % (and more accurate)

9)   Ability to specify specific updates with Remote Update Manager

10) Adobe Exceptions Deployer now in Exceptions folder

Okay, so I ran out of things for the Top Ten and had to include changes for RUM and xDA. But you get the point; the AAMEE crew has been b-u-s-y these last two months! And now get thee to the Internets. Oh wait, you are on the internet already. Okay, then, please follow these easy steps:

1) Go here: http://labs.adobe.com/technologies/aameetools/

2) Read the 3.1 Read Me and updated Deployment Guide

3) Read and accept the terms and download the AAMEE 3.1 beta

4) Use the AAMEE 3.1 beta and happily make update packages in the comfort of air conditioned rooms while drinking lemonade.

5) Provide your feedback about this release in the Labs forum:

http://forums.adobe.com/community/labs/aameetools/

6) Follow the @Adobe_ITToolkit and/or set your RSS reader to this blog so you can be informed of when AAMEE 3.1 ships

Thanks to the AAMEE crew for getting this out so quickly and thanks in advance to everyone for helping us out testing this beta.

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

Deploying Creative Suite 6 Webinar

If you do a web search for “deploy CS6″ do you know what comes up? The Nerf Deploy CS-6. What is that? A clip system Nerf blaster that was released in 2010 under the N-Strike series. How did I become such a Nerf expert? The Nerf Wiki of course. If you want to be in the know about the Deploy CS-6 then head to the Nerf Wiki page for the Deploy CS-6. If you want to be in the know about how to deploy CS6, as in how to do a mass software deployment of Creative Suite 6 using tools like the Adobe Application Manager Enterprise Edition (AAMEE) 3.0 then mark you calendars for Tuesday, May 22, 2012, 10AM PST for the Adobe Webinar “Deploying Creative Suite 6″ with your hosts Jody Rodgers and Rick Borstein. We will cover AAMEE, the new CS6 licensing changes, and the new command line tools Remote Update Manager and the Exceptions Deployer application. We will answer questions about imaging, activation, and possibly how to get the most performance out of your Nerf blaster.

UPDATE: Webinar recording available online:

http://seminars.adobeconnect.com/p5cusn6zish/

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

Where the party is at: Macworld | iWorld | MacIT Conference 2012

Are you attending the Mac IT conference this week? You know the one, the one that is part of the iWorld event in San Francisco. What is iWorld? Remember MacWorld? Well they dropped the “Mac” bit and now it is just “i” saving tons of money in printing costs by dropping two letters. Do note the “W” is now capitalized, which it had not been in the past. The “i” is small. Got all that?

Well if you are there this week, I’ll let you in on a secret, I know where the party is. No, not some secret hip party in some cool bar with umlauts in the name. No offense to the legitimate bars and their name in proper umlaut countries; carry on as you were. No, the party is from 11:45am – 12:30pm on Thursday Jan 26 at Moscone West!

The topic: IT823: Deploying & Managing Adobe Desktop and iOS Touch Apps.

What should you wear? I am thinking casual since it is an IT conference, but looking fabulous never hurt anyone.

Who from Adobe is going to be there? Me! I’ll be the MC of our panel talk. You can call me MC J-Rodg if you want. I’m cool with that. Also, we’ve got: Eric Widle, Senior Engineering Manager for the Creative Suite along with my awesome boss (who doesn’t read this blog but should) Carol Linburn: Director Creative Suite Product Management, Creative Suite. And last but not, least, we’ll have Steve Gottwals, Group Product Manager from Acrobat there. That’s right, Acrobat at the MacIT conference! History my friends, history.

What are we going to discuss? Creative Suite deployment tools like the forthcoming AAMEE 3.0 and our new Remote Update Manager tool we are working on. Our new Creative Cloud offering and what it might mean to IT. Also, we’ll discuss the emerging world of management of iOS apps, like our new Touch Apps. You’ll want to be there for that section as we’ll be giving away a few copies of the awesome new Peachpit “iOS 5 in the Enterprise” book by John Welch. John by the way has been instrumental in us getting to participate at these MacIT events and for the record has dropped more f-bombs about Adobe then anyone else on the planet. We listen to all complaints and suggestions; sugar coated ones and ones that are more, well, let’s coin a word: Welchian.

Hope to see you there. Please stop by and introduce yourself. It is always a pleasure to meet the IT admins who work with our tools first hand!

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