One possible way to get around this is to have a separate account created on that system specifically for running scheduled tasks, one which doesn't require its password to be reset as aggressively but which has the needed permissions to get everything done. (The Task Scheduler has built-in provisions for running a task with different user credentials.) This is the approach I used. If you use a fairly cryptic username and password,...
it should not be susceptible to attack (if that's a concern).
Dig deeper on Windows Operating System Management
Related Q&A from Serdar Yegulalp, WinIT
Frustrated admins have been dealing with extend.dat error messages since Outlook 97. Our expert sheds some light on this all-too-common Outlook error.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.