Infrastructure Master LDAP Bind Availability Monitor - Microsoft.Windows.Server.2012.AD.Availability.FsmoBind.Infra.Monitor (UnitMonitor)

Microsoft.Windows.Server.2012.AD.Availability.FsmoBind.Infra.Monitor (UnitMonitor)

Monitors that the DC is able to perform a LDAP bind against the FSMO holder.

Knowledge Base article:

Summary

This monitor verifies the availability of the Infrastructure Master FSMO using an LDAP (Lightweight Directory Access Protocol) request. It periodically binds to the Domain Controller to verify the availability using an LDAP query.

Configuration

IntervalSeconds: How frequently the monitor is run (seconds)

Causes

Possible causes include the following:

The domain controller needs resizing.
The domain controller is a bridgehead server, and it is compressing large amounts of data because a bulk load must be replicated intersite.
One or more other domain controllers failed, and their load transferred to this domain controller because it is now the closest available domain controller.
An application is placing a heavy load on the domain controller. This is usually caused by inefficient, CPU-intensive operations such as non-indexed queries.
The domain controller is critically low on memory.
The domain controller is under a denial-of-service attack.

Resolutions

View the error description in the alert for additional information.

View the overall system performance of the machine to determine if it needs additional resources.

Add additional domain controllers to help load-balance the load.

Ensure that there are a sufficient number of DCs in the active AD sites.

External

Capacity Planning for Active Directory Domain Services

Element properties:

Target

Microsoft.Windows.Server.2012.AD.DomainControllerRole

Parent Monitor

Microsoft.Windows.Server.2012.AD.ResponseMonitors.FsmoBind.Availability.AggregateMonitor

Category

Custom

Enabled

True

Alert Generate

True

Alert Severity

MatchMonitorHealth

Alert Priority

Normal

Alert Auto Resolve

True

Monitor Type

Microsoft.Windows.Server.2012.AD.Availability.FsmoBind.Monitortype

Remotable

False

Accessibility

Public

Alert Message

The Infrastructure Master LDAP Bind Availability health monitor has failed.

The health monitor script failed with an error.
Error: {0}

RunAs

Default

Source Code:

<UnitMonitor ID="Microsoft.Windows.Server.2012.AD.Availability.FsmoBind.Infra.Monitor" Accessibility="Public" Enabled="true" Target="AD2012Core!Microsoft.Windows.Server.2012.AD.DomainControllerRole" ParentMonitorID="Microsoft.Windows.Server.2012.AD.ResponseMonitors.FsmoBind.Availability.AggregateMonitor" Remotable="false" Priority="Normal" TypeID="Microsoft.Windows.Server.2012.AD.Availability.FsmoBind.Monitortype" ConfirmDelivery="false"> <Category>Custom</Category> <AlertSettings AlertMessage="Microsoft.Windows.Server.2012.AD.Availability.FsmoBind.Infra.Monitor.AlertMessage"> <AlertOnState>Error</AlertOnState> <AutoResolve>true</AutoResolve> <AlertPriority>Normal</AlertPriority> <AlertSeverity>MatchMonitorHealth</AlertSeverity> <AlertParameters> <AlertParameter1>$Data/Context/Property[@Name='ErrorString']$</AlertParameter1> </AlertParameters> </AlertSettings> <OperationalStates> <OperationalState ID="ResponseOK" MonitorTypeStateID="ResponseOK" HealthState="Success"/> <OperationalState ID="ResponseError" MonitorTypeStateID="ResponseError" HealthState="Error"/> </OperationalStates> <Configuration> <IntervalSeconds>300</IntervalSeconds> <TimeoutSeconds>300</TimeoutSeconds> <FsmoHolder>$Target/Property[Type="AD!Microsoft.Windows.Server.AD.Library.DomainControllerRole"]/InfrastructureMaster$</FsmoHolder> <BindIterations>3</BindIterations> </Configuration> </UnitMonitor>