Migrating Win2K to Win2K3 R2

Discussion in 'Server Migration' started by vvii, Mar 1, 2007.

  1. vvii

    vvii Guest

    Currently, we have 2 Servers:
    1) Win2K: DC (All 5 FSMO roles), Primary DNS/DHCP
    2) Win03: DC, Secondary DNS, Exchange, User/shared folder

    We are trying to add a new server and start taking away Win2K's roles

    Planning to add a new Server into our domain:
    1) Win2K3-R2: Primary DNS/DHCP (Replaced Win2K)

    Questions:
    a) Does the new Win2K3-R2 have to be DC, since it is taking over the role
    from Win2K? How? What tools?
    b) Does the new Win2K3-R2 have to take all those 5 FSMO roles from Win2K as
    well? How? What tools?
    c) How can I transfer Both DHCP/DNS from Win2K to Win2K3-R2? will that
    affect Win2K3, since Win2K3 is the Secondary DNS?
     
    vvii, Mar 1, 2007
    #1
    1. Advertisements

  2. vvii пишет:
    IF I all understand right you planing to replace old server, which the
    only DC of your network with new one... Of course, new server must be DC...
    I recommend you install new server, promote it as additional DC in your
    domain, wait some time (for full replication) or you can manually
    trigger replication process (for example, using repadmin utility), then
    transfer all roles to your new server typing this commands (they are
    unreadable, because I shortened them as I could, I'm to lazy to print
    full commands :) ):

    ntdsutil
    rol
    co to se <new DC name>
    q
    tra do na ma
    tra in ma
    tra pdc
    tra rid ma
    tra sch ma
    q
    q
    see above
    Backup DHCP on W2k server, deinstall DHCP on w2k server, restore DHCP on
    W2k3 server.

    DNS - are you using integrated DNS or not?
     
    Nick Domukhovsky, Mar 2, 2007
    #2
    1. Advertisements

  3. Hello,

    Thank you for using newsgroup!

    Since R2 has the different schema of Active Directory from Windows Server
    2003, you must run adprep /forestprep and adprep /domainprep with the
    CD-ROM of Windows Server 2003 R2.

    More information, please refer the following KB:
    Error message when you run the Active Directory Installation Wizard: "The
    version of the Active Directory schema of the source forest is not
    compatible with the version of Active Directory on this computer"
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;917385

    After doing this, you may promote Windows Server 2003 R2 to be a DC. From
    your post, you are trying to replace Windows 2000 Server with Windows
    Server 2003 R2, so you must take all FSMO roles. You may refer to the
    following to transfer FSMO role:
    How to view and transfer FSMO roles in Windows Server 2003
    http://support.microsoft.com/kb/324801/en-us

    If DNS Zone is an Active Directory Integrated Zone, DNS data will replicate
    with AD, so you needn't transfer this data manually, you only create a DNS
    Zone on the additional DC.

    To move DHCP to new Server, please refer to the following KB:
    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/kb/325473/en-us

    Thanks & Regards,

    Mike Luo

    Microsoft Online Partner Support
    Get Secure! - www.microsoft.com/security

    =====================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Mike Luo [MSFT], Mar 2, 2007
    #3
  4. vvii

    vvii Guest

    Can I get the complete commands for transfer roles to the new server?
    And the DNS is an AD integrated DNS
     
    vvii, Mar 5, 2007
    #4
  5. vvii пишет:
    Ok. Here you are:
    ntdsutil
    roles
    connections <---- I forgot this command last time!!!!
    connect to server <new DC name>
    quit <---- and this one!
    transfer domain naming master
    transfer infrastructure master
    transfer pdc
    transfer rid master
    transfer schema master
    quit
    quit
    So you should do as Mike Luo adviced you in parallel post (especially
    make sure to run adprep, i forgot about this one, but it's very
    important step).
     
    Nick Domukhovsky, Mar 6, 2007
    #5
  6. vvii

    vvii Guest

    I just want to clear something here, I am not trying to totally replacing the
    Win2K, it will still be part of our network, however, Win2K will be totally
    remove from our network next year, therefore, since we are planning to get a
    new server, that's why I would like to start taking over some roles from the
    Win2K, so that there will be less work to do when we remove the Win2K next
    year.

    On the other hand, I just found that both of our current Win2K and Win2K3
    are Global Catalog Server, is there something I should do while I add an
    Win2K3-R2 into my network?

    Where should I use the ntdsutil/Adprep command? on the new Win2K3-R2 Server
    or the Win2K Server?


    Ok. Here you are:
    ntdsutil
    roles
    connections <---- I forgot this command last time!!!!
    connect to server <new DC name>
    quit <---- and this one!
    transfer domain naming master
    transfer infrastructure master
    transfer pdc
    transfer rid master
    transfer schema master
    quit
    quit
     
    vvii, Mar 7, 2007
    #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.