New
#1
Scheduled Task history indicates task completed successfully but....
Hi,
New here. I'm using a Scheduled Task to fire a very simple bat file that pulls, compresses and pushes a set of files to a different network directory. The bat file runs fine manually. On a networked desktop I have set up the task to run at about 5am est (waking the machine), as highest authority, when connected to the network, even when user is logged off and such. The task history tab shows 'Action complete' and 'Task complete' as anticipated but there are no new files (or the log that is created) as expected. I've verified the paths in the bat file. I'm confused about the "history" interpretation.
If the task/action complete successfully - what exactly does that mean?! As I mentioned - I can run the file manually with success - the files are completed and exist. It seems when the machine is logged off and asleep - it will wake up, run 'something' and show success.
Any suggestions to help trouble shoot are greatly appreciated. I wanted to run the task 'at logoff' but seems that is not readily available due to possible corruption/hanging and preventing that type of trigger from happening. Logon may become my option next - I just didn't want to stress the network in anyway if everyone is at once - but it is actually a very small office of users.
Sorry for the long post.
John