I finally resolved the admin authentication, but now I'm dealing with a fully inconsistent response to my attempts to initiate the update.
I can use either the Jamf Console or an API Command embedded in a policy to trigger the update. The results in the computer management logs are the same either way:
ScheduleOSUpdate
AvailableOSUpdates
ScheduleOSUpdateScan
The problem is, sometimes it works, and other times it doesn't. I haven't figured out, yet, what I can do to consistently make the update command stick and proceed.
At first, I thought it was the update manager getting stuck, and I came across this command that, once issued and the computer rebooted, seemed to allow the update to go through:
sudo rm -rf "/macOS Install Data"
But that only worked for a couple of my test cases. I then found an alternate solution that involved sending this command in advance:
sudo launchctl kickstart -k system/com.apple.softwareupdated
Which, again, worked for several computers. This one did not required a reboot, so I added it to my API command script to hopefully fix the problem before it became a problem.
Unfortunately, after having updated 20 computers through a variety of the above fixes, I now have 10 more computers that seem resistant to update at all, and thus I'm back looking for another solution, because apparently nothing that I've done previously was actually a solution. They were likely all placebos, and I am thinking I was just lucky with the first 20.
If they would at least all succeed or all fail, that would be something, but this roller coaster of success and failure is just maddening.
