Today, Apple released the following updates
macOS Catalina 10.15.6 Update
Security Update for Mojave 2020-004
Security Update for High Sierra 2020-004
Patch & Security information, Download Links, Version info + size for BridgeOS, Combo, Delta, Full Installer app included in the links below!
@ClassicII The Jamf product update list for Mojave has the latest security update link already: https://updates.cdn-apple.com/2020/macos/001-26310-20200714-e6a25de7-33b9-46eb-bb7d-cbdacda4f7dc/Sec...
Looking forward to the blog update.... I'm going to hope against hope that Apple's fixed the keychain bug requiring odious workaround if a mobile/network account user changes their password otherwhere than their Mac.
@ClassicII Fixing a bug by requiring a major OS upgrade isn't really a bug fix, then, is it, it's a forced upgrade. I fail to understand how Apple can rationalize not fixing this in all impacted major OS versions when it has such significant consequences for enterprise support, especially when Apple releases such substantial OS security updates for the likes of Mojave and High Sierra which incorporate feature changes (e.g. the changes to the softwareupdate --ignore flag.)
Having a mobile/network user's keychain update properly on password change in Catalina doesn't help me for the portions of my fleet that need to remain on Mojave.
Anyone having issues with the 10.15.6 update? I have had two users report issues, I currently have it on hold.
I am not really sure how to troubleshoot or what to look for, but this has happened to one user with the last few updates.
I deploy updates by running the SWU payload in a jamf policy, so it is just using the command line software update utility to download and prompt to install in the background. So when the user reboots, they get the recovery screen, reboot back into the OS with no issue. Try again, same issue. Grab it from System Preferences, works no questions asked.
Not sure if this is just a Catalina issue, but Catalina is the only one getting major updates these days, so my primary Mojave fleet hasn't been complaining.
@T.Armstrong , @hdsreid I'm having the same issue. It seems to be a T2 issue. On my 2019 machine, I attempted the update via a software update policy, upon reboot I got the recovery prompt. However doing a full shut down, then booting triggered the update and everything went fine after that. A non-T2 (2013 MBP) updated without issue. I'll probably exclude T2 machines and figure something else out for those users.
Another annoyance I discovered is that it seems to reset the DisplayLink Kext, which I already allowed via a configuration policy. Not sure how to tackle this one yet.