I love the smell of a new release in the morning – CCP 1.6 is Live

Hi All,

What a lovely morning it is and you know what makes a morning even better? coffee and you know what else? a croissant. But after your coffee and croissant, that’s right a new product release! Fresh on the heals of the awesome 2014 product announcements + Ink and slide. We have also gone and released a new version of Creative Cloud Packager.

Features of this version include

The ability for Enterprise and Education Device License customers to create a license file.

Enterprise folks will remember this from the AAMEE days but it is also now possible to use CCP to create a license file. This is useful for enterprise customers if they wish to go from trial to serialised deployment or they wish to change from one license key to another.

For Education Device License customers this is especially important if you are trying to migrate from one license type to another for example going from a Team Named license to Device license.

CCP 1.6 copy

We have also added a nifty feature whereby when you create a license file we also produce a Un-License file that can be used to remove the Creative Cloud License from an existing machine.

The ability to create a package with just the Creative Cloud for desktop app

In the past it was not possible to create a package with just the Creative Cloud for Desktop app. This made things a little difficult if you wanted to deploy an update to the app across your environment. You can now create a CCP package containing just the desktop App.


InDesign CC 2014 & InCopy CC 2014 (32 Bit Windows) Issue

With the release of InDesign & InCopy CC 2014 we noticed an issue whereby when you select a 32 bit package in CCP an error is encountered during the build process. This is due to the maximum file path being exceeded during extraction. We are working on a long term fix however in the interim we have documented the required workaround here.

Adobe Muse CC 2014

On Mac, Muse CC 2014 is bundled in the main payload and it no longer requires an Adobe ID upon launch.

On Windows, Muse CC 2014 is still treated as an exception furthermore there is some nuances to how it is deployed. More information can be found here

Again we are working with the relevant teams to try and improve the process and make it as painless as possible to deploy.


Karl Gibson | Product Manager | Enterprise IT Tools

Announcing a new Creative Cloud for enterprise

Adobe announced today a number of exciting updates to Creative Cloud.  We are pleased to be able to offer these updates to our creative tools and services, including support for high performance platforms and latest industry standards, to our enterprise customers. Creative Cloud for enterprise customers have access to these updates through the Creative Cloud Packager as of today.  In addition, enterprise customers have access to a number of tools and services designed with the large enterprise in mind. Creative Cloud for enterprise customers now offers streamlined license management using the Adobe Enterprise Dashboard and Creative Cloud Packager. The web-based Adobe Enterprise Dashboard lets you manage users and provision entitlements centrally. Here, IT support can also access the recently updated Creative Cloud Packager to deploy software that supports the named user model.  Through Enterprise Dashboard, IT staff at Creative Cloud for enterprise customers will gain the ability to assign software to users instead of just devices.  This ability, called named user deployment allows for greater flexibility in setting up software and in supporting users in the office or at home. Named user deployments set the stage for Creative Cloud for enterprise customers to allow access to Creative Cloud services to their users.  This means that, if IT staff allow it and enable it, enterprise users will be able to use:

Creative Cloud for enterprise customers can also, by IT staff choice, access Creative Cloud storage.  This option allows for much more than simply storing creative assets in the cloud. This service allows storage, sharing, and versioning of creative assets.  Creative Cloud storage also allows for extra information like color palettes and font selection to be extracted from Adobe file formats.  This makes reusing style information between projects quicker and easier. If your organization does not want to use the Creative Cloud Services or Storage, that’s okay. Using Creative Cloud for enterprise,  IT staff can install Creative Cloud applications with serial numbers instead of named user accounts. This allows for installation on completely offline machines – an option not available in other Creative Cloud plans. Also included in this release is dedicated, enterprise-level customer care, which includes orientation programs and 24×7 technical support for IT. Adobe Enterprise Dashboard also is your one-stop shop for handling your organization’s support needs.  It provides access to submit and track support claims, phone numbers for priority support, and the ability to schedule 1:1 Expert Service appointments for your creative users. Access to the 2014 release of Creative Cloud and the availability of Adobe Enterprise Dashboard are the first in a series of steps that will make Creative Cloud for enterprise a more flexible solution for handling creative needs for our enterprise customers. Stay tuned for more news in the next few months. To get more information on accessing Adobe Enterprise Dashboard, please contact your Adobe Account manager.

