f Active Directory Monitoring | Complete Microsoft Monitoring

You are here

Active Directory Monitoring

Requires Opsview Cloud or Opsview Monitor 6.3
check_circle
Opsview Supported

Active Directory Monitoring

Active Directory (AD) is a Microsoft product that consists of several services that run on Windows Server to manage permissions and access to networked resources. The main service in Active Directory is Domain Services, which stores directory information and handles the interaction of the user with the domain. AD stores information about objects on the network using a structured data store as the basis for a logical, hierarchical organization of directory information which makes this information easy for administrators and users to find and use.

What You Can Monitor in AD

This Opspack allows you to monitor all the metrics you need to efficiently run a Microsoft AD Service, providing service checks for high level status information about services, threads, Security Accounts Manager, and Address Book, as well as important metrics for the Active Directory Replication status.

Host Templates

The following Host Templates are provided within this Opspack for AD monitoring. Click the name of each Host Template to be taken to the relevant information page, including a full Service Check description and usage instructions.

Active Directory Monitoring Prerequisites

Setup Windows Host for Monitoring

By default, Windows hosts will not allow remote PowerShell scripts to run, which is required for Opsview Agentless Monitoring plugins to work.

This can be configured manually by the Windows Host administrator, or automatically using our recommended approach by running the ConfigureRemoting.ps1 Powershell script on the Windows Host.

Powershell Agentless Monitoring requires at least version 5.0 of Powershell. Check the Powershell version on your Windows Host by running:

$PSVersionTable.PSVersion

Run the ConfigureRemoting.ps1 script with Administrator privileges using a Powershell terminal. This will configure firewall rules, self-signed SSL certificates and authentication for PowerShell remoting.

Check this has been configured properly by running:

winrm quickconfig

You should get the following output:

WinRM service is already running on this machine.
WinRM is already set up for remote management on this computer.

By default port 5985 must be opened from the Opsview monitoring server to the Windows host you wish to check. WinRM utilises the HTTP/HTTPS protocol and can be configured to use certificates to secure the data in transit.

Ensure the service is listening by running:

For HTTP: netstat -an | findstr 5985

For HTTPS: netstat -an | findstr 5986

When using basic authentication with WinRM, the following commands must also be run on the windows host:

winrm set winrm/config/service/auth '@{Basic="true"}'
winrm set winrm/config/service '@{AllowUnencrypted="true"}'
winrm set winrm/config/client/auth '@{Basic="true"}'

If you receive a 500 error, which is a known issue on Windows Server 2016, you may need to install WinRM-IIS-Ext. You can do so by running the following command:

Add-WindowsFeature winrm-IIS-Ext

Importing this Opspack

Download the application-microsoft-active-directory.opspack file from the Releases section of this repository, and import it into your Opsview Monitor instance. Now you can add the Host Templates you want following the info links in the table at the top.

For more information, refer to Opsview Knowlege Center - Importing an Opspack.