In our case FileVault can also be a sticking point.even though it usually has succeeded by looking at the build version on the failed Mac after it inventories into JAMF again. The security update returns a "failed" result to the JAMF policy which makes it hard for me to know what's happening in the fleet.This could cause users to do silly things that lead to bricked devices which are especially to be avoided right now! The security update seems to hang the Mac for about a minute just before it reboots.Is anyone else seeing this behavior? (Yes, I know we should be installing with Apple's native software updates, but we just can't do that at the moment, and the idea of deploying updates remotely right now when they have a pretty high incidence - 5% of our fleet or so - of generating downed users/Macs fills this admin with trepidation.) the screen freezes for a minute or more, and then the multiple reboot hell begins ASSUMING users didn't brick their Macs already when they saw the frozen screen by holding down the power button. What is the best practice method of deploying SecUpd*.pkgs through Jamf when not using Apple's Software Update functionality? Does anyone have any tips on how to successfully install Mojave's SecUpd2020-002Mojave.pkg from the downloaded DMG when deploying it directly with JAMF? I know that's not Apple's preferred way, but currently it behaves unpleasantly with how I configured the Jamf package as requiring a reboot and the "reboot if package requires it" option set in the install policy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |