Interestingly, the 64-bit version of our application runs fine, even if user is logged out!
A couple of our customers using the 32-bit version of our application on Windows 7 machines are complaining that they need to be logged in all the time in order for their scheduled tasks to run successfully.
Is this "by design" or a bug in Task Scheduler 2.0?
OS: Windows 7 64-bit
Option: "Run only when user is logged on" is NOT checked
Application is not accessing any remote servers...only local resources