Windows Server 2008 R2 User to Run Scheduled Tasks Under

7,634

Solution 1

Turns out SYSTEM account is the way to go. Another admin here had put some limits on the SYSTEM accounts that were stopping the processes from running. By removing these additional (not present out of the box) security settings everything now works fine.

And the SYSTEM account does not even have password, so it can't expire etc.

Solution 2

In AD you can set "Password Never Expires" (Account Tab) on the service account.

Share:
7,634

Related videos on Youtube

SvrGuy
Author by

SvrGuy

Updated on September 17, 2022

Comments

  • SvrGuy
    SvrGuy over 1 year

    On Windows Server 2008 R2, one must specify a user for each scheduled task to run under.

    We have a policy whereby each domain user must change their password every 30 days.

    This creates a problem, as we have many scheduled tasks that need to run on a large number of servers. When the user associated with a given scheduled task's changes his/her password (as required every 30 days), the tasks all stop working (until you log in and change the password on the task).

    We tried to run the scheduled tasks under the SYSTEM account but this did not work.

    I have thought of creating a new account (SCHED_TASK) that can not log in interactively, is an administrator, and is exempted from the password change requirements.

    This seems very much a "hack" to me. Is there a better way or a built in account of some sort that we should use?

    What is the best practice in this instance?

    • SvrGuy
      SvrGuy over 13 years
      I think of it as a hack because, it seems to me anyway, the #1 use of a scheduled task to perform the same actions, over and over again, no matter what indefinitely. I looked into it further and it turned out the SYSTEM account is the way to go. I just had to tweak SYSTEM permissions to enable the tasks to run et vollia -- success.
  • kralyk
    kralyk over 13 years
    and create your special accounts and maybe even servers under a new OU called "RESTRICTED" or similar. Block inheritance of GPOs to that OU and then set specific GPOs for that OU that you want for those RESTRICTED accounts.
  • kralyk
    kralyk over 13 years
    Also, we use _svc at the beginning of all our service accounts or special accounts like this. That way it is an easy AD search for all of these types of accounts.