Identity – We all have one, even Jason Bourne !

Hi All,

The Creative Cloud brings many advantages to Creative Professionals. The applications are as always, the focal point of this value but we have also added tremendous value via the services such as Storage, Behance, Typekit etc. Access to these services has thus far remained elusive for our Creative Cloud Enterprise customers due to the fact that in order to use a service you need to have an identity. Every enterprise is unique in how it implements and manages identities but what is paramount to all enterprises is security. Adobe has been working hard to offer it’s enterprise customers methods of identity implementation that will satisfy all these requirements.

There are two aspects to this.

-The identities themselves

-How the identities are managed

The identities

As you are no doubt aware the topic of identity is a complicated one (Jason Bourne took 2.5 years to learn his) and so the low level details will not be addressed here. What we did however want to do is provide a high level overview of the approach Adobe is taking to enterprise identities. So I asked Terry Ryan (Sr Creative Cloud Evangelist) to work his magic and provide a synopsis of the different types of identities and the use case for each. I think he has done a fantastic job at summarising such a complicated topic.

How identities are managed

A new centralised Adobe Enterprise Dashboard will be used to manage these identities, specify password complexity, control entitlements, download deployment tools and raise support tickets. This will be covered in more detail at a later time but here is a sneak preview.


I am incredibly excited to be sharing this news and I look forward to going in to more detail in the near future.


Karl Gibson | Product Manager | Enterprise IT Tools

Creative Cloud Packager 1.5 is Live

ccp copyccp copyCCP Segment screen

Hi All,

It has been a little while since my last post. That does not mean that I have embraced the dream to retire to some remote island off Fiji or at least spend 6 months out of the year there. A place with no internet connectivity, and just a small shop to get supplies from and make a long distance phone call across a crackled line once a month to touch base with the outside world. I guess this would also mean I would have no need for my pedometer, smart watch, tech glasses, Bluetooth headphones, smart thermostat, smart smoke detector and most distressingly my smart crockpot. On reflection, it seems as though I have invested way too much in technology to ever lead a life of solitude and so with that settled, let’s get on to business.

Some of you will already have noticed that Creative Cloud Packager 1.5 is live and available to download. This release includes several under the hood changes as well as customer facing features.

  • Creative Cloud Packager now supports Value Incentive Program (VIP) for education customers.
  • You can now deploy specific version updates, rather than just the latest updates.

-If a newer update is present in CCP and you wish to deploy and older version of it from some physical media you may do so via the offline media workflow.

  • Creative Cloud Packager also supports packaging non-Creative Cloud apps.

-Creative Cloud Packager will allow customers also entitled to Premiere Elements for Mac, Photoshop Elements for Mac and Technical Communication Suite to package and deploy using Creative Cloud Packager. This is accomplished when you enter a license key for the relevant product in to the packager and we will fetch the product and present it for packaging.

  • Adobe Update Server Setup Tool (AUSST) now supports secure connections (https).

-The product update binaries, however, are still transferred over http.

  • New customer segment Identification screen (as above)
  • Trial License workflow for enterprise renamed to Named License (can still be used for trial)

If you have not updated yet then all you need to do is launch CCP and you will be prompted to update.


Karl Gibson | Product Manager | Enterprise IT Tools

MacIT 2014

Hi All,

Last year Adobe was one of the sponsors of MacIT in SF. It was a great few days and we got to meet and have a chat with some awesome IT admins about the newly introduced Adobe Creative Cloud Offerings and the newest addition to the IT Tools, Creative Cloud Packager. These events are incredibly valuable to us as it gives us a great opportunity to speak with those who use the IT Tools like Creative Cloud Packager, AUSST and RUM on a daily basis. IT admins have always been incredibly generous with their time and knowledge and this has allowed us to steer the IT tools in the right direction up to now and hopefully continuing to do so in to the future.

