Skip to content

Possible conflicts between Jamf's Restricted Software and macOS installations

Darren Wallace edited this page Feb 4, 2020 · 3 revisions

Issue

When deploying a macOS installer in an upgrade or erase and install workflow, the update process fails shortly after starting.

If triggered via the command line (/usr/local/munki/managedsoftwareupdate -vvv), Munki will show one or both of the below error codes: startosinstall failed with return code 255 / is not a CoreStorage disk

If attempting to run the macOS installer App manually in the GUI, this will also fail.

Resolution

Check your Jamf Pro Server for "Restricted Software" settings ("Computers" > "Restricted Software") that could be blocking the macOS installer App (either a wildcard or specifically the version you are trying to run). Exclude this device/s or remove the restriction.

The "Restricted Software" option will also affect command line installations, therefore will also affect the Munki side of the deployment

Clone this wiki locally