Migration from Windows 2000 server to Windws Server 2008

Discussion in 'Server Migration' started by Joe, Jan 14, 2009.

  1. Joe

    Joe Guest

    Hi all,

    I have been searching the Internet and some of the newsgroups here to find a
    solution/step-by-sep guide for my problems described below. No luck. If
    there is someone among you to help me with the following tasks, I would be
    very glad.

    1.
    I have a single-label domain with one PDC running Windows 2000
    Server+DNS+DHCP+WINS. I need to replace that server with a new one running
    Windows Server 2008 Stadard.

    2.
    I have a fully qualified name domain with one PDC running Windows 2000
    Server+DNS+DHCP+WINS. I need to replace that server with a new one running
    Windows Server 2008 Stadard.

    3. Both domains are totally separate (no forest, no tree).

    Thans for any kind of information.

    Joe
     
    Joe, Jan 14, 2009
    #1
    1. Advertisements

  2. Hello Joe,

    1. Think about to get rid of the single lable domain name and use ADMT v3.1
    to migrate to a new named domain with server 2008. If you upgrade before
    to server 2003 with functional levels 2003 you can also think about domain
    rename and then upgrade to 2008 without ADMT.

    2. You can not inplace upgrade a 2000 DC to 2008, either you have to upgrade
    before to 2003 sp1 or higher or add the 2008 as an additional DC to the existing
    domain (my preferred solution)

    If you have the need for keeping the servernames and ip addresses you have
    the need for an additional temp DC. So if you are clear about the way i can
    give you more detailed info's.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Jan 14, 2009
    #2
    1. Advertisements

  3. Joe

    Jozef Zvonar Guest

    Hello Meinolf,

    I do appreciate your reply, support and help.

    Point 1. - OK, now I understand.

    Point 2. - Please follow my steps and confirm/correct me, if something has
    been misunderstood (please check if the steps are not preformed in correct
    order, either):
    a)
    I prepare the forest schema on Windows 2000 Server for migration to Windows
    Server 2008 Standard by running adprep and domainprep tools form the Windows
    2008 Server Standard installation disk. Those tools have to be run on the
    Windows 2000 Server PDC.

    b)
    I install Windows Server 2008 Standard on a new computer as described in
    this guide
    http://www.windowsreference.com:80/...-2008-domain-controller-and-dns-server-setup/
    except I choose 'Existing forest' and 'Add domain controller to an existing
    domain' options during the set up process. In the next step of installation
    I type the fully qualified domain name of my existing domain and finish the
    installation.

    c)
    I wait until the AD replicates between the two servers/domain controllers.

    d)
    After the successful replication I disconnect the old Win2K server and test
    the domain logon functionality on the new Windows Server 2008 Standard
    domain controller. If successful, i.e. I can add computers into domain and
    logon on the the new domain controller with a replicated account from the
    old PDC, I do follow as described further below in e).

    e)
    To finalize the migration/upgrade I have to:
    - transfer FSMO roles from 2000 to 2008;
    - transfer files/permissions and check I can access shares
    as per the permissions allowed ;
    - migrate DHCP and authorize it the new 2008 AD;
    - demote the old server;
    - run domain controller diagnostic tools dcdiag.exe
    and netdiag.exe (found on Windows Server 2008
    installation disk) on the new server to be sure
    everything is all right.

    Joe
     
    Jozef Zvonar, Jan 15, 2009
    #3
  4. Hello Jozef,

    1. A domain rename procedure has to be tested before so that you are familiar
    with everything.

    2.
    Before starting:
    - On the old server open DNS management console and check that you are running
    Active directory integrated zone (easier for replication, if you have more
    then one DNS server and better have it for redundancy)

    - run replmon from the run line or repadmin /showrepl, dcdiag and netdiag
    from the command prompt on the old machine to check for errors, if you have
    some post the complete output from the command here or solve them first.
    For this tools you have to install the support\tools\suptools.msi from the
    2003 installation disk.


    a) "adprep /forestprep" "adprep /domainprep /gpprep" and "adprep /rodcprep"
    you should run.
    (http://technet.microsoft.com/en-us/library/cc731728.aspx)

    b) install it as a member server in the domain and point the preferred DNS
    server to the running domain DNS only. Then follow the guide. After installation
    reconfigure the NIC to itself as preferred and another domain DNS as secondary.

    c) for DNS replication with AD integrated zones give at least 15 minutes
    and compare the zones before going on. After replication is done check with
    support tools as above.

    d) before disconnecting make the new server Global catalog (if not done during
    promotion) and move the FSMO roles to the 2008 DC. Do not forget to reconfigure
    the clients or the DHCP server, if used, for new DNS server.

    e) FSMO see above, for file transfer you can use robocopy, included with
    server 2008, is also able to copy permissions. BACKUP the data before copying.
    Export and import of DHCP database for 2008, choose "netshell dhcp backup"
    and "netshell dhcp restore" command (http://technet.microsoft.com/en-us/library/cc772372.aspx).

    Demoting the old DC:

    - reconfigure your clients/servers that they not longer point to the old
    DC/DNS server on the NIC
    - to be sure that everything runs fine, disconnect the old DC from the network
    and check with clients and servers the connectivity, logon and also with
    one client a restart to see that everything is ok
    - then run dcpromo to demote the old DC, if it works fine the machine will
    move from the DC's OU to the computers container, where you can delete it
    by hand. Can be that you got an error during demoting at the beginning, then
    uncheck the Global catalog on that DC and try again
    - check the DNS management console, that all entries from the machine are
    disappeared or delete them by hand if the machine is off the network for ever
    - also you have to start AD sites and services and delete the old servername
    under the site, this will not be done during demotion


    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Jan 15, 2009
    #4
  5. Joe

    Jozef Zvonar Guest

    Meinolf,

    this is to thank you very much. Your instructions are clear and straight,
    and I understand now hot to proceed.

    Best regards and thanks again.


    Jozef
     
    Jozef Zvonar, Jan 15, 2009
    #5
  6. Hello Jozef,

    You're welcome.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Jan 15, 2009
    #6
    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.