5.3.1 Impact of a Name Mapped / Non-Name-Mapped setup on a
Tree
This section analyses the various options of setting up a DSfW tree and the associated limitations.
"Using a Pyramid Design" on page 32
"Using a Flat Design" on page 32
Using a Pyramid Design
With a forest designed in the form of a pyramid, managing and initiating changes to large groups,
and creating logical partitions are easier. This structure is best suited for large organizations with
operations spread out across the globe.
Using a Flat Design
The alternative to the pyramid design is a flat tree that places all objects at one level of the tree.
However, the flat tree design is not supported in DSfW.
DSfW can have only one top level domain and all the other domains need to be organized
underneath the top level domain.
If you have mapped an existing container to a domain, you cannot map the sibling containers to
create a domain. It is also not possible to partition the root container and map it to create a DSfW
forest.
For more information, see
edir871/?page=/documentation/edir871/edir871/data/a2iiidp.html)
5.4 Meeting the Installation Requirements
Before you start the process of installation, ensure you have met the following prerequisites. These
steps can be used to validate the state of the system before beginning the installation process.
Section 5.4.1, "Installation Prerequisites For a Non-Name-Mapped Setup," on page 32
Section 5.4.2, "Installation Prerequisites for a Name-Mapped Setup," on page 35
5.4.1 Installation Prerequisites For a Non-Name-Mapped Setup
"Domain Name is Correct" on page 33
"eDirectory Version" on page 34
"DNS Server is Installed" on page 34
"Time is Synchronized" on page 34
"Schema is Synchronized" on page 35
"Servers in the Replica Ring are Synchronized" on page 35
32
OES 2 SP2: Domain Services for Windows Administration Guide
Designing the eDirectory Tree (http://www.novell.com/documentation/