AppleSoftwareUpdate

[mani2care]

Hi AppleSoftwareUpdate not working most of the time.

issue 1 :
If the mac battery low not connected to power then auto disappeared in the schedule it should wait till connect to power or can give the option to update later or connect the adapter recommended

issue 2 : In big-sur not running the update just rebooting scheduled 3 deferrals and 4 times forced update right but not forced update doing just rebooted and came back to the login window.

issue 3 : big-sur first time just run the script and it says no update but the machine has pending update not yet checked proper rebooted and came back without an update by click update button.
tested in bigsur , Catalina

issue 4 : before the reboot, you have to unlock the FileVault or disks because FileVault needs to unlock the during the update to avoid asking the user name and password during the update process. T2 chip machines will ask for a login password.
if granting local admin pls specify the parameter so can help to mention the admin user name and password for that.

looking forward to new features.

[bp88]

For issue 1: To avoid any problems with updates, the script requires an active power connection. I do not assume that just because a device may have 60% of battery life left that it won't drain quickly. I didn't add logic that requests the user to connect to power because I felt that would just provide the end-user a way to avoid performing the update.

For issue 2: I'm not sure I understand what happened here. Can you provide more details. What OS version were you on and did version was it supposed to update you to?

For issue 3: What OS version was this happening in? The script works off softwareupdate -l which means if that command line tool reports no updates then that's what you'll get in output. This may very well be a bug with the softwareupdate command line tool in macOS Big Sur. There were already some issues on macOS 11.0, 11.0.1, 11.1 which were supposedly resolved in 11.2. But it's possible there are other issues that have yet to be fixed.

For issue 4: I did consider this at one point. The only situation where this becomes applicable is when a user is forced to update. In that situation, there are two possibilities.

1. The end-user is already in front of their computer and can enter their credentials to authenticate and proceed with the update.
2. No user is available. I do not currently have plans to address this at the moment.

[Aceraney]

I'm also experiencing "Issue 2" as described above. I got through all the deferrals on the test machine and the force update, which was a restart update, just restarted the machine without installing the update. It seems that maybe it's not able to grab the PID and wait for it before restarting?

[bp88]

@Aceraney Check out the latest version of the script. I fixed it recently.

Or check out this new script that I've written to replace AppleSoftwareUpdate.sh: https://babodee.wordpress.com/2021/03/30/handling-major-upgrades-and-minor-updates-for-macos-with-jamf/