Scheduling rebooting of machines

New Contributor III

I have seen bunch of scripts online but if someone has a working script which can deploy will be very helpful.

I am looking a script which checks the last reboot of the machines. Then it would check if the reboot occurred less than 7 days or not. If the user hasn't rebooted for more than 7 days, the script will restart their machines. They will receive a popup that their laptop will be restarting and also allows them to extend the time by few hours before the laptop restarts.


New Contributor

I am very interested in this as well - lack of reboots has been problematic in our enterprise.

Contributor III

Hi @tegus232 ,
I'd start with the following Extension Attribute to check the last day the machine was rebooted. Make sure to set the Data Type to Date Format.

echo "<result>$(date -jf "%s" "$(sysctl kern.boottime | awk -F'[= |,]' '{print $6}')" +"%Y-%m-%d %T")</result>"

Then I'd create a Smart Group to check for machines that have not rebooted in over 7 days


I'd then set a policy to run a script like below to the user's machine.

Jamf Helper Reboot Script with Deferral

(You could probably bypass the EA creation and store the script natively on user's machines. You could call it via a Launch Agent, but I personally prefer Jamf handling the script deployment)

I have not tested this workflow.


How did you get Criteria "Uptime"

Honored Contributor III

@jschank The first part of @shaquir's post is an Extension Attribute (EA) to collect the info from a Mac during inventory, and he named the EA Uptime. When you're creating a Smart Group, click the Show Advanced Criteria button when adding Criteria, and you will then see all of the EAs being collected by your JSS.

Valued Contributor

Here is what I have...
The Mac Admin community has been helpful and I got this working.

With this, the user has the option to select time of restart, or cancel.


### Adam T.
### April 16, 2020
### This is a JamfHelper Script which will be used to notify user if they have not restarted the computer in 7 days
### This script will give the user options how to proceed (now, 1 min, 5 min, 30 min 1 hr, 2 hrs as an example)
### This is needed as staff members tend not to restart their computers often
### This script is called from another script that checks uptime
### Using Jamf Helper is cool

#Message type variables below

#Utility window gives a white background
title="Replace this text to enter the title of the notification"
heading="Please restart your computer (modify as needed)"
description="Your computer has not been restarted in at least seven days. A more frequent restart is recommended.

Doing so optimizes the performance of your computer as well as allows us to deploy security updates or new applications to you automatically.

Please restart now."


selection=$("/Library/Application Support/JAMF/bin/" -windowType "$window" -title "$title" -heading "$heading" -description "$description" -icon "$icon" -button2 "Restart"  -showDelayOptions "0, 60, 300, 3600, 7200" -button1 "Cancel" -cancelButton 1)


## Convert seconds to minutes for restart command

## Echoes for troubleshooting purposes
echo "Button clicked was: $buttonClicked"
echo "Time chosen was: $timeChosen"
echo "Time in minutes: $timeMinutes"

if [[ "$buttonClicked" == "2" ]] && [[ ! -z "$timeChosen" ]]; then
    echo "Restart button was clicked. Initiating restart in $timeMinutes minutes"
    shutdown -r +${timeMinutes}
elif [[ "$buttonClicked" == "2" ]] && [[ -z "$timeChosen" ]]; then
    echo "Restart button was clicked. Initiating immediate restart"
    shutdown -r now
elif [ "$buttonClicked" == "1" ]; then
    echo "Cancel button clicked. Exiting..."
    exit 0


Hey @atomczynski I do not see the logic where the script checks for the 7 days

Honored Contributor III

@Anton The script doesn't check for uptime, that's done via an Extension Attribute to report Uptime and a Smart Group to determine if the value of Uptime is more than 7 days which is used to scope a Policy which runs the script above.

New Contributor III

Is there a way to run a launch daemon every 8 hours?

Honored Contributor III

@ejadadic Use a <key>StartInterval</key> with <integer>28800</integer> as the value in your LaunchDaemon .plist.

And here's a handy web site for creating schedules for a LaunchDaemon: 

New Contributor III

Thank you for that information, can I simply input that in the script itself or compose the script and launchagent into a package?

Honored Contributor III

@ejadadic The StartInterval goes into your LaunchDaemon .plist. It doesn't matter if you have a wrapper script that writes out the LaunchDaemon and the script it's going to call, or if you have a .pkg install the LaunchDaemon and script.

New Contributor III

Thank you for that information 

I've been getting some issues on devices trying to restart

Shutdown at Thu Apr 14 00:09:23 2022.
shutdown: can't detach from console


Q about the script that is working perfectly,
In the defer options - can I change the Start now option to Reboot now?


Honored Contributor III

@atomczynski Be aware that by using shutdown -r now the Policy running this script will never get logged since it'll kill the jamf agent before it can log completion with your JSS.

shutdown -r +1 &

i use that at the end of my OS upgrade script
seems to give it enough time to let JSS know of the results (note, not doing a recon or anything)
that way a user doesnt get prompted multiple times to run the policy before a recon kicks in and theres no point running a recon before the upgrade as i need the new upgrade info post reboot.

New Contributor III

This is great.
The only issue I am experiencing is, the delay option does not seem to work, my checkin is every minutes, if I select anything greater than 15 min in the script it will re run the script on checkin
Any suggestions to get around this


every how many minutes?
Ours is set to 30 min and its fine, but it also depends on what you want to do.

Occasionally we see this when it comes to large downloads like OS or when a user has a slow internet connection, but my understanding is that when a script is running it wont prompt you again, UNLESS its waiting for your confirmation (we have cases when we auto kick off policy in X minutes and a user might get 2 prompts).

But i could be wrong about the policy part, though logically it should make sense.

New Contributor III

Question.. do you need to set an inventory update to occur at reboot to keep this from looping? the script will only recognize the new timestamp after an inventory update.

New Contributor III

nvm, I just added an inventory update at reboot.. thought I had that checked before..alas..