scheduled task change -- why type password twice?

[Tim Hanson]

hi,

i understand the wisdom of having a person type a password twice when
entering or changing it, but why require the user to enter the
password twice when changing attributes of a scheduled task? are we
allowed to enter an incorrect password?

cheers,

Tim Hanson

 

[Pegasus \(MVP\)]

It's standard practice to make you enter a blind password
twice, to protect you against accidental mistyping.

 

[Tim Hanson]

It's standard practice to make you enter a blind password

twice, to protect you against accidental mistyping.

Makes sense, as I posted, when you change your password (else you risk
locking yourself out), but why not check the password (once) in this
case when entered and complain if it's wrong??

Or would you also propose we enter passwords twice every time we log
in? [please pardon my impish sarcasm ]


p.s. Btw, why don't we need to change a password when we change the
schedule of a task? (I guess this is deemed less dangerous than
changing the program run or it's parameters.)

p.p.s. And why does the task scheduler occasionally forget to run a
task (this happened to me last night: left a task scheduled to run
once at 8pm; checked this morning; it hadn't run; the scheduled task
window showed next run time 8pm last night; i hit f5 and this changed
to "never"; sigh.)

 

[Pegasus \(MVP\)]

See below.

Makes sense, as I posted, when you change your password (else you risk
locking yourself out), but why not check the password (once) in this
case when entered and complain if it's wrong??

The Task Scheduler checks the password at run time, not at
schedule time. Maybe Microsoft did it so that you can enter
a password that is invalid now but will be valid at run time.
Maybe it was done just to annoy you.

Or would you also propose we enter passwords twice every time we log
in? [please pardon my impish sarcasm ]


p.s. Btw, why don't we need to change a password when we change the
schedule of a task? (I guess this is deemed less dangerous than
changing the program run or it's parameters.)

Standard security feature. Tasks often run with elevated privileges, and
you don't want every Tim, Dick and Harry to muck around with them.

p.p.s. And why does the task scheduler occasionally forget to run a
task (this happened to me last night: left a task scheduled to run
once at 8pm; checked this morning; it hadn't run; the scheduled task
window showed next run time 8pm last night; i hit f5 and this changed
to "never"; sigh.)

It's difficult to perform trouble-shooting with a one-off event.