So with that said I am very happy to announce that Adobe is returning as a sponsor for MacIT 2014. We will be presenting on Thursday 27th March at 1:15pm-1:35pm. Now you are probably thinking one of two things, wait that’s only 20 minutes and I really want to hear what Adobe has to say about Creative Cloud for enterprise and the IT Tools (you won’t be disappointed) or wait that’s only 20 minutes and I really want to give Adobe a piece of my mind, well good news my friends we will also have a booth and so you can pull up a chair and talk to us good or bad for even longer. If we are not at the booth then we are either having lunch , having a beer or being inconspicuous but if you can find us or identify us then feel free to come over and chat (warning please approach slowly, we scare easily and become shy)

Looking forward to seeing you all there.


Karl Gibson | Product Manager | Enterprise IT Tools

Creative Cloud Packager 1.4 is Live

Hi, All

As we enter this period of festivity the thought crossed my mind, what do you get an IT admin for Christmas to say thank you? To me the most obvious gift would be a smart watch, but you know what I have found thus far in my experiments with smart watches, they are not actually terribly smart. It is difficult enough to justify having another piece of technology with you but then you get the dreaded question, “so you can send text messages from the watch?”  or  “can you make phone calls from your watch?” Well, no, I can’t do either of those things, but I can have different watch faces, not bad for $150. Again I digress and so smart watches are not what I would like to give to the IT admin this festive period. Instead, how about a new version of Creative Cloud Packager?

Creative Cloud Packager 1.4 – Features

Package Modification

Quite some time ago in the AAMEE days, you (the IT admin) asked for a way to modify a previously created AAMEE package so you could add applications and updates without needing to create a new package from scratch every time a new update came out. This of course was a great idea and we added this feature to AAMEE. The problem is although this feature was great, we were not able to get it in to Creative Cloud Packager… until now.

In CCP 1.4, you now have the ability to modify a previously created package. You now can add updates, as well as add or remove applications to your existing package. There is a small caveat in that this feature is only possible from CCP 1.4 onwards, so packages created with CCP 1-1.3 cannot be modified.

Support for Physical Media

One of the great features of CCP is the ability to pull the Creative Cloud Applications and Updates directly from the cloud and create a customized package. However, there are some rare instances where the time or bandwidth required to pull down the Creative Cloud applications and updates is not possible or feasible. For this purpose CCP 1.4 will now allow you to create a package from physical media. This means that if you are in a location with poor Internet bandwidth or a locked down environment whereby access to the Internet is only briefly possible, then we would suggest you request physical media and use CCP 1.4 to create a package.

CCP 1.4 Physical Media CCP 1.4 physical media 2

Note: Although CCP supports packaging from physical media, online connectivity is still required to validate licensing information.

How to order physical media

Physical media is granted on an exception only basis. To obtain the media you must contact your Adobe Account Manager or Adobe Support.

CCP 1.4 is live now and you will be prompted to install the next time you launch.

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

Finally I just want to say a big thank you to the IT admin community for all your help this year. I have attended and spoken at many IT events, written on many blogs/forums and have been on conference calls with many of you. Your support, ideas and criticism are very much appreciated.

The CCP team wishes you and your families a great holiday period and we look forward to working with you next year.


Karl Gibson | Product Manager | Enterprise IT Tools

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.


Karl Gibson | Product Manager | Enterprise IT Tools

Creative Cloud Packager 1.3 Pre-Release

Hi All,

We have received great feedback since the Creative Cloud Packager 1.1 release in June and by all accounts it has been a success. That said the AAMEE team (which we should really rebrand to the CCP Team) have never been ones to rest on their laurels so we have been hard at work preparing the next major release. This is where we need your help. We would like to run a limited Pre-Release of CCP 1.3 for existing Creative Cloud for team and Creative Cloud for enterprise customers. This allows us to gather valuable feedback from you the IT admin because as I have said before this is why we do what we do.


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)
  • New Shortcut locations
  • New IT Tools Un-installer
  • Build information in Product UI
  • Support for Auto Proxy Pac files *in final release*


The highest priority has been to add the support for archived versions of products. This is to support Creative Cloud for team and Creative Cloud for enterprise customers who are entitled to the latest and greatest but also archived versions of products. Up until now you could use CCP to package the latest and greatest but what if you also wanted to deploy a previous version of Photoshop for example? In this scenario as it currently stands you would need to download AAMEE, point it at the CS6 media and create a separate package. This new release streamlines the entire process by allowing you to create a CCP package that contains the latest and greatest in addition to any archived versions you would like to select.


