Windows Server TechCenter > Windows Server Forums > Migration > Micration Windows 2000 Server SP4 to Windows Server 2008 Enterprise Edition

Answered Micration Windows 2000 Server SP4 to Windows Server 2008 Enterprise Edition

  • Wednesday, September 30, 2009 2:06 PM
     
     
    Hi Alls,
    I need to migrate my platform of network (DC) from a server with Windows 2000 Server to a new server with Windows Server 2008 Enterprise Edition.
    What steps must I consider?

    Thanks & regards.

Answers

  • Thursday, October 01, 2009 7:13 AM
     
     Answered

    Hello,

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

    - Do you use any kind of Exchange in the 2000 domain? If yes, which one?

    - 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 /showreps(only if more then one DC exist), 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 installation disk.

    - run adprep /forestprep and adprep /domainprep and adprep /domainprep /gpprep and adprep /rodcprep from the 2008 installation disk against the 2000 schema master(forestprep) / infrastructure master(domainprep/rodcprep), with an account that is member of the Schema/Enterprise/Domain admins, to upgrade the schema to the new version (44) or 2008 R2 (47)

    - you can check the schema version with "schupgr" or "dsquery * cn=schema,cn=configuration,dc=domainname,dc=local -scope base -attr objectVersion" without the quotes 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, think about disabling IPv6 if you are not using it, some known problems exist with it. Follow (http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabling-ipv6-on-windows-2008.aspx) to disable it

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

    - 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 on both domain controllers. For using netdiag.exe on 2008, NOT 2008 R2, you have to download and install (http://www.microsoft.com/downloads/details.aspx?familyid=96A35011-FD83-419D-939B-9A772EA2DF90&displaylang=en), ignore the compatibility warning, or extract netdiag.exe only and copy it

    - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801 applies also for 2008/2008R2), FSMO should always be on the newest OS DC

    - 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

     

    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 demotion


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

All Replies

  • Wednesday, September 30, 2009 2:48 PM
     
     
    Hello,

    -First make sure your w2k has sp4
    -Make and have an up to date backup from the w2k DC,if it is only a DC a system state will do
    -Run a complete dcdiag /v and repadmin /showreps and make sure there no errors
    -Insert the W2k8 installation disk into the w2k DC which is the schema master and logon with an id that is a member of the schema admin and run adprep /forestprep, and then adprep /domainprep and finally adprep /gpprep and if you plan to have RODC in your domain then run adprep /rodcprep
    -Prepare you w2k8 dc , give it a fixed IP and make sure it is looking for pri dns from the w2k dc (Only if it is a dns server as well) if not then point to a dns server in the domain.
    -Run dcpromo and promote into a domain controller in the exisiting w2k domain
    -Install DNS on the w2k8 dc
    -run dcdiag /v , repadmin /showreps and make sure that initialization is complete and there are no errors
    -Transfer FSMO roles to the new W2k8 DC and install other roles if any, that are on the w2k dc
    -Before decommissioning the W2k DC, test first to make sure the new w2k8 can perform all necessary DC functions...to do this, shutdown (Turnoff) temporarily atleast fir a day or two the w2kdc and see if users can still logon with o issues if no issues, then bring back the w2k dc online and decommission

    Isaac Oben MCITP:EA, MCSE
  • Thursday, October 01, 2009 7:13 AM
     
     Answered

    Hello,

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

    - Do you use any kind of Exchange in the 2000 domain? If yes, which one?

    - 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 /showreps(only if more then one DC exist), 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 installation disk.

    - run adprep /forestprep and adprep /domainprep and adprep /domainprep /gpprep and adprep /rodcprep from the 2008 installation disk against the 2000 schema master(forestprep) / infrastructure master(domainprep/rodcprep), with an account that is member of the Schema/Enterprise/Domain admins, to upgrade the schema to the new version (44) or 2008 R2 (47)

    - you can check the schema version with "schupgr" or "dsquery * cn=schema,cn=configuration,dc=domainname,dc=local -scope base -attr objectVersion" without the quotes 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, think about disabling IPv6 if you are not using it, some known problems exist with it. Follow (http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabling-ipv6-on-windows-2008.aspx) to disable it

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

    - 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 on both domain controllers. For using netdiag.exe on 2008, NOT 2008 R2, you have to download and install (http://www.microsoft.com/downloads/details.aspx?familyid=96A35011-FD83-419D-939B-9A772EA2DF90&displaylang=en), ignore the compatibility warning, or extract netdiag.exe only and copy it

    - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801 applies also for 2008/2008R2), FSMO should always be on the newest OS DC

    - 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

     

    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 demotion


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.