Return to Answer

Ok this answer doesn't explain how to get your tasks to schedule on a fixed UTC time but it might explain why you may need to look for a third party task scheduler. Windows task scheduler does not properly support summer time changes. SVR2012 didn't, SVR2016 didn't and SVR2019 definately doesn't. With SVR2016 you can set the 'run missed task option' to get around it, but SVR2019 doesn't work even if you set the option. With SVR2019 once BST change has occured, it seems all scheduled tasks for the next 24 hours are disabled and a reboot of windows is required to enable them immediately.

Ok this answer doesn't explain how to get your tasks to schedule on a fixed UTC time but it might explain why you may need to look for a third party task scheduler. Windows task scheduler does not properly support summer time changes. SVR2012 didn't, SVR2016 didn't and SVR2019 definately doesn't. With SVR2016 you can set the 'run missed task option' to get around it, but SVR2019 doesn't work even if you set the option. With SVR2019 once BST change has occured, it seems all scheduled tasks for the next 24 hours are disabled and a reboot of windows is required to enable them immediately.

• update * server 2019 v1809 ( os build 17763.2237 ) may have fixed task scheduler.

Ok this answer doesn't explain how to get your tasks to schedule on a fixed UTC time but it might explain why it's not worth bothering. Windows task scheduler doesn't appear to support summer time changes. SVR2012 didn't, SVR2016 didn't and SVR2019 definately doesn't. With SVR2016 you can set the 'run missed task option' to get around it, but SVR2019 doesn't work even if you set the option. With SVR2019 once BST change has occured, no more scheduled tasks run until you either create a new task, or reboot windows. If you want something that supports summer time changes you will probably need a different task scheduler to the windows one. One thing i have yet to try is fiddling with the option to support previous operating systems but i am not confident that will change anything. I would like to know if chron in debian suffers the same problem.

Ok this answer doesn't explain how to get your tasks to schedule on a fixed UTC time but it might explain why you may need to look for a third party task scheduler. Windows task scheduler does not properly support summer time changes. SVR2012 didn't, SVR2016 didn't and SVR2019 definately doesn't. With SVR2016 you can set the 'run missed task option' to get around it, but SVR2019 doesn't work even if you set the option. With SVR2019 once BST change has occured, it seems all scheduled tasks for the next 24 hours are disabled and a reboot of windows is required to enable them immediately.

Windows task scheduler doesn't appear to support summer time changes. SVR2012 didn't, SVR2016 didn't and SVR2019 definately doesn't. With SVR2016 you can set the 'run missed task option' to get around it, but SVR2019 doesn't work even if you set the option. With SVR2019 once BST change has occured, no more scheduled tasks run until you either create a new task, or reboot windows. If you want something that supports summer time changes you will probably need a different task scheduler to the windows one. One thing i have yet to try is fiddling with the option to support previous operating systems but i am not confident that will change anything. I would like to know if chron in debian suffers the same problem.

Ok this answer doesn't explain how to get your tasks to schedule on a fixed UTC time but it might explain why it's not worth bothering. Windows task scheduler doesn't appear to support summer time changes. SVR2012 didn't, SVR2016 didn't and SVR2019 definately doesn't. With SVR2016 you can set the 'run missed task option' to get around it, but SVR2019 doesn't work even if you set the option. With SVR2019 once BST change has occured, no more scheduled tasks run until you either create a new task, or reboot windows. If you want something that supports summer time changes you will probably need a different task scheduler to the windows one. One thing i have yet to try is fiddling with the option to support previous operating systems but i am not confident that will change anything. I would like to know if chron in debian suffers the same problem.