Upgrading domain controller. How to set my new dc as the primary one so I can remove the old one?
Hello Experts,
I just installed a new domain controller server running Windows Server 2008 R2. I have everything ready to go, except for two things...
I transferred all of the dns zones to the new server except for one zone that doesn't seem to want to transfer. Is it because it is a secondary zone that is not integrated in active directory? Would there be any issues with changing it to a primary zone and integrating it with active directory? Will it mess anything up? If I can't do that, is there another way to get that zone to the new server?
Last, how do I go about fully implementing the new domain controller so that I can physically remove the old one? Do I just change the ip addresses on both and then remove the old one?
Thanks in advance for the help.
I just installed a new domain controller server running Windows Server 2008 R2. I have everything ready to go, except for two things...
I transferred all of the dns zones to the new server except for one zone that doesn't seem to want to transfer. Is it because it is a secondary zone that is not integrated in active directory? Would there be any issues with changing it to a primary zone and integrating it with active directory? Will it mess anything up? If I can't do that, is there another way to get that zone to the new server?
Last, how do I go about fully implementing the new domain controller so that I can physically remove the old one? Do I just change the ip addresses on both and then remove the old one?
Thanks in advance for the help.
You can change it to primary/AD Integrated. Where did you originally pull that zone from? Make sure clients are pointing to the new box for DNS. Make sure the new box is also a global catalog.
What do you mean when you say change the IP. Do you want the new DC to have the same IP as the old box?
Thanks
Mike
What do you mean when you say change the IP. Do you want the new DC to have the same IP as the old box?
Thanks
Mike
ASKER
Mike,
Exactly. I want to basically clone the old dc using the new one. I want the new dc to look exactly the same as the old one.
That secondary dns zone was created before I started working here so I'm not sure who created it or why it was done that way.
Exactly. I want to basically clone the old dc using the new one. I want the new dc to look exactly the same as the old one.
That secondary dns zone was created before I started working here so I'm not sure who created it or why it was done that way.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
When I ran dcpromo.exe, I installed global catalog, but how do I make sure it is installed? nevermind i figured it out. yes, it is installed.
ASKER
Thanks so much for the help, Mike. Everything works amazingly! That link you provided is very helpful as well!
I'm actually going to leave the computer name on the new dc what I named it because it makes more sense than what the old one was named.
I'm actually going to leave the computer name on the new dc what I named it because it makes more sense than what the old one was named.
If your goal is to remove the old DC, then transfer the FSMO roles and make sure the new DC is a global Catalog server in AD Sites and Services.
As for that DNS zone, why wasn't it AD integrated in the first place? You can just change the type of zone and give it a few minutes (I like a day) to replicate and check the event logs to make sure there are no problems, and then run DCPROMO to demote the old DC. Once demoted, you can remove it from the network.
Why are you changing the IP addresses? Change the DNS info in DHCP in reset the DNS IPs on the static devices. Or better still, keep both servers for redundancy.