Since upgrading to 6.2.2, when the machine has been rebooted (due to Windows updates) jobs that had successfully completed in the morning and were not scheduled to run again until tomorrow morning were started again. Any suggestions on how to reboot without this behaviour?
Thanks!