Here are a number of things we've observed about software update queries in macOS Big Sur during its release availability: )Ĭhanges in macOS 11 to AvailableOSUpdate queries (I'm already sensing I'm writing a bit much here. More info on managing software updates and the specific sets of commands used for it can be found in Apple's MDM Guide for IT, or added to this post later. (There's also a Jamf Pro Applications and Custom Settings schema for the app, so the settings can be configured in the Jamf Pro UI.) For that, there's a great app called Nudge which can be deployed and configured to achieve user-led updates as well.

Note: Not all organizations wish to automate software updates with commands, and would rather guide users to install it on their own time. macOS updates via MDM commands are available to both types of computer processors, both Intel and Apple silicon, and further enhancements to end-user experience are coming to macOS 12 from Apple.Note: software updates scheduled by MDM commands override any deferral settings from configuration profiles, as devices report ALL available updates (even deferred) when an MDM server queries which are available.For computers with Apple silicon, updates require authorization with a volume owner user's password, or macOS can request and use a bootstrap token escrowed with Jamf Pro if an update was scheduled with an MDM command, avoiding the need for user interaction to authorize an update.Note: use of command line or agent-based updates can't update something if it's deferred by a configuration profile restriction.In Jamf Pro, policies can be made for software updates for Intel Macs, whether it's a native Software Update payload, or a specific 'Files and Processes' policy containing the ` softwareupdate -iaR` command.Some organizations deploy macOS updates leveraging a full installer and the startosinstall command, some will use tools to compel users to update on their own, and other will use Jamf policies or MDM commands to update.Īs the macOS 11.6 release is not yet distributed in a full installer by Apple, there can be some downstream consequences to an organization's preferred software update workflow, including issues updating to that version via MDM commands due to PI-009722, explained later in this post with workarounds. As a Jamf who knows a few things about macOS software updates and their various nuances, I want to share a couple tips, as well as explain a bit of what goes on behind the scenes in the macOS update process, specifically by way MDM commands on macOS 11.2 or greater. Many organizations are likely running software updates on their fleets this week, as well as with new Jamf Pro versions.

Download macos 11.6