Novell EDIRECTORY 8.8 SP3, Administration Manual, Page: 29 / 634

Understanding Novell eDirectory 29
n
ov
do
cx (e
n)
11
Ju
ly 20
08
Using Domain objects, a tree could look something like this:
DS=Novell.DC=Provo.DC=USA
In this example, all subcontainers are domains. You can also use Domain objects in a mixed tree,
such as:
DC=Novell.O=Provo.C=USA
Or
OU=Novell.DC=Provo.C=USA
Usually, the topmost Domain is the overall Tree, with subdomains under Tree. For example,
machine1.novell.com could be represented by
DC=machine1.DC=novell.DC=com
in a tree
representation. Domains give you a more generic way to set up an eDirectory tree. If all containers
and subcontainers are DC objects, users do not need to remember C, O, or OUs when searching for
objects.
Usage
NetWare 4 and 5 trees cannot have Domain objects at the top of the tree. With NetWare 4 and 5, the
NCP Server object can be placed in an Organization, Country, Organizational Unit, or Locality
container, but not in a Domain container. With NetWare 6, however, you can place Domain objects
at the top of the tree, and you can place the NCP Server object in a Domain container.
For older installations of NetWare (such as NetWare 4), when you prepare the tree to install or
upgrade to NetWare 5 or later, the nds500.sch file will automatically run. After the first server is
installed into the tree, this file extends the schema to allow the Domain container to be created
anywhere and hold most directory objects.
Domain name can be 64 characters long.
1.2.3 Leaf Object Classes
Š
“Server” on page 29
Š “Volume” on page 30
Š
“User” on page 31
Š “Group” on page 32
Š
“Nested Groups” on page 36
Š “Alias” on page 40
Š
“Directory Map” on page 41
Š “Profile” on page 42
Server
Description: Server object icon A Server object is automatically created in the tree whenever
you install eDirectory on a server. The object class can be any server running eDirectory.
You can also create a Server object to represent a NetWare 2 or NetWare 3 bindery server.