@PaulHazelden
I tried your steps describes above, but somehow I seem to miss something
I download a photoshop.pkg package from the adobe admin portal.
I put the pkg in a folder and tar.gz the folder
I move it to composer and the post script you added up there(with corrected path etc)
I build the package in composer and the package is called photoshop.tar.gz.pkg and upload it to a policy and deploy it
When it run on a machine the PKG is also extracted in the right folder, but the installation process does not seem to happen ?
@jameson I just posted a copy of the script in your thread.
https://www.jamf.com/jamf-nation/discussions/31493/how-do-you-deploy-adobe-cc-2019
Looks like you missed the post install script
Have been working on Adobe CC suite deployment with shared device license for the labs. Tried a number of methods.
Failed or not-good-enough methods:
1. Create full suite packages (zip file) from Adobe Admin Console. Use the pkg file under the Build folder to deploy. On certain machines failed with installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “AdobeSDL-CCAllApps_Install.pkg”.) When that problem occurs, I did notice Acrobat still got installed.
Create a dmg from the unzipped Adobe installer. Cache the dmg into waiting room. Use execute command in files and processes to mount and install the pkg. Then remove the dmg. More details can be found here. Problem with this approach is when the install pkg command fails in the execution, the policy log still shows completed, a bug reported here. It also started having the same issue in the first method regarding running script. Plus the extra effort to unzip and create dmg for the almost 20GB install files.
Similar to the 1st method. I found if I flush the log for the failed ones, without running the Adobe Application removal script again, just let the policy rerun and reinstall the same pkg. The 2nd time installation will magically be successful.
After reading many discussions online especially this one about Acrobat, I think we finally found the most stable approach:
4. Similar to the 1st method. But create the full suit package without Acrobat. Drag the pkg file (AdobeSDL-CCNoAcrobat.pkg) under the Build folder into Jamf Admin, which will zip it. Do the same thing for the package created only with Acrobat (AdobeSDL-DCAcrobat.pkg). Create a policy (custom trigger, once per computer) for each of these packages. Create the "master" policy (Check-in) to have the Adobe application removal script run first, then execute command jamf policy -event AdobeSDL-CCNoAcrobat && jamf policy -event AdobeSDL-DCAcrobat to call the other two policies (CCNoAcrobat first). So far almost all the deployments have been successful. When it fails on one or two machines (the CCNoAcrobat policy), I just use the 3rd method to flush the logs in the master and CCNoAcrobat policies until the logs show the successful installation.
Hope this helps.
