Easiest way to rename a domain?
Hi guys, long story short... I inherited a bunch of equipment from a company that was supposed to host our EMR, which fell through. I would like to use this stuff in our environment but they had things set up with a different doamin. i have tried the rendom utility, but im not having much luck. is there another utility that i can use to rename the domain on 2 domain controllers? i dont care if we have to pay, i just need to get this done. I cant wipe it out and start over because they never transferred licensing etc. All servers are 2008R2
Comments
-
RobertKaucher Member Posts: 4,299 ■■■■■■■■■■Print a copy of this and go through every single line:
Appendix C: Checklists for the Domain Rename Operation
You will have to follow this guide. I have never seen 3rd party software to do this because of the sensitivity of the operation.
Introduction to Administering Active Directory Domain Rename
And remember, this is complicated. The white paper for doing this in 2003 was literally book length. I love TE but TE is a certification forum it's not designed for this sort of level of technical help. Go tot he TechNet forums and solicit the help of MS MVPs - ask your questions before attempting something. This sort of thing could completely fubar the DCs and require you to restore from backup.
-
tdean Member Posts: 520yikes, i might just be better off setting up a new DC. thanks for the links!
-
Claymoore Member Posts: 1,637It's a good thing you aren't having much luck. Did you do any research into what is involved in renaming a domain? It's more than running rendom and grabbing a cup of coffee.
How Domain Rename Works: Active Directory
Are you trying to to get these servers that were in the hosting environment into your domain? Because rendom isn't the way to do that. Even if you did rename the domain to match your current domain, it wouldn't be the same domain and you would have a real mess on your hands.
Do you just want all these servers in your domain instead of the hosted domain?- Join your member servers to the new domain.
- Demote the domain controllers so they are no longer DCs.
- Join them to the new domain, and promote them if you want them as domain controllers again.
- Use the Active Directory Migration Tool to move the servers and accounts to your exisiting domain.
- Create the trusts, move the accounts and servers.
- Demote the domain controllers so they are no longer DCs.
- Join them to the new domain, and promote them if you want them as domain controllers again.
-
undomiel Member Posts: 2,818I will second all of what Claymoore said. Hopefully it is the first scenario and not the second one.Jumping on the IT blogging band wagon -- http://www.jefferyland.com/
-
tdean Member Posts: 520Hi guys, thanks for the help. Yeah, i just wanted to join them to our domain. I may just wipe the DC out and start over. i removed the term servers from the domain and rejoined them. the problem was that none of the MS licensing etc was transferred so i dont have the product keys etc to start over and i have to set up the licensing for the 2008 "term server" env.
starting over seems like the best way to go. none of this stuff is in production, its just sitting down stairs collecting dust.
what i'd like to do is put a DC and term server environment at our remote location so they are not as reliant on us at the main site. -
RobertKaucher Member Posts: 4,299 ■■■■■■■■■■After seeing Claymoore's post I question my understanding of your message.I would like to use this stuff in our environment but they had things set up with a different doamin.
When I read this I understood "... a different name than the one we wanted to use" and not "... a different domain than the one we are currently using." If this is the second, then you would just have to establish a trust between the two forrests.
But I think that is moot as you've already come to your decision and I think for the better. -
tdean Member Posts: 520RobertKaucher wrote: »After seeing Claymoore's post I question my understanding of your message.
When I read this I understood "... a different name than the one we wanted to use" and not "... a different domain than the one we are currently using." If this is the second, then you would just have to establish a trust between the two forrests.
But I think that is moot as you've already come to your decision and I think for the better.
sorry about the confusion. i meant the latter. they set up a domain we were connected to via vpn. card.corp was their name. we are med.com (for example). Originally i had planned on demoting etc but was told to use the rendom utility. i think i will try the demoting of that DC and rejoining. at least i will learn somehting from it, i have been away from this stuff for a while.
thank you for your help. -
MAC_Addy Member Posts: 1,740 ■■■■□□□□□□RobertKaucher wrote: »2017 Certification Goals:
CCNP R/S