There are a number of changes within Adobe’s licensing metric for Adobe Creative Cloud, and they have re-organised the software bundles. We have posted a number of documents and licensing guides for Adobe Creative Cloud, including Adobe Licensing Quick Guide 2014, Creative Cloud – A look into the crystal ball and The Pros and Cons of Adobe Creative Cloud.
Hopefully you have read the articles mentioned above, so you should be familiar with Adobe Creative Cloud. This isn’t a cloud application, you still need to install and deploy the software on machines, merely the updates and patches are provided by Adobe through the cloud, plus they allow each user a set amount of cloud storage (based on your contract).
There are a number of steps that each organisation needs to go through when upgrading to Adobe’s Creative Cloud. The following hints and tips are based on my experiences with Adobe CC, and what happened when I helped an organisation migrate to the new software and license metrics.
Firstly, you need some sort of discovery or SAM tool in place to see what current Adobe products are installed within your estate. Secondly, 3 months worth of reliable usage stats are then required to ensure you have trusted data in deciding which users should have which licenses moving forward.
There are a number of stages that you need to go through when identifying CC licenses for your users:
Whilst we have summarised the process down into 5 stages, it is a long and complex task (time and complexity obviously depends on the size of your organisation!). It took months for me to do the above work for a 16,000-seat organisation, with a lot of collaboration with users and deployment staff. I relied heavily on a SAM tool to look at current installs and usage before defining the new licenses that each user should have, and it took a lot of cross referencing between the old Adobe bundles and the new bundles to ensure everyone got the Adobe applications that they required.
Adobe Creative Cloud comes with ‘AdobeID’ logins for each user. The license assigned to the user is attached to their AdobeID login details, and also relates to the personal storage that they are allowed to use. Furthermore, the AdobeID allows users to access their Adobe software from other machines (other than their own) but logging on using their AdobeID details. Remember, this is allowed as the licensing is now by user and not device, although users are limited to installing/using Adobe software on up to 5 machines.
In essence, like Microsoft, this means that users can use their work AdobeID for using Adobe products at home. Organisations need to have a process in place for managing this to ensure that any leavers can no longer access software provided by the organisation. Incorporating the closure of an AdobeID account should be part of the leaver’s process.
Furthermore, whilst upgrading users to Adobe CC I encountered a number of problems in relation to firewall issues and allowing our security systems to automatically update CC applications. You may have to talk to your security team to ensure that Adobe CC has all of the accesses and rights it needs to access ‘cloud’ based services.
The deployment process is the same as previous versions of Adobe as a local installer still needs to be deployed to computers. The ‘cloud’ element in relation to the actual software is that some updates and patches can be pushed to machines via the cloud, however as we will mention in due course, the ‘major’ updates or releases will need to be re-packaged and re-deployed by an organisations packing and deployment team.
At the time in which I was upgrading to CC, Adobe could not give us a schedule for updates or patches. This may have changed, but at the time it was a pain for our packaging team. Deciding when to update and repackage ended up being a bit of a gamble, and we had to assess the time it would take to repackage and redeploy the updated versions of the software against that value add that the updates would have on our users.
We have conducted some research and still cannot find a diary or schedule online that provides dates and details of the coming years updates and patches for Adobe Creative Cloud. Customers may be able to get hold of some sort of rough schedule, but it is not out there in the public domain. We would suggest that CC organisations create their own diary for packaging updates for CC. So, for example, set a 3 or 6-month time scale for each update, so the packaging guys will package the latest version at that point in time, regardless of what is to be released by Adobe over the next few weeks. Until Adobe provides more and better quality information, we don’t see any other way for planning Adobe CC updates.
It depends on your organisation and how much you rely on Adobe products. If you want the latest versions of Adobe products and security patches and regular updates then yes, you should upgrade. However, if you were open to alternative software vendors then I would look around for a cheaper alternative that will work for your organisation.
There are a number of PDF creators and writers on the market, and there are a number of photo and video editing software. It’s the more bespoke applications that finding an alternative could cause some issues. The likes of Muse, Fireworks, InDesign and Dreamweaver are pretty unique to Adobe, so if your organisation are heavy users of applications like the above than it may be best for you to move to Creative Cloud.
Do you have experience in upgrading to Adobe’s Creative Cloud? If so, please leave a comment below to share your opinions on the best way to upgrade to Adobe’s (reasonably) new licensing model and software bundles.