Migrating from Windows 2000 to Windows 2003

Posted on 2006-05-25
Last Modified: 2010-04-18
Just looking for thoughts and possible issues we may incur with the following

We have a fairly decent sized client with the following

2 - 2000 domain controllers
1 - 2000 server running exchange 2000

various other 2000 & 2003 servers acting as file, print and citrix servers

100 + users always connected and active

We will be adding 2  Windows 2003 servers to replace the current end of life 2000 DC's and migrating AD over to them

the exchange server will stay as is with windows 2000 and exchange 2000

the 2 new 2003 servers will have new names

this client runs 24x7 and has experienced literally no noticeable downtime in 6 years so we would like to try not putting them through any major downtime now

thanks for any input
Question by:myrtlenet
    LVL 26

    Expert Comment


    Add the new servers to the domain.

    promote W2K3 server to DC, then the other.
    Reboot both.

    Move over FSMO roles to new DCs.
    Change DHCP to point to the new AD-integrated DNS servers (your new DCs) for DNS and WINS resolution as necessary
    Demote the two current DCs

    Go off to the pub for a few pints on the company tab.


    LVL 48

    Accepted Solution

    Hi myrtlenet,

    standard steps for me...

    can be done quite easily with a clean install of the new server

    **Note - If introducing a 2003 R2 Server into the network as a DC you will need to run the ADPREP tools from the second cd


    you can also download here

    this boosts the schema up to cope with R2 functionality

    1) Promote your new machine as an additional domain controller in an already existing domain - this will allow AD to replicate to the new server
    2) Make sure DNS is AD integrated on your old DC to allow all DNS replications also
    3) Transfer the FSMO roles to the new server;en-us;255690
    4) Make the new DC a Global Catalog under Sites and Services
    5) Deactivate DHCP on the old DC (if used) and recreate the scope on the new DC, note if you have a fairly complex or Large DHCP scheme you may want to export and import the database
    6) Run DCDIAG to make sure all is well and replication is fine
    7) Demote the old DC if you dont intend to keep it as a backup
    8) Recreate Shares etc on the new server
    9) Reinstall printers and share them etc....

    this will allow you to have the complete AD directory on the new DC and clients will barely be aware of any changes

    Featured Post

    What Should I Do With This Threat Intelligence?

    Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

    Join & Write a Comment

    It is a known fact that servers reach the end of their lives. Some get there quicker than others, based on age, manufacturer, usage and several other factors. However, if your organization has spent time deploying Microsoft's Active Directory server…
    Organizations create, modify, and maintain huge amounts of data to help their businesses earn money and generally function.  Typically every network user within an organization has a bit of disk space to store in process items and personal files.   …
    Sending a Secure fax is easy with eFax Corporate ( First, Just open a new email message.  In the To field, type your recipient's fax number You can even send a secure international fax — just include t…
    Illustrator's Shape Builder tool will let you combine shapes visually and interactively. This video shows the Mac version, but the tool works the same way in Windows. To follow along with this video, you can draw your own shapes or download the file…

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now