Task Scheduler Success on 2008 R2 but failure on 2012 R2

Question

Hi
I have currently got an issue with a Scheduled Task. It does not appear to run and returns a Last Run Result of (0x1).
So I went back to basics and created a simple task and compared between 2008 R2 and 2012 R2. On 2008 R2 the task completes and returns (0x0), on 2012 R2 the task returns (0x1).
The Service Account that runs the task is a member of the Administrators Group on both servers.
The task is to run a batch file that outputs the content of C:\ to a file called list.txt.
@ECHO OFF
DIR C:\ > C:\Temp\list.txt
Options that are selected are as follows:
Service Account set to Domain Account (Password is correct);
Run whether user is logged on or not;
Run with highest privileges;
No Trigger set (task is run by right clicking);
Action is Start a program (Program/script = TestScheduleTest.cmd, Start in optional = C:\Temp);
Start the task only if the computer is on AC power;
Stop if the computer swtiches to battery power;
Allow task to be run on demand;
Stop the task if it runs longer than 3 days;
If the running task does not end when requested, for it to stop.
Any ideas why on a 2012 R2 this would fail?
Regards

Answer 1

I would recommend referring to that: https://social.technet.microsoft.com/Forums/windowsserver/en-US/57c65328-d8c8-4e13-9b51-e017ae6c298c/task-scheduler-returns-0x1-code-when-run-whehter-user-is-logged-on-or-not-options-selected?forum=winserverManagement
Mainly check that the account you use to run the scheduled task has the required privileges to run it (You can running the script with
runas option in CMD and check if you get errors). Also, it might be possible that the batch file requires a privilege elevation.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile