upgrading vs migrating

Posted on 2006-05-18
Last Modified: 2010-04-13
Hi All,

we are planning to move our domain to w2k3 from w2k.

here is the setup like

one w2k domain server
one w2k3 exchange server

want to setup another w2k3 server and make it the domain controller.

i have already read alot of articles but still want to be 101% sure of what would be the correct path for success in this case will be and what can happen if not; also what would be the prime difference between migration and upgrading .

according to my thinking i would say the process should e something like this

no migration required, just add the new DC

1 Build new server
2 Running dcpromo on it to become a DC
3 Makeing sure that it is running a DNS
4 Changing the DNS entries to use this as primary DNS server (eg change the properties of your DHCP scope)
5 Moving all the FSMO roles to it and make it a GC (for exchange)
6. Turning off the old one for a while and test that everything works. & if it does, turn on the old DC, run dcpromo to make it a member only.

but but but... whatever i have read uptill now i only see the story of adperp untility running on OS 2000 . please help me out in this case as which method would be the correct one. thanks alot and thanks in advance

thanks alot and thanks in advance
Question by:lomaree
    1 Comment
    LVL 48

    Accepted Solution

    Hi lomaree,

    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

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Do You Know the 4 Main Threat Actor Types?

    Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

    NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
    Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
    This video is in connection to the article "The case of a missing mobile phone (". It will help one to understand clearly the steps to track a lost android phone.
    In this sixth video of the Xpdf series, we discuss and demonstrate the PDFtoPNG utility, which converts a multi-page PDF file to separate color, grayscale, or monochrome PNG files, creating one PNG file for each page in the PDF. It does this via a c…

    758 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

    11 Experts available now in Live!

    Get 1:1 Help Now