Skip to main content
Marist-Sion
Participant
October 6, 2016
Answered

Acrobat DC Being Removed

  • October 6, 2016
  • 1 reply
  • 395 views

Hi,

We've created a package in CCP, we've deployed this previously with no issues. What we're seeing now and it could be the newer build of Windows 10 is that Acrobat DC will install, the other suite applications Photoshop, Dreamweaver etc will install and then after that Acrobat DC will remove itself. The other suite applications remain. The package was created in May and we didn't have the problem then.

We've recreated the package and are going to test that.

Anybody else seen this before?

Thanks

Ben

This topic is closed to new replies. Start a new post to keep the conversation going.
Correct answer Doug Hanna

To answer your question - Yes, and no...

Keep in mind that Acrobat uses a separate installer system from the rest of the CC tools.  I know that the rest of CC is working towards the same robust installer tooling that Acrobat has, but they aren't quite there yet.

What I might suggest is to to create two - separate - independent - packages.  One for the CC tools (they tend to install happily together), and a the other for Acrobat using the enterprise deployment tools.  Then chain them together in in the back-end CCP tools.

Why keep a separate installer for Acrobat?

  • Acrobat has different & deeper OS integration than the other CC tools.  Fonts, printer/spooler subsystem, Office, IE, Chrome, FireFox, Explorer, etc. (Some is in HKLM, some is in HKCU)
  • Acrobat is on a different release cycle from CC.
  • Acrobat has different enterprise deployment tooling from CC.

Where do I find these magic Acrobat/Reader deployment bits... Acrobat-Reader Enterprise Toolkit Home

Good luck with your efforts.

Doug

1 reply

Doug Hanna
Doug HannaCorrect answer
Inspiring
October 6, 2016

To answer your question - Yes, and no...

Keep in mind that Acrobat uses a separate installer system from the rest of the CC tools.  I know that the rest of CC is working towards the same robust installer tooling that Acrobat has, but they aren't quite there yet.

What I might suggest is to to create two - separate - independent - packages.  One for the CC tools (they tend to install happily together), and a the other for Acrobat using the enterprise deployment tools.  Then chain them together in in the back-end CCP tools.

Why keep a separate installer for Acrobat?

  • Acrobat has different & deeper OS integration than the other CC tools.  Fonts, printer/spooler subsystem, Office, IE, Chrome, FireFox, Explorer, etc. (Some is in HKLM, some is in HKCU)
  • Acrobat is on a different release cycle from CC.
  • Acrobat has different enterprise deployment tooling from CC.

Where do I find these magic Acrobat/Reader deployment bits... Acrobat-Reader Enterprise Toolkit Home

Good luck with your efforts.

Doug