Gcku
asked on
windows 2003-2008- domain controller rename = no domain
Hello,
Big problems here.
There was a 2003 domain controller 'server2009'.
Raised from 2000 to 2003 functionality level, adprep ecc.
Added dc1 on windows 2008 r2 with dcpromo.
functional
Added a RODC "dc2zentyal" (zentyal not windows, hence read only)
Demoted server2009, rebooted, renamed to oldserver2009 = no more 2003 dc with new name.
Domain was fine working on dc1.
Then we renamed dc1 to server2009, using netdom computername dc1.domain.local /add:server2009.domain.loc
Tried a /makeprimary and remove. Both failed with reason: "" (no reason)
But the only rw domain controller now has hostname server2009. Unfortunately the domain does not work, netlogon does not start error 0000064.
Tried a dns clean up renaming any occurrance of dc1 to server2009
dcdiag /fix states still dc1, failed connection to dc1.
Currently no domain controller is reachable.
dc2zentyal had completed the replica but is now disconnected before it gets screwed up too.
So I have:
a non working dc1.
no backups of system states of a working dc1,
a rodc dc2zentyal,
a demoted and renamed server2003,
a bks ntbackup system state from one month ago (no important changes). should I remove DC1 new and restore system state on the old demoted dc so it comes back as a normal dc and start over? Would that work?
What can I do? And what was wrong in renaming the dc? Should I have had another extra dc as global master ecc?
Here there are no lab procedures and no test envirnoments unfortunately, just a situation to fix
Big problems here.
There was a 2003 domain controller 'server2009'.
Raised from 2000 to 2003 functionality level, adprep ecc.
Added dc1 on windows 2008 r2 with dcpromo.
functional
Added a RODC "dc2zentyal" (zentyal not windows, hence read only)
Demoted server2009, rebooted, renamed to oldserver2009 = no more 2003 dc with new name.
Domain was fine working on dc1.
Then we renamed dc1 to server2009, using netdom computername dc1.domain.local /add:server2009.domain.loc
Tried a /makeprimary and remove. Both failed with reason: "" (no reason)
But the only rw domain controller now has hostname server2009. Unfortunately the domain does not work, netlogon does not start error 0000064.
Tried a dns clean up renaming any occurrance of dc1 to server2009
dcdiag /fix states still dc1, failed connection to dc1.
Currently no domain controller is reachable.
dc2zentyal had completed the replica but is now disconnected before it gets screwed up too.
So I have:
a non working dc1.
no backups of system states of a working dc1,
a rodc dc2zentyal,
a demoted and renamed server2003,
a bks ntbackup system state from one month ago (no important changes). should I remove DC1 new and restore system state on the old demoted dc so it comes back as a normal dc and start over? Would that work?
What can I do? And what was wrong in renaming the dc? Should I have had another extra dc as global master ecc?
Here there are no lab procedures and no test envirnoments unfortunately, just a situation to fix
ASKER
i did run adprep or 2008 would not have become a dc
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you remove the old dcname by netdom command after rename operation:http://technet.microsoft.com/en-us/library/cc738341(WS.10).aspx
You also need to ensure the health of DC is good before you proceed with other DC promotion.Run dcdiag/q and repadmin /replsum to verify the same.It is not recommended to have file server role on DC but if you have budget issue then you have no choice.You can have file server as windows/linux.
I will also recommend to have two DC in network for redundancy.
You also need to ensure the health of DC is good before you proceed with other DC promotion.Run dcdiag/q and repadmin /replsum to verify the same.It is not recommended to have file server role on DC but if you have budget issue then you have no choice.You can have file server as windows/linux.
I will also recommend to have two DC in network for redundancy.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
You could try seizing the operations master role on the 2008 dc:-
http://technet.microsoft.com/en-us/library/cc816779(v=ws.10).aspx