My understanding is you no longer have to use a preinstall and can just run setup.exe from the command line (which there are 2 Btw, but this example implies use of the setup.exe from the exceptions folder, in which case why is there even another folder? I have tried both and neither work.
This is the information I can find about installing Acrobat DC in SCCM using the CCP.
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
Path of setup.exe:
<Package Location>\Exceptions\APRO12.0.0en_US\Adobe Acrobat\Setup.exe
So...
1. I create the 64- bit package in CCP and have two folders - build and exceptions
2. I create a package in SCCM as usual and run setup.exe from the command line from this path: Exceptions\APRO15.0en_US\Adobe Acrobat
When I run a test from the command line my application install stops and asks for a serial number. ( I already entered that when I created the package). Moreover, the number it is asking for is different than the CCP serial number I use to create the package. Do I need two serial numbers, one to use in CCP and put one in the Abcpy.ini file?
So, this procedure appears not to work and I am stumped.
Can someone correct me if I am doing it wrong? Also, where are the variables from the setup.exe command above documented?