We are trying to set up our Macs with a Software update policy from this link. I've set that up and deployed it to my test machine (M1 Mac running 11.2.1). I ran a 'sudo jamf policy' to kick it off and see what the process would look like. After the initial password to run the sudo command I was prompted again for my password and then it took awhile to I assume download the update (11.6). After downloading in terminal it says the update is complete and that it does not require a restart or a shutdown. However the update never installs, the Mac is still running 11.2.1, I rebooted the machine and it didn't apply any updates. Any thoughts on why its downloading but not installing?
Pretty sure this is due to the M1 Mac. It's not something that works via the command line softwareupdate method unfortunately. Only 2 valid ways to install OS updates on those models now is through the Software Update preference pane GUI or by sending an MDM command to the Mac to install updates. You can thank Apple for that. With each new OS and new Mac models Apple has made it harder and harder at every turn to get machines updated, for reasons that only they seem to know, because it sure doesn't make sense to anyone else.
Calling the softwareupdate binary (like this policy is doing) used to be reliable on older versions of the operating system, but became unreliable with the T2 chips and especially with M1.
You can try using MDM commands to update or look into something like nudge (https://github.com/macadmins/nudge) to try to prompt users to initiate the update, but I wouldn't rely entirely on the softwareupdate command for your updates
@beeboo , could you clarify a bit exactly what you are doing? We've been having this same issue, of course (Apple talked about it in their last field SE update), and are looking for better ways around it than downloading the entire full installer every time we need to do an update (which Apple is making noises about not supporting anyway). Thanks!
This is what has been tested to not really work (at least consistently)
Im running the API call from my machine locally using this as an example and it seems to work effectively, there just isnt a lot or many notifications for the user i run the command at night.
Seems to go from start to finish in about an hour, on average.