<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Active Directory Replication Errors Sensor

Member of Windows domain

This sensor only works if the probe system is part of the domain whose Active Directory you want to monitor. You must add this sensor to a device that represents the DC.

.NET 4.7.2 or later

This sensor requires .NET 4.7.2 or later to be installed on the probe system (on every cluster node, if on a cluster probe).

If the framework is missing, you cannot create this sensor.

For more information, see the Knowledge Base: Which .NET version does PRTG require?

Windows credentials

This sensor requires credentials for Windows systems in the settings of the parent device. We recommend that you use Windows domain credentials.

If you use local credentials, make sure that the same Windows user accounts (with the same user name and password) exist on both the probe system and the target system. Otherwise, the sensor cannot correctly connect.

Sensor Name

Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.

If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include?

Parent Tags

The tags that the sensor inherits from its parent device, parent group, and parent probe.

This setting is for your information only. You cannot change it.

Tags

Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.

It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

For performance reasons, it can take some minutes until you can filter for new tags that you added.

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

• ptfsensor

Priority

Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority () to the highest priority ().

Replication Neighbor

The replication neighbor whose replication connection this sensor monitors.

Naming Context

Select the Active Directory naming context that you want to monitor:

• Configuration (default): Includes information about partitions, sites, services, or the Active Directory schema.
• Schema: Includes the information by which objects, classes, and attributes that are used in the Active Directory are defined.
• DomainDnsZones: Includes information about the domain controllers that are in the domain.
• Domain: Includes domain information that is replicated to this domain's domain controllers, for example information about computers or users.
  The probe system must be part of the domain whose naming context you want to monitor.
• ForestDnsZones: Includes information about domain controllers in the forest.

You cannot change this value after sensor creation.

Result Handling

Define what PRTG does with the sensor result:

• Discard result (default): Do not store the sensor result.

• Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file names are Result of Sensor [ID].txt and Result of Sensor [ID].Data.txt. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.

In a cluster, PRTG stores the result in the PRTG data directory of the master node.

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.

You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.

Graph Type

Define how different channels are shown for this sensor:

• Show channels independently (default): Show a graph for each channel.
• Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
  You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).
• Show channels independently (default): Show a graph for each channel.
• Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
  You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you select Stack channels on top of each other above.

Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Consecutive Sync Failures

The number of consecutive synchronization failures

Downtime

In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down state

Is Deleted Source

If the source is deleted

• Up status: No
• Down status: Yes

Last Sync Attempt

The time of the last synchronization attempt

Last Sync Result

The result of the last synchronization

This channel is the primary channel by default.

Last Sync Success

The time of the last synchronization success

Modified Consecutive Sync Failures

The number of modified, consecutive synchronization failures

Pending Replication Operations

The number of pending replication operations

Scheduled Sync Disabled

If the scheduled synchronization is disabled

• Up status: No
• Down status: Yes