Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Adding a 3rd 2012 DC to 2 working DCs fails to populate SYSVOL and NETLOGON on the new DC

$
0
0

Hello Technet,

Have read into nearly every thread that deals with this issue from technet to some guys blog in Japanese and so on ... each instance is a little different, most of them contain a lot more errors, and none of them feel just right in terms of resolution.  

Short story, I installed a 3rd DC and it’s SYSVOL and NETLOGON did not populate.  I demoted it, created a new VM with a new name and different IP and same result.  Before I demote this one and burn my office to the ground… I would like to get to the bottom of this issue.  

Steps that let to this moment:

I had a S2008 based network with 2 DCs since 2009.  In the last 3 months I have slowly replaced  all my servers to S2012.  First was a S2012 DC and that went very well.  Then a second S2012 DC and that also went well.  After some time, I took the 2008 DCs off line and all good.  Upgraded Exchange /LYNC from 2007/2010 to 2013 and smooth.  

All of the new servers are Gen 2 S2012 VMs on Hyper-V 2012 R2

Last week, setup a second Hyper-V host for replication and to host a 3rd DC.

By the way, I did not clone any VMs.  

The new DC promotes successfully ahem, but then I notice sysvol and netlogon did not populate.  Now before I promoted, I ran DNSLINT on both DCs and they passed 100%, I ran DCDIAG on both DCs and they passed.  I ran nearly every possible DCDIAG test on the new member server before promoting it and it passed.  So why would DFSR fail to fly?  

AD objects seem to populate onto the new DC.  I can delete an AD object on one or add and it populates to the new DC.  But SYSVOL and NETLOGON are not populating  

REPADMIN

Replication Summary Start Time: 2014-01-07 08:50:17

Beginning data collection for replication summary, this may take awhile:

  ......

Source DSA          largest delta    fails/total %%   error

 JEFFERSON                 59m:04s    0 /  10    0

 REAGAN                    56m:18s    0 /  10    0

 ROOSEVELT                 59m:04s    0 /  10    0

Destination DSA     largest delta    fails/total %%   error

 JEFFERSON                 01m:18s    0 /  10    0

 REAGAN                    59m:05s    0 /  10    0

 ROOSEVELT                 56m:19s    0 /  10    0

(One warning here, got bored with the planets and opted for US presidents this time, no political preference here =))

Roosevelt is my PDC

Jefferson is the second DC that is working “ok”

Reagan is my new DC

C:\Users\darthvader>domain query fsmo

Schema master               JEFFERSON.domain.com

Domain naming master        JEFFERSON.domain.com

PDC                         ROOSEVELT.domain.com

RID pool manager            ROOSEVELT.domain.com

Infrastructure master       JEFFERSON.domain.com

What setting am I missing here?  Short of setting up a 4th DC on the same Hyper-V host… I would prefer to resolve this issue because I can’t find any communication issues between the two hosts.  They are both plugged into the same switch, latest drivers, both have Intel quad port NICs, and all other forms of communication is ok between...and the other 25 hosts plugged into the switch communicate ok.  I even ran ping and file transfer test and no dropped packets.  

Would really appreciate some help before I open a case with MSFT.   Below is all the info you will want to see, sorry if I’m leaving out details or assuming you know something, I have not slept in a few days.

Here is the link to all my DCDIAG IPCONFIG and DNSLINT reports: REPORTS

Thank you.  




Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>