Changing user password breaks task scheduler

[Alan Ramsey]

I know that I have to specify my password when I set up a task in the
XP scheduler. Since I am on a corporate network - and I want the
process to run when I might not be logged in - that is fine. However,
when I change my password - as I have to, every so often, at logon
time - why on earth can't Windows update the password on all of my
scheduled tasks?

 

[Guest]

Suppose that the reason you were changing your password was that someone else
knew it, and you did not want them to. If they had created a task that used
your credentials (remember that this task may even be set up on a different
computer in a corporate network, so you may not know about it), and windows
automatically changed the passwords for that task, they would still be able to
execute it as you. Thus, this behaviour is yet another example of how you
often have to trade convenience for increased security. If you could
completely trust everyone, you wouldn't need any passwords at all (or locks on
your doors, either).

It could have been made so that when you changed your password, it would ask
you about each task, and you could then confirm the password change on the
tasks, too (at least for tasks on the machine you are currently on).

|I know that I have to specify my password when I set up a task in the
|XP scheduler. Since I am on a corporate network - and I want the
|process to run when I might not be logged in - that is fine. However,
|when I change my password - as I have to, every so often, at logon
|time - why on earth can't Windows update the password on all of my
|scheduled tasks?

 

[Alan Ramsey]

If my password had become compromised I'd probably have more to worry
about than a scheduled task. In any case, Windows is set up is other
areas so that I can *choose* my level of security. The problem of a
rogue scheduled task is IMHO low risk.

If I manually change my password then surely the system should prompt
me with an option "Do you want to update passwords for scheduled tasks
[on this machine]"? It could even give appropriate risk warings.
Without that feature, task scheduler is a REAL pain in the butt.

It is not an example of trading convenience for security - it is an
example of poor programming.