?
Solved

HELP!!!  My current DC's are not reflecting the change of primary DC's in AD Sites & Services...

Posted on 2011-09-10
6
Medium Priority
?
220 Views
Last Modified: 2012-08-14
Hi, I need help.  Recently, I demoted what use to be my primary DC in my domain, Server 2003 SP2 from being a DC.  I have all my FSMO roles on my new primary DC, Server 2008 R2 SP1.

My new primary DC has been in place for several months now.  So, it should be good to go in this aspect of replication time, etc.

From a member here, mkline71, gave me this link  http://blogs.technet.com/b/markmoro/archive/2011/08/05/you-are-not-smarter-than-the-kcc.aspx
which states let KCC do it's job and recreate the AD Sites & Services connections between my multiple branch sites, hoping that KCC would be smart enough to select the correct new primary DC for all branch DC's to point back to for replication.

So, I have waited for nearly 2 hours and 1 of my 3 branch sites displays the correct new primary DC in AD Sites & Services.

The one branch DC that is displaying correctly in AD SItes & Services is a Server 2003 x64 with latest SP.

The other 2 branch DC's, one is a Server 2008 R2 SP1 & the other is Server 2003 x64 with latest SP.

Here is something even more strange, the one branch DC (Server 2003 x64) is still displaying the old primary DC that I have demoted and the other branch DC that is displaying the correct new primary DC in AD Sites & Services.

Should I just be patient and see if it corrects itself in the new couple hours or is there something more seriously wrong that needs my immediate attention?

Any ideas or suggestions will be greatly appreciated.
0
Comment
Question by:rsnellman
[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
  • 5
6 Comments
 
LVL 57

Expert Comment

by:Mike Kline
ID: 36516838
During the dcpromo the old DC won't be removed from sites and services, go in and delete the old dc manually.

Are you seeing any issues with replication?

I'll be on and off...in and out today.

Thanks

Mike
0
 

Author Comment

by:rsnellman
ID: 36516844
OK, I haven't deleted the old DC from Sites & Services yet, but my Central Site in ADSS is made the changes automatically, but 2 out of 3 of my branch sites (North Site & South Site) are not displaying / reflecting the change of the old DC being gone from the AD SItes & Services automatically generated connection for Replication From.
0
 

Author Comment

by:rsnellman
ID: 36516846
You want to to attempt a Replication Now from AD Sites & Services on each of my branch sites that does not display the correct "<automatically generated> From Server"?
0
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!

 

Author Comment

by:rsnellman
ID: 36516854
If I go into the properties of the "<automatically generated> old DC within the North Site or South Site/Servers/NorthServer/NTDS Settings.  

In General tab, it displays in Relicate from area
Server: invalid
Site: invalid
Relicated Naming Context(s): invalid

If I click the "Change" button, it allows me to select the new primary DC from the list, but then gives me a warning about it will not be a automatically generated connection.

0
 

Accepted Solution

by:
rsnellman earned 0 total points
ID: 36516859
Wait...the North Site server just changed to the correct new primary DC.  Now the South Site server has changed, but does not have the correct new primary DC displayed yet.  I am confident that it will change soon enough.  Guess I need to be more patient and stop stressing out over nothing.

Thanks anyways.
0
 

Author Closing Comment

by:rsnellman
ID: 36541411
This is the answer.  Just needed to be patient and wait for KCC to do its magic.

Thanks.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

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

Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
This process allows computer passwords to be managed and secured without using LAPS. This is an improvement on an existing process, enhanced to store password encrypted, instead of clear-text files within SQL
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Suggested Courses

765 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