locked
Replikation from a Win 2000 standart Server to a 2003 Standart Server? RRS feed

  • Question

  • How can i replicate a active Directory from a 2000 SP4 Server   to a   2003 server R2 first installation and is it possible  to create a DFS file replikation

    BG
    Martin
    old Man
    Tuesday, June 30, 2009 7:34 AM

Answers

  • Hello,

    see here about adding a new OS version DC to an existing domain:

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

    One question first:
    Is the old server also Exchange server and will it be taken out of the domain forever, when the new server is running?

    - 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 (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 from the second 2003 R@ 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

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


    Demoting the old DC (if needed, but i prefer to have at least 2 DC/DNS/GC)

    - 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.
    • Proposed as answer by David Shen Tuesday, June 30, 2009 12:05 PM
    • Marked as answer by David Shen Wednesday, July 1, 2009 8:59 AM
    Tuesday, June 30, 2009 10:55 AM

All replies

  • Hello,

    see here about adding a new OS version DC to an existing domain:

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

    One question first:
    Is the old server also Exchange server and will it be taken out of the domain forever, when the new server is running?

    - 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 (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 from the second 2003 R@ 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

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


    Demoting the old DC (if needed, but i prefer to have at least 2 DC/DNS/GC)

    - 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.
    • Proposed as answer by David Shen Tuesday, June 30, 2009 12:05 PM
    • Marked as answer by David Shen Wednesday, July 1, 2009 8:59 AM
    Tuesday, June 30, 2009 10:55 AM
  • Hello,

    for DFS file repliation, what do you mean exactly? Do you have DFS running in 2000?
    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, June 30, 2009 10:57 AM
  • Hello,

    see here about adding a new OS version DC to an existing domain:

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

    One question first:
    Is the old server also Exchange server and will it be taken out of the domain forever, when the new server is running?

    - 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 (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 from the second 2003 R@ 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

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


    Demoting the old DC (if needed, but i prefer to have at least 2 DC/DNS/GC)

    - 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.
    Hi Meinolf,

    first answer, i don use a Exchange Server on the 2000 Server.

    the tips  you post et  are very helpful and useful. i do that exactly on the same way, but after the first restart i hath a totally crash in server 2003 r2 include the raid 5 was broken.
    what was the PROBLEM ??
    so, now i start again, i hope the second try will be better ;-)

    thank you for your help

    best regards

    Martin  
    Wednesday, July 1, 2009 3:51 PM