DC in remote site isn't replacting after PDC failure

Over the weekend our main domain controller failed.  I've transferred roles and cleaned up metadata using ntdsutil.  A DC in a remote site doesn't seem to be replicating properly; when I run "dcdiag /test:Knowsofroleholders /v' on it, it has the wrong server listed in the FSMO roles.

How can I be sure that it's replicating, and what else should I check?
LVL 2
David WilliamsonIT DirectorAsked:
Who is Participating?
 
Mike KlineConnect With a Mentor Commented:
If the box failed did you seize the FSMO roles?
Check the logs on that DC, use dcidag, and repadmin  (/showreps /replsummary and /showrepl are decent switches)
You can also check FSMO holders by  
netdom query fsmo
Is this the only box that is reportin gthe wrong FSMO holders?
Thanks
Mike
0
 
David WilliamsonIT DirectorAuthor Commented:
Yes, I seized the roles on another local DC.  Running readmin /showreps, a replication attempt to the new holder of all the FSMO roles shows "Last attempt @ (never) was successful."

running 'netdom query fsmo' on the remote server shows mixed results.  It has one of the roles correctly listed (Schema Master), but the rest still show the failed server name.  Running that same command on the new recipient of the seized roles shows that it has all the roles assigned.

0
 
David WilliamsonIT DirectorAuthor Commented:
I just ran dcdiag /fix, and re-ran the netdom query, and now the remote DC shows all the proper roles!

What else should I verify before calling it good?
0
 
Mike KlineCommented:
double check the event logs (directory services and FRS logs)  Just to make sure there are no other issues.  Nice work!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.