best strategy for domain name change

[Kevin Laro]

Hi,

I need to rename our domain name, because it was set up as top level
domain (xxx instead of xx.yy) and causes problems.

Now I am looking for the best strategy to do that without removing AD
and setting evrything up again (user entries, rights and so on)

Environment:

1 Win2k server = dc, dns, dhcp (first server)
20 clients (win2k,winXP)

temporary I have an additional pure with win2k installed server to
use for the procedure (second server).

My current plan, thanks to some help, is to

1. set up a temporary second domain temp.yy on the second server
2. change all user profiles to server based profiles
3. migrate with admt all entries to second server (including user
profiles on server)
4. demote first server with dcpromo and set up the right domain name
xx.yy
5. again migrate with admt from second server to first server
6. change user profile to be saved locally again
7. get rid of second server again

However I was told I can also set up second server with the domain
name I want to use and do not need to migrate a second time back to
first server (apparently tis works with delegation too). I dont know
exactly how...?!

Can anyone confirm those steps or does one know a better strategy??

Thanks for any comment,

Kevin Laro

 

[Paul Bergson {MCT, MCSE}]

If you are only looking to change the domain name and not any of the
hierarchy. You might want to look at migrating to 2003. Natively 2003
allows domain name changes, it isn't a perfect migration. It has been a
while since I have looked at it, but if I remember right you still have to
remove and add all client workstations just like you would if you were to
move them from one domain to another. But you would have to only do it once
as compared to having to do it twice with your way. Take a look at this
option as well. I can't give you a complete scenario since I'm still
educating myself on 2003.

Paul Bergson MCT, MCSE, CNE, CNA, CCA

 

[Kevin Laro]

If you are only looking to change the domain name and not any of the
hierarchy. You might want to look at migrating to 2003. Natively 2003
allows domain name changes, it isn't a perfect migration. It has been a
while since I have looked at it, but if I remember right you still have to
remove and add all client workstations just like you would if you were to
move them from one domain to another. But you would have to only do it once
as compared to having to do it twice with your way. Take a look at this
option as well. I can't give you a complete scenario since I'm still
educating myself on 2003.

Paul Bergson MCT, MCSE, CNE, CNA, CCA

Thanks Paul,

thats an option. However win2k is sufficient for our little network
and I dont want to upgrade and maybe being forced with new issues. I
guess I just go the hard way...)

Kevin