Why do you need to have the domain controller using the same name as before?
I wouldn't do this at all. Bring up a new DC, and point whatever you need to (via logon scripts or group policy) to the new name. Much cleaner... If you insist on ending up with the same DC names, then build a temp DC, get it working, decommission the old DC (then rename it), and then build a new DC with the old name. Still something I would seriously avoid... * * *ASB* *http://about.me/Andrew.S.Baker* *Harnessing the Advantages of Technology for the SMB market… * On Tue, Jul 19, 2011 at 5:58 AM, Pierre Camilleri < [email protected]> wrote: > I re-ran DCpromo and then DNS worked well. Prefer the Swing migration. > I have a further query if you don't mind. I now have two domain > controllers, one is the current source domain controller and the other one > is the target domain controller. I now wish to promote the target domain > controller to be the main domain controller. The source domain controller > will be decomissioned. How best should I go about it? Are the following > steps correct and in the right order? > > 1. Rename the target domain controller using the same server name and same > ip address. > 2. Demote the old domain server by running DCpromo on it. This will then > become a member server. Rename it as otherwise there would be two servers > with the same computer name. > > Thanks > Pierre > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
