![]() ![]() We can utilize the WMI class Win32_PingStatus. In this case, it will be an internet DNS server. In this scenario, we want to make sure that the server can ping some outside resource. The final action module will be for the Client Access Server. Set the condition to NOT= and the desired value is Started Testing Connectivity for the Client Access Server The second condition is Add \ Remove –> Set Computer Condition –> Services –> Software Services –> State This is the actual service name, not the “friendly” name. Set the condition to = and the desired value is the service name. The first condition is Add \ Remove –> Set Computer Condition –> Services –> Software Services –> Name The service action modules are nearly identical except there are two conditions. ![]() The desired value is the Process name we are monitoring. This means, if the process does not exists, proceed with the action, in this case Send Email. In this example, we choose Add \ Remove –> Set Computer Condition –> Processes –> Name. You can enter a condition in the section labeled “Only if the following is true.” This is where we define what we wish to monitor. The second part of the action module is the condition. We use a Dynamic Value Definition for the subject line to include the name of the server being processed. The fields are self explanatory except for the Subject. Here is how the arguments should be set for the email action. NOTE: The email action does not require any user to be logged in to the server or anywhere. This can be found under Add \ Remove –> Execute Computer Action –> Logged in User –> Send Email. Remember you can replace any of these modules for specific criteria you wish to monitor.Īll the action modules follow the same format.įirst add the email action. The Action module should look like the following for our example. For example, all of the Exchange mailbox servers or all of the SQL servers. Create one module with a list of servers that will have the same monitoring criteria. This method will provide the most granularity for monitoring your server. Each Process and Service will have its own action module. If you create an action module for each process or service then you can be notified of the specific process or service that has failed.įor this tutorial, we will go with the latter. For example, if you add all the processes or services to the same action module, Goverlan will alert you if any one of them is no longer running. The number of action modules will depend on the how you wish to monitor the objects. ![]() If you have several servers that have the same criteria, feel free to add them to the same scope action. We need this because each server will have different processes and services to monitor. In this topology, we would like to monitor some processes, services and internet access. Also, this method can apply to any application server or line of business application on Windows. For the purposes of this, we will simplify the topology a bit. To demonstrate this we will use the example of monitoring an Exchange Server Setup. With a Goverlan Scope Action, we can create an action module for each of these areas. Verifying communication between different component servers (ie: can the Exchange Hub Transport Server communicate with the Client Access Server or internet DNS servers).Monitoring a Windows application running on a server comes down to a few key areas. Please test all Scope Actions before deploying them into production.** IT Process Automation Objectives **These tutorials are for demonstration purposes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |