Bare Metal Domain Controller Migration

[Guest Craig Lewis]

Hello,

 

We have a domain controller running on a dell 2850 server which we want to

migrate to a new piece of hardware. This machine is a domain controller,

smtp server and DNS server. For a host of reasons we need the new hardware

to run a domain controller with the same name and same IP address as the

currently running domain cotroller. We have started to investigate products

from Symantec, PlateSpin and Altiris. One of the reasons we feel like we

need to look at such products is that we don't feel like the server can be

down for an extended period of time. To do this manually would require

demoting from the domain, changing the name, IP, etc. Then Bringing up new

server, promoting to DC, configuring smtp, etc. This would take a long time

if it went smoothly with no problems. Any advice you might suggest or

vendors that would be helpful would be much appreciated.

 

Thanks.

[Guest Meinolf Weber]

Re: Bare Metal Domain Controller Migration

 

Hello Craig,

 

!!!BEFORE STARTING ANYTHING PREPARE A GOOD BACKUP!!!

 

I would prevent keeping the old name, would be made live really easier.

 

Anyway, choose a machine even an older one, which is capable of running the

actual OS, BTW which one?, promote it as additional DC in

the running domain, make it DNS server (AD integrated zones) and the rest

you need, please specify in detail, so maybe we can give you more detailed

infos.

Run dcdiag /v, netdiag /v and repadmin showreps to check for errors, additional

check event viewer and solve existing errors.

 

If it is up and running transfer, NOT seize, the 5 FSMO roles to the temporary

DC, make it Global catalog and give it time for replication all infos.

Run dcdiag /v, netdiag /v and repadmin showreps to check for errors, additional

check event viewer and solve existing errors.

 

If no errors exist, you have to find a time where you are able to remove

the DC which should be replaced. Run dcpromo to demote it, after reboot stop

DNS server service and delete all existing DNS server entries. If this is

done, rename the computer to whatever or delete it from the domain. Check

in AD and DNS that no entry exists for the old name and start with the new

server, install OS, give it the now free name and add it to domain. Then

promote it to DC, make it DNS server, add everything it should do etc.

Run dcdiag /v, netdiag /v and repadmin showreps to check for errors, additional

check event viewer and solve existing errors.

 

Now again:

If it is up and running transfer, NOT seize, the 5 FSMO roles to the new

DC with the old name, make it Global catalog and give it time for replication

all infos.

Run dcdiag /v, netdiag /v and repadmin showreps to check for errors, additional

check event viewer and solve existing errors.

 

After that remove the temp DC, the same way like before the other DC.

 

And you should really think about at least one additional DC for redundancy.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hello,

>

> We have a domain controller running on a dell 2850 server which we

> want to migrate to a new piece of hardware. This machine is a domain

> controller, smtp server and DNS server. For a host of reasons we need

> the new hardware to run a domain controller with the same name and

> same IP address as the currently running domain cotroller. We have

> started to investigate products from Symantec, PlateSpin and Altiris.

> One of the reasons we feel like we need to look at such products is

> that we don't feel like the server can be down for an extended period

> of time. To do this manually would require demoting from the domain,

> changing the name, IP, etc. Then Bringing up new server, promoting to

> DC, configuring smtp, etc. This would take a long time if it went

> smoothly with no problems. Any advice you might suggest or vendors

> that would be helpful would be much appreciated.

>

> Thanks.

>