Why should I bother to monitor Windows Task Scheduler?

avatar image By swordfish 16 asked Sep 26, 2012 at 05:11 PM
more ▼
(comments are locked)
10|5000 characters needed characters left

1 answer: sort voted first

Task Scheduler 2.0 saw a major overhaul with Window Server 2008/Vista. As a result, the Windows OS now uses tasks much more extensively than previously -- there are over 30 tasks installed on every Windows Server 2008 machine! A detailed list is provided below. Unfortunately there still is no native alerting system for tasks, nor any easy way to see what they are all doing.

In addition: - Many 3rd party software packages use Task Scheduler as their native scheduler and create tasks behind the scenes, unbeknownst to the user. These tasks kick off jobs such as antivirus, defrag, backups, etc. that can compete for resources on the server and impact performance just like SQL Agent jobs. - A common practice used by hackers for years has been to create temporary tasks using the AT command to carry out malicious tasks (copy files, delete files, etc.), then auto-delete leaving no trace.

As long as you are watching a Task Scheduler instance with Event Manager, if software or a user creates a task on the machine, you’ll receive an email alert about it, and you’ll see the tasks on the EM calendar alongside all other events.

Bottom line, it’s more important than ever to watch all Task Scheduler instances, otherwise you’ll end up with a gap in visibility regarding everything that’s happening on a server.

Here is a link for more information on Windows Task Scheduler:


avatar image By James Holden ♦ 1.6k answered Sep 26, 2012 at 05:18 PM
more ▼
(comments are locked)
10|5000 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 4.2 MB each and 8.4 MB total.