Task Scheduler query

[Delboy]

I have finally got Task Scheduler to create System Restore Points. Why it
stopped, I have no idea. Maybe something to do with the reload recommended
by Packard Bell following DVD R/RW drive. Question: What is "Universal
Time"? Does this mean GMT? (Zulu Time) If so my SRs are due 00.00 British
Summertime (UT not ticked). But since I am an early bird, this now means SR
at next Start Up. No a desperate question, just curious.

--

Delboy

A common mistake that people make when trying to design something completely
foolproof is to underestimate the ingenuity of complete fools.

Douglas Adams

 

[Jon]

I have finally got Task Scheduler to create System Restore Points. Why it
stopped, I have no idea. Maybe something to do with the reload recommended
by Packard Bell following DVD R/RW drive. Question: What is "Universal
Time"? Does this mean GMT? (Zulu Time) If so my SRs are due 00.00 British
Summertime (UT not ticked). But since I am an early bird, this now means SR
at next Start Up. No a desperate question, just curious.

--

Delboy

A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete fools.

Douglas Adams

Now that you've configured it to work correctly, it might help others if you
exported the working task as .xml, opened it up in notepad, and pasted it in
here. I know a number of people have had problems with that partcular
scheduled task, so it would be interesting to see if / how your
configuration differs from the default. (remove any personal details if you
like).

 

[Delboy]

Hi Jon,

Here are my settings (also attached as SR 3day.xml). I think I have set it
to make RPs at 3 day; or ASAP after the trigger (in case I have gone to bed
early).


<?xml version="1.0" encoding="UTF-16" ?>
- <Task version="1.2"
xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
- <RegistrationInfo>
<Source>Microsoft Corporation</Source>
<Author>Microsoft Corporation</Author>
<Description>This task creates regular system protection
points.</Description>
<URI>Microsoft\Windows\SystemRestore\SR</URI>
</RegistrationInfo>
- <Triggers>
- <CalendarTrigger id="1135f611-8faf-40e6-9fe7-deb23224f0b1">
<StartBoundary>2007-06-03T00:00:00</StartBoundary>
<Enabled>true</Enabled>
- <ScheduleByDay>
<DaysInterval>3</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
- <CalendarTrigger id="16a2fa56-feae-455a-8dea-0ab1e6f2212b">
<StartBoundary>2007-06-05T00:00:00</StartBoundary>
<Enabled>false</Enabled>
- <ScheduleByDay>
<DaysInterval>1</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
</Triggers>
- <Principals>
- <Principal id="LocalSystem">
<UserId>SYSTEM</UserId>
<RunLevel>LeastPrivilege</RunLevel>
</Principal>
</Principals>
- <Settings>
- <IdleSettings>
<Duration>PT10M</Duration>
<WaitTimeout>PT1H</WaitTimeout>
<StopOnIdleEnd>false</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>true</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>P3D</ExecutionTimeLimit>
<Priority>7</Priority>
- <RestartOnFailure>
<Interval>PT1M</Interval>
<Count>3</Count>
</RestartOnFailure>
</Settings>
- <Actions Context="LocalSystem">
- <Exec>
<Command>%windir%\system32\rundll32.exe</Command>
<Arguments>/d srrstr.dll,ExecuteScheduledSPPCreation</Arguments>
</Exec>
</Actions>
</Task>

Not that it answers my question :-}. Incidentally, it seems as though
setting Backup & Restore ALSO triggers a RP at the same time although I have
not tested any restorations. Here is a simple test (courtesy of Mike M over
on windowsme.general).

1 put any shortcut on the desktop.
2 create or wait until next SR point.
3 Delete the shortcut made in 1.
4 Restore to SR made in 2.
5 If shortcut reappears, RP & R both successful.

BTW, I mentioned in my OP that following problems with my DVD R/RW drive,
Packard Bell had me re install back to "out of the box" status. Before doing
this, I am half sure I saw a System Scheduled Set Point, but never again
since. Perhaps I imagined it ...

--

Delboy

A common mistake that people make when trying to design something completely
foolproof is to underestimate the ingenuity of complete fools.

Douglas Adams

 

[Jon]

Hi Delboy

Thanks for that. Imported it here sucessfully. Looks like you've made some
interesting changes, compared to the original task.


I see you've unchecked all the conditions on the conditions tab
eg the 'on idle' condition (which I have a feeling may well be the culprit)
and the 'start only when on ac power' setting.

and you've also enabled the 'If the task fails, restart every..' every
minute for once a minute for 3 minutes' which probably helps too.

That may well help other people who are having problems with the task.



Re your UTC question, this is pasted from the Task Scheduler 'Help' section
regarding 'Triggers' which may help to resolve that question.....

