Whats left todo in 2000 to 2003 migration

Discussion in 'Server Migration' started by David Lewis, Jul 20, 2004.

  1. David Lewis

    David Lewis Guest

    I had a 2000 domain I did the following
    Installed 2003 member servers
    ran adprep /forestprep and adprep /domainprep on 2000 server
    installed AD on 2003
    shut down dns and dhcp on 2000 box
    Setup dns and dhcp on 2003 box
    moved print queues's and other programs to 2003 box

    What is left to do. I don't think I can format the old 2000 box yet so what is left?

    thankx
     
    David Lewis, Jul 20, 2004
    #1
    1. Advertisements

  2. Hi David,

    Thanks for your posting here.

    Please move the Global Catalog to the new Windows 2003 DC. You can refer to
    the following article.

    HOW TO: Create or Move a Global Catalog in Windows 2000
    http://support.microsoft.com/?id=313994

    You also need to transfer all the FSMO roles to the new Windows 2003 DC.

    HOW TO: View and Transfer FSMO Roles in Windows Server 2003
    http://support.microsoft.com/?id=324801

    In addition, please make sure that you point two DCs to the same internal
    DNS when you perform the above actions.

    Wish it helps.

    Regards,
    Bob Qin
    Product Support Services
    Microsoft Corporation

    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.
     
    Bob Qin [MSFT], Jul 20, 2004
    #2
    1. Advertisements

  3. David Lewis

    David Lewis Guest

    I was able to transfer the
    Global Catalog
    Domain Naming Master Role
    RID Master
    PDC Emulator
    Infrastructure Master Roles

    But not the Schema
    I get the error
    The requested FSMO operation failed. The current FSMO holder could not be contacted. The transfer of the current
    Operations Master could not be performed.

    I followed these instructions on the new DC

    Register Schmmgmt.dll
    Click Start, and then click Run.
    Type regsvr32 schmmgmt.dll in the Open box, and then click OK.
    Click OK when you receive the message that the operation succeeded.

    Transfer the Schema Master Role
    Click Start, click Run, type mmc in the Open box, and then click OK.
    On the File, menu click Add/Remove Snap-in.
    Click Add.
    Click Active Directory Schema, click Add, click Close, and then click OK.
    In the console tree, right-click Active Directory Schema, and then click Change Domain Controller.
    Click Specify Name, type the name of the domain controller that will be the new role holder, and then click OK.
    In the console tree, right-click Active Directory Schema, and then click Operations Master.
    Click Change.
    Click OK to confirm that you want to transfer the role, and then click Close.


    (Bob Qin [MSFT])
    |>Hi David,
    |>
    |>Thanks for your posting here.
    |>
    |>Please move the Global Catalog to the new Windows 2003 DC. You can refer to
    |>the following article.
    |>
    |>HOW TO: Create or Move a Global Catalog in Windows 2000
    |>http://support.microsoft.com/?id=313994
    |>
    |>You also need to transfer all the FSMO roles to the new Windows 2003 DC.
    |>
    |>HOW TO: View and Transfer FSMO Roles in Windows Server 2003
    |>http://support.microsoft.com/?id=324801
    |>
    |>In addition, please make sure that you point two DCs to the same internal
    |>DNS when you perform the above actions.
    |>
    |>Wish it helps.
    |>
    |>Regards,
    |>Bob Qin
    |>Product Support Services
    |>Microsoft Corporation
    |>
    |>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.
     
    David Lewis, Jul 22, 2004
    #3
  4. Hi David,

    You can also try Ntdsutil.exe tool to seize the role on the new DC.

    Please refer to the following document for the detailed steps.

    Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain Controller
    http://support.microsoft.com/?id=255504

    Have a nice day!

    Regards,
    Bob Qin
    Product Support Services
    Microsoft Corporation

    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.
     
    Bob Qin [MSFT], Jul 22, 2004
    #4
  5. David Lewis

    David Lewis Guest

    I tried that and it gave me errors.
    Not the seizing part yet.
    I ended up messing with the dns settings and I finally
    got it to transfer the schema the normal way.
    Weird how the other FSMO operations would transfer, but not the schema.

    What is left to do now? Can I format the old 2000 DC or do I need to demote
    it first? I have never demoted a 2000 DC before. The DCPROMO command
    seems to uninstall active directory and it said that it would delete all user accounts.
    I am assuming that is only on that 2000 DC, not the new 2003 DC.

    Is there any way to run a check to see that every thing has been transferred to
    the new DC properly before shutting down the old DC?

    (Bob Qin [MSFT])
    |>Hi David,
    |>
    |>You can also try Ntdsutil.exe tool to seize the role on the new DC.
    |>
    |>Please refer to the following document for the detailed steps.
    |>
    |>Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain Controller
    |>http://support.microsoft.com/?id=255504
    |>
    |>Have a nice day!
    |>
    |>Regards,
    |>Bob Qin
    |>Product Support Services
    |>Microsoft Corporation
    |>
    |>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.
     
    David Lewis, Jul 22, 2004
    #5
  6. Hi David,

    You can just refer to the article of 324801 to check if all the FSMO roles
    are on other DCs.

    It is recommend that you run dcpromo to demote the DC before formatting it.
    It just remove the AD data from this DC and all the related records of this
    DC will be remove from AD database.

    In addition, you can also find useful information in the Windows Help
    document.

    Thank you again for using our news group.

    Regards,
    Bob Qin
    Product Support Services
    Microsoft Corporation

    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.
     
    Bob Qin [MSFT], Jul 23, 2004
    #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.