![]() ![]() So far, I was under the impression that trigger at X, then repeat every 10 minutes is just a needlessly complicated way to write trigger at every xx:x0 in Task Scheduler.Īpparently, it isn't. This problem only seems to affect tasks with the Repeat task every. I know this isn't great for schedules that are "weird" but works fine for things that we want to run every 3 minutes or whatever. This works after restarts just like you would expect. Create a one time schedule that runs indefinitely. The Next Run Time column shows that it should run but doesn't.īesides creating two triggers, one that starts in the future and another that starts on reboot (which we don't want to do since some tasks should only run at specified times), is there a better way? This seems to be a bug. Now the start time is in the past and it won't run. So we had to schedule it to start in the future. In Server 2016 schedules that start in the past don't run. ![]() The task would start at its next scheduled time. In Server 2012 we would schedule the task to start at 1200AM of the current day (so a time in the past) and reoccur every X minutes. We have built a 2016 server to replace it and as I move tasks to the new server I have run into an issue. ![]() We have a 2012 server that has about 20 scheduled tasks that are used for monitoring. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |