I have a number of tasks that I schedule to run on our server every morning. I had some problems with the batch files executing when it was setup to run whether or not the user was logged in so my scripts are setup to run only when the user is logged in. I run into a problem on Saturdays and workweek holidays when the user is NOT logged in for a variety of reasons.
The user the task is trying to run under is the administrator login and has full permissions.
For the last few months I've had the scripts set to run only when the user is logged in which is fine 90% of the time. I'm getting tired of adjusting my scripts because they did not run the previous day because the user was not logged in. The research I have done so far has indicated that there is a problem with Windows Server R2 SP1 that will not allow the tasks to run using the setting that will log the user in if it does not happen to be logged in.
My research has uncovered a number of "recommended solutions". I've seen information about adjusting permissions on cmd.exe as well as "patches" from Microsoft for a known issue.
The task scheduler does not indicate an error when the script fails to launch when it is set to "run whether users is logged in or not". The task simply says "running" and it appears in the running processes in the task list but never gets to step #1 of the script.
Please help...my current fallback is to develop "Monday scripts" so I can setup scripts to run to pull system statistics for Friday using TODAY-3 for a date instead of my TODAY-1 I use for tasks launched daily.