Learn about various errors that can be reported from Managed OS for macOS
"No update candidate found."
When Kandji queries the device for available updates, it parses the response and looks for a matching product key that aligns with the latest approved version of macOS in Kandji. This is also known as "the library item version" (shown in the upper right-hand corner of the Library Item). As of this article drafting, this is 12.5.1, and the product key is MSU_UPDATE_21G83_patch_12.5.1. When this error surfaces, the list of available updates returned from the device did not include a match for the library item version.
This is often a transient error that will resolve itself on the next agent run and/or device restart.
"Only % battery remaining, and device is not connected to a power source."
This happens when Kandji tries to initiate an update, and the device drops below 50% power or is not connected to a power source. The Kandji Agent checks for this requirement before kicking off an update. Still, sometimes due to the time it can take to install an update, the battery level can drop below the threshold once macOS starts to actually install the update.
Charge the Mac and/or connect it to a power source and try the update again.
"Device is Apple Silicon without bootstrap token."
This is a requirement in macOS to install software updates using MDM on Apple silicon. For more information on Secure and Bootstrap Tokens, see Apple Platform Deployment.
This is not a common issue as a Bootstrap Token should be escrowed automatically to Kandji during enrollment as long as the user doing the enrollment is a SecureToken enabled user or if Automated Device Enrollment is being used.
Log out or restart and log in as a SecureToken enabled user (of any type -- standard or admin), and one will be escrowed automatically to Kandji. You can confirm this by looking at the MDM section of the Device Details page.
Alternatively, the following can be run interactively by a SecureToken-enabled administrator on the Mac:
sudo profiles remove -type=bootstraptoken sudo profiles install -type=bootstraptoken
Then try the update again.
Failed to personalize the software update. Please try again.
macOS updates on Mac computers with the Apple T2 Security Chip and Apple silicon are personalized for each piece of hardware. For more information on this process, see Apple Platform Security.
It's possible that a transient server issue happened with Apple's software personalization servers, or there may be a network problem contacting the hosts listed in the Device Setup section of this Apple support article. Check that connectivity is properly allowed to those services and try the update again.
Could not complete ScheduleOSUpdateScan after 3 attempts
The device is not properly processing a scan for available updates.
Running the following custom script once daily on your devices may help.
#!/bin/sh /bin/launchctl kickstart -k system/com.apple.softwareupdated
Apple lists this as being fixed in macOS 12.3:
"Resolves an issue where software update scans become unresponsive."
Took too long to find status for product key...
In macOS 12.3 and later, the download progress of an update reported to Kandji by macOS may get stuck at 0%. Kandji has reported this to Apple in feedback ID FB9981183.
After this error happens 3 times (over the course of 3 agent runs, or approximately 3 hours), the agent will proceed with assuming the update is properly downloaded, and the user will be prompted to install the update.
To reduce the frequency of this error, turn off the option to automatically download updates in any Software Update Library Items being used in the same Blueprint(s) as Managed OS for macOS. Managed OS automatically downloads updates 5 days in advance leading up to enforcement.
The ScheduleOSUpdate command failed
This is a generic error that can have many causes. One may be that in macOS 12.3 and later, users may receive an additional notification with a countdown timer when an update begins the installation process. This notification appears on top of the Kandji agent notification, as shown here:
If this notification is interacted with by a user and dismissed, the update does not proceed. Kandji has reported this to Apple in feedback ID FB9981183.
Restart the device and try the update again.
Unsupported InstallAction for this ProductKey
macOS 11.x only returns full installers to Kandji, instead of both full installers and delta updates, the first time it is queried for updates. When Apple has a full installer available for the same macOS version that is currently approved for minor updates, this error may occur.
This error should resolve itself after ~30 minutes once an affected device receives its next query for available updates and the Kandji agent checks in after that second query. This is also resolved in macOS 12 and later.
An error occurred executing this item: command failed: unknown error
This is a generic error that can have many causes.
Restart the device and try the update again. Contact Kandji support if this error persists.
Couldn’t communicate with a helper application/Helper tool crashed
Kandji has observed frequent occurrences of this error when upgrading macOS Big Sur clients running a macOS version less than 11.6.4 to macOS Monterey, and has filed it with Apple in feedback ID FB11546032.
Update the device manually to the latest version of macOS Big Sur using System Preferences, and then try the update again.
Errors referencing startosinstall
The macOS full installer's startosinstall tool is used to upgrade Intel-based Mac computers between major OS versions. Errors referencing startosinstall may indicate a problem with the download of the installer, or the usage of it, depending on the error.
Check the device's network connection. Restart the device and try the update again.
I need more help
Contact Kandji support for additional help with Managed OS.