J
Jose
Flightless Bird
On Mar 15, 12:18 pm, J Tinsby <n...@present.com> wrote:
> On Mon, 15 Mar 2010 04:46:53 -0700 (PDT), Jose <jose_e...@yahoo.com>
> wrote:
>
>
>
>
>
> >Check the Task Properties, Settings tab and check the box to Wake the
> >computer to run this task.
>
> >If the system is in Stand By and the Task is configured properly, it
> >will wake the computer and run the task. Any task.
>
> >There will will be info in the Task log, and in the Auslogics log.
> >This is what I see when I used set Auslogics to run a task a few
> >minutes in the future, then I adjusted the Task Properties by hand to
> >Wake the computer to run the task (you can't set this property for the
> >task using Auslogics) and put my computer in Stand By - then waited 3
> >minutes:
>
> >"Auslogics Boost Speed Disk Defrag Console
> >Defragmentation.job" (cdefrag.exe)
> > Started 3/15/2010 7
2:12 AM
> >"Auslogics Boost Speed Disk Defrag Console
> >Defragmentation.job" (cdefrag.exe)
> > Finished 3/15/2010 72:28 AM
> > Result: The task completed with an exit code of (0).
>
> >If you do not set the Wake the computer to run this task box in the
> >Task Properties by hand, the task will never come out of Stand By to
> >run. If you check the box, the task will wake the computer and run.
>
> >If the computer is turned off the task will of course not run.
>
> >If the computer is in Hibernate, the task may or may not run depending
> >on your hardware. That has nothing to do with Auslogics or Task
> >Scheduler.
>
> >You should leave the Task credentials and NT AUTHORITY\SYSTEM. That
> >account has no password.
>
> Hello Jose ,
>
> Well I am hoping to get the TS to run the defrag when the machine is
> on standby , yes it is set to wake up the machine to run the process.
>
> As far as Auslogics they promised twice to answer my questions but
> never did, they are a bit of a disappoinment as far as I am concerned.
> If they don't have tech support for a free program they should just
> say so and not lie and say "we'll get back to you in 24 to 48 hours."
>
> Maybe I am expecting the TS to run the program EXACTLY AT THE TIME I
> HAVE IT SET FOR................. maybe for whatever reason it won't
> start then but many minutes later. But if the machine is on standby
> it's not doing anything else I would think it would start relatively
> quickly.
>
> J T
In that case, remove Auslogics from the equation and just test your ST
mechanism.
Create a new ST that runs something basic like cmd.exe. Configure to
start next week, then run it manually and see if a command window
opens immediately.
You will see the command window open if the ST credentials are the
same as your login.
If you set the ST to use NT AUTHORITY\SYSTEM or some other account
just for STs, you will see in running in Task Manager under that
account user name. SYSTEM for NT AUTHORITY. All is good!
When all that is working, change the task to run a few minutes in the
future and engage Stand By and wait.
No matter what the credentials, the ST will awaken the system and
either be showing you a command window or you will be looking at your
desktop and be able to see cmd.exe running in Task Manager. If your
monitor switches off you may need to move (not click) the mouse or
press a keyboard key to turn your monitor back on, but the cmd task
should start.
If that doesn't work, Auslogics will never work either. If it doesn't
work, it is broken, so now you should fix it the simple task. I just
tried it all like that here and with Auslogics again.
I also do not understand why (?) you keep saying S-3 standby. Are you
clicking Start, Turn Off Computer, Stand By or are you engaging Stand
By in some other fashion?
Does your power button blink when you are in Stand By?
If your task does not get you out of Stand By, can you click the mouse
to wake the machine up?
Please do this too:
Click Start, Run and in the box enter:
msinfo32
Click OK, and when the System Summary info appears, click Edit, Select
All, Copy and then paste the information back here.
There will be some personal information (like System Name and User
Name), and whatever appears to be private information to you, just
delete it from the pasted information.
> On Mon, 15 Mar 2010 04:46:53 -0700 (PDT), Jose <jose_e...@yahoo.com>
> wrote:
>
>
>
>
>
> >Check the Task Properties, Settings tab and check the box to Wake the
> >computer to run this task.
>
> >If the system is in Stand By and the Task is configured properly, it
> >will wake the computer and run the task. Any task.
>
> >There will will be info in the Task log, and in the Auslogics log.
> >This is what I see when I used set Auslogics to run a task a few
> >minutes in the future, then I adjusted the Task Properties by hand to
> >Wake the computer to run the task (you can't set this property for the
> >task using Auslogics) and put my computer in Stand By - then waited 3
> >minutes:
>
> >"Auslogics Boost Speed Disk Defrag Console
> >Defragmentation.job" (cdefrag.exe)
> > Started 3/15/2010 7
2:12 AM> >"Auslogics Boost Speed Disk Defrag Console
> >Defragmentation.job" (cdefrag.exe)
> > Finished 3/15/2010 7
2:28 AM> > Result: The task completed with an exit code of (0).
>
> >If you do not set the Wake the computer to run this task box in the
> >Task Properties by hand, the task will never come out of Stand By to
> >run. If you check the box, the task will wake the computer and run.
>
> >If the computer is turned off the task will of course not run.
>
> >If the computer is in Hibernate, the task may or may not run depending
> >on your hardware. That has nothing to do with Auslogics or Task
> >Scheduler.
>
> >You should leave the Task credentials and NT AUTHORITY\SYSTEM. That
> >account has no password.
>
> Hello Jose ,
>
> Well I am hoping to get the TS to run the defrag when the machine is
> on standby , yes it is set to wake up the machine to run the process.
>
> As far as Auslogics they promised twice to answer my questions but
> never did, they are a bit of a disappoinment as far as I am concerned.
> If they don't have tech support for a free program they should just
> say so and not lie and say "we'll get back to you in 24 to 48 hours."
>
> Maybe I am expecting the TS to run the program EXACTLY AT THE TIME I
> HAVE IT SET FOR................. maybe for whatever reason it won't
> start then but many minutes later. But if the machine is on standby
> it's not doing anything else I would think it would start relatively
> quickly.
>
> J T
In that case, remove Auslogics from the equation and just test your ST
mechanism.
Create a new ST that runs something basic like cmd.exe. Configure to
start next week, then run it manually and see if a command window
opens immediately.
You will see the command window open if the ST credentials are the
same as your login.
If you set the ST to use NT AUTHORITY\SYSTEM or some other account
just for STs, you will see in running in Task Manager under that
account user name. SYSTEM for NT AUTHORITY. All is good!
When all that is working, change the task to run a few minutes in the
future and engage Stand By and wait.
No matter what the credentials, the ST will awaken the system and
either be showing you a command window or you will be looking at your
desktop and be able to see cmd.exe running in Task Manager. If your
monitor switches off you may need to move (not click) the mouse or
press a keyboard key to turn your monitor back on, but the cmd task
should start.
If that doesn't work, Auslogics will never work either. If it doesn't
work, it is broken, so now you should fix it the simple task. I just
tried it all like that here and with Auslogics again.
I also do not understand why (?) you keep saying S-3 standby. Are you
clicking Start, Turn Off Computer, Stand By or are you engaging Stand
By in some other fashion?
Does your power button blink when you are in Stand By?
If your task does not get you out of Stand By, can you click the mouse
to wake the machine up?
Please do this too:
Click Start, Run and in the box enter:
msinfo32
Click OK, and when the System Summary info appears, click Edit, Select
All, Copy and then paste the information back here.
There will be some personal information (like System Name and User
Name), and whatever appears to be private information to you, just
delete it from the pasted information.