• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 673
  • Last Modified:

Windows server 2003R2 to 2008R2 migration.

I am looking for advice or guidance...here is my scenario:
I have a single domain, 5 total sites.  I have 6 domain controllers-2 Server 2003R2 servers in main site running DNS.  1 of these servers also runs DHCP, is the main print server and holds all FSMO roles except PDC emulator.  2 sites have 2003R2 servers (all dcs are GCs) with DNS, DHCP and 2 have 2008R2 servers running the same.  
I want to replace the main server which runs DHCP and DNS in the main site with new hardware running 2008R2 and reuse the IP address.  The domain and forest are prepped as I already have 2 dcs running 2008.  
Does anyone know of the steps required to re-use the IP address of the main 2003 server for the new 2008R2 server and eventually have it hold all roles, run DHCP and be the secondary DNS server for the remote sites running DNS?
To preempt, I would seize all roles to the secondary dc running 2003 first before installing the new server and demoting the main 2003 dc.  I would then dcpromo the new server running 2008R2 and transfer the roles there.  
Ultimately I need to replace all 2003R2 servers with new hardware running 2008R2.
I appreciate any input.
  • 2
1 Solution
Are you replacing the old Main Office 2003 DC or are you upgrading it? Essentially, are you using the same hardware?
If your using new hardware, just add the new 2008 R2 server, run adprep/forestprep, then run dcpromo to add DNS and sieze all of the roles. Add DHCP to your new server and split the scopes so both the old and new are active. When you have all of the roles siezed, run dcpromo on the old DC unless its a certificate server. Remove the DNS role from the old DC, then change the IP address. Now go back to the new 2008 R2 server then change the IP to the old IP of the 2003 server. Now run ipconfig/flush +ipconfig/registerdns on the new server. Verify the following: AAA record is correct as well as ALL SRV records are correct (_kerberos, _ldap, etc.)SOA Records, NS Records and CNAME records. Clear DNS Cache. Then use Sites&Services to replicate DNS updates to the other DCs. Now remove the old DHCP scope from the old 2003 server and add the IPs back to the new ones scope.

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now