So we're using JAMF Pro, no cloud. Our JAMF Admin does NOT zip anything, never has. Pretty much do the same as G_Zirrak.

1) Adobe Admin Console & package each App separately as Offline All Apps Restricted with RUM
2) Download downloader DMG, open & run App to download ZIP
3) Extract ZIP, move uninstaller out of Build folder, use Disk Utility to create DMG from Build folder, drop DMG in JAMF Admin
4) Create policy Ongoing Custom trigger w/ Self Service, add DMG set to Install, use installPKGfromDMG.sh set After w/ Param4 set to DMG name, allow restart id user logged out, Update Inventory.
5) Either Admin OR end user/usergroup scoped can install via Self Service. It queues, but runs out of order.

For some reason, since last month, RUM does NOT update to newest version till like a week AFTER release. You know, so if you're heavily Security minded or orientated, you have to uninstall/install new. At least CC App is NOT forced into these ... yet. But it will, at some point I'd bet.

Only issue we currently have is that updating a non 2021 version with 2021 does NOT change the App & Folder names. I have to set policies based off Name Has & Version instead of Name & Version. For more accurate policies where non 2020/2021 version may exist, make sure you use Name Has, else Version out of date will be inaccurate.

We were having tons of issues installing Adobe apps, and after months on a support ticket with JAMF and wrapping our head around log files, we found this that I have listed below, not sure if it will help everyone, but it definitely helped us.

Turns out the Apple ethernet card goes from a full 1G down to 100M when you're at the login screen unless someone is logged in and then it stays at a full 1G when logged in.

I found this script here that fixes the issue, it runs the caffeinate terminal command.
https://community.jamf.com/t5/jamf-pro/prevent-mac-from-sleeping-best-practise/td-p/188961

This is how I changed mine, just making 24 hours the default instead of the three hours they had set.  We install more packages and I just wanted to test to make sure they are awake for that time in case of other loads we throw at them.  You can add whatever time that you want in "$4" when running it up to 48 or anytime other than 24 hours.

#!/bin/sh

declare -i LIVE_TIME
LIVE_TIME=86400
if [[ "$4" -gt "0" ]] && [[ "$4" -lt "49" ]]; then
LIVE_TIME=$4*3600
fi
echo Machine will not sleep for $LIVE_TIME seconds.
( caffeinate -sid -t $LIVE_TIME ) &
disown
exit

I'm having no issues running Adobe or anything because the card doesn't sleep anymore if you run this first script first.  Hope that helps someone.

Hello,

I recently was able to deploy Adobe 2021 packages to Intel and M1 machines through Self Service. About a month ago, I was having a lot issues getting a handful of Adobe apps to run on M1 Macs. I would sometimes get installation failed errors on Self Service, but the install was actually completed, with a complete status in the actual policy logs. So just a heads up on that. But most recently, I've had the apps install complete properly without any error messages. And with recent Adobe updates to its applications, all apps seems to now function on Intel and M1's Macs.

With that said, below is a brief summary of my implementation:
1. I configure each Adobe application separately on Adobe admin console. Which then downloads the DMG file from the browser. 2. Next I run the DMG which opens the Adobe Package Downloader which creates a Zip folder of the applications.
3. Within the zip folder is the build folder, then the install pkg. and uninstall .pkg. I then drag the Install .pkg file directly into JAMF Admin. Depending on the App some take longer to upload than others.
4. After uploading the packages through JAMF Admin, I created a policy for each app, and enabled the Self Service feature. I did not set the policy to cache and then install from cached. Just a straight install of the app.

Just some side notes: From the testing I have done, I recommend uploading Adobe packages using JAMF Admin. I ran into issues uploading with the JAMF web interface. JAMF Admin automatically Zips the .pkg file, so no need to zip the file yourself before uploading. Also, if you happen to delete a certain Adobe app from JAMF and want to re-upload the same application, make sure to change the name of the .pkg file. As I was doing extensive testing, I kept uploading each applications a couple of times that were configured differently from the Adobe console. I also noticed sometimes if the app got corrupt while uploading to JAMF, the checksum portion of the app in JAMF Admin is blank. If there are random characters in the checksum portion then guess thats a good sign that the package is uploaded properly.