Results 1 to 4 of 4
  1. #1
    Super Moderator RetiredGeek's Avatar
    Join Date
    Mar 2004
    Location
    Manning, South Carolina
    Posts
    9,436
    Thanks
    372
    Thanked 1,457 Times in 1,326 Posts

    Task Scheduler Anomaly?

    Hey Y'all,

    I've noticed & verified an anomaly in Windows Task Scheduler.

    I have a task scheduled to run at Boot Up and then repeat every 10 minutes.
    TS-Trigger-PSBatterySave.JPG
    However, it doesn't run for the first time until 10 minutes after boot-up. Am I missing something here? Is this the way it is supposed to work?

    Machine Last Boot Time: 16:03:56
    First Task Run Time: 16:14:12

    From MSDN article:
    Repeat task every : This setting allows you to set a repetition time interval for the task. The task will run, wait for the time interval specified, and then run again. This cycle will continue until the duration time is met.
    May the Forces of good computing be with you!

    RG

    PowerShell & VBA Rule!

    My Systems: Desktop Specs
    Laptop Specs

  2. #2
    Super Moderator BATcher's Avatar
    Join Date
    Feb 2008
    Location
    A cultural area in SW England
    Posts
    3,421
    Thanks
    33
    Thanked 195 Times in 175 Posts
    I would suggest that you cut your losses and make two almost identical tasks: one to run at startup and one which runs every ten minutes (yours does this only for one day).

    But my concern would be: what account do you want the task to run under at startup/boot time when there is no account logged on?
    BATcher

    Time prevents everything happening all at once...

  3. #3
    Super Moderator RetiredGeek's Avatar
    Join Date
    Mar 2004
    Location
    Manning, South Carolina
    Posts
    9,436
    Thanks
    372
    Thanked 1,457 Times in 1,326 Posts
    Quote Originally Posted by BATcher View Post
    But my concern would be: what account do you want the task to run under at startup/boot time when there is no account logged on?
    Ah, and there's the rub! Actually, I was thinking about this last night while in bed waiting to go to sleep. You're right on the nose as usual. Changing the Trigger to At Logon fixes the problem and the program fires up right away.

    I only have it set for 1 day as I never leave my computers running overnight (no I'm not trying to get that whole discussion started again ) and I was only testing the concept for a post in the Windows Programming forum.

    Thanks again.
    May the Forces of good computing be with you!

    RG

    PowerShell & VBA Rule!

    My Systems: Desktop Specs
    Laptop Specs

  4. #4
    Super Moderator BATcher's Avatar
    Join Date
    Feb 2008
    Location
    A cultural area in SW England
    Posts
    3,421
    Thanks
    33
    Thanked 195 Times in 175 Posts
    I'm pleased you determined the best solution!
    BATcher

    Time prevents everything happening all at once...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •