Solved

DC replication broken

Posted on 2016-09-19
4
32 Views
Last Modified: 2016-11-04
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
Comment
Question by:ajdratch
4 Comments
 
LVL 19

Assisted Solution

by:Peter Hutchison
Peter Hutchison earned 250 total points
ID: 41805579
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
 
LVL 9

Assisted Solution

by:Zenvenky
Zenvenky earned 250 total points
ID: 41805732
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
 

Accepted Solution

by:
ajdratch earned 0 total points
ID: 41806422
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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A safe way to clean winsxs folder from your windows server 2008 R2 editions
This article runs through the process of deploying a single EXE application selectively to a group of user.
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…

808 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question