If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
COURSE of the MONTH
8 days, 8 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
DC replication broken
Posted on 2016-09-19
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\CurrentControl
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?
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\CurrentControl
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?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
4 Comments
Active today
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.
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.
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.
Active 2 days ago
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/
http://exchangeserverpro.com/recovering-a-single-domain-controller-from-a-usn-rollback/
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
A hard and fast method for reducing Active Directory Administrators members.
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job.
The first step is to acquire the necessary licen…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month8 days, 8 hours left to enroll
764 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.