home.social

#taskscheduler — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #taskscheduler, aggregated by home.social.

fetched live
  1. Run a Windows task on system unlock

    You can't do it through any of the normal scheduler commands. But if you write an XML block that includes a SessionStateChangeTrigger, like

    <SessionStateChangeTrigger>
    <StateChange>SessionUnlock</StateChange>
    </SessionStateChangeTrigger>

    Then you can pass the whole XML block to Register-ScheduledTask:

    Register-ScheduledTask -Xml $xml -Force

  2. Make sure that the first scheduled trigger of a #Windows #ScheduledTask lies in the future, due to a bug in Windows #TaskScheduler introduced with #Microsoft Windows Server 2016. The task will never start otherwise.

  3. Found another issue: one must start up the #MSWindows #TaskScheduler as the server administrator. Not as a member of the Administrators security group, mind you. It only works if you are the server admin. Great. (Not.) #DevOps

  4. #TIL: the #MSWindows #TaskScheduler on #Windows10 can be used to adjust scheduled tasks on remote servers. But it's hard to get the scheduled date to change: you MUST open the calendar dropdown by mouse, and you MUST click a date by mouse. Keyboard control will get ignored, and not cause the schedule to update.

    #TodayILearned #devops #UserExperience #UX #QualityAssurance #QA

  5. #TIL: #MSWindows #ScheduledTask triggers must be scheduled to a future date in order to get kicked off automatically. Otherwise the #TaskScheduler will simply and silently ignore the trigger.

    This is an unexpected change from older behavior, in which the operating system simply extrapolated the next run time and would trigger the task.

    Also, if you schedule for daily execution, auto trigger won't kick in until tomorrow. Instead, schedule once with infinite repeat.

    Lovely.

  6. #TodayILearned that the #TaskScheduler in #MSWindows2019 will claim that its service is unavailable, when that clearly is NOT the case. It's lying. But it doesn't know any better. Thank you, #Microsoft!

    What actually happened is that the environment didn't meet the criteria I set in the scheduled task. What Microsoft should do is recognize that, and report that.