Home / server / Questions / 361724
Accepted
vlannoob
Asked: 2012-02-20 16:48:30 +0800 CST

Server 2008DC Replication issues with 2003DC

  • 772

Still have an ongoing replication issue on my network. Long story short:

Existing 2003 Domain (2003 Level). Added a new 2008R2 server. Did the usual Adprep/forestprep steps as required. Transferred FSMO roles etc.

Had some initial issues creating Sysvol and Netlogon shares. Rectified with assistance from here running the Burflags reset workaround.

Now, strangely, I have the following issues:

In AD Users and CLients on the 2008DC I have all the users....but nothing in any of the other OU's. Nothing in Computers, Builtin, Domain Controllers etc but on my 2003DC they are all there. So its not pulling the info out of 2003DC and putting it into the 2008DC.

But, if a create a user on the 2008DC it will successfully replicate back to the 2003DC AND if I create a user ont he 2003DC it will replicate successfully back to the 2008DC.

Any ideas?? I'd like to kill off the 2003DC but can't till I get this working 100%.

Also, ont he 2008DC, and this may be related. I get repeated Event 6's and 13's - to do with failing to auto-enroll - RPC server unavailable. Again, any help is apprciated.

active-directory certificate-authority windows-server-2008-r2

1 Answers

  1. Best Answer

    Given that there have been issues, it's possible that inbound replication from the 2003 DC has been stopped due to detection of a lingering object. This is due the feature known as strict replication.

    You can use repadmin /showreps to determine if replication is working. If replication is not working, the date in the output will not be recent.

    If this is the case, the fix is to remove the lingering objects, and hopefully there aren't many. One tool is to use repadmin /removelingeringobjects /advisory_mode to detect lingering objects that may be removed, and run without the advisory_mode switch to fix them. In practice, this only works on small domains with a reasonable number of objects. It can run forever on large domains.

    Fixing Replication Lingering Object Problems (Event IDs 1388, 1988, 2042)
    http://technet.microsoft.com/en-us/library/cc949124%28v=ws.10%29.aspx

    • 1