Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 152
  • Last Modified:

DC replication broken

I have a network with a few DC. One of them is SBS 2007. That server is no longer running Exchange but it is used for Document redirection and more importantly RD Gateway services.

This was a physical server that recently was converted to a VM.

All of a sudden I am having very strange issues. I believe the problem is all related to replication. An OU is missing on SBS server. Even DNS is not quite working correctly.  I can't access a member server by \\servername  I get the error "The target account name is incorrect." I can ping servername and servername.domain.local What is very bizarre is any workstation that has SBS server as it's DNS server, also gets this message. I change the workstation  DNS to point to another server and they can access the member server.
      
In HKLM\System\CurrentControlSet\Services\NTDS the key DSA not writable is set to 4. That appears to be from converting to VM

In sites and services when I try to replicate from that server I get "The naming context is in the process of being removed or is not replicated from the specified server"

I ran repadmin /showutdvec servername dc=lf,dc=local.
It shows the SBS server as "Retired" and it also shows it it replicating. I believe this is the way it should be since I converted it to VM.

Is there a way to fix this. Is demoting the SBS server the only option?
0
ajdratch
Asked:
ajdratch
3 Solutions
 
Peter HutchisonSenior Network Systems SpecialistCommented:
If replication has not worked for 60 days or more, then it is effectively passed its tombstone limit and should be demoted to a member server. Run dcpromo and remove it from your domain, use ntdsutil to do any meta data cleanup afterwards.
0
 
ZenVenkyArchitectCommented:
Is the old SBS still in the network??
DO NOT DEMOTE SBS server.

As per your update I think that replication was broken before you converted SBS to VM. If SBS server still in network, bring it back and remove VM SBS completely. Fix replication first and then convert SBS to VM again. If you tries to demote current VM SBS server then I guess it might give you more issues. Because you have USN rollback issue at this moment.
0
 
ajdratchAuthor Commented:
I tried this and so far it looks like it has solved my problem
http://exchangeserverpro.com/recovering-a-single-domain-controller-from-a-usn-rollback/
1

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now