At our institution, we have separate license agreements for Adobe CC (via an ETLA) and Acrobat Pro. We have many more Acro Pro seats purchased than we do CC seats and have separate serial numbers for CC and Acrobat Pro. We learned that we are eligible now to start deploying Acrobat Pro DC to our users.
Though Adobe has updated the Acrobat Customization Wizard for DC, the current deployment documentation (Creative Cloud Help | Deploying Adobe Acrobat) says that we need to use command line syntax with setup.exe rather than msi.exe. However, setup.exe does not include syntax to point to our transform mst file with the Acrobat license key. The document instructs us to use the Creative Cloud Packager to build an Exceptions package with Acrobat. Entering our Acrobat DC license key actually seems to have "broken" CCP, it only lists "Core Components" as an available install, even when we restart and use our CC license key.
The question is how do we build pre-licensed Acrobat DC packages (Win and Mac) using our separate license key and the available tools (CCP, Customization Wizard)? This circumstance does not seem to be covered in your documentation. I'm apparently going to have to put in a separate ticket for our new CCP problem, as well.
Thanks,
Ric