About a month ago, I was having a lot issues getting a handful of Adobe apps to run on M1 Macs. Note: On Jamf Pro 9.95 or earlier, if the principal distribution point in your environment is an SMB share, use the deployment instructions in the Deploying PKGs Created with AAMEE or Creative Cloud Packager Knowledge Base article.I recently was able to deploy Adobe 2021 packages to Intel and M1 machines through Self Service. After adding the installer package to Jamf Admin, you can deploy it using a policy. Deploying the Installer Package.UMD Jamf Pro Services to help manage share mappings on multiple Mac hosts.2. And with recent Adobe updates to its applications, all apps seems to now function on Intel and M1's Macs.The Creative Cloud for Labs and Adobe Acrobat Pro DC for Labs packages are. But most recently, I've had the apps install complete properly without any error messages. So just a heads up on that.
I configure each Adobe application separately on Adobe admin console. Scenario/ Use case: Computing recommends using Adobe Acrobat Reader (or.With that said, below is a brief summary of my implementation:1. 4.Intended for: Mac users that wish to read and/or digitally sign PDF documents. Open this document using Adobe Acrobat, which will allow you to fill out the number fields and ‘Save As’ to save the completed workbook. Unfortunately, you will not be able to save the completed workbook. ![]() Pkg file, so no need to zip the file yourself before uploading. JAMF Admin automatically Zips the. I ran into issues uploading with the JAMF web interface. Jamf Adobe Acrobat Reader Offline All AppsPretty much do the same as G_Zirrak.1) Adobe Admin Console & package each App separately as Offline All Apps Restricted with RUM2) Download downloader DMG, open & run App to download ZIP3) Extract ZIP, move uninstaller out of Build folder, use Disk Utility to create DMG from Build folder, drop DMG in JAMF Admin4) 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. Our JAMF Admin does NOT zip anything, never has. If there are random characters in the checksum portion then guess thats a good sign that the package is uploaded properly.So we're using JAMF Pro, no cloud. I also noticed sometimes if the app got corrupt while uploading to JAMF, the checksum portion of the app in JAMF Admin is blank. As I was doing extensive testing, I kept uploading each applications a couple of times that were configured differently from the Adobe console. Created package in Adobe Admin Console, went through process to download, extract. 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. I have to set policies based off Name Has & Version instead of Name & Version. 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. At least CC App is NOT forced into these. You know, so if you're heavily Security minded or orientated, you have to uninstall/install new. Downloaded zip file on target computer using jamfcpr. Ran policy on target computer, failure as usual. Uploaded zip file via JamfAdmin, changed policy to use new file When you first power i a new mac what program starts automatically and prompts you for informationAttempted installation with installer -pkg -target /, which tells me I must be the root user. Attempted installation with installer -pkg -target /. Logged in via SSH as admin user, sudo -i to become root. The problem didn't exist with the 2020 installers, nor did it exist at first with the 2021 installers. But previously with 2020 I had each individual application packaged and put up with no issues.This is exactly why you're having success. Works.Why does sudo from an admin user work, but not root? If an SSH session as root isn't working to install the package, then installing via a Jamf policy isn't going to work, at least not without some fancy scripting.I repeated this process with a second package, with only these steps:This seems to confirm that installation will work via SSH with an admin user using sudo, but not root.Nowadays I only package Adobe CC 2021 with the ability for end users to update and install and I let them choose what they want. It'll zip itself and it should be good to go after that.Yes, that's the original method that was being used. Extract the Install.pkg in the build folder and upload it via Jamf Admin. The companies that make that hardware are a little slow to update their plugins, but our clients are quick to upgrade thus we cannot just go the 'let the CC Desktop app manage installs' route.It should be noted, however, that the problem exists on a fresh machine, with absolutely no Adobe application installed, ruling out our side-by-side setup as the culprit as well. If the CC Desktop app is what's doing the installations, then that's happening in the GUI not via a Jamf policy.In our environment, we need often to have both the version for "this year" and "last year" installed side-by-side because there are plugins we use that go with some enterprise hardware. ![]()
0 Comments
Leave a Reply. |
AuthorShannon ArchivesCategories |