Posted on 05-31-2012 12:58 PM
From the "Administering Adobe Creative Suite 6 with the Casper Suite" white paper:
"JAMF Software makes the following recommendations for deployment packages:
If you plan to deploy Acrobat® Pro X, include it in a package with other CS6 products instead of deploying it separately."
Does anyone have experience with the reasons for this? We have a separate, customized pkg already created for Acrobat Pro X (from its release last year), and I was able to successfully deploy it with our AAMEE-created CS6 installer (which does not contain Acrobat Pro X). No problems so far with them separate, so just curious if there's a specific reason they suggest against this.
Thanks for any insight.
Posted on 05-31-2012 01:07 PM
My guess is JAMF recommends deploying with CS6 because deploying with a suite is easier and maintaining one license is easier than maintaining two.
Deploying Acrobat X standalone means having to enter its serial number manually or use the Acrobat provisioning toolkit to do it for you. Using the toolkit requires you to devise your own method for deployment. Using AAMEE doesn't.
Technically, nothing stops you from doing what you're doing.
Posted on 05-31-2012 02:04 PM
All together or having to use a script to serialize your CS Suite
up to you