WellingtonIS
asked on
Transfer Domain Naming Master from a Crashed Server
I had a 2003 domain controller and it crashed and no chance of recovery and no backup. I also have a 2008 r2 server and the roles were split. I need 2 things a)add a 2012 to the domain and it will not add because it still thinks the domain is 2000 and add domain naming master role to this 2008r2 server. Is this possible?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The new 2012 server is seeing the old DC and I can't promote it.
Yes i realize that. You need to follow my steps in order, which i have provided in my first post. You need to seize the roles, perform metadata cleanup, then you will be able to promote the 2012 server as a DC.
Please read and follow all of the instructions and you will be fine.
Will.
ASKER
When I run metadata clean up message says a global connection already exists. No arguements should be specified. I ran everything and the roles seemed to have transfered. Yet the new server still sees the old server
Did you Seize the Role first to the 2008R2 DC?
You need to do that first. You cannot perform a metadata cleanup if a fsmo role is still assigned the domain controller.
Will.
You need to do that first. You cannot perform a metadata cleanup if a fsmo role is still assigned the domain controller.
Will.
ASKER
Yes I did. I seized the roles first. I'm rebooting my 2012 server. All the roles are transferred 100% I think the problem is AD on the new server. I added AD before I realized it was seeing the old DC. I just removed AD and I'm rebooting. I'll start over once the new server comes up
ASKER
OK when I reboot and try to add AD roles it's only seeing the old server??? I"m not sure why this is still occuring...
Before I continue repeating myself, please tell me what steps YOU have so far.
Will.
Will.
ASKER
OK here's what I've done I ran ntdsutil and siezed all the roles. I tried to run metadata cleanup and got that error You cannot perform a metadata cleanup if a fsmo role is still assigned the domain controller. This is the error when I try to run metadata cleanup
Now I can see the server but the new server still thinks the domain is a 2000 domain. Do I need to run adprep or domain prep? So now when I'm trying to promote the serve its tell me the domain is 2000??? The function level is 2008
error.png
Now I can see the server but the new server still thinks the domain is a 2000 domain. Do I need to run adprep or domain prep? So now when I'm trying to promote the serve its tell me the domain is 2000??? The function level is 2008
error.png
You need to run metadata cleanup from the 2008R2 Domain Controller when you are seizing the roles. If you have seized the roles successfully then try running this command repadmin /fsmo (you should see the 2008 DC as the new role holder, you can also check within ADUC as well).
Once you have done that Launch NTDSUtil Runas Administrator. Perform the cleanup (you also need to make sure that your account has the proper permissions as well. I would add you account to domain, enterprise and schema admins, just to be sure).
When these items have been removed from NTDSUtil, make sure that the 2003DC computer object has been removed from the domain controllers OU. Check DNS _msdcs.yourADdomain.com zone and go through all of the SRV records i.e. (pdc/gc/domain/forest etc) to ensure that the 2003 DC is removed. If you do see objects in the SRV records for the 2003 server you can just delete them.
Once this has been cleaned up, you then need to raise the Forest/Domain functional level to 2003 (at least) before you can promote your 2012 server to a DC.
Will.
Once you have done that Launch NTDSUtil Runas Administrator. Perform the cleanup (you also need to make sure that your account has the proper permissions as well. I would add you account to domain, enterprise and schema admins, just to be sure).
When these items have been removed from NTDSUtil, make sure that the 2003DC computer object has been removed from the domain controllers OU. Check DNS _msdcs.yourADdomain.com zone and go through all of the SRV records i.e. (pdc/gc/domain/forest etc) to ensure that the 2003 DC is removed. If you do see objects in the SRV records for the 2003 server you can just delete them.
Once this has been cleaned up, you then need to raise the Forest/Domain functional level to 2003 (at least) before you can promote your 2012 server to a DC.
Will.
ASKER
Ran everything and the old server is gone! All roles are transferred to 2008 r2 server. I still can't promote the 2012 server! It's doesn't see the Domain controller? I don't get it because I've installed AD on that box and it's there
ASKER
I think I'm going to have to wind up demoting the DC and redoing the entire domain. That's will be next time I get back here. Thanks for trying to help but nothing is working.
Whoa! Seriously? All of those steps i provided are the correct way to remove a DC from the domain. Re-creating the domain will take a lot of work, i would consider re-trying it.
Will.
Will.
ASKER
Everything you said was 100% correct. The issue was I was able to raise the function level of the domain but neglected to realize that the forest level was still 2003 because it wasn't showing up. Once I found out where is was I raised the forest level to 2008 r2 I rebooted the server and tried again. This time I was successful in creating the 2012 domain controller.
ASKER