Windows 2000 domain controller to Win2k3 domain controller

Discussion in 'Server Setup' started by LiteTech07, Oct 18, 2007.

  1. LiteTech07

    LiteTech07 Guest

    I am currently looking to change a windows 2000 server for a win2k3 server.
    The old server is the DC, DNS, DHCP and print server. i want the new W2k3
    server to be the DC, also the DNS ans DHCP, and have the users
    login/authenticate to the new server. I will probly keep the old server doing
    the print serving. This is a small office, 15 users, but being architects a
    lot of data here. I am their part time IT help. Any suggestions would be
    helpful.
     
    LiteTech07, Oct 18, 2007
    #1
    1. Advertisements

  2. Hello LiteTech07,

    On the old DC check that DNS is active directory integrated. A lot easier
    for replication.

    Run adprep /forestprep and adprep /domainprep from the 2003 installation
    disk on the 2000 schema master, with an account that is member of the schema
    admin groups to upgrade the schema to the new version.

    Install the new machine, add it to the domain.

    Configure preferred DNS only to the old one on the NIC, run dcpromo and add
    it as additional DC. If DNS is not installed during dcpromo, install it after
    dcpromo. Replication will start automatically, can take 15 to 20 minutes,
    just wait.

    Run dcdiag and netdiag to check for errors. If no errors, change ip configuration
    on the new, preferred itself, second the old server.

    Make the new server Global catalog server

    Install DHCP server, move the database, change DNS to the new DNS only in
    DHCP options:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;325473

    Transfer all 5 FSMO roles to the new machine, give time for replication,
    check event viewer for errors/success:
    http://support.microsoft.com/kb/324801

    Run dcdiag and netdiag to check for errors.

    If you use forwarders in DNS, check that they are also configured in the
    new one.

    To be sure that authentication, DNS and DHCP is running on the new one, disconnect
    the old one from the network. Do not forget to inform the user about this,
    because of the files they are using. Or test it after close of business.

    If still everything works you can start with demoting the old DC. Do NOT
    just delete it in AD, e.g. you get a lot of replication errors in event viewer.
    Run dcpromo on the old and follow the wizard, read carefully.

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
     
    Meinolf Weber, Oct 19, 2007
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.