I would also check if you have any apps that are hardcoded to use the DNS name of either of the existing DCs - you may need to create CNAMEs for those.
Make both the new DCs global catalogs Anything else on old DCs (print queues, file shares, certificate services, etc) They will need to be migrated If you are deploying software via GPO, and the software is coming from a share on an existing DC you will need to think about how to migrate that. Cheers Ken From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Friday, 22 August 2008 12:01 AM To: NT System Admin Issues Subject: RE: moving AD's You should demote the old domain controllers in order to clean up DNS and NTDS metadata; not just shut them down. I also presume that in step 1 you will point DNS to the "old" DCs. Before step 8, you'll need to update DNS "everywhere" to point to the new DCs. Otherwise, seems like a good plan. Regards, Michael B. Smith MCITP:SA,EMA/MCSE/Exchange MVP http://TheEssentialExchange.com From: Sohail Qadir [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 9:43 AM To: NT System Admin Issues Subject: moving AD's Good Morning Everyone, I Currently have two domain controllers server1 and server2 running windows server 2003. I am planning to replace both of these servers with two new servers server3 and server4 Installed on new hardware with server 2003 R2 sp2. These are the steps I have planned, Please Let me know if I am missing some thing. 1 Install windows 2003 R2 sp2 and patch it up 2 Join it to the Domain 3 Run DCpromo to make it into a Domain controller 4 Install DNS and make it AD-Integrated 5 Wait for the replication so all the DNS records and SRV'S are replicated to this DNS server 6 Transfer the FSMO roles 7 Next move the DHCP 8 Shut down the old Domain Controller. Please Let me know if I am missing anything or anything I should look out for. Thanks in advance. Best Regards Sohail Qadir ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
