How Up to Date Are My Domain Controllers?

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2

Checkprop compares properties of specified domain controllers to determine if they are up-to-date with each other. The source domain controller contains the original information that needs to be checked. The destination domain controller data is compared to the source domain controller data.


repadmin /checkprop <DC_LIST> <NamingContext> <OriginatingDCInvocationID> <OriginatingUSN>




Specifies the host name of a domain controller, or a list of domain controllers separated by a space. For details about <DC_LIST>, see repadmin /listhelp.


Specifies the distinguished name of the directory partition on the source domain controller.


Specifies the unique hexadecimal number that identifies an object on a source domain controller. The InvocationID can be retrieved by using the /showrepl operation.


Specifies the Update Sequence Number (USN) for the object on the source domain controller. The USN is for the object whose InvocationID is already listed.

Example: Checking replication latency on the BRANCH3 domain controller

Latency output reveals that the highest OriginatingUSN that BRANCH3 has knowledge of for its HUB site bridgehead server, BRANCH-HUB-BH, is 137844. It is also apparent that the last successful replication attempt with this HUB site bridgehead server was just less than 5 minutes.

Repadmin /showutdvec

Example: Comparing how up-to-date other domain controllers in the enterprise are with respect to the OriginatingUSN

In Figure 3.6.2, note that BRANCH2 domain controller is not up-to-date with the rest of the domain controllers.

Repadmin /showutdvec

Example: Further investigation from the perspective of the BRANCH2 domain controller

Latency was calculated for BRANCH2 which revealed that it is not aware of the latest OriginatingUSN from BRANCH-HUB-BH and in fact it is behind by approximately 20 minutes. Because the latency in this example is just less than 20 minutes (replication interval being 30 minutes) it is expected to catch up during the next replication cycle.

Repadmin /showutdvec