Problem setting up scheduled task

  • Thread starter Thread starter Mike B
  • Start date Start date
M

Mike B

I'm on Vista Ultimate. I'm trying to set up a scheduled task which will copy
a file from within my AppData folder (I'm an Admin, running with UAC on) to
another local user's AppData folder (they're a normal User).

My basic Action in the task is:

Program:
robocopy
Arguments:
"C:\Users\Mike\AppData\Local\Microsoft\Media Player"
"C:\Users\Hesper\AppData\Local\Microsoft\Media Player"
CurrentDatabase_360.wmdb /SEC

I've ticked the "Run with highest privileges" box on the General tab, since
I think that is necessary to copy stuff into another users folder?

I've set this to Trigger on login to my account, but a Condition is that
there should be idle time for 1 minute.

OK. So, when I select this scheduled task and manually hit the Run button
in the scheduler window, it works fine: a cmd window pops up and I see
robocopy's progress in copying the file to completion.

BUT... when I leave this task to self-trigger, things do NOT work out so
well. The file is NOT copied. Nothing ever seems to happen.

In the top panel, under the "Last Run Result" column, it says (0x41325).

So, what gives? Why does this work when I run the task manually, but not
when it self-triggers?

Thanks for any help.

Mike
 
OK, here's an update.

I mentioned that I'd set this scheduled task to Trigger on login to my
account, but also with a Condition that there should be idle time for 1
minute.

So, I tried removing the "idle time" condition, and lo and behold the
scheduled task now runs fine, and copies the file, a short time after I log
in.

So, the question is now: "why doesn't the idle time condition work for me in
this situation"? I have read that "idle time" is always assumed to be
happening when the screensaver is on, whatever the CPU is doing in the
background on other tasks? Is that right?

It seems that my previous task *did* try to trigger on idle time, but for
some reason couldn't complete properly (0x41325 code).

Any idea why this happened?

I am running Diskeeper, which itself looks for CPU idle time and then
defrags during idle time... could that be messing up my scheduled "idle time"
task? I thought not, given that (apparently) the scheduler assumes it's idle
time if the screensaver is on... and the screensaver *does* come on even when
Diskeeper is running in the background.

Thanks for any help.

Mike
 
Seem to be talking to myself here, but never mind.

I seem to be having real problems in getting any scheduled task having an
"idle time" condition to run at all, when I expect it should.

I set up one to run "shutdown /s /f" at 1.30am each day, but only if the
computer has been idle for 15 minutes... but this task has never run
successfully at the appointed time. But when I manually hit the run button
on this task, sure enough the computer shuts down OK -- so no problem with
the command itself.

I suspect that anytime I include an "idle time" condition the task refuses
to run, for some reason.

Any ideas on this?

Thanks,

Mike
 
Back
Top