Best practice to deploy adobe creative cloud over network

[ThePhoenixSaga]

Hi

 

School has recently purchased some adobe creative cloud software, and I wanted to know what is the best way to deploy the program over multiple computers on the network. I have looked around, but haven't found anything useful yet.

 

Also, I am having difficulty deploying adobe acrobat, is anyone else having the same issue, and is there a solution to for it?

 

Additional:

By the way we have already set up the software in the packager, we just wanted to know the best way to deploy it.

Edited May 22, 2015 by ThePhoenixSaga
forgot to add something

[Norphy]

What do you use to deploy software at the moment? Group Policies? SCCM? Something else?

 

Personally, because it's so hilariously huge, takes such a long time to install and is required everywhere anyway, I put it into my main Windows image and deploy it that way.

 

Acrobat is installed using the exception deployer which is the Exceptions folder in your deployment. If you're deploying Acrobat DC (and I don't see why you wouldn't be), run the following command:

 

exceptiondeployer.exe --workflow=install --mode=post

[ThePhoenixSaga]

We use group policy

[Brimstone]

Have a look here...

 

https://helpx.adobe.com/creative-cloud/packager.html#

[ThePhoenixSaga]

We created the package using the creative cloud packager. We was unaware that adobe reader went into the exception folder. Running the above command has worked.

 

Thank you

[Arthur]

If you're deploying Acrobat DC (and I don't see why you wouldn't be), run the following command:

 

exceptiondeployer.exe --workflow=install --mode=post

You don't need to run exceptiondeployer.exe for Acrobat DC though.

 

For Acrobat DC, Exception Deployer Application is not required. For Acrobat DC, you only need to run the setup.exe, which ensures Acrobat DC is installed. However, for the EULA, registration, and updates suppression on client, you need to run the main CCP package msi after running the Acrobat DC setup.exe.

 

However you need to run Exception deployer in post mode, if there are other application (except Acrobat DC) in the Exceptions folder of win package. (Source)

 

^ IIRC, Lightroom CC doesn't have an Exceptions folder either now.

[Arthur]

We created the package using the creative cloud packager.

Did you run both Setup EXEs in the correct order?

 

http://vgy.me/SjNiE8.png

 

We was unaware that adobe reader went into the exception folder.

Adobe Reader doesn't.