We have a Catalina upgrade script that allow users to defer the installation for 1, 2, and 3 hours, checks for free space on the HD and for computer power status (skips laptops not plugged in to PS and systems with less than 20GB usable space). Policy is set as recurring check-in, once every day, executed at 4PM (client-side limitations).
The script runs, log looks good, nothing happens.
I flush the policy on that system, run sudo Jamf policy, I see the same prompts (deferral), and... the upgrade starts happening. Same script.
I have modified the policy, removing the 4PM setting, still nothing. Flushing the policy and running sudo Jamf policy works again.
The installer package works for deployment with no script (execute command, /Applications/Install\\ macOS\\ Catalina.app/Contents/Resources/startosinstall) so I don't think there is something wrong with it.
Is there any difference between policies that are forced manually and those scheduled to run at recurring check-ins? And if yes, what is it?
I can provide the script in question, of course. Any advice will be greatly appreciated.
H.
