Sign up today to participate, stay informed, earn points and establish a reputation for yourself!Sign up! or login
The full suite is divided in 2 parts :
In SCCM 2012 I created 3 Software :
ExceptionDeployer.exe --workflow=install --mode=pre
ExceptionDeployer.exe --workflow=install --mode=post
Then I created the following dependencies:
Creative Exceptions post -> Creative Cloud -> Acrobat Pro Update 3 -> Creative Exceptions Pre
I published only the Creative Exceptions post deployment type on the catalogue
The client will install
I hope this will help, in the future Adobe should (will ?) include all CC software as part of the bundle so all exceptions should disappear (except Acrobat XI which will always stays separated I'm afraid )
This is for enterprise licenses only!
Create the Adobe Creative Cloud package with the CCP tool.
Get the Creative Cloud Packager from the Adobe Licensing Website (LWS) or Enterprise Dashboard. See here for more details.
This is the information that states Acrobat will not get installed, reads the notes section.
Read this link, this contains the information for the Batch script you will use in SCCM. Its important to note that if you use the MSI installer, Adobe Acrobat will not get installed as mentioned above.
The document states that if you use the setup.exe then Acrobat will get installed. The problem is that is if you use the setup.exe, the deployment is inconsistent from SCCM. Check in Program & Features (Add/Remove Programs), sometimes it will install 20 line items, the next machine will install 23 line items, the next machine will install 28 line items etc etc. The full suite consists of 28 line items, including Acrobat.
Quote: For Acrobat DC, Exception Deployer Application is not required. For Acrobat DC, you only need to run the setup.exe in the Build folder which will install Acrobat DC, the chosen type of license and any main applications not found in the Exceptions directory.
So following the guidance from the link above from Adobe, we will be using the Batch script with some modifications. After the Exceptions Deploy Pre section, we want to add this code to the script. Make sure you are traversing up and back down the correct amount of folders!
Its important you install Acrobat before the main Creative Cloud install! This will allow Acrobat to be licensed correctly, otherwise when you start Acrobat, it will ask you to sign into AAM.
exceptionDeployer.exe --workflow=install --mode=pre --installLanguage=en_US
cd ..\Build\Setup\APRO15.0\Adobe Acrobat
Start /WAIT setup.exe /sALL /rs /sPP /extUI /sl "en_GB" /msi INSTALLDIR="C:\Program Files (x86)\Adobe\Acrobat DC" EULA_ACCEPT="YES" SUITEMODE=1 OWNERSHIP_STATE=1 LANG_LIST="en_GB" AS_DISABLE_LEGACY_COLOR=1 IGNOREAAM=1 REMOVE_PREVIOUS_ACROBAT=NO DISABLEDESKTOPSHORTCUT=2 DISABLE_ARM_SERVICE_INSTALL=1cd ..\..\..\
start /wait msiexec /i "Adobe CC All.msi" /qn /lv* "%TEMP%\CC_all_msiexec.log"
If you want to have no shortcuts on the desktop then add this after the Exceptions
exceptionDeployer.exe --workflow=install --mode=post
del "C:\Users\Default\Desktop\adobe*.lnk" /s
del "C:\Users\Public\Desktop\adobe*.lnk" /s
Adobe Acrobat, you can either use the command line above. Or you can use the Adobe Customization Wizard to create a transform to apply via the ini fill within the Acrobat setup 'bits'.
Key to disable Acrobat to take ownership causing a UAC prompt, will need to GPO this bit.
Windows Registry Editor Version 5.00
As built, the "Build" folder MSIs created by Creative Cloud Packager clobber the SCCM 2012 R2 client. If installing the app from Software Center, Software Center exits at the end of the installation. When installing as part of an OSD Task Sequence, the task sequence hangs forever on the installation step.
I tracked the problem down to MSIEXEC's Restart Manager which exits and restarts processes using files the installer needs to touch. Restart Manager was shutting down the SCCM client and when it restarted, SCCM didn't know what to do.
The solution to this problem is to suppress reboots using
as part of the command line calling MSIEXEC and to also pass along the property
which disables Restart Manager. Once I did this, the MSI installed without trouble and SCCM worked correctly. Software Center didn't crash and my task sequences moved on.
View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.