Secondary Domain Controller Setup
-
@bbiAngie said:
Based on what you all say, all I really need to do is promote it to a DC, then point it back to my current "primary," let it do its thing then I should be done. (besides re-pointing DNS)
You don't even need to do that. Promoting it will do all of this for you.
-
@Dashrender said:
DNS isn't required, or mandated by the promotion (unless that was changed in 2012 R2) but I'd highly recommend it (might even be considered best practices) and should be offered to be installed during promotion if you don't already have it installed.
DHCP isn't required. DNS very much is a required part of a DC (but doesn't have to be on the same server)
-
Cool, like I said, it just seemed way to easy to be correct. Glad made sure before!
-
A delegation for the DNS server cannot be created because the authoritative parent zone cannot be found or it does not run in Windows NS server. If you are integrating with an existing DNS infrastructure, you should manually create a delegation to this DNS server in the parent zone to ensure reliable name resolution from outside the domain "domain.name.". Otherwise, no action is required.
Translation?
-
@bbiAngie said:
Based on what you all say, all I really need to do is promote it to a DC, then point it back to my current "primary," let it do its thing then I should be done. (besides re-pointing DNS)
Pretty much - I've never seen a failure when promoting a DC. Before you promote the DC, make sure the primarily DNS points to one of the other DCs (which it probably already does). You don't need to change this until just before you demote the old one.
-
@Dashrender said:
Pretty much - I've never seen a failure when promoting a DC.
I see it most times, normally a DNS error.
-
@bbiAngie said:
A delegation for the DNS server cannot be created because the authoritative parent zone cannot be found or it does not run in Windows NS server. If you are integrating with an existing DNS infrastructure, you should manually create a delegation to this DNS server in the parent zone to ensure reliable name resolution from outside the domain "domain.name.". Otherwise, no action is required.
Translation?
It means it couldn't created one at the root, this is expected in many cases as the .com or root dns is not yours.
-
@Jason Is that most likely since one already exists? Should I just click through the error and do all the dns stuff after?
-
Do you get that when you try to install DNS before you promote your server to AD DS?
-
I am getting it during the DNS options while doing the Promo
-
click through, I always get that one
-
@bbiAngie said:
I am getting it during the DNS options while doing the Promo
Click through it it's normal in most setups as the parent zone is not something that's yours.
-
How did your DC promotion go? Is it working now?
-
Pretty sure it is all working. I need to fix a few DNS settings but that's related to the hardware firewall. Other than that it seems to be working/replicating.
-
Awesome, glad to hear that the project worked. Go MangoLassi team!
-
Yes, Thank you all for the help. The confirmation that it was "really that easy" was exactly what I needed!
-
Sweet - a tech question answered!!!
-
-
This is my week to resurrect threads from the dead.
I am doing this as well this week.
Currently have 2 physical DCs running 2003. One of them is also our data server. (I know, I know, on all these fronts.)
Anywho...
I have installed a fresh 2003 Server, and am planning to promote that, and move all the roles to it. Then demote the other two DCs and P2V them.
So, hoping it really is "just that simple."
-
I did something similar a while back with ancient win2k3 server serving AD, DNS, DHCP, file, print services. I demoted, removed AD, removed dns and dhcp. Then i p2v'd it.
It really is very simple to do.
