application Integration
microsoft-active-directory-201x (en)


ServicePilot application-microsoft-active-directory-201x


# Microsoft Active Directory 201x

Overview

This package monitors a Microsoft Active Directory 201x using WMI.

Description

This package automatically configures the ServicePilot Windows System Agent in order to monitor Microsoft Active Directory 201x by using WMI counters. The statistics gathered in this way include:

  • CPU, Memory and Disk utilization (optional)
  • Microsoft Active Directory Replication
  • Microsoft Active Directory service and process (optional)

Requirements

  • You will need to install the ServicePilot Windows System Agent directly on the target server to monitor.

    • Windows System Agent installed on target machine: The Windows System Agent needs to run under an account with local administrative privileges. The Windows System Agent uses the local system account by default which has these privileges.
    • Windows System Agent installed remote to the target machine: An account with WMI Remote Access privileges on the machine to be monitored is required. See Authorize WMI users and set permissions.
  • Network Flows - It is is necessary to ensure network connectivity between ServicePilot and the monitored device. In case of a network infrastructure using a firewall, the port below must be opened:

    • Windows System Agent installed on target machine:
      • ServicePilot Manager Web server access (by default TCP/80 when using HTTP or TCP/443 when using HTTPS although this port is configurable): Between ServicePilot Windows System Agent and ServicePilot Manager
  • ServicePilot Requirements

    • ServicePilot Manager minimum version: 8.5
    • ServicePilot Windows System Agent Minimum version: 8.5 installed and configured

Installation

Before adding a resource to monitor, make certain that all pre-requisites are in place and if a ServicePilot Agent is required, that it is communicating correctly with the ServicePilot Manager. Resources can be added to ServicePilot configuration in a number of ways:

Add resource using Views Configuration web interface

  1. As an administrative user of ServicePilot, open the ServicePilot web interface.
  2. Navigate to Administration. The Configuration > Views web page will open.
  3. Click on the view in which to place the new resource in the Views hierarchy on the left of the interface. The View editor section will show the existing view contents.
  4. From the Packages list on the right of the interface, click and drag the application-microsoft-active-directory-201x package into the View editor and let go.
  5. The Package properties dialog box will open to allow resource configuration.
  6. Click OK to close the Package properties dialog box. Note that the dialog box will not close if required parameters are not set.
  7. Click Save to apply the new resource to ServicePilot configuration.

Add resource by changing servicepilot.conf configuration file

Resources can be added to ServicePilot configuration by directly editing the servicepilot.conf or other included YAML configuration files. The ServicePilot web interface can be used to make these changes and apply them to the running configuration.

  1. As an administrative user of ServicePilot, open the ServicePilot web interface.
  2. Navigate to Administration.
  3. Navigate to Configuration > Edit configuration.
  4. Expand the configuration to find the provisioning: and then packages: section of the view in which the new resource will be placed.
  5. Add the example package configuration line below.
  6. Click on the green - package: word to open then Package properties dialog box to allow resource configuration.
  7. Click OK to close the Package properties dialog box. Note that the dialog box will not close if required parameters are not set.
  8. Click Save to apply the new resource to ServicePilot configuration.

Example:

- package: "application-microsoft-active-directory-201x;;;;;;;;application-microsoft-active-directory-201x;;Y;Y;Y;;"

Key field notes

  1. In the Monitoring Policies tab, specify the policy or policies to apply to the package

  2. Resources tab:

    1. Monitor Server Resources Enable monitoring of server resources If checked, the next 3 fields will be available.
      1. Disks: Tick to get statistics for all disks
      2. Interfaces: Tick to get statistics for all network interfaces
  3. Processes tab:
    1. Processes: A multi-line text field containing one process per line. Each line consists of 4 fields that are comma (,) separated. The first field is the process Name. The second field is a process alias. If the alias field is empty then the process name will be used. Use an alias if the process Name is not unique. The third field is the process CommandLine parameter. If the CommandLine parameter is empty then it is assumed that only one process with a particular name is running. The last field is the process ExecutablePath parameter. If the ExecutablePath parameter is empty then it is assumed that only one process with a particular name is running. Following is an example:
    `svchost.exe,DCOM Server Process Launcher,C:\Windows\system32\svchost.exe -k DcomLaunch,C:\Windows\system32\svchost.exe`

Notes

  • It is posible to get a list of processes by opening a Windows Command Prompt as Administrator with escalated UAC privileges and running wmic process|more. The process Name is 16th parameter, the process CommandLine is the 2nd parameter and the ExecutablePath is the 8th parameter.