What is wrong with forced OS Updates?!

[Sclewis]

I'm having a really hard time consistently getting forced updates to work through Jamf. I finally was able to get a upgrade via packaged policy to work yesterday but I'm not having a lot of success using the Software Update payload within the policy for minor updates. 

I need to figure this out because ensuring that our computer operating systems are up-to-date are the whole reason why we upgraded to Jamf Pro in the first place. 

I'm currently testing computers going from 13.0.1 to 13.1 and 12.6.0/1 to 12.6.2 

It says the policy executes correctly, but it's not installing the updates on the computer

[jamf-42 · Accepted solution]

this hasn’t been a working option for a while 

Updates are now user driven or MDM push or via script requiring user interaction on ARM 

None are ideal.. we await Jamfs promises to address this.. (choose one of the above) 

[sdagley]

@jamf-42 While I do give Jamf a lot of grief for not recognizing that a mechanism to schedule macOS update MDM commands needs to be added as a basic function of Jamf Pro it is Apple that's solely to blame for the unreliability of the MDM commands. Hopefully macOS Ventura brings some significant improvements here.

[Sclewis]

I think it would be less frustrating if the MDM commands worked reliably and not just 70% of the time. 

[Sclewis]

Thanks! What a hot mess 🙄

[SMR1]

We were running in the same issue when deploying the OS updates. It would update Safari, but that was it. Like everyone else, the MDM commands aren't reliable. I've been testing the erase-install and it works, but have issues with users not following directions, because if you restart it before it auto-restarts it breaks the update.

[adminapple]

Same issue we are also facing. While impletmenting JAMF theye asured OS could be upgrader using jamf. In JAMf console getting logs success, but target machine not happing.