New AD Replication Status Tool

Microsoft has released a new Active Directory replication diagnostics tool called ADREPLSTATUS.  Features include:

  • Auto-discovery of the DCs and domains in the Active Directory forest to which the ADREPLSTATUS computer is joined
  • “Errors only” mode allows administrators to focus only on DCs reporting replication failures
  • Upon detection of replication errors, ADREPLSTATUS uses its tight integration with resolution content on Microsoft TechNet to display the resolution steps for the top AD Replication errors
  • Rich sorting and grouping of result output by clicking on any single column header (sort) or by dragging one or more column headers to the filter bar. Use one or both options to arrange output by last replication error, last replication success date, source DC naming context and last replication success date, etc.)
  • The ability to export replication status data so that it can be imported and viewed by source domain admins, destination domain admins or support professionals using either Microsoft Excel or ADREPLSTATUS
  • The ability to choose which columns you want displayed and their display order. Both settings are saved as a preference on the ADREPLSTATUS computer
  • Broad OS version support (Windows XP -> Windows Server 2012 Preview)

Check out the original blog post by Microsoft to learn much more.

Broken AD replication has proven to be a bit of a curse in the past. I’m amazed at how many sites (not small ones either) don’t monitor this stuff, relying on cheapware ping-based monitoring rather than the application-layer monitoring of something like System Center 2012 – Operations Manager.  They end up with fragmented AD, all sorts of weird crap happening, etc.  If you’re a consultant in a site and you’re deploying/configuring something with a reliance on AD, then here’s a handy warning sign: the customer “approves” security updates manually, and the last update to their PCs/Servers was the most recent Service Pack for the OS (usually for Windows XP).  Take a little time and check the AD replication status before you proceed Smile

Note that this new tool does not support Windows Server 2000 – that’s long since left extended support.

5 thoughts on “New AD Replication Status Tool”

  1. Hi,

    Dynamic AD Replication Checker Tool Version 2.0 has been released at
    I have also fixed a number of bugs reported by the users. Thanks Users!

    New Features supported in Version 2.0:

    Ø Monitor AD Replication based on schedules
    Ø Check,Troubleshooting Replication issues for all or individual Domain Controllers
    Ø Check Orphaned Domain Controllers, if any
    Ø Individual Naming Context Replication Status
    Ø Easy navigation of Objects in Objects Pane
    Ø Execute Individual Columns
    Ø Populate Instance Groups in Object Pane
    Ø Add Site/DC Manually
    Ø Save Session in local database
    Ø Switch to Monitoring and Console Version at any time
    Ø Check Error or Warning Events on Domain controllers
    Ø Perform DNS Test, check SOA, NA, and Forwarders
    Ø DC Event Log Tests
    Ø DC Patch Status
    Ø Network Configuration on the Destination Domain Controllers
    Ø Easily check Status of Domain Controller Services
    Ø Check AD Pending Replication Jobs and Naming Contexts in Sync
    Ø 164 Dynamic Columns for Server Object available

  2. I have a working copy of ADRST and use it daily. I’ve cleared up a lot of replication issues however I still have old entries that are false positives and I would like to remove them. Replication is successful (or a last successful sync within 24 hours) so I know replication is working.

    How do I remove entries that are false positives?

  3. In case the old records are stored in application’s data, just uninstall the tool, try to even remove it from registry and reinstall it. It should be ok this time.
    The best approach would be to install the tool on other machine (a fresh install) and check for what you call ‘false positive’. Still having them in this scenario means this data is stored in AD and you should perform a metadata cleanup there.
    I am curious – can you give us some examples of false positives.

    George Costache
    AD PFE

    PS. I am always using two powerful utilities to check the health of the replication
    Repadmin /replsummary
    Repadmin /showrepl /v
    Dcdiag /test:topology
    Dcdiag /test:replications

    Are these lines showing no errors for you?!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.