ccp 1.3 archive

Pre-Requisites for Pre-Release

Open for Existing Creative Cloud for team customers

Open for Existing Creative Cloud for enterprise customers


How long is the Pre-Release running for 

The Pre-Release will run for around 3 weeks however we do have a threshold in terms of how many users we will be able to add. So please don’t take it personally if you do not get a response from us as chances are we have reached our quota.


How to apply

If you are an existing Creative Cloud Team or Creative Cloud Enterprise customers. I would ask that you please go to the following link and provide the required information.





Karl Gibson | Product Manager | Enterprise IT Tools


Creative Cloud Packager 1.1 – A big week for CC Team & Enterprise customers

Hi All,

There has been many big days in my life but very few big weeks. Perhaps the week I got married and the week I went to Disneyland (not the same week) but this week must also be up there. On Monday 17/06 Adobe released it’s brand new Creative Cloud branded applications. Which I must say are extremely impressive with lots and lots of new features. On Tuesday 18/06 we realised that as a result of the changes on Monday there was an issue with Creative Cloud Packager 1.0 which was preventing package creation.  Ooops this was obviously not intended. However stay with me we have a fix.

We are now on Wednesday ,  which also happens to be my favourite day of the week, just in case that comes up in the Karl Gibson trivia quiz at your local bar. Today we are going to release Creative Cloud Packager 1.1. for our Creative Cloud Team customers.

Fear not Creative Cloud Enterprise customers we have not forgotten you. The great and really exciting news is that Creative Cloud Packager 1.1 will also be available for you. Since we released Creative Cloud Packager 1.0 in April for Creative Cloud Team customers the feedback has been overwhelmingly favourable. With this in mind it was really important to us that Creative Cloud Enterprise customers also have this this experience when it came time to packaging the new Creative Cloud applications & updates. Here is the breakdown of Creative Cloud Packager Features


  • Downloads applications & updates directly from Adobe’s Creative Cloud- No physical media/ LWS downloads
  • Create customised packages containing just the applications you wish to deploy.
  • Support for Feature Bearing updates- Updates are broken up in to Feature bearing & regular updates. IT admin can choose which they want to package.
  • Creative Cloud allows you to select the locale you wish to create packages with
  • Ability to modify update behaviour of client applications
  • Ability to disable or enable Creative Cloud Desktop Application.
  • Caching of Applications and updates to save bandwidth- Ability to change where cache is located.
  • CCP offers in app updating. When a new version is detected you are asked if you want to update.


CCP 1.1 Sign In

CCP 1.1 Application Screen


How do you get Creative Cloud Packager 1.1 ?

Creative Cloud Team customers

CCP 1.1 is now live. if you already have CCP 1.0 then when you next open or launch the application you will be prompted to install an update.

CCP Update screen


If you do not already have CCP then you can go to the Team admin portal creative.adobe.com and sign in with your Team admin ID and you will see a deployment section on the right hand side. You can download CCP 1.1 from here.

CCP admin portal link


Creative Cloud Enterprise Customers

On June 21st we will be making Creative Cloud Packager 1.1 available on Adobe’s Licensing Website (LWS) licensing.adobe.com In the past when you have signed in to LWS you would see a list of all the applications. This has now been replaced and you will see only Creative Cloud Packager 1.1,  your License Key and a handful of applications CCP cannot currently package. These include Edge Code, Reflow, Scout and Gaming SDK.

Note although we are making CCP 1.1 live on LWS on the 21st it does take time to replicate on peoples LWS account.


The Roadmap

I am incredibly proud of the work the Team has done on Creative Cloud Packager. By downloading the applications & updates directly from the cloud we are removing a massive headache from the IT admin and also as you can see from the above there is lots of other great features. This is just the beginning however. We have lots of plans in store for CCP. As the Creative Cloud evolves the Creative Cloud Packager will also evolve and offer greater customisation of the services the Creative Cloud offers. Also top of our To Do list is to add support for packing of archived versions. As of right now if the IT admin for a Team or Enterprise need to package previous versions i.e CS6 they need to use AAMEE 3.1. This is something we are looking to remedy.

One more thing

Yes I did the one more thing……..thing

