Use this Knowledge Script to detect whether the computer on which you run the script can communicate with one or more remote Windows computers. This script requires that you first use the ConfigMachineDown Knowledge Script to store a list of remote computers in the local repository on the managed client computer where this script runs.
This script does not require the AppManager agent to be installed on the remote computers you want to monitor.
To run this script on a Windows Vista computer, the Remote Registry service on the agent computer must be running to connect to the Windows registry on the remote computers you want to monitor. If the Remote Registry Service is down when this script runs, an event is raised to indicate the remote computer was unresponsive and the connection to the Windows registry failed.
Once you have run ConfigMachineDown on each computer in a group, you can use MachineDownLR in a monitoring policy for the group. On each computer, the script knows what to monitor because ConfigMachineDown previously stored that information in the local repository. The use of MachineDownLR is the same as for MachineDown.
Note that this script displays event information in AppManager even if the remote computer is in maintenance mode.
If you want each computer in your environment to be able to check whether other selected computers are down, run ConfigMachineDown on each computer and specify the particular machine list you want that computer to monitor.
You can then put the MachineDownLR jobs in a monitoring policy that covers all those computers. As the job runs on each computer, it picks up the machine list from the local repository where ConfigMachineDown set it.
In this way, each instance of MachineDownLR can check a different list of computers from each computer where it runs.
Windows 2003 Server or later
The default interval for this script is Every 5 minutes.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
Collect data for computer availability? |
Set to y to collect data for charts and reports. If enabled, data collection returns the following:
The default is n. |
|
Event severity when computer is down |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the target computer is down. The default is 5 (red event indicator). |
|
Ping router? |
Set to y to routinely ping the default gateway router. If enabled and the ping fails, the script stops and raises an event. The default is n. When this script runs, it first pings the default gateway router if the Ping Router parameter is enabled. If the ping fails, an event is raised. If the ping is successful or if no ping is requested, this script checks the registry of the destination computer. If that check fails, an event is raised. It also traces the route to the destination if the Trace the route parameter is enabled. If the registry check succeeds, communication with that computer is verified. |
|
Number of seconds to wait for ping response |
Specify the maximum number of seconds to wait for the ping to return a positive result. If the Ping router parameter is set to n, this threshold parameter is ignored. The default is 3 seconds. |
|
Trace the route to a destination computer |
Set to y to trace the route to a computer that is down. A traceroute can help you determine where the problem lies. The default is n. |
|
Raise single event for all computers that are down? |
Set to y to raise a single event regardless of the number of computers that are down. Set to n to raise a separate event for each computer that is down. The default is n. |