All of my scheduled tasks that use NT AUTHORITY\system for the run_as are reporting "could not start." The log says:
The attempt to log on to the account associated with the task failed, therefore, the task did not run.
The specific error is:
0x80041314: The task has been configured with an unsupported combination of account settings and run time options.
Verify that the task's Run-as name and password are valid and try again.
Thinking something was corrupted, I deleted one of the tasks and recreated it with an AT command, which by default again set the run_as to NT AUTHORITY\system. When I tried to start the task again I got the same error message as I listed above.
I then set one task to run_as to a regular user (me). The task ran just fine, but that doesn't fix my problem.
The AT service account is configured to use the System account. The System account has not been granted the user right "Deny logon as a batch job" (and by default has the user right Log on as a Batch Job) so I don't think it's a a permissions problem.
The Task Scheduler service, btw, is is set up to log on with the "Local System account". One would think if there were a problem with the system account the service wouldn't start, but that's not the case. The service is set to automatic and starts without incident. Also, the "Allow service to interact with desktop" is checked.
I checked the security event log and this is what's there:
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 529
Time: 9:11:34 AM
User: NT AUTHORITY\SYSTEM
Reason: Unknown user name or bad password
User Name: system
Domain: NT AUTHORITY
Logon Type: 4
Logon Process: Advapi
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Workstation Name: xxxxxxx
Anyone know what's going on? Is there a way to fix this? Are these error messages misleading?