![]() So while this happened yesterday, the same issue did not occur on the same device with the same network connection today: However, there are devices where the tasks starts at 20:00 and keeps repeating until 10:00. The tasks starts at 20:00 and the last run is at 07:00. On the device where I took the screenshot, everything is working as expected. ![]() "Run task as soon as possible after a scheduled start is missed" is NOT enabled. "Synchronize across time zones" is NOT enabled. The triggers are defines as shown in the screenshot. The task should run at every full hour from 20:00 (8 pm) to 7:00 (7 am) during the week and every hour on weekends. The behavior is so inconsistent that I could not come up with any logical explanation. Both XCOPY and ROBOCOPY are provide logs and I can use the suggestion to capture stdout/stderr and dig further.įor the reason(s) the jobs take so long, I feel comfortable using the logs to dig further.įor the start time, will change one setting at a time and report back on results.We have an issue where a scheduled task configured by GPO is running out of schedule on some devices. That could explain the longer time, as AppData has a ton of files, but I'm not convinced that explains it completely. I now realize I had excluded AppData for the old computer but included it with the new one. ![]() Each has only 1 command: Backup changes using XCOPY and full (mirror) backup using ROBOCOPY. There are 2 jobs to backup the files under \computer\user to an external (USB) disk. Sorry, didn't mean for anyone to get out their crystal ball :-)Ī reminder this is a personal home computer, not a server or corporate setting. Best to change one thing at a wrote Without knowing what you have in C:\BackupTools\MirrorBackup.cmd I will have to refer to my Magic Crystal Ball, but sadly it has dead batteries at the moment. Will try that first, then move on to "Synchronize Across.". I have noticed "WakeToRun" is disabled for the new computer. For years the jobs started on time, every time and "Synchronize Across." was disabled. That is my experience on the old computer. So I would think, based on what Limitless wrote, I can set the time of the job and it runs at that (local) time. There is no computer-to-computer communication involved.Sometimes they start 3 hours late, sometimes 9 hours late. Since I first wrote I see the start times are not consistently 6 hours late.For example, if a trigger’s start date/time is set to 10am on the 1st February 2020, the task will run once that date/time has been reached according to the computer’s time zone. Thank you all for your Baumgarten wrote have you tried the option Synchronize across time Technology wrote: When Synchronize Across Time Zones is disabled, a trigger’s start date/time is relative to the computer’s time zone. I originally posted this on the MS Community but was asked to post it here, so I am probably in the wrong place. I have no idea what the available tags are, and which ones would be relevant to my issue. Sorry if I entered "tags" that meaningless. Forgot to activate it until today.īonus points if you can also tell me why these tasks took 3 hours to complete when they typically took minutes on the older and MUCH slower computer. I edited it to anonymize the Author (\computer name\account), and UserID. These ran successfully for years on my old computer and I just setup these same tasks on a new one. FYI they make backups for my computer - one for changes and one to mirror all files under \users\folder. This is regarding the home version of W10. Looking for a reason why this might happen. Two scheduled tasks set to start at 11:30pm both started at 5:30am, the next morning.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |