How to migrate from W2k to 2003/2008 changing Hw?

Discussion in 'Server Migration' started by mad, Dec 9, 2008.

  1. mad

    mad Guest

    Hi,
    I have a net with only one DC running on win2000 server.
    Now OS and hardware are obsolete and I need to migrate to newer ones.
    Exchange 2000 and SQL2000 server are running on the same DC too.
    How can I migrate to windows 2003 or 2008 on another machine without loose
    every settings and configuration?
    Is it possible (in one step or more)?

    Thanks
    mAd
     
    mad, Dec 9, 2008
    #1
    1. Advertisements

  2. I have a net with only one DC running on win2000 server.

    Run adprep on your Win 2k DC, Add the new server to your existing domain as
    a member server. Run dcpromo to make it a DC. Set up DNS, DHCP, use print
    migrator to move over the printers, robocopy over the user files. Work out
    how you are going to handle your scripts, either change them to match the
    new server name or renaming the new server.

    Test DHCP, DNS, file access, printers etc..............
    Post this to an exchange and SQL news group along with the plan you have so
    far.


    hth
    DDS
     
    Danny Sanders, Dec 9, 2008
    #2
    1. Advertisements

  3. Hello mad,

    For change to 2003 Domain controller:

    !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOU DATA/MACHINE!!!

    - for Exchange/Schema check first this one: http://support.microsoft.com/?id=314649

    - 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)

    - run 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 2000 or 2003 installation disk.

    - run adprep /forestprep and adprep /domainprep from the 2003 installation
    disk against the 2000 server, with an account that is member of the Schema
    admins, to upgrade the schema to the new version

    - Install the new machine as a member server in your existing domain

    - configure a fixed ip and set the preferred DNS server to the old DNS server
    only

    - run dcpromo and follow the wizard to add the 2003 server to an existing
    domain

    - if you are prompted for DNS configuration choose Yes (also possible that
    no DNS preparation occur), then install DNS after the reboot

    - for DNS give the server time for replication, at least 15 minutes. Because
    you use Active directory integrated zones it will automatically replicate
    the zones to the new server. Open DNS management console to check that they
    appear

    - if the new machine is domain controller and DNS server run again dcdiag
    and netdiag and now repadmin /showrepl on both domain controllers

    - if you have no errors, make the new server Global catalog server, open
    Active directory Sites and Services and then double-click sitename, double-click
    Servers, click your domain controller, right-click NTDS Settings, and then
    click Properties, on the General tab, click to select the Global catalog
    check box (http://support.microsoft.com/?id=313994)

    - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)

    - you can see in the event viewer (Directory service) that the roles are
    transferred, also give it some time

    - reconfigure the DNS configuration on your NIC of the 2003 server, preferred
    DNS itself, secondary the old one

    - if you use DHCP do not forget to reconfigure the scope settings to point
    to the new installed DNS server

    - export and import of DHCP database (if needed) (http://support.microsoft.com/kb/325473)

    - backup WINS (http://technet.microsoft.com/en-us/library/cc727901.aspx)

    - restore WINS (http://technet.microsoft.com/en-us/library/cc727960.aspx)


    Exchange and also SQL should not run on a DC for performance reasons and
    also security. Better install both on a separate member server. Or is you
    server SBS version of windows?

    For 2008 see next posting for the Domain controller part. Exchange and SQL
    remains the same.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Dec 9, 2008
    #3
  4. Hello mad,

    !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR DATA/MACHINE!!!

    - 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)

    - run 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.

    - run adprep /forestprep and adprep /domainprep and adprep /rodcprep from
    the 2008 installation disk against the 2003 schema master, with an account
    that is member of the Schema admins, to upgrade the schema to the new version
    (44), you can check the version with "schupgr" in a command prompt.

    - Install the new machine as a member server in your existing domain

    - configure a fixed ip and set the preferred DNS server to the old DNS server
    only

    - run dcpromo and follow the wizard to add the 2008 server to an existing
    domain, make it also Global catalog.

    - if you are prompted for DNS configuration choose Yes. If not, install DNS
    role after promotion.

    - for DNS give the server time for replication, at least 15 minutes. Because
    you use Active directory integrated zones it will automatically replicate
    the zones to the new server. Open DNS management console to check that they
    appear

    - if the new machine is domain controller and DNS server run again repadmin
    /showrepl, dcdiag and netdiag (copy the netdiag from the 2003 to 2008, will
    work) on both domain controllers

    - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801
    applies also for 2008)

    - you can see in the event viewer (Directory service) that the roles are
    transferred, also give it some time

    - reconfigure the DNS configuration on your NIC of the 2008 server, preferred
    DNS itself, secondary the old one

    - if you use DHCP do not forget to reconfigure the scope settings to point
    to the new installed DNS server

    - 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 (if needed)

    - 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 promotion

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Dec 9, 2008
    #4
  5. mad

    AronS Guest

    Hi, I am also prepping for migration to 2003 from 2000, I have 2 Windows 2000
    DC's, no exchange server, No WINS, and DHCP is being administered by our
    firewall. I' ve been using Q325379 as a guide
    (http://support.microsoft.com/kb/325379) but find it a little confusing in
    parts- is there a better article to reference? The steps below are helpful,
    but with setting up two 2003 domain controllers I know the process will be a
    little different...like when to promote Global catalog server (there can be
    only 1 correct?) and the FSMO roles (again only on one server?)
     
    AronS, Dec 15, 2008
    #5
  6. little different...like when to promote Global catalog server (there can
    You can have more than 1 global catalog in the domain. Each of our 50 branch
    office domain controllers are Global catalogs.

    FSMO roles are one to a domain/forest and can be moved or spread out on
    different servers.


    hth
    DDS
     
    Danny Sanders, Dec 15, 2008
    #6
  7. mad

    AronS Guest

    thank you. If anyone knows of or comes across abetter article for the
    upgrade process than Q325379 let me know please
     
    AronS, Dec 15, 2008
    #7
  8. Hello AronS,

    In a single forest domain make all DC's Global catalog server. The FSMO roles
    can be hold from one DC.

    !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOU DATA/MACHINE!!!

    - 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)

    - 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
    2000 or 2003 installation disk.

    - run adprep /forestprep and adprep /domainprep from the 2003 installation
    disk against the 2000 server, with an account that is member of the Schema
    admins, to upgrade the schema to the new version

    - Install the new machine as a member server in your existing domain

    - configure a fixed ip and set the preferred DNS server to the old DNS server
    only

    - run dcpromo and follow the wizard to add the 2003 server to an existing
    domain

    - if you are prompted for DNS configuration choose Yes (also possible that
    no DNS preparation occur), then install DNS after the reboot

    - for DNS give the server time for replication, at least 15 minutes. Because
    you use Active directory integrated zones it will automatically replicate
    the zones to the new server. Open DNS management console to check that they
    appear

    - if the new machine is domain controller and DNS server run again replmon,
    dcdiag and netdiag on both domain controllers

    - if you have no errors, make the new server Global catalog server, open
    Active directory Sites and Services and then double-click sitename, double-click
    Servers, click your domain controller, right-click NTDS Settings, and then
    click Properties, on the General tab, click to select the Global catalog
    check box (http://support.microsoft.com/?id=313994)

    - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)

    - you can see in the event viewer (Directory service) that the roles are
    transferred, also give it some time

    - reconfigure the DNS configuration on your NIC of the 2003 server, preferred
    DNS itself, secondary the old one

    - if you use DHCP do not forget to reconfigure the scope settings to point
    to the new installed DNS server

    Second 2003 DC:

    - Install the new machine as a member server in your existing domain

    - configure a fixed ip and set the preferred DNS server to the old DNS server
    only

    - run dcpromo and follow the wizard to add the 2003 server to an existing
    domain

    - if you are prompted for DNS configuration choose Yes (also possible that
    no DNS preparation occur), then install DNS after the reboot

    - for DNS give the server time for replication, at least 15 minutes. Because
    you use Active directory integrated zones it will automatically replicate
    the zones to the new server. Open DNS management console to check that they
    appear

    - if the new machine is domain controller and DNS server run again replmon,
    dcdiag and netdiag on all domain controllers

    - if you have no errors, make the new server Global catalog server, open
    Active directory Sites and Services and then double-click sitename, double-click
    Servers, click your domain controller, right-click NTDS Settings, and then
    click Properties, on the General tab, click to select the Global catalog
    check box (http://support.microsoft.com/?id=313994)


    Demoting the old DC's (if needed)

    - 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], Dec 16, 2008
    #8
  9. mad

    AronS Guest

    Thanks for all your assistance, just to be sure I'm clear...the 2003 servers
    should not be added to the domain as member servers until AFTER adprep
    /forestprep and adprep /domainprep are run on the current 2000 domain
    controller, correct?
     
    AronS, Dec 24, 2008
    #9
  10. Hello AronS,

    No. member servers in a domain do not require a schema update, only if the
    servers become domain controller then you have first to upgrade the schema.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Dec 24, 2008
    #10
  11. mad

    AronS Guest

    But do I add the new 2003 servers before or after running adprep
    /forestprep and adprep /domainprep on the current 2000 domain controller?
    Will the 2000 dc allow the new 2003 servers to join the domain once adprep
    /forestprep and adprep /domainprep have been run?
     
    AronS, Dec 24, 2008
    #11
  12. Hello AronS,

    It doesn't matter when you add them, 2003 member servers work in a 2000 domain
    without a schema upgrade. SO you can add them and run then the schema upgrade
    or upgrade the schema and then add them if that is your question.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Dec 24, 2008
    #12
    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.