Hey fellow MacAdmins,
Heads up if you are using the automated Jamf App Catalog to push Monotype Connect (formerly Extensis Connect / Suitcase Fusion).
Monotype just pulled a massive backwards move with their version 28.1.9 release this week. They shifted their upstream media source URL directly from an enterprise-ready .pkg over to a consumer-facing .dmgpackage layout:
👉 https://bin.extensis.com/ExtensisConnect-M-28-1-9.dmg
Because the Jamf App Catalog simply mirrors the vendor's raw source bucket, Jamf is now locally slapping an identity signature (Developer ID Installer: JAMF Software) over a raw unmanaged disk image.
The Result: MDM pipelines are throwing major installation blockages, local file executions are stalling out, and silent background pushes are completely broken because macOS blocks root-volume automation directly out of unmanaged consumer disk bundles. To top it off, we still have to handle separate scripting for Adobe Creative Cloud auto-activation plugins since they aren't baked in, but now the baseline application wrapper pipeline doesn't even complete.
If you are experiencing broken deployment loops or high-priority helpdesk tickets on your creative endpoints this week, do yourself a favor: freeze your automatic update policy for this title right now and force it to manual until Monotype restores an actual Enterprise Model PKG installer.
Let’s get some tickets escalated to Monotype Account Executives to make them fix this wrapper.