"Check the Universal check box to make the time relative to Coordinated
Universal Time (UTC) instead of the time zone that is set on the computer
that runs the task. Use the Universal setting when you want to coordinate a
set of tasks to run simultaneously in multiple time zones. "

So I suppose the task would run at the same time, regardless of whether
you've switched to a different time zone in the course of your travels.

--
Jon

Hi Jon,

Here are my settings (also attached as SR 3day.xml). I think I have set
it
to make RPs at 3 day; or ASAP after the trigger (in case I have gone to
bed
early).


<?xml version="1.0" encoding="UTF-16" ?>
- <Task version="1.2"
xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
- <RegistrationInfo>
<Source>Microsoft Corporation</Source>
<Author>Microsoft Corporation</Author>
<Description>This task creates regular system protection
points.</Description>
<URI>Microsoft\Windows\SystemRestore\SR</URI>
</RegistrationInfo>
- <Triggers>
- <CalendarTrigger id="1135f611-8faf-40e6-9fe7-deb23224f0b1">
<StartBoundary>2007-06-03T00:00:00</StartBoundary>
<Enabled>true</Enabled>
- <ScheduleByDay>
<DaysInterval>3</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
- <CalendarTrigger id="16a2fa56-feae-455a-8dea-0ab1e6f2212b">
<StartBoundary>2007-06-05T00:00:00</StartBoundary>
<Enabled>false</Enabled>
- <ScheduleByDay>
<DaysInterval>1</DaysInterval>
</ScheduleByDay>
</CalendarTrigger>
</Triggers>
- <Principals>
- <Principal id="LocalSystem">
<UserId>SYSTEM</UserId>
<RunLevel>LeastPrivilege</RunLevel>
</Principal>
</Principals>
- <Settings>
- <IdleSettings>
<Duration>PT10M</Duration>
<WaitTimeout>PT1H</WaitTimeout>
<StopOnIdleEnd>false</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
<AllowHardTerminate>true</AllowHardTerminate>
<StartWhenAvailable>true</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>P3D</ExecutionTimeLimit>
<Priority>7</Priority>
- <RestartOnFailure>
<Interval>PT1M</Interval>
<Count>3</Count>
</RestartOnFailure>
</Settings>
- <Actions Context="LocalSystem">
- <Exec>
<Command>%windir%\system32\rundll32.exe</Command>
<Arguments>/d srrstr.dll,ExecuteScheduledSPPCreation</Arguments>
</Exec>
</Actions>
</Task>

Not that it answers my question :-}. Incidentally, it seems as though
setting Backup & Restore ALSO triggers a RP at the same time although I
have
not tested any restorations. Here is a simple test (courtesy of Mike M
over
on windowsme.general).

1 put any shortcut on the desktop.
2 create or wait until next SR point.
3 Delete the shortcut made in 1.
4 Restore to SR made in 2.
5 If shortcut reappears, RP & R both successful.

BTW, I mentioned in my OP that following problems with my DVD R/RW drive,
Packard Bell had me re install back to "out of the box" status. Before
doing
this, I am half sure I saw a System Scheduled Set Point, but never again
since. Perhaps I imagined it ...

--

Delboy

A common mistake that people make when trying to design something
completely
foolproof is to underestimate the ingenuity of complete fools.

Douglas Adams

 

[Delboy]

You're welcome Jon,

After considering the options and a couple of NBG efforts, that's what I
came up with. I more or less unticked everything that seemed to do with
laptops, which seemed to work.

Always willing to help others (unlike some of the trolls one sees in here).
A pleasant "thank you" helps as well. :-}

--

Delboy

A common mistake that people make when trying to design something completely
foolproof is to underestimate the ingenuity of complete fools.

Douglas Adams

Hi Delboy

Thanks for that. Imported it here sucessfully. Looks like you've made some
interesting changes, compared to the original task.


I see you've unchecked all the conditions on the conditions tab
eg the 'on idle' condition (which I have a feeling may well be the
culprit) and the 'start only when on ac power' setting.

and you've also enabled the 'If the task fails, restart every..' every
minute for once a minute for 3 minutes' which probably helps too.

That may well help other people who are having problems with the task.



Re your UTC question, this is pasted from the Task Scheduler 'Help'
section regarding 'Triggers' which may help to resolve that question.....

"Check the Universal check box to make the time relative to Coordinated
Universal Time (UTC) instead of the time zone that is set on the computer
that runs the task. Use the Universal setting when you want to coordinate
a set of tasks to run simultaneously in multiple time zones. "

So I suppose the task would run at the same time, regardless of whether
you've switched to a different time zone in the course of your travels.