Posted on 01-03-2019 05:33 AM
So I deployed the 10.14.2 update to mac´s (cached) as pkg. But just getting stuck in how actually to start the update without any user interaction - or what is the best practise to deploy a OS security patch . We don´t have any update server and of course want to control what updates the users install, so not just enabling auto update on clients
Posted on 01-03-2019 05:40 AM
Posted on 01-03-2019 05:45 AM
Thanks for the input. Machines are already running Mojave, so it is not a full upgrade - as far I can read from the script it is based on self service, something that we would rather not use
Posted on 01-03-2019 05:49 AM
We use the full macOS installer for both update and upgrade.
Since Apple broke preauthorized reboot and there are mixed reviews on whether this is fixed in Mojave, they recommend the full installer even for patching.
A second reason for using the full installer is firmware updates, which can only be applied through the macOS Installer.
Just a thought, it might take a bit longer (the 10.14.2 Combo Update is also huge at 2.3GB, vs 6GB for the full installer), but the results are worth it for us. At least until Apple fixes their s**t. :)
Posted on 01-03-2019 06:04 AM
OK - just tried to search a bit, but where does Apple state the full installer should be used ?.
Think many users will be quite sad that everytime a Security update is comming a whole installer needs to run for est. 45 minutes or so
Posted on 01-03-2019 08:15 AM
I just packaged the combo update for 10.14.2. I extracted the pkg and dropped in JAMF Admin. Added the pkg to a policy and added to self service.