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).
Additional Expert Help:
Be sure to check our Answer FAQ for more expert advice.
For faster answers, visit ITKnowledge Exchange.
Dig Deeper on Windows client management
Related Q&A from Serdar Yegulalp
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
Corrupt Windows user credentials can cause problems at login, but that's not the only thing that can interfere with a Windows user profile. Continue Reading
This week, our expert answers a question on mounting a disk volume as a read-only Windows disk partition, as in Linux. Just don't do it by accident. Continue Reading