Windows 2000 to Windows 2003 migration-Files and apps on DC
Posted on 2011-04-29
We have recently aquired another organization and we are in the process of upgrading their domain from Windows 2000 to Windows 2003, so we can eventually move them to our domain. The problem that I am experiencing is that the two Domain Controllers are also DNS, DHCP, application servers, and fileservers. The organization is also a 24 hour shop that accesses critical data from the DC's, so they cannot be shut down. I am trying to find a way that I can upgrade the domain and check the schema upgrade before replicating it to the two DC's that hold apps, data etc. In addition to the fact that they hold other roles then just the DC roles, there are two DHCP zones. One zone on each DC. I am planning to:
Create an additional Windows 2000 DC that has been patched to SP4, and enable schema upgrade.
Add the DHCP roles for both zones to the new Win 2000 server. (this would be a temporary solution)
Create a secondary DNS on the 2000 DC and replicate the DNS information to all of the clients. (If I remember correctly, this can be done via the DHCP server, correct?)
Move the FSMO to the new Win 2000 server.
Check replication, and event logs for any issues.
Disable outbound replication on the DC where the upgrade will be performed. (How long can replication be disabled before the DC is no longer recognized, or is this an issue since inbound replication is still allowed?)
Run adprep /forest and ad prep /domain on the new 2000 DC.
Check logs for any issues in logs.
Turn outbound replication on. Are there any additional steps I should take, or are there any other ideas about the best way to do this upgrade?