TIL:1) If a Windows Scheduled task fails to run due to invalid stored credentials for the task, the Last Run Result will say The operation completed successfully (0x0)2) Event logging for the TaskScheduler Windows component is disabled by default.

[wdormann@infosec.exchange]

TIL:
1) If a Windows Scheduled task fails to run due to invalid stored credentials for the task, the Last Run Result will say The operation completed successfully (0x0)
2) Event logging for the TaskScheduler Windows component is disabled by default. Presumably because it's super important to save a few bytes of disk space, and/or nobody uses Task Scheduler?

Fine, the pedant might annoyingly point out that the column is Last Run Result, so if it doesn't run, then this column won't get updated. To you, I say: Get bent.

[kaaswe@swecyb.com]

@wdormann
Yeah, the Task-scheduler has always been quirky as long as I can remember back to NT, even the one in SQL (job scheduler)

I used to always create a .cmd script to run that does my tasks, checks and validate the results and finally reports the results as an output in a file, that later could be picked up by the central monitoring software to report and set the status.

Doing that for backup jobs and a lot of stuff. When you have found your way to tend to stick to it.