[quote=Richard H.]Your only issue is if the password changes you will need to change it on all the machines, which is why I suggest that you use a local account or a service account whose password expiry is long.
Just as a point of reference, the tcLib UDF library has functions that make this situation very easy. If you have a list of systems, you can get a list of tasks from each system with one command, use a For/Next to enumerate each task, checking an array value for the presence of a particular user id, and - if found, use the SetCred UDF to change the credentials.
When we ran into this situation at my last job, the guys were crying that changing the sched-task account on 400 servers across 5 sites would take a week of work. With about 30 lines of code - most to enumerate domain computer accounts, filter out the workstations, and then enumerate the individual tasks, I had all tasks that used the task-sched account updated to use the new-task-sched account and password in less than an hour. Not a single task event was impacted!
The SchTask UDF is primarily designed to DEFINE a task event. It's quick, easy, and effective for this. The tcLib package is designed to MANAGE task events. It's simple, once you get the hang of the multiple UDFs, and very effective for analyzing and modifying task events.
Glenn
_________________________
Actually I
am a Rocket Scientist!
