Migration from Windows 2000 to windows 2003
- Hi,
currently I have Domain control with win 2000 sp2 server with name EP1.com holding AD,DNS and all FSMO roles. there are aprox 120 client are there on EP1 domain.
I want to migrate that domain from 2000 that is EP1.com server to 2003 server that is EP.s1hosting.com along with AD, DNS, all FSMO Roles and all client which are on EP1.com.
please let me know step by step migrating process.
Answers
Hello,
BEFORE upgrading you have to install SP4 and latest patches. Then go on with:
!!!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 /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 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)
- after transfer of the PDCEmulator role, configure the NEW PDCEmulator to an external timesource and reconfigure the old PDCEmulator to use the domainhierarchie now. Therefore run on the NEW "w32tm /config /manualpeerlist:PEERS /syncfromflags:manual /reliable:yes /update" where PEERS will be filled with the ip address or server(time.windows.com) and on the OLD one run "w32tm /config /syncfromflags:domhier /reliable:no /update" and stop/start the time service on the old one. All commands run in an elevated command prompt without the quotes.
- 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)- 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.- Marked As Answer byJoson ZhouMSFT, ModeratorTuesday, November 24, 2009 9:29 AM
All Replies
- See the enclosed link
http://technet.microsoft.com/en-us/library/cc731188(WS.10).aspx
Introduce 2008 serversCommand Domain Controller
adprep.exe /forestprep Schema Master
adprep.exe /domainprep Infrastructure Master
adprep.exe /domainprep /gpprep Infrastructure Master
adprep.exe /rodcprep * Domain Naming Master
Hello,
BEFORE upgrading you have to install SP4 and latest patches. Then go on with:
!!!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 /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 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)
- after transfer of the PDCEmulator role, configure the NEW PDCEmulator to an external timesource and reconfigure the old PDCEmulator to use the domainhierarchie now. Therefore run on the NEW "w32tm /config /manualpeerlist:PEERS /syncfromflags:manual /reliable:yes /update" where PEERS will be filled with the ip address or server(time.windows.com) and on the OLD one run "w32tm /config /syncfromflags:domhier /reliable:no /update" and stop/start the time service on the old one. All commands run in an elevated command prompt without the quotes.
- 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)- 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.- Marked As Answer byJoson ZhouMSFT, ModeratorTuesday, November 24, 2009 9:29 AM
