<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Active Directory Replication Errors Sensor
The Active Directory Replication Errors sensor checks a Windows domain controller (DC) for replication errors.
Active Directory Replication Errors Sensor
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
Sensor in Other Languages
- Dutch: Active Directory Replicatie Fouten
- French: Active Directory erreurs de réplication
- German: Active Directory Replikationsfehler
- Japanese: AD レプリケーションエラー監視
- Portuguese: Erros de replicação Active Directory
- Russian: Ошибки репликации Active Directory
- Simplified Chinese: 活动目录复制错误
- Spanish: Errores de replicación Active Directory
Remarks
You cannot add this sensor to the hosted probe of a PRTG Hosted Monitor instance. If you want to use this sensor, add it to a remote probe device.
Detailed Requirements
|
|
.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?
|
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 the sensor to a device that represents the DC.
|
Windows credentials
|
This sensor requires credentials for Windows systems in the settings of the parent device. Preferably, 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 computer. Otherwise, the sensor cannot correctly connect.
|
Add Sensor
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.
|
|
Replication Neighbor
|
Select the replication neighbor whose replication connection you want to monitor.
Enable check boxes in front of the respective lines to select the items. Use the check box in the table header to select all items or to cancel the selection. In large tables, use the search function in the upper-right corner.
|
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.
|
Basic Sensor Settings
Click the Settings tab of a sensor to change its settings.
Basic Sensor Settings
|
|
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
|
Shows 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:
|
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 ().
|
Usually, a sensor connects to the IP Address/DNS Name of the parent device. See the device settings for details. For some sensors, you can explicitly define the monitoring target in the sensor settings.
Sensor Settings
Sensor Settings
|
|
Replication Neighbor
|
Shows the replication neighbor whose replication connection this sensor monitors.
PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.
|
Naming Context
|
Shows the Active Directory naming context that this sensor monitors.
PRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.
|
Debug Options
Debug Options
|
|
Result Handling
|
Define what PRTG does with the sensor result:
- Discard result: 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.
|
Sensor Display
Sensor Display
|
|
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).
|
Stack Unit
|
This setting is only visible if you enable Stack channels on top of each other as Graph Type. 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.
|
Inherited Settings
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
Scanning Interval
Scanning Interval
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
Schedules, Dependencies, and Maintenance Window
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
Access Rights
Access Rights
For more information, see section Root Group Settings, section Access Rights.
Channel Unit Configuration
Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.
Channel Unit Configuration
For more information, see section Root Group Settings, section Channel Unit Configuration.
Channel List
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
|
|
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 status in percent.
|
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
|
More
Knowledge Base
Which .NET version does PRTG require?
What security features does PRTG include?