Good idea.... but that means having a file with a password in plain txt on the LAN?
No, not really
Once the scheduled task has been created it is there forever (as long as it is not a one-time-only task).
You only need to create the task (and set the password) once on each machine.
The password that you create the task as is saved with the job in an encrypted form, so it is not exposed.
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.
You might want to use "/SC ONSTART" rather than a particular time of day.
Use the "/S systemname" option to schedule the task on a remote computer.
Use the "/U" and "/P" parameters to specify the user to connect as (to create the job) and the "/RU" and "/RP" parameters to specify the user that the job will actually run as.
