Keep computers updated and set a delay for installation of updates to a specified number of days.
Article Contents
- Delay macOS software updates
- Software Update Profile
- Create a Software Update profile
- Configure the Software Update Profile
- Restrictions Profile
- Block Beta & Standard Upgrades
Delay macOS software updates
To maintain a consistent software update schema across your organization you can defer software updates and choose when they will automatically be installed. There are two places you'll want to configure this; Blueprint Parameters and Restrictions profile from within your Library.
Software Update Profile
Navigate to macOS Applications & Services and then Software Update.
For macOS devices, you can use the Software Update Profile to manage downloading, installing, and deferring updates for macOS & App Store apps. This is a great way to make sure that, at minimum, security updates are being automatically installed on all of your computers.
Create a Software Update profile
- Navigate to the Library module.
- Click Add New in the upper right-hand corner.
- Select the Software Update Profile option.
Configure the Software Update Profile
- Give your software update profile a Name.
- Select a Blueprint to deploy your Software Update profile.
- Select your desired settings for Automatic Updates.
- Select your desired settings for Update Settings.
- Click Save in the bottom right corner.
Restrictions Profile
You can defer OS updates with the Restrictions profile in your Kandji Library. This option allows you to defer updates for a specified number of days. This can be especially helpful if you are managing Mac computers, iOS, iPadOS, and tvOS. The Restrictions profile allows you to choose whether any of the options set are applied to the specific platform you want to restrict.
Block Beta & Standard Upgrades
The native options for blocking beta updates are also enabled using the Software Update profile in your Blueprints and utilizing Kandji's Application Blocking Parameter. Learn more about Restricting access to beta OS releases.
The following examples are specific to macOS Ventura, macOS Monterey, and macOS Big Sur. For each release, you'll need to update each setting with the relevant info specific to that release.
Ventura - Public Release
- Process name: Install macOS Ventura
- Match Type: Contains
- Path:/Applications/Install macOS Ventura.app
- Match Type: Contains
- Bundle ID:com.apple.InstallAssistant.macOSVentura
- Match Type: Exact
Monterey - Public Release
- Process name: Install macOS Monterey
- Match Type: Contains
- Path:/Applications/Install macOS Monterey.app
- Match Type: Contains
- Bundle ID:com.apple.InstallAssistant.macOSMonterey
- Match Type: Exact
Big Sur - Public Release
- Process name: Install macOS Big Sur
- Match Type: Contains
- Path:/Applications/Install macOS Big Sur.app
- Match Type: Contains
- Bundle ID:com.apple.InstallAssistant.macOSBigSur
- Match Type: Exact