What's the best practice for setting up a scheduled job (like a software build) so that it's not tied to a single user?
Our situation is that we need to schedule a job that runs overnight on a Windows 7 box, and we want anyone in our group to make changes or restart the job as necessary (i.e. in case the owner is on vacation or out sick). I can make the files themselves accessible to multiple users, but the problem is the job itself. I'm guessing our security group would balk at a local account with a known password, and our group policy seems to not allow jobs that auto-log-in as a user.