New answers tagged

2

If you run Task Scheduler as Administrator, the option to Change User or Group will be available. There you can set the task itself to run as a non-privileged group.


0

My solution (noted here to give others help in addition to the accepted answer): The task used to run under a local user. Run whether user is logged or not ticked; Do not store password not ticked. Everything was OK until we renamed the machine - I then had to reassign the user which the job runs under to be the same user - but under a different computer.


0

I realize this question has already been answered with a perfectly good resolution that is native to Windows and thus should be the most compatible, and I agree completely. I also wanted to say that I disagree with @splattne's comment (but not his actual answer) -- that the resolution in the other referenced thread deserves the credit. That answer involves ...



Top 50 recent answers are included