Here we will select “Use a separate list” and click the Manage Custom List link. Go to Add \ Remove –> Report Computer Property –> WMI Objects –> Manage WMI Objects. Action Module Constructionįirst we will need to add the query to our Scope Action so we can use its properties. If we need to ping Computer B from Computer A, this will be Computer A.Īdd as many computers as necessary to test connectivity to the secondary resources. The scope module should consist of the source Windows computer. If you have never created a Scope Action before, please refer to the below video and the Scope Action Creation Basics article for more information. For example, we may need to be notified if round trip time goes above 10 ms. With the information retrieved, we can then use a condition to evaluate the data and determine if we need to be alerted. The remote system will then ping another system and report back all the statistics and data to the Goverlan Scope Action. In this tutorial we will use a WMI query based on the Win32_PingStatus class and execute it on a remote system. Using the Win32_PingStatus WMI class, we can execute a ping from one system and target another system This may be useful when testing communication between two Exchange server roles or between a server and an internet resource. Monitoring connectivity between the monitoring server and a remote system is fine but there is an even greater value in knowing when there is a problem between two systems that need to communicate with each other. Please test all Scope Actions before deploying them into production.** Information **These tutorials are for demonstration purposes.
0 Comments
Leave a Reply. |