On Wed, Feb 24, 2010 at 6:17 PM, Michael B. Smith <[email protected]> wrote: > On the "bad" system, you should be able to stop netlogon, remove > netlogon.dns, start netlogon, ipconfig /registerdns, force replication. That > should take care of it.
I tried (most of) that. I didn't remove the "netlogon.dns", but did try the stopping/starting the service, registerdns, and "netdiag /fix" and "dcdiag /fix". None of that helped. And then I couldn't DCPROMO it back to a member server. So we eventually manually removed it from AD, using the "How to remove a completely orphaned DC" method in KB 555846. We'll rebuild that DC from scratch today, and try again. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
