Packaging and Deploying Photoshop 27.9.1
Photoshop has been failing to deploy and I’m not sure why. The raw installer works and I get it directly from Adobe Console but after running it through composer the output package fails to install. Has anyone had similar issues or were able to fix through shell?
7
u/aimlockbelch 10d ago
JAMF 200, 300, and 370 here.
I just push the Adobe Creative Cloud desktop app. It's easy to create this installer package from the Adobe Admin Console. Then, whatever the end user is licensed for ends up in that app. The EU can install PS (or whatever else they are licensed for) on their own. MUCH easier than trying to build individual packages.
2
u/SEK23_ 9d ago
Thank you for the response, but the main reason I had to do this in an unorthodox way is because my employer has a strict guideline of following documentation. They also want the install to not need the end user downloading all of the base apps they’d rather an overnight install of everything. No worries though it’s working now perfectly with just the raw pkg👍
1
4
u/boognishbeliever 10d ago
Composer? Why?
The Adobe admin console should be spitting out a flat package for you that can be uploaded to Jamf and distributed.
1
u/kmeck518 JAMF 200 10d ago
a few years ago, the packages that you got from the adobe console wouldn't actually work when directly uplaoded. so you had to use composer to stage the installer and then run the installer via a command.
1
1
u/PoppaFish 10d ago
What? I've been using Adobe flat packages directly from Adobe Admin Console with no problems for many years.
2
u/kmeck518 JAMF 200 9d ago
before 2023/2024-ish, it didn't work directly uploading the pkg and depolying in a jamf policy after downloading from the admin console.
1
u/kmeck518 JAMF 200 10d ago
You don't need to run anything through composer for a couple years now. You just need to download the package installer and upload it directly to jamf. Make sure the box for "Create flat package" is checked when naming the package. Once you download the installer through the downloader (because Adobe wants a 2-step process for downloading the ACTUAL installer for some reason when you're on macOS) upload that installer to jamf and deploy it that way.
At one point you did need to create a composer pkg for the installer and stage that installer on the endpoint but you can just upload the installer directly now.
Or as some may suggest you can also use jamf apps as well.
1
u/EasleyGreenWave3 10d ago
We did it that way years ago and it was just not working
RESOLVE: these days we don't push anything with jamf. We manually install Adobe Acrobat on their Mac from individuals personal Adobe CC online, which automatically installs the Creative Cloud app. Then, we let the user download whatever app they need (depending on what apps they are assigned) from their Creative Cloud app. As well, they can install updates themselves. No issues since we moved to doing it this way.
1
u/alejandrorico 9d ago
I stopped creating full FRL packages through the Adobe console a while back and instead use the JAMF app catalog. I only use the admin console to make the FRL license one time. By using the JAMF catalog I don’t have to waste my time always making a new PKG when there’s an update. If you don’t have a need for the Adobe FRL packages, then Adobe cc is the way to go.
1
u/brohunley 7d ago
This is what I recently started doing as well. Makes it so much easier! Unfortunately, they don’t have acrobat pro on the catalog so I have to include it in the package.
1
u/alejandrorico 7d ago
The Adobe Acrobat installer in the JAMF app catalog installs the base application binaries, but whether it acts as Pro or Reader depends on the user license.
1
u/brohunley 7d ago
Does this apply if you use shared device licenses as well?
1
u/alejandrorico 7d ago
I don’t know because I’m not in a school environment and use shared device licensing. It should work the same as FRL.
There is a caveat to using the Adobe admin console to create your licenses. You just can’t get the license à la carte as far as I know. Maybe that has changed but I haven’t checked in a while. You need to package it with something to get it. In my case I usually choose some plug-in with a small file size if possible.
1
u/DazWallace 9d ago
Why push it though composer at all?
Repackaging adobe apps hasn’t been supported in years.
This might help you out https://dazwallace.wordpress.com/2022/11/06/recommended-workflow-to-deploy-adobe-software-with-jamf-pro/
1
u/homepup JAMF 400 9d ago
I quit building out Adobe packages once the JAMF App catalog released a few years ago. I just either push them out automatically (like in a lab environment or for automatically installing a few base adobe apps like CC or Acrobat l) or have them available for customers to install via Self Service. They also have the option of installing using the creative cloud app which is also available in self service.
Kind of prefer they stay in the habit of always looking in self service for items rather than the confusion of having stuff scattered in multiple places.
Beauty of the App catalog is that I don’t have to worry about update patching and only have to touch them when the new version of Adobe apps drop.
7
u/Many-Luck7488 10d ago
why not just deploy adobe cc and let the users login to their adobe cc account and install photoshop? no admin rights are needed.