I'm testing out a policy that just has the machine install updates from it's default software update server, which is just apple, we don't host one ourselves.
I have the restart options to restart immediately if no one is logged in, and if a user is logged in, I have the delay set to 60 minutes, with Start the restart timer immediately checked off.
Under User Interaction, I have a restart message set to:
"This computer has applied updates and needs to restart. It will restart in 1 hour. Please save anything you are working on."
So my test machine was on 10.14.3, meaning 10.14.4 would be applied upon running the policy. The machine checks-in, runs the policy, then I get a window that says updates have been applied, the machine will restart in 5 minutes.
Where is it getting those settings, and why is it ignoring my delay settings and custom restart message?
Apple has gotten very heavy handed with their updates in my opinion. We noticed the last few have just restarted after install. Our post flight script wasn't running and no prompting to the user. We finally started trying to tell the user that the restart will occur prior to the installation, but they do not read the dialogs, so...
If you take your package and run it in the terminal with
sudo installer -pkg <path to package> -target /
Does the machine try to restart immediately without you doing anything. That has been my experience with the new security updates. No warning and the only thing that really stops it or slows it down is a Terminal window running it seems. If that does just force a restart, then I do not believe Jamf can stop it. Apple seems to be doing the restarts differently now.
I am also seeing this issue - and only appears to have started since we updated to JAMF Pro 10.13. Occurs on both High Sierra and Mojave mac devices. Custom message is not displayed AND default message advises users to log off rather than restart, which then results in the machine eventually rebooting at logon prompt.