Hi all,

Every few months I have to change the passwords using the Set Password
button at the Run as field of each jobs in my task scheduler.

Does anyone knows how to automate this boring task if I have about 6 Windows
servers to change?

Thanks
ld

"Desmond Lim" <(E-Mail Removed)> wrote in message news:cis083$hpn$(E-Mail Removed)...
> Hi all,
>
> Every few months I have to change the passwords using the Set Password
> button at the Run as field of each jobs in my task scheduler.
>
> Does anyone knows how to automate this boring task if I have about 6 Windows
> servers to change?
>
> Thanks
> ld

Use VBScript via WSH!
http://groups.google.com/groups?q=script+mstask

Find me via Instant Messenger if you need some
customization of your script. It should be
a small script -- less than 30 lines.

I recently helped out with a major Int. Corporation
in San Francisco to change the pwd in 600 jobs via script.
The running time of the script was 3 minutes. Interacting
with the RunAs feature of Mstask via script is expected
to be slow, since the usernames are validated each time
the AccountInfo is set.

hth,
tlviewer
---------
AIM:YahooIM:tlviewer

"Desmond Lim" <(E-Mail Removed)> wrote in message news:cis083$hpn$(E-Mail Removed)...
> Hi all,
>
> Every few months I have to change the passwords using the Set Password
> button at the Run as field of each jobs in my task scheduler.
>
> Does anyone knows how to automate this boring task if I have about 6 Windows
> servers to change?
>
> Thanks
> ld

You may not need to automate this after all.
If you pay attention to the way Mstask swallows
the password, you will notice that it only stores
one password for every different UserName. It seems that,
but I have no way to be 100% sure, the password is stored
in the system SAM, keyed by UserName.

Since the passwords are classed by UserName, you only
have to change the password once for each different
UserName. If you have 200 jobs, but only 5 different users,
then you only have to change 5 jobs.

The bad news here is that you can't see the Job's UserName
from the GUI, only the creator. If would be a good idea
to change the Job's creator to its UserName, for
all Job's -- that can and should be automated. Also
filtering by UserName can be automated.

hth,
tlviewer