Active directory

i have 2 sites and to domains. The first site I would like to hold the first domain conroller which will be the forest root. The second site needs to have a child domain. The DNS zones will be on the first domain controller and will have active directory zones for both domains. Please can somone advise the procudures involced with setting up the child domian controller in the second site. There is a network link established, and I can ping the dns server. The child domain controller is at the moment a 2003 server in its basic. I am not sure what the next step is. Does the installation place the child domain controller in the site 2 automatically when updating the server to a child domain controller?

Answer Wiki

Thanks. We'll let you know when a new response is added.

First off; do you need 2 domains? AD will cope happily with 1 domain spread over 2 sites, and it may reduce the complications further down the line.
You should set up your sites in AD first, specifying the IP address ranges in both. Then you can install the second DC and get them talking to each other. Once you give the 2nd DC its IP address within the correct range for its site, it will reside in that site.

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • PaulieEddie
    You can ping the domain controller from the other site, which is good. You may also want to be more thorough and run the NETDIAG tool on the domain controller is Site2 as well as the domain controller in Site1. This will clue you in to other issues like DNS problems. Next you should validate that you have the subnets set up in the Active Directory Sites and Services. You will need to define the subnets for the current site and assign them to that site. Then create the second site. Add the subnets in for the second site and assign them to Site2. The first site is always called Default-First-Site-Name unless you have changed it. All subnets for both locations on the network should be accounted for and assigned to their respective sites. Now you can use DCPROMO to make the Windows 2003 server in Site2 into a domain controller, specifying that it will be a child domain in the original domain. Now - I have to agree with the previous respondent regarding the creation of an additional domain. In general domains are not necessary - the use of Sites and OU's is more efficient and easier to manage. You should only create additional domains if: 1) The other domain requires a different password policy than the original domain. This sometimes comes into play with a multi-national computing enterprise or government work. 2) There is a business reason, such as an impending diversification of the company and the removal of a division from the companies portfolio. You will want to have an easy way to separate them. 3) There is a highly decentralized (and often highly-political) separation within IT to manage the locations. #1 is the only real technical reason. :) Paul
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: