Opselith
POWERSHELL / ACTIVEDIRECTORY
ProAdvancedRead-onlylow

Find AD replication failures

Finds current Active Directory replication failures for one target domain controller, or for the current forest when the target is left blank.

Open in PowerShell Builder →Browse all scripts

Pro generation after license validation · Review before running · Opselith does not connect to your tenant

What this PowerShell script does

Finds current Active Directory replication failures for one target domain controller, or for the current forest when the target is left blank.

Requirements

  • Target domain controller - Optional: DC01; leave empty for the current forest

Environment

  • Module: ActiveDirectory
  • Permissions: Directory read access
  • Output: CSV report
  • Context: Windows host with RSAT
  • Risk: Low
Review before you run The full Pro script is generated by Opselith after license validation. Test outside production first.
NEXT STEP

Ready to generate

Configure Find AD replication failures in the Builder, review the generated PowerShell and run it yourself in your own PowerShell session.

Configure this script →Open Builder
More about this script

Why use this template?

Use this Pro PowerShell script when you need to export current replication failures from domain controllers. It can be previewed in the Builder; Pro access is required to generate it for your own environment.

The template uses ActiveDirectory and requires Directory read access. Output: CSV report. Level: Advanced. Action: Read-only. Risk: Low.

Review before running

The script remains preview-only until Pro access is enabled. Review it before running it, and test it outside production first. “Read-only” describes the script itself; anything you add around it can still change data.

Preview the script

  1. Open the template in the PowerShell Builder.
  2. Review the purpose, requirements, permissions, output and risk.
  3. Activate Pro when you are ready to generate the full script, then test it outside production.

Pro templates remain previewable before purchase or activation. No tenant connection is required. When you generate a Pro script, only the configuration values needed for that template are sent to Opselith after license validation.Preview Find AD replication failures →

Before you runModule, permissions, inputs, compatibility and script checks
OPS / SCRIPT DETAILS

Script details

Finds current Active Directory replication failures for one target domain controller, or for the current forest when the target is left blank. Review these details before generating or running the script.

securityexportfindpermissionsdomains
Generated here. Run by you.Opselith does not connect to your tenant or run PowerShell. After generating, review the script and run it in your own PowerShell session.

What it works with

Module: ActiveDirectory

ActiveDirectory lets PowerShell work with on-premises Active Directory and is normally installed through Windows RSAT.

Context: Windows host with RSAT

Compatibility: Windows PowerShell 5.1 / ISE is supported for this Active Directory template.

Permissions and changes

Permissions: Directory read access

Risk: Low

Read-only: designed to collect information without intentionally changing the target environment.

Changes: Read-only. The script reads data and does not intentionally change the target environment.

Inputs

  • Target domain controller - Optional: DC01; leave empty for the current forest (Optional)
  • CSV output path - Example: C:\Temp\report.csv (Required)

What to expect

Output: CSV report

Expect a CSV file at the path you choose. Open it in Excel or another CSV viewer and review the rows.

Example: C:\Temp\report.csv

This template is in the Pro library. Generating the full script requires eligible Pro or tester access. Opselith receives only the values needed to build the script; it does not connect to your tenant, run PowerShell or store the generated script. You review and run the result in your own PowerShell session.

Example use

Finds current Active Directory replication failures for one target domain controller, or for the current forest when the target is left blank.

Enter the required values in the Builder, review the generated script and confirm the output before running it.

Before you run: Make sure your account has Directory read access. Check that the ActiveDirectory PowerShell module is available and that you are using the supported PowerShell version. Review the generated script and output path, then test outside production first.
Script checksWhat has been verifiedQA reviewed
Static checksPassed
PSScriptAnalyzerPending
Real-world run testNot yet recorded
Last checkedNot yet recorded

Real-world run results are shown only after Opselith reviews and accepts a tester report.

Tester: report a result →
TEST STATUSWhat Opselith has checked

Last reviewed: 10 Sept 2026

PSScriptAnalyzer: Awaiting a release PSScriptAnalyzer gate that includes this script. No analyzer pass is claimed yet.

Pending or Not yet recorded means there is no accepted result on file yet. A passed analyzer check does not mean the script has been run in a real tenant.

PRACTICAL GUIDE

How to use this result

Use this report to identify current AD replication failures and quickly see which server/partner pairs need investigation.

When this helps

  • Triage replication health after domain-controller maintenance or connectivity incidents.
  • Capture a CSV of current failures for handover or incident tracking.
  • Compare failure counts and first-failure times to distinguish new problems from persistent ones.

How to read the result

  • Server and Partner identify the replication relationship; FailureCount shows the current failure count returned by AD.
  • FirstFailureTime and LastError help prioritize which failures have persisted and which error needs deeper investigation.

Things to check

  • A clean export only describes the query result at that moment; it is not a long-term replication-health history.
  • The script reports failures but does not repair replication, DNS, connectivity or authentication problems.
What to do next: Start with persistent or high-count failures, confirm the affected domain controllers are reachable, and investigate the reported LastError before making changes.
NEXT IN THE LIBRARY

Scripts for similar admin tasks and Microsoft services.

Browse Active Directory PowerShell scripts →
POWERSHELLExport domain controllersreporting · export · permissionsPOWERSHELLExport AD domain password policysecurity · export · permissionsPOWERSHELLFind AD passwords expiring soonsecurity · find · users