On Tue, Apr 14, 2015 at 11:53 AM, Miller Bonnie L. < [email protected]> wrote:
> Have you run > > > > DFSRDIAG POLLAD > > > > or restarted the DFSR services on the two servers in question, just in > case? I’m wondering if the old 2008 R2 box isn’t looking at the new DC for > updated info, or vice-versa. > > > I think/hope this did it. I did DFSRDIAG POLLAD on the demoted DCs (and restarted both of them), and I haven't seen a DFS related error in DCDIAG since yesterday at 8:25AM, so over 24 hours,. (oddly, it was only 1 of the 2 demoted DCs that were referenced in the errors). (I am running DCDIAG /C /E /V in my parent domain, so it does the entire forest) These errors were in my parent domain. To avoid such errors in my child domain, and to more accurately reflect the actual environment, I now have 2 Win2008 R2 DCs, and 2 Win 2012 R2 DCs in that domain. And I will demote both Win2008 R2 DCs. This will leave me with more than 1 DC in the child domain, which more accurately reflects my production environment. (here in the testing environment, I now have only 1 DC in the parent; in reality, I will always have at least 2 DCs at all times in all domains. That may help with the DFSR errors ...)
