@mhegge When Jamf Admin zips a pkg, it is because it is not a flattened package. The policy deployment mechanisms are smart enough to unzip first, so there is no need to run a script to start these installations. Just deploy the .zip file in the same manner you would a ,pkg and Jamf Pro should work as expected.

From what I remember in my testing last year, that method fails. That's why I had to go with the caching and script method.

@mhegge, just to clarify, have you tested with the current release of Jamf Pro and the new Adobe package? I will likely be doing something similar in the near future, so I'm curious what your results are. I haven't had any issues deploying zip files in the past.

@mscottblake You are correct sir!!! A test late yesterday confirmed your process. Sweet! @irobinso I had issues deploying the packages created in Adobe Creative Cloud Packager last year, pre version 10 (I am now on the latest version). The zipped files would alway fail, so I had to research other methods and found that caching the zip file, then running a script that would unzip and install, was a successful, although time consuming was of getting things done.

I would have to have a script for each and every package created that I wanted to deploy.

Thanks for everyone's input.

Something you can do before uploading that saves me time is to simply zip the non flat .pkg before uploading.

I know this is an old thread but my installations are still failing. I'm uploading the pkg to jamf which jamf zips it and then I get the following under the policy logs.

@MikeG

What version of macOS and what version of Adobe CC (2019, 2020, 2021) are you to install?

@MikeG Sounds like a problem with the installer itself, not the method.

Are you able to successfully double click to install it manually?