With Creative Cloud Packager we have included a new version of the Adobe Update Server Setup Tool (AUSST 3.0) the new version offers significant performance improvement and we have also made AUSST proxy aware and so you can now use AUSST even if you are behind a proxy. AUSST is included in the Creative Cloud Packager build.  We are also making AUSST 3.0 available on the Devnet site for those who are still pondering the Creative Cloud but want to take advantage of the new features, please keep an eye out over the next few days.

Help Page

The Creative Cloud Packager Help Page is located here




Karl Gibson

Product Manager | Enterprise IT Tools

Top 5 Myths of Creative Cloud ***IT Edition***

I’ve been retired from blogging for almost six months, which in Internet Years is like six millennia. This whole post should be simply a Vine clip, right? You probably missed my retirement party when I retired from blogging. The guys all chipped in on a gold-toned watch. The inscription on the back “Did you notice the green squiggly lines?” was particularly touching.

What could draw me out of retirement? The fame? The money? Well seeing how I saw neither of those while I was blogging I’d have to say no. It was actually a blog post that my esteemed and ridiculously talented co-worker Terry White wrote entitled “5 Myths About Adobe Creative Cloud” a couple of months ago.

It is a good post, and features a photo of Nessie, the famed cryptid from Scotland. Which instantly makes me think of the show “In Search Of” which I loved as I child and honestly, creeped me out as well. Myths about Bigfoot or UFOs are still cool in my book, but myths about products…not so much. I always considered myself more Mulder than Scully but here I am dispelling myths, shining my over-powered flashlight on the the dark shadows of misinformation and confusion that IT have about the Creative Cloud.

1) Creative Cloud is virtualized or streamed

Wait, isn’t that pretty much the same as Terry’s #1 myth “I don’t want to run my Applications in a web browser!”??? Yes, but mine is phrased slightly differently, which in the world of blogging is legit. Seriously though, this gets brought up continually and it is worth mentioning again that the Creative Cloud is a new method of distributing our creative desktop applications but they are still applications that are installed and run the old school way. They still take up GBs of your hard drive. Oh wait, I wasn’t supposed to highlight that fact. Shrug. But you get it. Our beefy products like Photoshop work best installed on systems with lots of RAM and a modern GPU. Now, it has to be stated that virtualization technology is rapidly evolving and advancements like virtualization of the GPU is just plain awesome. But, the Creative Cloud at present remains a way to download the software from the Cloud, not run the applications in a browser or thin client.

2) Creative Cloud can’t be deployed

What? After spending the last 3-4 years trying to do right by the IT community by making packaging tools like AAMEE, licensing tools like APTEE, and updating solutions like AUSST and RUM do you really think we’d roll out a major offering and forget about the IT deployment infrastructure your organization has invested in? Seriously?

Now let me explain, briefly, that we have three different types of the Creative Cloud and I believe some of the misconceptions about deployment have been rooted in the lack of clarity about the different types of the Creative Cloud. If you are an individual, a freelance designer or one-person video production shop, then you can buy the Creative Cloud for individuals. They are admins on their systems. They are their own IT, Procurement, Accounting, etc. No deployment needed, obviously.

Now the next offering is tailored for small businesses or small groups within a large organization, they might want to look at Creative Cloud for teams. An ideal number of folks would be like 5 to 30. Let’s say it is a small game developer that buys 25 seats of Creative Cloud for teams, and they have an IT guy who has setup a deployment solution to manage their Macs. The IT admin would log into the Creative Cloud for teams admin portal on the Creative Cloud website and they see an interface for inviting Team members via email. They’ll also see a Deployment section and they’ll be able to download the new Creative Cloud Packager 1.0. This new tool allows the IT admin to download the Creative Cloud desktop applications and their updates and package them. So unlike AAMEE, it doesn’t point to locally downloaded media like the ginormous Master Collection but rather the IT admin can cherry pick applications they want to download to package. See, better! I’d like to take credit for this but I am no longer over the IT tools, so hats off to Karl Gibson and the crew formally known as the “AAMEE crew!”

A 1.1 version of the Creative Cloud Packager is due shortly after the new set of Creative Cloud applications are released next month. The 1.1 version will work for both Creative Cloud for teams and for Creative Cloud for enterprise. The Creative Cloud for enterprise is the third type of the Creative Cloud and is meant for larger institutions who need higher levels of control.

