1 of 1 people found this helpful
Thank you for your post. This issue you've come across is a known Microsoft Task Scheduler issue. Essentially what happens is if the task is set to execute on a specific occurrence of a day of the week (4th Wednesday, 2nd Saturday, etc.) or the task is scheduled to execute is a multiple of 7 (7th, 14th, 21st, or 28th), the task will run one week early.
There is currently no fix that Microsoft has provided for this issue. More information related to this problem can be found in the below document.
I hope this helps and sorry for the inconvenience!
That makes sense as I upgraded to 2016 in February..
Thanks for the info. I will reach out to Microsoft to see where they are at with this fix.
Sounds great! Please feel free to update this thread with any information you find out from Microsoft.
Wanted to reach out and give an update here. We found that Microsoft released update, KB4343884, on August 30th that indicates is resolved this issue with the task scheduler. You should be able to deploy this out to your machines and have that bug rectified.
Awesome thanks for the reply, I hadn't reviewed the out of band patches yet.
I have it installed and will report back if I notice any issues on my Friday deployments.
All good! No unexpected deployment on the 14
Thanks again for seeing that in the KB notes!