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

decomissioning old 2003 DC's/DNS Servers

Currently have two physical 2003 DC's, both run internal DNS and one runs DHCP.  I've prepped the domain for 2008 and added a virtual 2008 DC a few months back, installing DNS and testing since then with no issues.  I would now like to decommission the old 2003 DC that runs DNS at this point.  After the first old DC is decomissioned, I have new hardware that I will then build up as the second 2008 DC (running DNS and DHCP) and then take the other 2003 offline.....What's the best way to shut down this first old 2003 DC/DNS server?  Is there anything in Exchange(2003) that points to a certain DC?  
0
tenover
Asked:
tenover
3 Solutions
 
Mike KlineCommented:
I'd first build up the second 2008 DC first.  That way you will never be running with only one DC.  Make sure the new DCs are also global catalogs.  Make sure clients (DHCP and static) are pointing to the new boxes for DNS.

Transfer the FSMO roles to the 2008 DC.

I'd first just shut the 2003 box off for a day or two before final decom.

Thanks

Mike
0
 
tenoverAuthor Commented:
Is there a way to setup the exact same DNS scope on one of the new 2008 DC's and just stop DHCP on the old 2003 server in case something doesn't go as planned?
0
 
tenoverAuthor Commented:
Can I transfer the FSMO roles during working hours without any downtime?  
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
GovvyCommented:
Yes, FSMO transfer has no impact to end users - it is a backend configuration change
0
 
tenoverAuthor Commented:
With two old 2003 DC's and 1 new 2008 DC, with FSMO roles now transferred to the 2008 DC and DNS setup on all three DC's, how can I verify everything is working as it should before moving forward?  I've run some DCDIAG's and I get some errors, but after researching them, they seem that they are due to the Domain Level not being raised, having both 2003 and 2008 DC's online and can be "safely ignored".  Is there some kind of test I can run before turning off at least one of the 2003 DC's to make sure everything functions properly (Logins, Group Policies, Exchange, etc...).
0
 
GovvyCommented:
Check exchange 2003 directory access tab: http://www.msexchange.org/tutorials/closer-look-directory-service-access-dsaccess-part1.html

You can manually specify DC's to connect to temporarily.

Also turn on DNS debugging to determine which clients use the 2003 DC's for lookups and then repoint DNS config...
0
 
ZenVenkyArchitectCommented:
First you need to raise the functional level of 2003 DC using 2008 DVD,  join 2008 server to domain. Once it is done, run DCPROMO in 2008 to make it as ADC. Now transfer all the 5 FSMO roles to 2008. Then change DNS settings in 2008 as primary DNS to itself and additional to second DC. Now demote 2003 DC and run metadata cleanup to remove all the traces of demoted DC.
0
 
tenoverAuthor Commented:
So each new 2008 DC should have it's primary DNS setting pointing to ITSELF and the secondary should point to the other 2008 server? I have all 4 DC's up and running now. All running DNS and seem to be propogating ok. The next thing to do is to change the DNS settings on all our servers and static clients, and then configure DHCP on one of these 2008 servers...Then turn off the 2003 servers for a couple days ago, correct?
0
 
tenoverAuthor Commented:
Can someone tell me what the DNS settings should be on these two new 2008 DC/DNS Servers?  I would like to point them too each other and leave the two old 2003 DC/DNS Servers off on their own....Should each 2008 DC/DNS Server point to ITSELF as the primary DNS server and the other as it's secondary or vice versa?  I keep reading that you DO NOT want to point a DNS server at itself as a primary, but then I read that this "Islanding" issue has been resolved in Server 2008 and that you SHOULD point each DNS server to itself.....??
0
 
GovvyCommented:
I would recommend secondary DNS points to localhost and primary points to other 2008 DNS
0
 
tenoverAuthor Commented:
Ok, both old 2003 DC's have been unplugged for 5-6 days without any issues.  Should I go ahead and plug them back in and run DCPROMOI on them, and then shut them down?  How long should I wait after that until I raise the domain level to 2008? And last but not least, I was reading some horror stories about people who have done this same thing and had serious Exchange 2003 issues in regards to RUS.....Any tips or suggestions so I don't run into these issues after decommissioning the old DCs?
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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