3) Organizations can’t control the frequent updates

One of the coolest parts of the Creative Cloud is that we are no longer waiting for annual or 18 month cycles to get new functionality from the products. If the engineers have a cool new feature in Illustrator they release it to the Creative Cloud members as soon as it has gone through the regular QE process. That team doesn’t have to wait for a year to have it be a part of a new boxed copy of the Creative Suite or wait for a marketing event. Nope, bam! Into the hands of their users straight away. Sounds great for individuals or people in design studios with mohawks right? But what about my enterprise production environment? What about my strict policy of evaluating all updates before they are released? Nothing changes. The updates are available via the Creative Cloud Packager and can be packaged at the IT admin’s discretion. Same level of control.

4) Adobe IDs aren’t for us

The way the Creative Cloud for individuals and teams versions work is that the applications, services and storage use a licensing/authentication process that involves an Adobe ID. For Creative Cloud for teams we have an admin portal that allows the IT admin or production manager the ability to send out email invites and those users have to create Adobe IDs in order to sign into the Creative Cloud (i.e. the applications or at creative.adobe.com.) The end users who are using Creative Cloud for teams have to obviously be online to authenticate with their Adobe IDs. Now that is the Creative Cloud for teams which stated above is ideal for small organizations.

Frankly, this doesn’t scale for large organizations for hundreds or thousands of users. It doesn’t work for organizations like video production places with offline workstations. Larger organizations want to use their own identity systems (like Active Directory or LDAP) and do not want to use Adobe IDs to identify their organization’s users who have access to the Creative Cloud. Of course. This is why the Creative Cloud for enterprise offering has this in mind. Presently if you purchase Creative Cloud for enterprise then the IT admin has the same flexibly to package and deploy the creative desktop applications without use of Adobe IDs. What? Yep. How are the applications licensed? A contract-defined expiring serial number. A serial number? Boring, right? Old school. Status quo. Status Quo.

Now there are a lot of great aspects of the Creative Cloud that go beyond just the core applications. It is essential that we provide this functionality to our enterprise customers. We are working on the ability for your organization to control login into the Creative Cloud using your authentication infrastructure by using Single Sign-On authentication via SAML 2.0. This will allow for the use of the cloud functionality including storage and services. I’ll come back and do an entire blog that outlines our strategy around supporting SSO and will separately write an entry explaining all the advantages you and your users will have once they are signing into the Creative Cloud for enterprise. Some really cool stuff. Are we aware that not every enterprise customer is ready to support SSO or use a different authentication method? Yes. Will we support other methods of authentication down the road? Yes. But we are presently working on Single Sign-On authentication via SAML 2.0 as a foundation of our authentication strategy.

5) Cloud storage isn’t for us, so neither is Creative Cloud

I have saved one of the most contentious myths for the end. First, there are always concerns from IT about files stored in the cloud and rightfully so. The “Adobe Creative Cloud Security FAQ for IT” doc covers a good portion of questions you or your organization might have about our cloud storage aspect of the Creative Cloud.

And for every CIO, CTO, or IT admin who tells me they are shrinking their data center and using more cloud services there is always a set of IT folks who tell me the opposite: My user’s data will never be in the cloud. To that I say: okay. No fight here. Seriously. You can’t turn off the cloud storage component for the Creative Cloud for teams, but there are ways of course for IT to control traffic and block ports. These are documented in the “Adobe Creative Cloud Network Endpoints”  and “Controlling Access to Adobe Creative Cloud Services” docs.

And restricting storage access is certainly an option for the Creative Cloud for enterprise. Presently there is no identity login component for the Creative Cloud for enterprise so hence no accessibility to the cloud storage. When your organization begins to have access to the Creative Cloud via SSO then the IT admin will have access to an admin panel which will include granular levels of control over who has access to what applications, services and storage. Want to turn off storage? Okay. Want to give more storage to the marketing group. Okay. High levels of control for IT, is at the heart of my personal vision of the Creative Cloud for enterprise.

We’ll be more than happy to squash some more myths and answer questions in the comments. Or we can discuss who would win in a fight between Chupacabra or Moth Man. Your call.

Jody Rodgers | Sr. Product Manager | Creative Cloud for enterprise