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 client management
Related Q&A from Serdar Yegulalp
This week, our expert answers the question of how to get DVD data off a disc, even if the user's PC doesn't have an optical drive. Continue Reading
This week, our expert answers a question on how to connect a phone or tablet to a USB drive with a micro-USB connector. Continue Reading
Open source and free suites such as LibreOffice and OpenOffice could save organizations money, but not effort in comparison with Microsoft Office. 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.