The way to do this is as follows
Install Windows 2003 on the new machine
Assign the new computer an IP address and subnet mask on the existing network
Make sure that the preferred DNS server on new machine points to the existing DNS Server on the Domain (normally the existing domain controller)
Join the new machine to the existing domain as a member server
Make sure our 2000 Domain Controler is at least Win2000 SP4.
Put the Windows 2003 Server CD in your W2K domain controller and copy the i386 directory somewhere on a local drive.
Run the following steps with minimal activity on the server.
Open a command prompt and switch to that I386 directory.
Type:
adprep /forestprep
It will prompt you to press C then ENTER to continue.
Let this run. It normally about 10 minutes before. You see several "command completed successfully"
Next, type
adprep /domainprep
It won't prompt you for anything. It will just do its thing (less than 5 mins)
You are now ready to add your 2003 domain controller to the 2000 domain. On your 2003 server, run DCPROMO
Select "Additional Domain Controller in an existing Domain"
Once Active Directory is installed then to make the new machine a global catalog server, go to Administrative Tools, Active Directory Sites and Services, Expand ,Sites, Default first site and Servers. Right click on the new server and select properties and tick the "Global Catalog" checkbox. (Global catalog is essential for logon as it needs to be queried to establish Universal Group Membership)
Assuming that you were using Active Directory Integrated DNS on the first Domain Controller, DNS will have replicated to the new domain controller along with Active Directory.
If you are using DHCP you should spread this across the domain controllers, In a simple single domain this is easiest done by Setting up DHCP on the second Domain controller and using a scope on the same network that does not overlap with the existing scope on the other Domain Controller. Dont't forget to set the default gateway (router) and DNS Servers. Talking of which all the clients (and the domain controllers themselves) need to have their Preferred DNS server set to one domain controller, and the Alternate DNS to the other, that way if one of the DNS Servers fails, the clients will automatically use the other.
You now need to move the FSMO roles to the new machine see http://www.petri.co.il/tra
You can transfer user data files using robocopy or xcopy with the approprate switches to copy the NTFS security (but you will have to reset the shares and share permissions). or you could use the file server migration kit http://www.microsoft.com/w
Once the new DC is up and running then you can take the old machine off-line to test functionality.
You should reconfigure the clients so that they have the new DC as their preferred and only DNS server, and you may want to extend the DHCP scope now that there is only one DHCP server
Once you are happy, bring the old machine back online and run DCPROMO on it to demote it to a member server - you can then remove it from the domain.
Main Topics
Browse All Topics
by: dan_blagutPosted on 2009-11-03 at 07:12:11ID: 25729674
Hello
There are many procedure for a migration but the essential is:
1. install Windows Server on the new box, and don't forget the DNS server
2. If you will install W2K3R2 and your domain is W2K3 you need to run adprep on the controller to prepare your domain/forest for R2
3. Install DC on the new box (adpromo)
4. Check the replication and the DNS to be OK
5. Transfer the FSMO roles to the new box http://support.microsoft.c
6. stop the old machine and wait some time (do some restart on the new machine)
7. uninstall the AD on the old machine
Finish.
You can pase from 5 to 7, but I think is better to wait few days if you can.
Good luck
Dan