Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Windows Scheduled Task monitor applications not imported in scheduled discovery task when selecting an entire node

Windows Scheduled Task monitor applications not imported in scheduled discovery task when selecting an entire node

Updated 9-1-2016

Overview

Scheduled discovery for a WMI node does not import the Windows Scheduled Task monitors when selecting the entire node for the discovery task. This occurs when you have at least one Windows Scheduled Task monitor on your node and a scheduled discovery task with the entire node selected. When discovery runs, the Windows Scheduled Task monitors do not import, with no WST monitors displaying in the Application tab.

To resolve, create a scheduled discovery task, expand child entries, and select the WST monitors on each node. Or you can select the Windows Scheduled Task monitor and then select the entire node.

 

Environment

  • SAM 6.2.4

 

Cause 

When running a scheduled discovery selecting the entire node, Windows Scheduled Task monitors are not imported by default. You need to select the monitor to specifically import in the scheduled discovery task.

 

Resolution

To resolve, create a scheduled discovery task, expand child entries, and select the WST monitors on each node.

Or you can select the Windows Scheduled Task monitor and then select the entire node.

 

 

 

Last modified

Tags

Classifications

Public