Determining The Forest Root Domain

By Author: Mike Jones
Total Articles: 256
Comment this article

As you learned in Chapter 1, the forest root domain is the first domain you create in an Microsoft exam 70-291. The forest root domain must be centrally managed by an IT organization that is responsible for making domain hierarchy, naming, and policy
decisions. When planning a domain structure, you should start with a dedicated forest root domain. A forest root domain is dedicated when it is set up exclusively to administer the forest infrastructure. A dedicated forest root domain is recommended for the following reasons:
You can control the number of administrators allowed to make forestwide changes. By limiting the number of administrators in the forest root domain, you
reduce the likelihood that an administrative error will impact the entire forest.
You can easily replicate the forest root across the enterprise. Because a dedicated root domain is small, it can be easily replicated anywhere on your network to provide protection against catastrophes.
The forest root never becomes obsolete. Because the only purpose of the forest root domain is to serve as ...
... the root, there is little chance of it becoming obsolete.
You can easily transfer ownership of the root. Transferring ownership of the root domain does not involve migrating production data or resources.
The role of a dedicated forest root domain is to define and manage the infrastructure. Therefore, when you plan domains, you should reserve the dedicated forest root domain for free 70-291 test questions forest administration only. Avoid including users or resources not dedicated to forest administration in the forest root domain.
Determining the Number of Domains
After you've planned the dedicated forest root domain, you should begin planning your domain structure with a single child domain under the root, and add more domains only when the single child domain model no longer meets your needs. One domain can span multiple sites and contain millions of objects. Keep in mind that site and domain structures are separate and flexible. A single domain can span multiple geographical sites, and a single site can include users and computers belonging to mul?tiple domains. Planning your site structure is covered in Chapter 5, "Configuring Sites and Managing Replication."
You should not create separate domains to reflect your company's organization of divisions and departments. Because functional structures such as divisions, departments, or project teams are always subject to change, defining domains based on these structures in the organization is strongly discouraged. Within each domain, you can model your organization's management hierarchy for delegation or administration using organizational units (OUs) for this purpose. You can then assign Group Policy and place users, groups, and computers into the OUs. Planning free Microsoft practice questions structure is covered in Chapter 6, "Implementing an OU Structure."