spiritualsetr.blogg.se - Macbook pro software update it taking too long

Macbook pro software update it taking too long install#
Macbook pro software update it taking too long password#
Macbook pro software update it taking too long mac#

We currently have a practice that "works" but is overly complicated and I'm trying to simplify.ġ) If available SWU count is > 0 they get a jamfHelper notification stating that they have a week to apply the update. I'd love to see any other suggestions that balance keeping the user informed of what's happening (and perhaps even giving them deferral options) while at the same time providing a near iron-clad assurance to us that machines WILL get updated. I'm not really considering scripting options since it sounds like that won't work in an Apple Silicon world. Another option is to use the MDM command to force the update (similar to pushing those updates on iOS devices) immediately with no warning to the user.

One option is the nagging route of popups via policy until they apply the updates. If a user doesn't want to take the time to update their system, our options seem to be pretty limited. After that though, all the "Automatically apply updates" boxes are checked but it's still pretty much up to the user to respond to the update prompts. We've got the Config Profile in place that postpones updates x number of days just to give us a little breathing room in case Apple does release a problematic update. Pulling up a chair for this one and grabbing some of that popcorn. Managed Software Updates - using deferrals via a m. You “can” do this with apple silicon, but it will prompt the user to enter their password.

Macbook pro software update it taking too long install#

The command would be “sudo softwareupdate -aiR” (i = install / a = all / R=Reboot).

Intel – You can create a policy using the softwareupdate binary and shove that in self-service.

You can get crafty with API, but I would not recommend it. Unfortunately, the only way to issue a software update command is from the JAMF console by an admin. However, as many things they failed to deliver. JAMF teased about letting us use MDM commands in a policy last fall for OS updates.

Apple Silicon – MDM can only push updates using MDM commands.

If the user wants to run updates, empower them to run updates themselves.Īs far as using self-service, your experiences will vary between Apple Silicon and Intel Macs. My suggestion: If a user changes their mind and wants to run updates before their deferral just tell them to open system preferences > software update. You question is more of a user agency than management action question. JAMF and softwareupdates have sucked for a very long time, and changes apple has made only exacerbate the issue with how poorly JAMF manages OS updates. I suggest making a new JAMF nation post rather than commenting on a post that is over a year old. Your questions are getting rather detailed.

Macbook pro software update it taking too long mac#

What is the best way to handle software updates? Is there MDM magic I am missing? What is the downside to having the checkbox "keep my mac up to date" checked via a config profile? I would like to use Nudge, but, my confidence in my users is low enough to not expect Nudge to work fine on its own.

I recently rolled out the UEX-Tool-For-Jamf, and two of the components in it are no longer developed and throw gatekeeper issues in Big Sur.

Macbook pro software update it taking too long password#

In addition to that, this requires a password if the computer is Apple Silicon. As stated in the Nudge channel, Since 2018 this has been a problem since Apple doesn't test softwareupdate commands that are triggered by a script. I understand that theres resistance to using any terminal commands for software updates. While this is, arguably, a feature that Jamf should be able to handle at its core, what is the best method in 2021, across the gamut of supported OS's and architectures, to enforce Apple software updates?