I can create deployment packages for all apps on Win and OSX.. Only Windows Acrobat Pro does not install.

Report · Nov 12, 2015

I can create deployment packages for all apps on Win and OSX.. Only Windows Acrobat DC Pro does not install. redownloaded and created package on two different machines (both 32/64 bit)

Tried install on Win 8.1 win 7

no error messages...just progress bar during install then exits

other packages created install fine

Report · Nov 12, 2015

Moving the discussion to Deployment for Creative Cloud Team, Enterprise, & CS

Report · Nov 13, 2015

In this context Acrobat is an 'exception'

Acrobat DC should be installed first, with the following command.

Setup.exe /sALL /extUI /sl "[installLanguage]" /msi INSTALLDIR="" EULA_ACCEPT="NO" SUITEMODE=1 OWNERSHIP_STATE=1 LANG_LIST="[installLanguage]" INSTALLLEVEL=101 AS_DISABLE_LEGACY_COLOR=1 IGNOREAAM=1

See our documentation for further details.

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

Report · Nov 13, 2015

Thank you....I wonder why this app is different from the rest....I did all the app we needed as sep deployments so we can pick and choose...and this was the only one I couldn't use the main setup.exe

Report · Nov 13, 2015

I did the above command line...along with using the Acrobat Customization tool....still getting the EULA prompt and asking user to login to Adobe ID

Report · Nov 16, 2015

OK, to include the mst you would need to do this:

msiexec /i <path\AcroPro.msi> TRANSFORMS="AcroPro.mst"

You can find full documentation around these command line options at http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/cmdline.html

Report · Nov 23, 2015

Ok...getting confused....been using SCCM and been deploying software for years, using custom transforms via msiexec command line... This is the first I've used the Adobe CC deployment tool. And so far using that and the Adobe Acrobat Customization Tool I deployed the Reader no problem, with no EULA, no Key request or prompts for Adobe ID...but by running the setup.exe which uses the setup.ini settings.not a msiexec command line...did the same for doing each app individually (photoshop, etc) worked fine, no prompts....the only exception was the Full Adobe Acrobat...which this forum told me to use the exceptions folder.

initially the first suggestion from here was to use this on the exceptions setup:

Setup.exe" /sALL /extUI /sl "en_US" /msi INSTALLDIR="" EULA_ACCEPT="NO" SUITEMODE=1 OWNERSHIP_STATE=1 LANG_LIST="en_US" INSTALLLEVEL=101 AS_DISABLE_LEGACY_COLOR=1 IGNOREAAM=1

doesn't install the msp files...and I still get the EULA, and request to login with Adobe ID... (i selected to bypass them in deployment tool just like the other apps) We are K-12, have a full district license, kids should not be using the Adobe cloud.

So I did the same process I did on the CC Reader, used ACT after the deployment tool to further costimezie, as per the whitepaper. to select and bypass all online resources and EULA...etc.. and run the setup, which uses the setup.ini file.... I get farther this way, but still asks for Adobe ID login, and sometimes asks for Key, even though I selected to disable all that in ACT.

Report · Nov 24, 2015

So,

The setup.exe route should work and is our recommended way to do this. When you save your .mst from customization wizard it enters a line in the setup.ine to run the transform.

Another option is to run the APTEE tool to re-apply the serial number.

https://helpx.adobe.com/creative-cloud/packager/provisioning-toolkit-enterprise.html

Report · Nov 30, 2015

yes the CmdLine=TRANSFORMS="AcroPro.mst" is there.....I will try the APTEE tool