It is the password changes that will kill me. Assume I set up an identical task on 700 servers. Then 90 days later, I change the local account password on all 700 servers, and that account is the one under which each scheduled task runs. Now I have 700 broken scheduled tasks and my brainiac co-workers will be thumbing their noses and laughing at my plight.

IF (<-- note big if) all NT/W2K/W2K3 servers running IE 6 have effectively the same task scheduler, I could probably put together a process to change the password on one server, then push the task file to all servers. Anyone tried anything like this?

NMM