Our Macs all reboot when a new MacOS patch comes out. We've had JAMF pro for over a year and I don't think this started till 10.14.1. Our users get a pop up saying 'Updates were installed and the system needs to reboot in 5 minutes'. Oddly enough my machine got the pop up and it didn't install the update.
After talking with JAMF support when this happened on 10.14.2 we added restart options to NOT reboot if a user was logged in. That apparently did nothing.
Any other suggestions?
@nategraham Do these happen to be newer Macs with the T2 chip? There was some chatter in the #mojave MacAdmin Slack about this when 10.14.3 was released. Apparently, if there is an update for BridgeOS on the chip it doesn't play well with restart commands or prompts following an update. Some users may even receive a message to fully shut down their Mac if you run
softwareupdate -i -a vs just a restart.
There's a similar bug/quirk in the normal GUI, too. If you have a MBP with Touch Bar (T1 or T2 chip) and click "Download and Update" from System Preferences, the 10.14.3 update downloads, but there is no prompt to reboot. You have to manually click the Install/Update button again in System Preferences, and then the Notification Center alert appears saying an update will restart the Mac with a 60 second countdown.
According to JAMF support, it's a known bug:
"PI-006540 Deploying a software update policy to a macOS computer reboots the computer even if "Do Not Restart" is selected from the Restart Options pop-up menu."
It's listed here as well: https://www.jamf.com/jamf-nation/my/products/known-issues
We got that as well... Unfortunately it was at the exact same time as we pushed a corporate wide update policy that rebooted the entire company in the middle of the day...
Jamf support got a blast from us that day.
After all the investigations and back and forth with support they just eventually created the known issue article that you see above and called it a day.
I'd LOVE some update on that if anyone from Jamf is reading this. It's keeping me from executing the update policy I want and forcing all our updates to be manual which is a MASSIVE pain.
If you want to put in place a quick fix while this PI is solved, the problem is due to a LaunchDaemon that The JSS is not deleting after the restart.
Go to /Library/LaunchDaemons and delete the jamf reboot plist and that will fix the issue.
If it’s happening on a lot of machines you can create a script that deletes that file if it exists and stick it in a policy :)
Hope this helps!
Has there been any movement on this?
We are seeing a similar issue, the 5 min reboot pops up, and reboots the mac outside of our reboot window.
We even have the reboot payload set to 60minutes, but it always gives a 5min.
this is not affecting all users, we have about 200 macs but only a couple users seeing this issue.
Our team is also experiencing this issue, users machines are being rebooted and seeing a 5 minute warning message, even when no reboot payload is configured in a policy. We've configured an explicit "Do not restart" in our policy, but the behaviour remains.
Are there any updates on a resolution for this issue, or workaround?
My hosts that are impacted by this PI only have:
In their /Library/LaunchDaemons directory besides other non-JamF plists. I can't seem to find the one you reference with reboot in the filename.
Looks like this issue has finally been solved in 10.14!
"[PI-006540] Fixed an issue that caused a computer to reboot when running Software Update even if "Do Not Restart" is selected from the Restart Options pop-up menu."
You all should transition to a "forked" restart. This method utilizes a launch daemon to run the "jamf reboot" command. The use of a launch daemon is necessary so that the machine checks into Jamf after the daemon is loaded. If you simply ran the "jamf reboot" command, an inventory update would not have time to run to completion.
#!/bin/sh # Create restartcomputer.sh echo > /tmp/restartcomputer.sh '#!/bin/bash #Restart Computer with jamf reboot command sudo /usr/local/bin/jamf reboot -minutes 1 -background && exit 0' # Create and load a LaunchDaemon to fork restart echo "<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>com.company.restart</string> <key>UserName</key> <string>root</string> <key>ProgramArguments</key> <array> <string>sh</string> <string>/tmp/restartcomputer.sh</string> </array> <key>RunAtLoad</key> <true/> </dict> </plist>" > /tmp/restart.plist sudo chown root:wheel /tmp/restart.plist sudo chmod 755 /tmp/restart.plist sudo launchctl unload /tmp/restart.plist sudo launchctl load /tmp/restart.plist exit 0
Simply change the minute flag in my "jamf reboot" command to customize when you want the machine to restart. Then create a policy with jamf helper message to notify the user before the launch daemon is placed.
I have exactly the same problem today. Just in 30 mins I got five pop-up windows "Updates were installed and the system needs to reboot in 5 minutes". If I click OK, my MacBook Pro (Catalina 10.15.7, 2019) will reboot in 5 mins. I have read through all the posts here, seems no solution. BTW, I only have three Jamf files: com.jamf.management.daemon.plist; com.jamfsoftware.jamf.daemon.plistl; and com.jamfsoftware.task.1.plist. Worked with Apple IT team today, no succeed in 40 mins.