The Task runs a BAT file that calls a VBS file on a network drive which in turn automates populating a Word document. Microsoft Task Scheduler does not work properly when the Run whether user is logged on or not is checked. The problem happens even if I am logged in, the Windows Task Scheduler that just checking the Run whether user is logged on or not causes the problem no matter whether I am logged in or not. How do I properly configure a scheduled task to run when not logged in?
If the task doesn’t work properly even when the user is logged in, it doesn’t seem to be a problem with the definition of running whether the user is logged in or not. Check the following:
- If you call the BAT manually from CMD, does it run correctly?
- Is it possible to edit the initial BAT file to output a simple test line to a text document just to see if the command is even triggered?
- What other settings have you enabled? (What triggers and what should Windows Task scheduler do if trigger was matched but a previous run isn’t yet finished) etc.
- Under which user credentials are you running your task? This user needs access to all resources such as network folder.
- Replace all network folders letters (like G:) with full UNC names (like \\servername\sharedname\…)