Migrating from Windows 2000 Server SP4 to Win 2k3 Standard

Active Directory
Microsoft Windows Server 2003
Windows 2000 Server
Windows 2000 server upgrades and migration
Hello all, I have an older Windows 2000 Server which stands alone as our File/Print/Exchange 2000 Server. It is the alpha and omega of the organization. It is now being replaced with a new machine, which will be running Windows 2k3 Standard. I am looking for some tips a little more specific to my scenario of a one to one server replacement. I see references to tools such as ADPrep, which will prepare Active Directory for the installation of a Windows 2k3 server on my domain, as well as ADMT to migrate my active directory. Are these still valid tools for my needs? Also, in order to migrate AD to the new server, do I need to first join that server to the Domain? This is a big project for me, and I am new to this, so any advice would be very much appreciated.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Thanks alot. Thats a great idea.

*** Updated by Wrobinson on 02/02/2008 ***

Please refer to the following migration guide from Microsoft.

The reason that the solution provided in the discussion below is not recommended is because it introduces risk to the procedure by first upgrading the existing server to Windows Server 2003. There are several things that can go wrong and if this server is the Alpha and Omega for your organization then I don’t think it is a good idea and I would strongly recommend against it.


  1. Install and configure Windows Server on new server
  2. Promote new server to domain controller in existing forest/domain
  3. Install Exchange 200x into existing Exchange organization
  4. Migrate users using ADMT or Mailbox Move Wizard in Exchange

Discuss This Question: 2  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Kb3cgj
    Good Luck. When I did this at a customer site..we opted to upgrade the 2000 Server to 2003 and then bring the new server into the 2K3 Domain. We then promoted the new server to the PDC and moved all of the Data. Here is one of the documents we used for the upgrade: http://www.commodore.ca/windows/windows_2003_upgrade.htm
    580 pointsBadges:
  • Jlcelestine
    Thanks for the replies. And thanks for the follow up Wrobinson. I am still in the process of getting all of this done, and I'm just double checking all of the suggestions. After doing a lot more reading i already stumbled on the guide you linked and decided to go that route, as to not have my network down over the weekend upgrading the OS, and also keeping the original server in working order incase something in this transfer goes wrong and i have to fall back on it. At present time I'm just trying to make sure that the old server and exchange 2000 is up to date as far as fixes and patches go, because I have read of some of the nightmares it can cause if they are not and i run the ADPREP tool prematurely. From what i read, since Exchange is already installed on this Windows 2k domain, i will need to enable some schema updates so that Active Directory doesn't get mangled and littered with duplicate names. However, i dont have the Schema snap in installed on my old machine. Not sure if its not installed because this is a single server environment or what, but in any case, i am going to install the snap in and enable the updates before i run ADPREP. I'll definately be checking this post for any more advice, as well as updating you all on my progress in hopes that this may help someone else in the future. Thanks alot guys!
    35 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: