12 replies
by robshan
by bkubai
by viperian
Promote the other BDC to PDC, demote the PDC to a BDC. After this, synchronise the entire domain. Wait some time (depends on how large the domain is)to let the sync do its work. Then stop the netlogon service on the demoted PDC. Try logon with a client. If this works. Start the logon service again on the demoted PDC. Promote the BDC (demoted PDC) an demote the new PDC.
Good Luck.
by bkubai
by viperian
What you also can do is, to get a workstation, make it a BDC of the domain, promote this machine to pdc. Check the eventlogs on all domain controllers wether they accept it. Otherwise you have some machines running in a other domain (because of the SID's) but with the same name. Take the original PDC offline. Remove the computer account from the domain. Sync the domain. Then make a new computeraccount for the former PDC in this domain a put the former PDC back online.
Good luck
by bkubai
by calves
I can't tell you what's wrong, but I can tell you that I learned long ago:
DCs do not like to have name and domain info changed on them. I seen it happen before, but I never seen a fix. Perhaps in the registry...
Good luck!
by bkubai
by mmohammed
by bkubai
by guy
I agree with calves. Do not rename Domain controllers.
So, the only way out is to reverse all the renaming. THEN Promote the BDC that you want to be the PDC.
by bkubai
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending