It seemed this was an issue with an easy answer: scope the deployment of OS-specific profiles to smart groups of devices that meet that OS. In this post, I’ll share a short script I used to achieve this with Jamf Pro.

What was needed was something to flag and trigger the installs as soon as the device was updated. Mac Admins soon realised that if these settings were deployed on an OS that doesn’t support them, they’ll often not take affect if the device was updated until they were redeployed. Each of these had a minimum OS required for them to work. Over the years, Apple have released a number of new and helpful profile payloads such as PPPC, System Extensions and the like. Migrating macOS Devi… on Migrating macOS Devices from o…ĭazwallace on Moving devices from Adobe Shar… Richard Glaser on Changes to Docker Desktop for… Stephan Peterson on Submit Jamf inventory update o…

Recommended workflow to deploy Adobe software with Jamf Proĭeploying Docker Des… on Changes to Docker Desktop for….

Submit Jamf inventory update on OS changes.

Speaking at London Apple Admins for Beginners.

Creative cloud not installing mac