Still seeing this issue. I can repeat it on my VM with the latest Apple Update. We need a fix for this ASAP.


We're seeing this with JPC on 10.15.5, deff not resolved as indicated above.
Had this issue today. One of the bosses was about to go on a video call and that message popped up.
As a bandaid, I changed the client-side limitations so it cant check between 8am and 4pm. Looking for a fix.
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.
Any solutions to this? We're getting hammered at least once a week on all our devices. Ventura 13.3.1(a) on and with NO pending updates. Just bloop, there it is interrupting everyone's workday. It actually doesn't restart the computer either, it will just sit there forever if I don't hit OK.
If we hit ok, it reboots the computer. There is no com.jamfsoftware.task.reboot.plist in my Daemons.

Any solutions to this? We're getting hammered at least once a week on all our devices. Ventura 13.3.1(a) on and with NO pending updates. Just bloop, there it is interrupting everyone's workday. It actually doesn't restart the computer either, it will just sit there forever if I don't hit OK.
If we hit ok, it reboots the computer. There is no com.jamfsoftware.task.reboot.plist in my Daemons.

It looks like one of your ongoing polices has user interaction enabled. That message usually comes from the user interaction restart message. I would take a look at the policy history of the affected machines and turn off that message.
It looks like one of your ongoing polices has user interaction enabled. That message usually comes from the user interaction restart message. I would take a look at the policy history of the affected machines and turn off that message.
Yep! i found it. It's a top lvl policy from our central IT office. Off to make a change request ticket. Thanks!
I know this is an old thread but wanted let everyone know it seems the issue has returned. Our devices are stuck in an endless reboot loop.
The only way to resolve the issue was to start the problem computer in targeted disk mode and delete the com.jamfsoftware.task.reboot.plist file from libray/launchdaemons/ folder. Very annoying and frustrating.