Best practice for managing osx minor update

New Contributor III

So we have more than 200 macbooks pro that all is running at least osx 12 (a few are M1 macbooks and Intel macbooks). 

However, we dont have control, some still running 12.1. While others running 12.3.1 and a few already on 12.4.

I tried to do mass remote command to a few computers group to update the osx however i find the end user experience is not very good. After i send mass remote command update to update the osx, after 40minutes - 1 hours the end user macbook suddenly installing the update and restart. 

I use this guidelines for sending the remote command


What is the best practice to rollout this minor update?

I am using jamf pro cloud and i am having a look of this article

however i already get stuck with the first step. 

Add the .app File for macOS to Jamf Admin or Composer


Surely for something this minor there should be a more holistic and simple way to do


New Contributor

I'm a big fan of using Nudge.


Nudge is a popup that directs the user to update using software update with configurable time intervals. So you can have it popup every 4 hours while the deadline is 2 weeks out, every 2 when 72 hours remain from deadline, etc. It gently annoys users into updating themselves. We've had great success using it!

New Contributor III

@Rukongai i have a look of nudge deployment - would you be able to guide us with the deployment of nudge using json