Migrate 2000 AD to 2003 on new hardware

[jmikow]

I am new to AD and am trying to pick up where someone else left off.

We currently have a Windows 2000 domain (I'm pretty sure it's in native mode) running on very old hardware.

We recently purchased new hardware and it came with Windows 2003 Standard.

What I am looking for is a list of things to watch out for and what steps I need to take to make the Windows 2003 server our login server. I'd also like to setup a failover server so that if it goes down our users can still login. Does the failover need to be 2003 as well? or can it be a 2000 server?

Any suggestions, hints or advice would be greatly appreciated as I am trying to get my footing before I try to take on this task.

We just received the hardware so I know we'd like to do it as soon as possible, but I also don't want to rush it.

Thanks in advance!

Josh

 

[wcs91]

Hi Josh, did you get any answers from anywhere - because I will be trying to do the same thing.

P.

 

[adcfaq]

check MS site for admt v2. I've done a million projects of nt4--->2003 using this free cool tools.

 

[aftertaf]

you can add your 2K3 server to your existing domain, then decommission the old 2K server.....

This might be best!

Things you need to answer for us to guide you correctly:

Do you want to keep the same domain name?
Are you going to get a 2nd server to replace the old 2K one, or rather keep both?

you can have a 2K3 DC and a 2K DC.... but in order to join a 2K3 server and make it a DC, you need to prepare the AD structure first:
-run adprep /forestprep
-run adprep/ domainprep
on the 2K DC before promoting 2K3 to a DC...


Aftertaf

"Solutions are not the answer." - Richard Nixon

 

[wcs91]

Thanks for that.
I'll take a look at admt.
I would like to keep W2K as a backup but move everyone to point to W2K3. The domain name doesn't have to be the same - it depends whats the easiest.

Cheers, P.