Windows 2003/Schedule Task failed to start randomly

  • Article

 

Issue: Schedule Task failed to start randomly

image

Cause: There is a Domain Policy defined for “Logon as batch job”, this settings will overwrite all local account’s right.

Repro Step:

1. Create a Schedule Task using local administrator account and password

2. Test run these tasks

clip_image002

3. Define “Logon as batch job” at domain level

clip_image003

4. Run gpupdate /force at Server 2003

5. Once we did apply this policy from Domain, try to run task, it will failed

clip_image004

       Failed with “could not start”

clip_image005

Workaround:

· Include the default administrator account at “Logon as batch job” policy

clip_image006

Reference:

https://technet.microsoft.com/en-us/library/cc755659(v=ws.10).aspx

Log on as a batch job

In Windows 2000 Server, Windows 2000 Professional, Windows XP Professional, and Windows Server 2003, the Task Scheduler automatically grants this right as necessary. The Task Scheduler injects this right for the user into the computer's effective policy immediately after the task is scheduled. If there is a contradictory group policy defining the Logon as a batch job user right, the effective policy settings will be overwritten by the group policy only upon policy refresh.