I have 25 servers that have a scheduled task that runs at 7:00. Most of them
run without fail every night. I have a couple that will run one night and
won't run the next. I've checked the event logs and nothing out of the
ordinary shows.

Its not that the job within the scheduled task doesn't run. Example: The
task ran at 7:00 on 10/20/06, as it was supposed to. You look at it at about
8:00 on 10/23/06 and it shows last run time as 10/20/06 at 7:00.

This is driving me nuts. I can't see any explanation as to why it will run
one night but not the next.

"Rob" <Rob@discussions.microsoft.com> wrote in message
news:7418611E-6888-4ABC-8C47-E5244EB30915@microsoft.com...
This usually happens when the task does not finish, e.g. while
it's waiting for user input. It would be helpful if you told us
exactly what the task is supposed to do.

All the task does is start a remote desktop session that, in turn, runs a
batch file. If the task doesn't finish, I at least get an indication that it
started. What I'm seeing is that the task never starts.

"Pegasus (MVP)" wrote:

Instead of running the Remote Desktop session directly,
embed it in a batch file like so:

@echo off
echo %date% %time% Start of RDP >> c:\test..txt
mstsc /v:.....
echo %date% %time% End of RDP >> c:\test..txt

Now examine c:\test.txt to see when the task started and
ended. You should also examine the log file maintained
by the Task Scheduler.

"Rob" <Rob@discussions.microsoft.com> wrote in message
news:90A98E18-DA15-4984-95D6-305B3AEB0B78@microsoft.com...

You might have better luck using this tool.

http://www.sysinternals.com/Utilities/PsExec.html

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Rob" wrote:
| All the task does is start a remote desktop session that, in turn, runs a
| batch file. If the task doesn't finish, I at least get an indication that
it
| started. What I'm seeing is that the task never starts.