Skip to main content
Question

Few Questions about Mac management with Jamf Pro

  • June 16, 2026
  • 2 replies
  • 32 views

Forum|alt.badge.img+2

I have 2 questions with my Mac management with my on premise Jamf Pro instance.

Before news MacOS is launch we would like to block the update while we made a couple of tests with our applications used in my university.

What is the best way to block MacOS upgrade and for how long can we block the update?

 

Second questions, 

After the pre stage enrollement i execute Jamf Setup Manager to install few applications and apply some configurations, i try to execute a script to reboot the computer but after reboot JSM runs again, how could i execute a reboot action after JSM properly?

Thank you very much.

2 replies

dsavageED
Forum|alt.badge.img+8
  • New Contributor
  • June 23, 2026

1. You can defer the update for 90 days, however a far better approach is to start testing now by signing up to https://beta.apple.com/for-it

2. You n eed to kill the setup manager etc and then cleanly restart...

# Make sure all apps are closed
killPIDs=$(pgrep -flia Applications | grep -v "[J]amf" | grep -v "bash" | grep -v "/bin/sh" | grep -v "grep")

# Kill each process
# shellcheck disable=SC2086
kill -9 $killPIDs

# Perform a clean restart
osascript -e 'tell app "loginwindow" to «event aevtrrst»'

 


PaulHazelden
Forum|alt.badge.img+13
  • Jamf Heroes
  • June 23, 2026

If JSM is running as a part of a policy, use the Policy to perform the reboot. Scripted reboots run before the Policy reports as complete, hence it restarting on you.
If it has to be a script, You will need to test this, Try setting the Reboot command to run in 5 mins, with a & at the end of its line. This should run the reboot and schedule it for 5 mins, and the & makes the script continue without waiting for the line to complete. The reboot should execute in a new shell and the shell you are running in should complete and report complete to the policy.