Migrate to new server

Discussion in 'DNS Server' started by DD, Nov 26, 2008.

  1. DD

    DD Guest

    I create the server using the same name, not sure is it because the server 1
    still hardcord the crash server GUID, cause I can't run the adprep/forest
    which I have post the error message.

    I post few questions cause I encounter different error when I try to promote
    the new server as member server and this post is quite some times ago so
    worry nobody reply or help.

    Do I need to remove any crash server infor from the AD ?
     
    DD, Dec 1, 2008
    #21
    1. Advertisements

  2. Hello DD,

    Yes, you have to remove the old server and also make sure that the FSMO roles
    are existing on the other server. The new fresh installed one should not
    have any role until now. In your dcdiag was stated that 2 roles are missing,
    How did you assign the roles to the new installed DC, which the netdom query
    fsmo output states?

    Best regards

    Meinolf Weber
     
    Meinolf Weber, Dec 1, 2008
    #22
    1. Advertisements

  3. DD

    DD Guest

    i din't not assign the roles to the new installed DC, it automatically
    assigned.currently server 2 hold the schema owner and domain role owner and
    server 1 hold the pdc , rid & infrastructure.

    Can you guide me in detail how to remove the old server ? understand I can
    use ntdsutil . but a bit worry if I remove the wrong entry may cause the
    whole AD not working .

    Appreciate your help.

    If still can run the adprep /forest, i intend to install the new server as
    windows 2000 and the upgrade from there. what is your comment ?
     
    DD, Dec 2, 2008
    #23
  4. Hello DD,

    I got confused now, please describe exactlyt the steps about the installation
    from the new DC and the problem with the broken one. Is the new DC installed
    in the domain before the other breaks? Did you rename it maybe? the dcdiag
    output states that there is no schema holder, so how did the new DC get this
    role, when the old one is broken and you did not seize or move the role?
    If the FSMO roles existing on a DC they will not automatically move to another
    DC, except you demote a DC correctly and do not move the FSMO roles to another
    one yourself, then it choose one available DC. But when a DC breaks this
    will not happen.

    Best regards

    Meinolf Weber
     
    Meinolf Weber, Dec 2, 2008
    #24
  5. DD

    DD Guest

    Previously we chave two DC runnign, server 1 & server , server 2 crash last
    two months, we temporary setup a temp server to replace the server 2.at that
    time i did not check the fsmo , so i not sure which server is holding the
    role. by right should be server 1. i just setup the new temp server and I did
    not do any transfer also did not delete any entry for the crash server, i
    just setup using back the same computer name.

    one month later, the new server arrived, so I decide to install this server
    as windows 2003 and as recommended, i will setup the new server as memeber
    server and then promote it to DC , it is more clean way to do it.

    so I start checking the fsmo, and noticed that the server 2 hold the shema
    owner 7 domain owner role.

    Then I start encounter problem can't run the adprep /forest to upgrade the
    new windows 2003 server as DC.


    i have spend a lot of time to troubleshoot , so just wondering can i setup
    the new server as windows 2k as DC and then promote it.

    What is your suggestion. as you see i have post many questions but until now
    i still can't proceed the new server upgrade.
     
    DD, Dec 2, 2008
    #25
  6. Hello DD,

    Well with this description to start your posting would be better.

    I n this case now i would only keep your server1 and disconnect the new installed
    DC from the network. Then seize the FSMO roles to server1 with this: http://support.microsoft.com/kb/255504

    If this is succesful remove all old DC's from AD database with metadata cleanup
    using ntdsutil, the old server2 and the new server2 according to this:
    http://support.microsoft.com/kb/216498

    After that remove all old entries in AD sites and services and DNS zones
    and server properties and also on the NIC's from the cleaned up server2 old
    and server2 new.

    If this is all succesful i would reinstall the new server again to have it
    really clean, add it to the domain and promote it to DC. Then make sure that
    replication works correctly.

    Best regards

    Meinolf Weber
     
    Meinolf Weber, Dec 2, 2008
    #26
    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.