Retiring/replacing a Domain Controller
I have an older Windows 2003 box that serves as my Domain Controller - Active Directory, Group Policy, DNS and I believe DHCP as well. What steps do I need to do to replace that Domain Controller with another Brand New 2003 server box giving it the same IP address and name as the old box. I know I will need to transfer everything including the roles to the new box but what/how should the steps look like?
Thanks for the help!
Thanks for the help!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
If I am not using AD-Integrated DNS, should DNS replicate over?
ASKER
Or maybe i should be asking if there is a way to actually replicate my DNS settings over. I am totally new to DNS configuration as well...
Is there any reason that you are not using AD integrated DNS - its the most sensible option in all but a very few "specialist" cases.
Check by right clicking on the zone and selecting properties (you can also make it AD integrated here if needs be)
Check by right clicking on the zone and selecting properties (you can also make it AD integrated here if needs be)
>> If I am not using AD-Integrated DNS, should DNS replicate over <<
No it will not - you will need to set up a secondary DNS server, do a zone transfer from the primary DNS server and then make the secondary the primary - a lot of faffing about - Use AD Integrated DNS.
No it will not - you will need to set up a secondary DNS server, do a zone transfer from the primary DNS server and then make the secondary the primary - a lot of faffing about - Use AD Integrated DNS.
ASKER
Are you talking about the Load Zone Data on Startup dropdown? If so, Active Directory & Registry are chosen. I see no other area where AD is mentioned. However, the DNS was showing as not configured until I went in and told it to copy as a secondary zone and it copied everything... Is that what I wanted to do?
DO NOT CREATE A SECONDARY ZONE. SECONDARY ZONES ARE READ ONLY COPIES.
Go to the current (old) DNS server, Open the DNS console. Right click on the Zone and select Properties and make sure it says AD Integrated - that is the defaiult - and its the default for a very good reason, its the most efficient, most secure and simplest to manage.
Go to the current (old) DNS server, Open the DNS console. Right click on the Zone and select Properties and make sure it says AD Integrated - that is the defaiult - and its the default for a very good reason, its the most efficient, most secure and simplest to manage.
ASKER
I just saw what you were talking about and it IS NOT checkmarked. This is how the domain was set up before I got here. If I check that box what will happen? I am just afraid of everything going down on me...
Is there any good reason why it is not ticked - for example are you using UNIX BIND DNS servers? If not make it AD Integrated.
ASKER
To my knowledge I have no unix box's here... I have Linux based servers but none of which are handeling DNS to my knowledge. So if I tick that box, what happens next? Sorry for being so "worried"
See http://support.microsoft.com/kb/198437
It makes more sense to have all DNS servers AD integrated as effectivly all DNS servers are writeable primary DNS servers and its all so much more efficient.
It makes more sense to have all DNS servers AD integrated as effectivly all DNS servers are writeable primary DNS servers and its all so much more efficient.
ASKER
Ok I went a head and did it. I also manually told it to replicate to the other servers, I am guessing it may take a little bit of time... I will keep you posted, Thanks again KCTS for putting up with me, I will make sure i keep you updated and award points, etc.
ID AD is integrated, all you should need to do now if you install another DC is to point it at an existing DNS server to begin with, DCPROMO it, then add DNS - DNS will then replicate automatically along with AD.
All that then remains id to point the new DC/DNS server to itself as preferred DNS server (and possibly to another DNS server as the alternate DNS)
All that then remains id to point the new DC/DNS server to itself as preferred DNS server (and possibly to another DNS server as the alternate DNS)
ASKER
It was as easy as pie! Thanks again for helping me and putting up with my n00b ways.
It is much appreciated!
Thanks!
It is much appreciated!
Thanks!
Set up the new server.. join it to the domain as a member server.. install DNS, DHCP, WINS and don't configure them yet. On the current DHCP server set the TTL to 1 day.. Once it is all up to date on all updates DCPROMO it and make it a domain controller and make sure the active directory DNS is configured (which DC promo should do).. once it is a domain controller make it a global catalog server as well.. let things settle for a day then you can configure the DHCP and then at the end of the day authorize it to do DHCP and deauthorize the old one. Let that settle.. a day or two later change the master rolls from the old server to the new one.. let that settle and within a day or two you can DCpromo the old server and then finally decommission it.