Replace a Win2000 server

[Jorge]

Hi,

I have to replace a win2000 adv server. The machine is running without problems,
this replacement is only for increase the performance ( from Pentium III to IV).

This is the only one, in my network. It is the DC, it has a DNS, an AD and DHCP.

The question is what is the best way to change it? or what options do I have?

I have scripts running for different users, policies in this server, and of course
users files.

I would like keeping the same name machine and the same IP address, is it possible?

Thanks in advance

 

[Bruce Chambers]

Hi,

I have to replace a win2000 adv server. The machine is
running without problems, this replacement is only for
increase the performance ( from Pentium III to IV).

This is the only one, in my network. It is the DC, it has
a DNS, an AD and DHCP.

The question is what is the best way to change it? or
what options do I have?

I have scripts running for different users, policies in
this server, and of course users files.

I would like keeping the same name machine and the same
IP address, is it possible?

Thanks in advance

How to Move a Windows 2000 Installation to Different Hardware
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q249694&ID=KB;EN-US;Q249694


--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever
count on having both at once. - RAH

 

[Enkidu]

Hi,

I have to replace a win2000 adv server. The machine is running without problems,
this replacement is only for increase the performance ( from Pentium III to IV).

This is the only one, in my network. It is the DC, it has a DNS, an AD and DHCP.

The question is what is the best way to change it? or what options do I have?

I have scripts running for different users, policies in this server, and of course
users files.

I would like keeping the same name machine and the same IP address, is it possible?

Well, Bruce has told you how to do it. But why not *add* the faster
machine to your network as a DC, and then migrate all services to the
new machine. There is much less risk (I think) in a migration compared
to a fork-lift replacement of a server.

You could leave the old DC (now with a lighter load) as a second DC in
the network in case the new server fails.

Cheers,

Cliff

 

[Jorge]

Thanks for your reply.
I had read it that KB, but I didnt want to follow it because it says
"Important This procedure is not recommended for domain controllers".

Can I use it or not?

Thanks again.

 

[Frankster]

Good call on not using that procedure, Jorge. Bruce and Enkidu must not
have actually read your question about yours being a domain controller.

Anyway, my take is, your best bet with a domain controller is to first set
up your new box as another domain controller. Let all the replication
happen. Then, transfer the roles to the new box, including the FSMO role.
Take the old box offline (demote it to a member server, then workgroup. And
then, I believe you can change the name/IP of the new box to that of the
old.

Do some more research on MS website. I'll bet you can find a recommended
procedure for domain controllers.

-Frank

 

[Guest]

How does one migrate settings from one dc to another?

 

[Jorge]

I havent done anything yet, my boss suspended the server change.

Thanks.