Windows Server Version : 2016
Problem Description :
This is indeed a weird problem I am facing. I have a .bat file that I have scheduled to run every 15 min but it does not start on its own at the scheduled time if I disable and re-enable it. But the moment I update the job (any parameter) it just works fine. But if I disable it and re-enable it again it won't kick start.
There is no problem with the .bat file as it just runs fine when I manually start the job from task scheduler or from the command line.
I have tried following things:
- Give full permissions to .bat file connected folders
- 'Run with highest priority' selected
- Change user to system & administrator
- 'Run whether user is logged on' selected. I cannot have the other option
- 'Configure for' = 'Windows Vista, Windows Server 2008' & 'Windows Server 2016'
- Tried 'Start in' option
- Power settings in Conditions tab (all combination) Selected 'Run task' as soon as possible after a scheduled start is missed'
- Also restarting windows after creating the job (as suggested in some forums)
I am pretty confident that the job setup is fine as I have been using this job for past many years and recently migrated to a new server. This disabling of job is doing something which I am unable to figure out. I am sure some of you have encountered this problem and I am not alone. Any help or clues appreciated. Thanks in advance.