Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > ipMonitor > Monitor Windows task schedule

Monitor Windows task schedule

Table of contents


Using ipMonitor's External Process Monitor and two ipMonitor utilities (sem_check.exe and sem_stamp.exe), it is possible to ensure that a task scheduled using the Windows Task Scheduler has run.

The process works as follows:

  1. The Windows Task Scheduler is set to run a specific task via a batch file. When the task completes successfully, an ipMonitor utility is used to create a file containing a timestamp. This timestamp marks the time when the task must run next.
  2. ipMonitor uses the External Process Monitor to run a separate ipMonitor utility (sem_check.exe) that checks the file to ensure its timestamp is acceptable, confirming that the Task Scheduler has successfully run. If the timestamp is too old, ipMonitor will view this test as a failure, and Alerts will be sent. Using this method, you can verify that tasks are running correctly using only drive shares and read permissions on the remote machines. 




Before configuring the External Process Monitor or creating the desired task, proceed with the following:

  1. Create a new folder named logs on the remote server. This folder can be located on any drive you choose.
  2. Set security permissions for the new folder. Grant read access to the user account ipMonitor will be running under.


Note: Imported Monitors are initially disabled. This allows you to make changes to the default settings before the Monitor is enabled to go live in a production environment. Once the Monitor is imported, the following settings will need to be verified (and if necessary, modified) for the Monitor:

  • Executable Name
  • Directory
  • Command Line Parameters
  • Startup Directory
  • Credential for Monitoring


Sample Monitor Settings:


Monitor Name Exec:: Task file
Monitor Type External Process Monitor
Returns Timing state (expired or valid) of the file generated by the scheduled task.
Monitoring Condition Expected Return Value: 0

Monitor failure indicates that the file is older than 24 hours.



Last modified