Oddly enough, it wasn’t to the latest available Big Sur release (11.2.3, at the time of the test) but to a slightly older Big Sur release (11.2.1). So I left the VM up all night with some unsaved changes in a Numbers spreadsheet as well as Chrome open with a bunch of tabs.Ĭame to find out the update installed by itself (no user interaction or approval) at 5:30pm (at “night”) and the OS, rather than updating to the latest Catalina build, upgraded to Big Sur. The next morning, the update was still pending. Since this was a VM, I suspended it (I don’t believe this is the same as putting a real Mac to sleep), because I wanted to see if the update would install the next morning. I clicked on the details, and it opened in System Preferences > Software Update with a note about the update being scheduled to install later tonight (no specified time). Then, I got another notification about the update being available (that appeared on top of the first notification) with the option to click for details. This is what my testing experience was like…įor a VM Mac on an older build of Catalina, I sent a command from the MDM to install OS updates (no ability from Jamf, it seems-someone correct me if I’m wrong-to specify which update).Īfter about a minute, a notification appeared on the Mac in the top-right corner of the screen saying that an OS update is available, with the options to try again in an hour, try again later tonight, or remind tomorrow. I’d tried it before and found it lacking, but I tried it again recently, and I’d recommend avoiding it at all costs. Well-apart from the fact that Apple will allow you (via configuration profile) to delay updates for only up to 90 days-the user experience is terrible. Well, why not use your MDM to send a command to install an update? That’s what Apple wants you to do. Testing the MDM command to install macOS updates So a lot of Mac admins are relying on the “bother users until users install updates” approach, leveraging open source tools like Munki, Nudge, or Deprecation Notifier. (More details in Using a full macOS installer with Munki to patch macOS.) You can patch Macs with the full macOS installer, but there are downsides to that, too. What we used to be able to do was use the softwareupdate binary to script installs of software updates, but Apple’s made it so that binary is unreliable for installing updates. I think you’ll find the vast majority of Mac admins (at least the ones on the MacAdmins Slack) don’t use MDM commands to install Apple software updates. People who administer Mac deployments at a large-ish scale (hundreds to tens of thousands-i.e., large enough that you have to automate things and can’t physically touch every machine to change settings or install updates) generally want to be able to patch software and macOS while giving a decent user experience.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |