How to make schtasks work after the user's password has changed?

Question

On Windows machines, schtasks is a utility similar to cron for scheduling jobs to run on a regular basis.

Problem is, when you define a schtask, you must specify the userid and password of the account to run the job.

Then later, when the user changes his password, that schtask will no longer work. It must be deleted and rescheduled with the new password.

So, how can I setup a scheduled job (via schtasks, at, whatever) that's immune to password changes?

score 3 · Answer 1 · answered Mar 10 '09 at 15:31

3

This doesn't quite answer your question, but a common workaround is to create a user (with appropriate privileges) and use that account solely for executing scheduled tasks.

As the user account is created with a non-expiring password, the sysadmin who creates it should choose an appropriately strong password.

answered Mar 10 '09 at 15:31

teedyay

23,293
19
66
73

Hah, just when I wanted to click "Post your answer"...beat me to it ;-) +1 – RuudKok Mar 10 '09 at 15:32
In a production environment this is general the best practice as well. Regular user accounts can have their permissions changed or revoke, or can be removed or disabled entirely. A service account is much easier to manage, as well as limit the scope of. – David Mar 10 '09 at 15:38

score 1 · Answer 2 · answered Aug 28 '20 at 19:58

1

Just add this to your command:

/RU "NT AUTHORITY\SYSTEM" /RP *

Will run as System and ignore passwords.

answered Aug 28 '20 at 19:58

Jhollman

2,093
24
19

score 0 · Answer 3 · answered Feb 20 '13 at 22:11

There is also a way to update existing tasks. In cmd prompt you would use the following to help you:

schtasks /change /tn TaskName [/s computer [/u [domain\]user /p password]] [/tr TaskRun] [/ru [Domain\]User | "System"] [/rp Password]

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/schtasks.mspx?mfr=true

How to make schtasks work after the user's password has changed?

3 Answers3