Welcome to MSFN

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


jcarle

Renaming a domain in Server 2008 R2

7 posts in this topic

I'm preparing on doing a domain rename (I'm changing a domain from "domain.com" to "network.domain.com") and I've been reading on the documentation provided here : http://technet.microsoft.com/en-us/library/cc738208(v=WS.10).aspx

One part has got me a bit nervous : "Be sure to avoid any possible name conflicts with the new names that you choose. Name conflicts can cause unpredictable and severe results. For example, a conflict with the NetBIOS name can render a domain controller unusable because you might not be able to properly remove AD DS from it."

Now, even though "domain.com" will be changing to "network.domain.com", the NETBIOS name of "DOMAIN" will still be "DOMAIN". Is that in itself a conflict?

Also, this is a single DC domain without Exchange or DFS shares. Can someone please check over my notes and see if I've missed anything?

Prepare DNS

Create new DNS zone for "network.domain.com"

Prepare the domain rename

rendom /list

edit DomainList.xml

check DomainList.xml using rendom /showforest

Do the actual rename

rendom /upload

rendom /prepare

rendom /execute

Update group policy

gpfixup

Clean changes

rendom /clean

Update DC DNS

Use My Computer and change primary DNS suffix

ipconfig /registerdns

Update DHCP information

Change all domain related paths in DHCP configuration to clients

Update computers

Reboot all domain attached computers twice

Edited by Tripredacus
fixed link
0

Share this post


Link to post
Share on other sites

Never did a domain rename, indeed if you keep the same netbios name, it shouldn't proceed properly.

Also, when you choose the dns suffix domain name be sure not to use something already registered in the internet. It might cause wrong resolution and create a lot of problem if your dns are configured to also cache/resolve external adresses. The right way is either using something that can't exist ( ex: Mydomain.internal )or buying a domain and make it point on your dns.

0

Share this post


Link to post
Share on other sites

The domain DNS does resolve to external DNS and the domain is an internet registered domain which we own. However DNS resolution is properly setup and does not conflict.

If the NETBIOS name does not change and it is in fact a requirement that it does change, does that mean I'll have to do a double rename? Once to a fake and temporary domain, then a second time to the final desired domain?

0

Share this post


Link to post
Share on other sites

Have you looked into adding a child domain and migrating the objects to that?

0

Share this post


Link to post
Share on other sites

Have you looked into adding a child domain and migrating the objects to that?

I have but you can't remove the parent domain from the forest after doing so. Since I am going from a parent domain as the forest root to a child domain as the forest root, the only options are to either rename the existing domain or create a new forest all together.

When you restructure a forest, you can move a domain (except the forest root domain) anywhere within the forest in which the domain resides.

Edited by jcarle
0

Share this post


Link to post
Share on other sites

The domain DNS does resolve to external DNS and the domain is an internet registered domain which we own. However DNS resolution is properly setup and does not conflict.

If the NETBIOS name does not change and it is in fact a requirement that it does change, does that mean I'll have to do a double rename? Once to a fake and temporary domain, then a second time to the final desired domain?

Yep a double rename might be the way but you may be stuck with the temporary domain for a long time.

The best way should be to test it with a few servers and workstations (cloned from the real ones) in an isolated virtual/physical environment. I'd test and validate all the steps there (and working with virtual machine would help a lot as you can create snapshot at each step). You'll need at least 2 DC and 1 workstation to make useful tests. If possible, i'd try to have more than those.

0

Share this post


Link to post
Share on other sites

Couldn't you use a VM and migrate the root domain to it, then create a child domain and then migrate the objects? You could even use any old computer to house a root domain that does nothing other than just sitting there.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.