AD Replication Sensor
The AD Replication sensor checks a Windows Domain Controller for replication errors, reporting one status per discovered Active Directory partition.
This sensor checks a Windows Domain Controller for replication errors. Add it to a machine that is a Domain Controller, and provide credentials that can access the root\MicrosoftActiveDirectory namespace. The sensor shows one status per discovered AD partition.
Microsoft documentation about AD partitions
Statuses
The total number of statuses depends on the Domain Controller configuration. Three statuses always occur:
- Domain Partition Replication Status
- Configuration Partition Replication Status
- Schema Partition Replication Status
Each status carries the following properties:
- NumConsecutiveSyncFailures - number of consecutive sync failures
- IsDeletedSourceDsa - whether the source is deleted
- TimeOfLastSyncAttempt - time of the last sync attempt
- LastSyncResult - result of the last sync
- TimeOfLastSyncSuccess - time of the last successful sync
- ModifiedNumConsecutiveSyncFailures - number of modified consecutive sync failures
- ReplPendingOp:PositionInQ - number of pending replication operations
- DisableScheduledSync - whether the scheduled sync is disabled
Default Alerts
- Alert on any partition replication error
- Generated when any status value changes to
Error, which means replication has failed.
Credentials
Any credential that allows access to the root\MicrosoftActiveDirectory namespace will work. Administrative rights might be required.
The AD Replication sensor is one of the WMI sensors - see WMI Sensors for the rest of the family.
- NetCrunch Security Features
How NetCrunch protects access to the console and the credentials it holds — multi-factor authentication, a master key for stored secrets, encrypted backups, and restricted access to the data folder.
- NetCrunch as an Inventory Database
NetCrunch is an inventory database as well as a monitoring system. Everything it monitors, it also records — hardware, installed software, hotfixes and your own asset data — and because it keeps looking, it tells you when any of it changes.
- Managing Monitoring Credentials
Store credentials for monitored systems as reusable profiles, or set them per node. Passwords are kept on the server and are never sent back to a console.
- WMI Sensors
NetCrunch offers a collection of WMI sensors. Basic sensors are designated to serve specific purposes such as monitoring perfmon, process, shares, or time difference. The advanced sensor is more general and allows us to explore WMI classes or create custom WQL queries.
- Windows DHCP Server Sensor
Monitors a Windows DHCP Server and its scopes, tracking address pool usage and lease health, and alerting before a scope runs out of addresses.
- Backup
NetCrunch automatically creates data backups each day. What a backup contains, whether it is encrypted, and what it can be restored onto all depend on the same thing: the credentials inside it.
- Getting Started
Learn how to create a NetCrunch API key and use it with both REST API and MCP Server access channels.