Deploying Acrobat CC through SCCM?

[agarabaghi]

has anyone managed to deploy Acrobat with SCCM using the new creative cloud packager?

 

It seems like you would need to run

 

Exceptions\ExceptionDeployer.exe --workflow=install --mode=pre

 

and then run

 

Build\setup.exe

 

Im kinda confused how to build said package in SCCM? could i make a cmd file with the install triggers?

 

something like install.cmd:

 

%~dp0exceptions\ExceptionDeployer.exe --workflow=install --mode=pro

%~dp0Build\setup.exe

 

would something like that work in SCCM?

 

Thanks

[Norphy]

You could do it like that. The way I did it was to create two applications, one for Acrobat and one for the rest of the suite. Make the creative cloud suite package depend on the Acrobat package and deploy the CC suite package. The computer will detect that Acrobat isn't installed, install that before CC then install CC.

 

Alternatively, forget the whole stupid thing and download Acrobat as a separate package from the Adobe license site and customise it using the Adobe Customisation Wizard. I've personally found that to be the better approach because you can do things like suppress the EULA and roll updates into the package.

[agarabaghi]

Thanks for your reply...

 

I did try the 2nd method, I used creative cloud packager to download only adobe acrobat using the acrobat key. Then i used the Acrobat customization wizard, set it to silent, add the acrobat product key, and supress reboots. Created the .mst and saved the package.

 

In SCCM i created a new application, pointed it to the .msi in the exceptions folder using the xxx.msi TRANSFORMS=acropro.mst /qn

 

Deployed it to the device collection as a required software, but as soon as a user logs into the machine and launches acrobat, it says please sign in to use the trial.

[SHimmer45]

i havent used SCCM for adobe acrobat but im sure you still need to use the adobe deployment toolkit (adobeprtk) to activate and turn off prompts for keys/logins

this was the case with CS6 and even since CS4 they still make deplying the product painful imo

[agarabaghi]

We ended up doing it like the 1st response mentioned. We made 2 packages, 1 for Master Collection CC 2014 and 1 for adobe acrobat CC 2014. We pushed the MC package with a dependency that Adobe Acobat must be install prior.

 

All the licensing seems to be in order now... kind of a pain but it works now.