Mac Admin

Adobe and macOS Catalina

This evening Apple released their latest Mac operating system, macOS 10.15 or Catalina. This was just in time for the folks this side of the pond to get home after an evening of work (totally not annoying 😉).

Around the same time, Adobe released a related KB, Known issues with Creative Cloud packages on macOS 10.15 Catalina.

TL; DR

The KB isn’t too long and is certainly worth a read but there are 4 key points:

1) The zipped archive/s downloaded from the Adobe Admin web console will contain a quarantine bit. In macOS Catalina you won’t be able to unzip these until the quarantine bit is removed. Workaround: Remove this using the below command, then extract the packages from the zip and deploy as normal:

xattr -d com.apple.quarantine /path/to/zip

2) If your packages were created before 16th September 2019, they may fail to deploy on 10.15 devices if they are extracted on a 10.15 device. Workaround: Create a new update package, create a brand new package or extract the package on a device that isn’t running macOS Catalina

3) Adobe Creative Cloud Packager (CCP) can (will?) create packages containing 32-bit components, and these will fail to install on macOS Catalina. Workaround: If you need to deploy these packages to 10.15 devices, you will need to delete the two following paths before deploying the package (also note point 4 below):

[PackageName]/Build/[PackageName]_Install.pkg/Contents/Resources/ASU2

[PackageName]/Build/[PackageName]_Install.pkg/Contents/Resources/Patches/AdobeApplicationManager-1.0_update14

4) CC2018 and early Adobe applications contain 32-bit components and will not launch on macOS Catalina. Workaround: Only Adobe CC2019 Apps are compatible with macOS Catalina and you will need to upgrade.

BONUS:

5) There looks to be an issue when running Adobe Admin Console generated deployment packages on macOS Catalina in certain contexts, which cause the installs to fail. This is still a developing issue and looks to possible affect Jamf and Munki deployments, as well as deployments over SSH (it’s not known if it’ll affect other management deployment tools but it is likely).

Some working of the issue can be found in the Munki-Discuss mailing list and if you’re affected, it is strongly recommended to log tickets with Adobe and / or Apple.

Hmm, how do I postpone the install of macOS Catalina until I can workaround these?

Mac Mule (Blocking macOS Catalina With Jamf Pro) and Rich Trouton (Preventing the macOS Catalina upgrade advertisement from appearing in the Software Update preference pane on macOS Mojave) have you covered.

Summary

This post covers the newly released Adobe KB regarding known issues with macOS Catalina. As always, if you have any questions, queries or comments, let me know below (or @daz_wallace on Mac Admins Slack) and I’ll try to respond to and delve into as many as I can.

Standard