So I create a new package in the Jamf console and select my Adobe package's zip file from my local MacĦ. I'm using Jamf Pro 10.26.0 and upload through the Jamf web console instead of Jamf Admin. Right click the _Install package and select Compress, which should compress it into a new zip file in that same Build directoryĥ. Go into the unzipped directory of your Adobe package, find the "Build" directory, and there should be the _Install and _Uninstall non-flat PKGs for your Adobe packageĤ.
Go through Adobe's tedious process to download that package to your local Mac, which will be a zip of all the package contents. My package was Adobe CC Desktop App and Acrobat DC, named user licensing.Ģ. Build the Adobe package in the web-based Adobe admin console. Here are the more detailed steps of what I did:ġ. The notable difference here is to zip the non-flat pkg locally on your Mac before uploading to Jamf instead of having Jamf zip it when you upload it. Then add that package to the Jamf policy, and it successfully installed from Self Service and the policy event name. My workaround was to go into the "Build" folder of the downloaded Adobe package, find the non-flat installer pkg, compress and zip it locally first, and then upload the zipped install pkg to Jamf Pro. So it's the latest version of the Adobe apps to the date of writing this, and I was getting the same error message when installing it on Catalina from Self Service or using the policy event name. My package included Adobe CC Desktop App and Acrobat DC and was built on Dec 20, 2020. Not sure if this workaround will work for everyone, but I had this same problem, and I was getting the same error message with an Adobe package that was created from the Adobe admin console.
0 kommentar(er)
