On 6/1/2011 2:11 PM, Miller Bonnie L. wrote: > I hadn't seen your second reply before sending, but have you ever removed a > DC from your production domain? You might have a lingering object somewhere.
We've removed DCs before, sure. But they've all been graceful removals, with DCPROMO. (for example, when we upgraded from AD 2003 to 2008, we did it by adding a new 2008 machine, and then installing AD onto it. Later, we removed this temporary DC. And I don't see any DC references anyway (using ADSIedit) except the current ones. In fact, I see the problematic DC listed under the DFSR-Global Settings (as it should). When I run DCDIAG on DC #1, pointing at DC #3 (the one showing the error), it does not show the error. It knows it's supposed to use DFSR, and not NTFRS. It's only when I run DCDIAG *on* DC #3 that I see that error. Not when I run DCDIAG on #1 or #2, and not when I do a DCDIAG /S "DC #3" from DC #1 or DC #2. Time to try the classic MS fix ... a reboot. :-) We'll run Windows Updates, and bounce the box, and see what happens ... ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
