Novell EDIRECTORY 8.8 SP3, Руководство администратора, Страница: 78 / 634

78 Novell eDirectory 8.8 Administration Guide
n
ov
do
cx (e
n)
11
Ju
ly 20
08
The alternative to the pyramid design is a flat tree that places all objects in the top layers of the tree.
eDirectory can support a flat tree design; however, a flat tree design can be more difficult to manage
and partition.
Using One eDirectory SP3 Tree with a Unique Name
A single tree works best for most organizations. By default, one tree is created. With one tree you
have single-user identity on the network, simpler administration of security, and single point of
management.
This recommendation for a single tree for business use does not preclude additional trees for testing
and development.
Some organizations, however, might need multiple trees because of legal, political, or corporate
issues. For example, an organization consisting of several autonomous organizations might need to
create several trees. If your organization needs multiple trees, consider using Novell Nsure Identity
Manager to simplify management. For more information on Novell Nsure Identity Manager, see the
Novell Identity Manager 3.0.1 Administration Guide (http://www.novell.com/documentation/idm/
index.html)
.
When you name the tree, use a unique name that will not conflict with other tree names. Use a name
that is short and descriptive, such as EDL-TREE.
If two trees have the same name and are located on the same network, you might encounter the
following problems:
Š
Updates going to the wrong tree
Š
Resources disappearing
Š
Rights disappearing
Š
Corruption
You can change the tree name using the DSMERGE utility, but do so with caution. A tree name
change impacts the network because you need to reconfigure the clients to use the new tree name.
Creating a Single Organization Object
Generally, an eDirectory tree should have one Organization object. By default, a single Organization
object is created and named after your company. This allows you to configure changes that apply to
the whole company from a single location in the tree.
For example, you can use ZENworks
®
to create a Workstation Import Policy object in the
Organization object. In this policy, which affects the whole organization, you define how
Workstation objects are named when created in eDirectory.
In the Organization container, the following objects are created:
Š
Admin
Š Server
Š
Volume
Networks with only a Windows, Linux, Solaris, or AIX server running eDirectory have no
Volume objects.