Task scheduler cannot open batch file when set to run whether user is logged on or not

Question

OS: Windows Server 2008 R2 Enterprise

I am unable to get the Task Scheduler to run .bat files while I am logged off. I have a a production .bat file I want to use, b

Answer 1

I have resolved this problem with help from a contractor who was doing some other work for my institution.

In the properties window for the task, on the Action tab, when creating or editing the action that opens the batch file (in my case test.bat), there is the "Program/script:" field and there is also a "Start in (optional):" field. I previously had the "Program/script:" field containing the full path to the file, ending with the file name, and I had the "Start in (optional):" field null. This configuration appears to work without issue when the task is set to "Run only when user is logged on" in the General tab of the task's properties window. However, this configuration does not work when the task is set to "Run whether user is logged on or not".

In order to resolve the problem, I changed the action so that the "Program/script:" field contained only the file name, not the file path. I put the file path in the "Start in (optional):" field. This configuration works when the task is set to "Run only when user is logged on"! I have tested with the task running on a trigger and also with running it manually.

Answer 2

Not sure if this helps. My issue was using a interactive program (in particular Excel) as well.

Creating the 2 empty folders (Desktop) solved it. Create both even if you are running on x64.

C:\Windows\System32\config\systemprofile\Desktop
C:\Windows\SysWOW64\config\systemprofile\Desktop

I debugged my code and realised the code exited at this line

ExcelFile excelFile = new ExcelFile(directory, filename);

I read this solution somewhere and I cannot find the URL now.

Answer 3

Verifying the following has worked for me:

1) 'Run if user is not logged in' option in Task Scheduler does not work for programs that is interactive mode. Example notepad, clock. Tasks will not run interactively. Make sure your program does not requires any interactive actions.

2)Check the “Start in (optional) “ If your program path is not one of the system paths. You have better to add you program path in it. On the "Program/Script" enter only the name of the program, and enter the path of your script in "Start in".

3)The user account you setup for your program must have permission not only to run your program itself and but also to run all other program that related to your program.

Here is a sample program:

On C:\myprogram\folderOne\test.cmd

date /t >> c:\Temp\testAuto.log
date /t >> c:\temp\testAuto.log
echo ----->> c:\temp\testAuto.log
cls
exit

-Create a Tasks, selecting on General>SecurityOptions "Run whether user is logged on or not" -Enter on Action>Program/script: test.cmd on "Start in" C:\myprogram\folderOne -Run, you might see the cmd windows open and closes very quickly. The testAuto.log file should be in c:\tmp folder.

Answer 4

It might be because you don't have permission. I was facing the same problem and i found the solution like this - Open Task Scheduler right click on your task and than select properties option. In properties click on General tab and then click on 'User Group or User' and select the appropriate user.

Answer 5

Try this as well..

Resolved the "Run whether user is logged on or not" by setting the “Log on as Batch Job” security policy.

Here is details on the setting… https://danblee.com/log-on-as-batch-job-rights-for-task-scheduler/

You may take another approach, but here is the steps… 1) I updated the default domain group policy by adding my admin account (that I fire the task with) to the “Log on as Batch Job” security policy. (Even though ADMIN group is listed, and I am using an admin account) 2) I forced GPUPDATE on the client 3) Rebooted the client 4) Looked at the policy on the client to make sure it made it over from the DC 5) Set the task "Run whether user is logged on or not" 6) Ran the task on demand and it worked creating a PDF file. 7) Logged out and ran the task at scheduled time and it worked creating a PDF file.

Answer 6

I had similar problem, but it was related to the fact that there was a space in the path of my executable batch file. I have removed the space and now it works fine.