Skip to main content
R
RH75_2
Participating Frequently
July 13, 2016
Answered

Adobe Acrobat DC via CCP - continuous or classic track?

  • July 13, 2016
  • 2 replies
  • 1704 views

What track of Adobe Acrobat DC is used when creating a package via the Creative Cloud Packager - continuous or classic? Is it dependent on the license used? We would like to use the 'classic' track as it is a better fit for our environment and the way we deploy updates.

Thanks!

-Rob

This topic has been closed for replies.
Correct answer AnkitTech101

Hi Rob,

You are right in your approach about deploying Acrobat DC. It has to be a stand alone package for DC including the .mst and then deploying the rest of the CC Apps through a package created by Creative Cloud packager.

Also, the update patches would have to be packaged separately as and when updates are rolled out for the product.

So yes, it all sounds like you are following the right approach towards the deployment of the CC Apps + Acrobat Classic.

Regards

2 replies

AnkitTech101
Adobe Employee
AnkitTech101Correct answer
Adobe Employee
July 17, 2016

Hi Rob,

You are right in your approach about deploying Acrobat DC. It has to be a stand alone package for DC including the .mst and then deploying the rest of the CC Apps through a package created by Creative Cloud packager.

Also, the update patches would have to be packaged separately as and when updates are rolled out for the product.

So yes, it all sounds like you are following the right approach towards the deployment of the CC Apps + Acrobat Classic.

Regards

R
RH75_2Author
Participating Frequently
August 4, 2016

Thank you ankising, this appears to be working as described. Appreciate the help!

AnkitTech101
Adobe Employee
AnkitTech101
Adobe Employee
July 13, 2016

Hi Rob,

If you are creating a named user package for Acrobat using Creative Cloud Packager, it creates a package for the Continuos track.

If you wish to deploy it as Classic, you would have to use your Acrobat serial number from the licensing website and use the customization wizard to package it. Instruction for it are mentioned in the below article:

Welcome to the Wizard — Acrobat Customization Wizard DC for Windows

Hope this helps

R
RH75_2Author
Participating Frequently
July 14, 2016

Hi ankising,

Thank you for your reply - that is what I was thinking we would have to do - though I should've provided more detail in my original message.

We are creating Serial Based packages for all of our Adobe apps/bundles created via CCP. We are creating a 'Creative Cloud Enterprise' package that will be a big bundle of apps, then also individual stand-alone apps, such as Acrobat, Photoshop, etc. We are using SCCM as our deployment tool.

For the 'classic' track, I'm thinking for the 'Creative Cloud Enterprise' bundle we will have to deploy Acrobat Pro DC stand-alone app first as a separate package (using an MST via the Customization Wizard), then deploy the bundle (which will not have Acrobat Pro DC included because of classic track).


Our deployment would look something like the following...
Adobe Acrobat Pro DC (stand-alone app) + Bundled Apps = 'Creative Cloud Enterprise' bundle

(This is how we are currently deploying Acrobat Pro XI along with the bundle, but I was hoping that with the new CCP we could bundle them all together using the classic track method.)

When it comes time to apply security patches/updates, we would then create an update for Acrobat Pro, and a separate update for the bundled apps, which could then be deployed via SCCM.

Does that sound reasonable considering the track we have to use?

Thanks again,

-Rob

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices