DCDiag error
-
I have the following DCDiag error
Starting test: NCSecDesc Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn''t have Replicating Directory Changes In Filtered Set access rights for the naming context: DC=ForestDnsZones,DC=mydomain,DC=net Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn''t have Replicating Directory Changes In Filtered Set access rights for the naming context: DC=DomainDnsZones,DC=mydomain,DC=net ......................... myserver-AD2 failed test NCSecDescI found this post http://www.squidworks.net/2013/02/solved-dcdiag-fails-for-ncsecdesc-test-and-adprep-rodcprep-fails-to-fix-it/ which talks about running
adprep /rodcprepto solve the problem as a first step.
Since my setup isn't purely 2008 R2 (i.e. I have one 2008 R2 DC and one 2012R2 DC) I don't know if I should run adprep from the 2008 R2 media or the 2012 R2 media?
Additional information - I'm running FFL and DFL of 2003. Don't think this matters, but wanted to mention it anyhow.
Thoughts?
-
The above posted link references this MS KB https://support.microsoft.com/en-us/kb/967482
It says you can ignore this error if you're not planning on deploying any RODCs - which I don't, but come on, who likes to see failures in tools they run, even if they can ignore them?
-
Yeah I never liked that about MS's tools, oh hey, here's an Error, but "Next" is available anyways.
I understand the logic of it, if you were doing something special that they want you to see the errors, but yeah. It's annoying to say the least.
-
@Dashrender said:
The above posted link references this MS KB https://support.microsoft.com/en-us/kb/967482
It says you can ignore this error if you're not planning on deploying any RODCs - which I don't, but come on, who likes to see failures in tools they run, even if they can ignore them?
We had quite the discussion about that just recently
-
@scottalanmiller said:
@Dashrender said:
The above posted link references this MS KB https://support.microsoft.com/en-us/kb/967482
It says you can ignore this error if you're not planning on deploying any RODCs - which I don't, but come on, who likes to see failures in tools they run, even if they can ignore them?
We had quite the discussion about that just recently
Where? Am I just blanking on it, or was I not involved?
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
The above posted link references this MS KB https://support.microsoft.com/en-us/kb/967482
It says you can ignore this error if you're not planning on deploying any RODCs - which I don't, but come on, who likes to see failures in tools they run, even if they can ignore them?
We had quite the discussion about that just recently
Where? Am I just blanking on it, or was I not involved?
It was mostly with @JaredBusch and ownCloud
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
The above posted link references this MS KB https://support.microsoft.com/en-us/kb/967482
It says you can ignore this error if you're not planning on deploying any RODCs - which I don't, but come on, who likes to see failures in tools they run, even if they can ignore them?
We had quite the discussion about that just recently
Where? Am I just blanking on it, or was I not involved?
It was mostly with @JaredBusch and ownCloud
Oh the whole repo has old stuff thread.
