Adobe Systems Incorporated

Adobe Installation and Licensing

Blog to post all Installer and Licensing related info to users of Adobe products

Jul 21, 2015

Major Milestone- Cloud Packaging has arrived

Hi All,

Lately posts have been a little thin. This past year the team has been heads down, focused on a new initiative that I’m excited to share with you.

History

As many may know, Adobe has used its own installer technology called RIBS for the past several years. RIBS was created to bind the individual products together when we first released Creative Suite and the technology is still used in todays Creative Cloud products.

We realize RIBS is not ideal for enterprise workflows and in order to deploy the software you are required to use either Creative Cloud Packager or it’s predecessor AAMEE. While those products offer features beyond their core competency of converting from RIBS to native installer such as the ability to specify update behaviour, pre-serialise, create update packages and license files, it is still an additional step IT need to take.  Also in order to use CCP, you need both Mac and a Windows systems clean of other Adobe software and network connectivity, requiring IT to open firewall ports.

The Change

Now, Adobe will pre-populate packages for Creative Cloud for enterprise customers. When a user logs into the Adobe Enterprise Dashboard, they will go through the following process

overview

Adobe entitlements are detected and packages will be created automatically,

created automatically

When you select packages you can filter by “created automatically

These Pre-Created packages will leverage the default and most common settings. Users can change certain settings such as language, update behaviour and for Windows, bit architecture,

Once satisfied with the packages and settings select “build”

confirmation

build

The system will start building and downloading packages

download copy

It’s as simple as that !

Users can also, delete packages and can filter by package creator.

Future

The question I am sure that will arise is, why doesn’t Adobe just use native installers  ?. It is a very valid question. As i mentioned RIBS allows you to deploy multiple products in the same binary but other advantages are limited to Adobe itself. This is changing and in the not so distant future I will go in to more detail about the changes that are being made to the RIBS installers to increase the benefit to end users.

The Team

Finally (I know long post) I was in Noida nearly two years ago when we sat down as a team and discussed this new direction. We discussed the pain points and how we could remove the packaging step for IT admins. Since then the team have worked tirelessly to make this a reality. We have many features still to implement to get this where we want but as a 2.0 release this is a huge step and I want to publicly thank each member of the team who worked crazy hours and put up with my stress levels.

Now the real question is, if you have a big launch at 6am is it too early for a celebration beer ?

Video Walkthrough

Cheers

Karl Gibson | Product Manager | Enterprise IT Tools

Creative Cloud, Deployment Tips, Uncategorized, Updates

Comments

  • By John Welch - 3:44 AM on July 22, 2015   Reply

    Woohoo!

    Awesome news y’all!

  • By Anthony Reimer - 8:54 AM on July 22, 2015   Reply

    It’s important that people watch the video. If you use serialized licenses, you must continue to use CCP. Only “named” licensing can use this new tool.

  • By Shane Palmer - 8:35 AM on July 30, 2015   Reply

    My first question is why can’t this be used for serialized deployments? The followup question is will that ability be added soon?

    I really look forward to posts that expand on your comments regarding the future of native installers. I really appreciate everything your team has done to make it easier to deploy Adobe products in the Enterprise, but I have always wondered why waste time on building tools to convert from one installer to another when you could have spent the last four or five years getting your application developer workflows aligned with producing native installers in the first place instead of spending that time on AAMEE/CCP.

    • By Karl Gibson - 11:46 AM on July 30, 2015   Reply

      Hi Shane,
      You raise quite obviously perfectly valid points. The ability to use this functionality for serial deployments will come it was just from an architecture perspective easier to support just named license first and I wanted to get this functionality out there as quick as possible and start getting feedback.

      Regarding native installers. Yes I agree the community would like to see us just have native installers but there is a lot of products heavily invested in the current technology and it also allows for an uber package or a package of just the apps you want. Outside of that as I mentioned there will be significant improvements that will benefit end users. One such benefit is Multi language installers whereby you don’t need to create one installer per language. I will post about more benefits in time.

      Cheers
      Karl Gibson | Product Manager | Enterprise IT Tools

  • By BW~Merlin - 5:37 PM on November 18, 2015   Reply

    The documentation in the exceptions folder needs to be updated. I have just finished making a new package of Master Collection and included Adobe Acrobat DC which installs very differently to Adobe Acrobat Pro (Pro uses the exceptions deployer while DC use command line switches which I had to Google to find). If the documentations about the exceptions folder mentions nothing about how Adobe Acrobat DC needs to be installed differently.

Add a comment