Monitoring a Windows Scheduled Task

With the Scheduled Task check, people can check if a scheduled task has completed successfully or not. A Scheduled Task check can only be applied to a task that should run today. I.e. you cannot check the completion of a task that ran - for instance - yesterday.

An Scheduled Task check takes the following parameters:

Scheduled Task Log File - The fully qualified path name to the Scheduled Task Log File (SchedLgU.txt), in UNC format; for instance: \\Server01\C$\Windows\Tasks\SchedLgU.txt. Please note that this file is hidden in the Windows Explorer. Use a command prompt and type DIR C:\WINDOWS\TASKS to list the file;.
Job Name - Job name, as it appears in the SchedLogU.txt file. For instance, job name should be mytask.bat according to the following log entry: "mytask.job" (mytask.bat)
Finished 1/19/2006 1:43:00 PM
Result: The task completed with an exit code of (0).
Completed Keyword - The keyword that determines the completion of a scheduled task. For many servers, the keyword will be Finished. However, the keyword can be different on non-English Operating Systems you are monitoring;
Today's Date Format - The string that determines the date format used in the Scheduled Task Log File. Note that your network servers can use different time formats. For that reason, you must specify the date format, so Network Monitor will be able to find the log entries that match the day of today. Default format: mm/dd/yyyy, i.e. month (2 digits), day (2 digits), year (4 digits), separated by a '/';
Match Result - The string that indicates a successful/unsuccessful completion of the task. A successful completion is usually determined by the following string:
Result: The task completed with an exit code of (0);
An unsuccessful completion is usually determined by the following string:
Result: The task completed with an exit code of (1);
Note that the string can be different on non-English platforms and on legacy (e.g. Windows NT 4) platforms;
If pattern matched, result is - Indicates the result of the check if pattern is matched: Success or Error.

About MS Exchange

Exchange is the Microsoft messaging and collaboration server designed to help your business communicate more effectively. Along with the rich client functionality provided by Microsoft Office Outlook, Exchange offers mobile, remote, and desktop e-mail access with state-of-the-art security and privacy; lower cost of ownership through the services provided by Microsoft Windows Server; high reliability and outstanding performance; e-mail-based collaboration; and easy upgrading, deployment, and administration.

Exchange features the following:

Distribution lists restricted to authenticated users. You can allow only sending from authenticated users or specify which users can or cannot send mail to specified distribution lists.
Support of real-time Safe and Block lists. Reduce the amount of unsolicited mail delivered to your organization with connection filtering.
Inbound recipient filtering. Reduce unsolicited e-mail messages by filtering inbound messages based on the recipient. Messages that are addressed to users that are not found, or to whom the sender does not have the permissions to send, are rejected. This applies only to messages sent by anonymously authenticated users.
Kerberos authentication between a front-end and back-end server. To help ensure that credentials are secure, Exchange uses Kerberos delegation when sending user credentials between a front-end server, such as Microsoft Office Outlook Web Access or Outlook Mobile Access, and a back-end server such as the mailbox store.
Privacy protection in Outlook and Outlook Web Access. By default, content from outside your network is blocked in Outlook and Outlook Web Access. This feature helps prevent spammers from identifying valid e-mail addresses through links to external content. You can, however, override this feature to view external content.
Virus Scanning API. Third-party antivirus products can run on servers running Exchange that do not have resident Exchange mailboxes and are allowed to delete and send messages to the sender.
Antispam integration with Outlook and Outlook Web Access. You can upload the Safe and Block Senders List to Exchange for filtering.
Clustering security. Exchange clustering supports Kerberos authentication against an Exchange virtual server. Exchange also supports Internet Protocol security (IPSec) between front-end servers and clustered back-end servers running Exchange.
Administrative permissions. Cross-forest support and the ability to administer both Exchange 2000/2003 and Exchange helps organizations that have segmented the administration of their Microsoft Windows®–based environment and Exchange environment into two unique groups and are concerned about security.
Restricted relaying. You can restrict relaying to a limited number of security principles through the standard Windows 2000/2003 discretionary access control list (DACL). The ability to grant relaying to an IP address is still present.
Restricted submissions. You can restrict submissions to a limited number of security principles through the standard Windows 2000/2003 DACL. This feature helps prevent blocked senders from sending to internal-only distribution lists by spoofing, which is the practice of tricking users into providing passwords and other information to allow unauthorized access into a system.
Public folder permissions for unknown users. Folders with distinguished names in access control lists that cannot be resolved to security identifiers drop the unresolvable distinguished names.
Public folder store replication. Public folder servers replicate with local servers for updates even if the local servers do not have the full set of replication content that they need. You can use a registry key to identify the first server that is used for backfilling. For more information, read the Exchange Security Enhancements white paper.