I have scheduled a task to run a SSIS job using the Task Scheduler (TS). It is configured to run as a User who belongs to the Admin group.
The security is \"Run wh
Follow like this:
You might find in sig606's solution that the "Add User or Group" is greyed out in Administrative Tools->Local Security Policy->Local Policies->User Right Assignment->Log on as a batch job, Local Security Setting tab. If that's the case, you need to check your Group Policy in AD. A good reference is here.
Basically on your DC, Administrative Tools->Group Policy Management->Computer Configuration->Policies->Windows Setting->Security Settings->Local Policies->User Rights Assignment->Log on as a batch job, edit and add your user there.
Try storing the password. If the user isn't logged in and the password isn't stored there may be no proper authentication. If its a domain user, you can also try creating a local user whose password never expires.
When I setup tasks to "run whether user is logged on or not", I take this approach:
I create a user on that computer that is a member of no groups. This user is the designated task scheduler user. Open the Local Security Policy and grant that new user "Log on as batch job" permission. If you do not, you'll get this error: "This task requires that the user account specified has Log on as batch job rights." Specific instructions on how to set that permission are here: http://power-programming.co.uk/post/2010/11/18/Task-Scheduler-This-task-requires-that-the-user-account-specified-has-Log-on-as-batch-job-rights.aspx
Create the task in the Task Scheduler. Select the "Run whether user is logged on or not" radio button. Check the "Do not store password" checkbox. Check the "Run with highest privileges" checkbox. Assign the task to run under the new user account.