NetWare Directory Services

7-10
Planning NetWare Directory Services Implementation
Organizing Objects into a Logical Hierarchy
Organizing Objects into a Logical Hierarchy
Keeping your Directory tree structure as shallow as possible (three to five
levels) benefits both small and large Directory trees. Nevertheless, NDS
supports any degree of subordination you need to best support your
organization’s infrastructure.
Your Directory tree can model any or all of the following structures:
• Organizational chart structure
You can begin with your organizational chart, and modify it according to
network access requirements and other factors.
• Geographic structure
You can use geographic locations as Organizational Units. Then, you could use
your organizational chart for each location to organize those divisions.
• Functional structure
If users or groups in your department or organization perform similar functions,
consider organizing your Directory tree by function. Such users are likely to
share servers and other resources, so it makes sense to group them together.
This is especially useful for groups of bindery services users.
• Bindery services structure
The portions of the Directory used by bindery services users should use a
combination of all three of the previously mentioned structures.
Bindery services users should be grouped within bindery contexts defined by
workgroups, shared resources, and information usage and exchange.
Placing similar users in the same container object makes it easier to give bindery
services users access to the resources they need.
Planning the Directory Tree Levels
You create container objects to form the top level of the Directory tree for
both departmental and organizational strategies. These container objects
help you manage and organize the network by relating groups of other
container objects and leaf objects.