Swapping out Domain Controller hardware (need to make sure all bases are covered)

We are getting ready to swap out or domain controller hardware and want to make sure we do this right. Right now we have 2 domain controllers, one is Windows 2003 and one is Windows 2000. We are going to keep the same names and ip addresses on these servers. I have a few questions reguaring this process.

1. Is there any certain order we should swap out the servers? Should we do the 2000 DC first?
2. Is there any reason to do an inplace upgrade on the 2000 DC before we swap out the hardware?
3. FSMO roles are spread out betwen the two DCs. We should transfer all of the roles before swapping out a server, transfer them to the new one before swapping out the remaining DC. Is this correct?
4. When we swap out the first DC is it as simple as running dcpromo and the AD info will be synchronised onto the new server? I'm assuming there will be some manual work involved.
5. What are we missing? My colleague and I have both built several domain controllers but have not done as hardware swap. This will be a learning experience for both of us.

Thanks in advance for your input.
deh5Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NJComputerNetworksCommented:
I would upgrade the Windows 2000 DC to Windows 2003 just so that all DC's are Windows 2003.

This is how I would do it...but there are several ways:

1) inplace upgrade the Windows 2000 server to Windows 2003
2) Add the two new servers to the network as member servers.  
3) Run DCPROMO on both and join the existing domain
4) transfew the FSMO roles to the new servers. (http://support.microsoft.com/default.aspx?kbid=324801&product=winsvr2003 )
5) Make the new DC's GC's... and remove the GC from the old servers:  http://technet2.microsoft.com/WindowsServer/en/Library/7b1c3e1c-ef32-4b8e-b4c4-e73910575f611033.mspx
6) wait and make sure DCDIAG and DNS looks right..  Also run Netdiag ... Use replemon to verify replication...  And validate that you can create new user accounts ...and that these show up on the new DC's.
7) Add the DNS role to each DC...and any other roles that your existing DC's might have ...like DHCP or WINS.
8) point your environment to use the NEW DNS servers....including your old DC server... point these to your new DNS servers...
9) run DCPROMO on the old DC's and choose to remove the domain controller roles.

At this point, your old DC's are out of AD.  Now, delete the computer accounts for these DC's in the domain (us AD users and computers).

Now...if you want to rename these computers, you can.

Now ... if you want to change the ip of these computers, you can... but make sure that you plan for the updates of DNS, WINS, etc for you clients.  If you are using DCHP, this is very easy to accomplish.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.