Server 2000 to Server 2008 NO exchange

Discussion in 'Server Migration' started by Brendan, Jul 28, 2008.

  1. Brendan

    Brendan Guest

    Hello, we are getting a complete new server with server 2008. Our current
    2000 Server only does DHCP, Domain control and file sharing. Nothing fancy.
    What are the steps to migrate from 2000 to 2008? I have seen a lot of
    examples for going from 03 to 08 but none to go from 2000. This will be the
    first time I personally have done a server migration but I've been working
    with Windows Servers for a long time. Thanks!
     
    Brendan, Jul 28, 2008
    #1
    1. Advertisements

  2. Hello Brendan,

    Thank you for posting in newsgroup.

    According to your description, my understanding is that:

    You want to migrate active directory database, DHCP service and File
    sharing service from Windows Server 2000 box to Windows Server 2008 box
    because of the replacement of hardware.

    If I have any misunderstanding, please feel free to let me know.

    Based on the experience, here is some information for your reference.

    Analysis and Suggestions:
    =======================

    The general steps to migrate from Windows Server 2000 to Windows Server
    2008 is almost the same as the steps to migrate from Windows Server 2003 to
    Windows Server 2008.

    Scenario:

    Old server: Windows Server 2000 box
    New server: Windows Server 2008 box

    1. Verify that Windows 2000 SP4 have been installed on the old server and
    Windows Server 2008 SP1 have been installed on the new server

    Note: the domain functional level should be in Windows 2000 native mode for
    the Windows 2000 domain.

    2. Upgrade the Windows 2000 forest schema by running "adprep /forestprep"
    command on old server

    Note: you can copy the adprep folder from the Windows Server 2008
    installation disc to the old server to run "adprep /forestprep".
    The location is \source\adprep on the installation disc.

    3. Upgrade the Windows 2000 domain schema by running "adprep /domainprep"
    command on old server

    4. Verify the new server's TCP/IP configuration has been pointed to
    existing DNS server.

    5. Add new server to existing Windows 2000 domain as a member server.

    6. Run dcpromo on new server to promote it as an additional domain
    controller in existing Windows 2000 domain, afterwards you may verify the
    installation of Active Directory.

    7. Enable Global Catalog on new server and manually Check Replication
    Topology and afterwards manually trigger replication to synchronize Active
    Directory database between 2 replica.

    8. Disable Global Catalog on old server.

    9. Use NTDSUTIL utility to transfer all the 5 FSMO roles from old server to
    new server. You'd better transfer FSMO roles via GUI method instead of
    using NTDSUTIL.

    10. Install DNS component on new server and configure it as a new DNS
    Server(Active Directory Integrated-Zone is preferred)

    Note: all the DNS configuration need to be transferred from the existing
    DNS Server.

    11. Migrate DHCP service from Windows Server 2000 to Windows Server 2008

    Please refer to:
    How to move a DHCP database from a computer that is running Windows NT
    Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is
    running Windows Server 2003
    http://support.microsoft.com/default.aspx/kb/325473
    (This should work on Windows Server 2008)

    12. Migrate File Sharing service from

    You can also use robocopy.exe from the Windows Server Resource kit to copy
    the files and maintain NTFS permissions.

    For the shares, the shares definitions and permissions are stored in the
    following registry key on the server:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\Shares

    If you export out the whole key and import in the new server, and if you
    have the files and folders in the same path as in the old server, then you
    will retain all you shares and share permissions.

    12. It's better to make the old DC offline for several days and check
    whether everything works normally with the new server online. If so, you
    may let the old DC online and run DCPROMO to demote it.

    For more information, please refer to:

    Identifying Your Windows Server 2008 Functional Level Upgrade
    http://technet2.microsoft.com/windowsserver2008/en/library/4e703a77-d9ba-4a2
    6-b756-eba5499f15581033.mspx?mfr=true

    How To Install and Configure DNS Server in Windows Server 2003
    http://support.microsoft.com/kb/814591/EN-US/

    How To Convert DNS Primary Server to Active Directory Integrated
    http://support.microsoft.com/kb/816101

    Hope it helps.
    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Jul 29, 2008
    #2
    1. Advertisements

  3. Hello Brendan,

    Prepare the domain with adprep from the 2008 install disk, add the 2008 as
    member server to the domain.

    Make in DNS on the 2000 DC ADintegrated zones(if not already done), run dcpromo
    on the new one, make it DNS server and let DNS replicate.

    Then move the 5 FSMO roles to the new server, make it Global catalog server.
    Reconfigure the clients to use the new server for DNS.

    With robocopy from MS resource kit you can copy the files including the permissions
    to the 2008 server.

    Best regards

    Meinolf Weber
     
    Meinolf Weber, Jul 29, 2008
    #3
  4. Hello Meinolf,

    Thank you for the knowledge sharing.

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Jul 30, 2008
    #4
  5. Brendan

    Brendan Guest

    David and Meinolf, thanks very much, that is exactly what I was looking for.
    Much appreciated!

    Brendan
     
    Brendan, Jul 30, 2008
    #5
  6. Hello Brendan,

    I am glad that the information is helpful to you. If you have any question,
    please welcome to the newsgroup again.

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Jul 31, 2008
    #6
  7. Hi CubeIT,

    Generally, we answer one issue per post in the newsgroup. In order to
    concentrate fully on this new issue we ask that you post it as a separate
    thread. That way each issue can receive full attention and make the thread
    more clear for others' reference. Please open a new post for this issue and
    we will be very glad to work with you there.

    Thank you.

    David Shen
    Microsoft Online Partner Support
     
    David Shen [MSFT], Sep 1, 2008
    #7
  8. Brendan

    Nigelb Guest

    Great information, I'm sure it will help me.

    There is one thought that occurs to me as I read this...

    It seems like it might be worth doing a trial run of the install/update
    first, rather than starting on the production environment. I'm suggesting
    possibly creating a test environment with the old server image (recreated on
    a test machine) together with the new 2008 server hardware & at least one
    client. Install as described here
    http://technet.microsoft.com/en-us/library/dd379526(WS.10).aspx to keep
    the new server ip address the same as the old. Thoroughly test the new server
    in the test environment. At the end of a successful trial would it then be
    possible just to swap out the old server from the production environment for
    the newly created 2008 server from the test environment?

    Obviously you'd have to take the production server offline to migrate file
    sharing to the new server at the last moment. But this would reduce downtime
    to a minimum & should result in a fully functional debugged installation...

    Am I right in this thought or would there be any other issues?

    Thanks.
     
    Nigelb, Mar 30, 2010
    #8
    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.