First, check your AAMEE settings to ensure it will continue even if other processes are running, to disable Adobe AIR and to disable registration and updates.Additionally, keep in mind that although it looks like a regular PKG from the outside, inside it's a big garbage-dump of files - dmgs, frameworks, symbolic links, etc. Downloading 1GB of a single flat PKG is much faster and more reliable than downloading 1GB of 100s of files of varying types and sizes. This is particularly true when you use SMB servers as your distribution points (ours are managed over SMB, but clients download over HTTP) - symbolic links don't survive being copied to an SMB share.You can test this by installing the PKG manually. On the machine where you created the Adobe PKG, run the following in Terminal:- sudo jamf install -package "MyAdobePackage.pkg" -path /path/to/pkg/ -target /
If this works on your freshly built Adobe PKG, then your issue is with getting it to your client machine(s) intact.We've found there are two main ways to reliably deploy an AAMEE-created PKG - or any other PKG that uses a messy non-flat PKG format:- Wrap the Adobe PKG in a flat PKG: Create a new package in Composer that places the Adobe PKG into /private/tmp. Add a postinstall script that runs: installer -target / -pkg /private/tmp/MyAdobePackage.pkg. Build it as a flat PKG.- Use JAMF's "installPKGfromDMG.sh" script: You package the Adobe PKG into a DMG. You use a Policy's Cache Package function to put the DMG into Casper's Waiting Room. The script is an "After" script, which opens the DMG (name is passed in as a parameter), copies the PKG out and installs it. https://jamfnation.jamfsoftware.com/viewProductFile.html?id=3&fid=58
Using these methods to ensure the Adobe PKG arrives on the computer identically to how it was originally built, we've been deploying Adobe products quite reliably for the last few versions. Don't bother trying to install and snapshot Adobe products. Even if you get lucky and manage to capture working snapshots of individual products, you won't be able to install two snapshots together and have two working products. They share files and databases that AAMEE and its install logic knows how to handle, but you can't snapshot on an individual file basis.
