Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities
on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export
laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses.
Please refer to www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no
responsibility for your failure to obtain any necessary export approvals.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent
applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the online documentation for this and other Novell products, and to get
updates, see www.novell.com/documentation.
Novell Trademarks
Client32 is a trademark of Novell, Inc.
eDirectory is a trademark of Novell, Inc.
NetWare is a registered trademark of Novell, Inc., in the United States and other countries.
NetWare Core Protocol and NCP are trademarks of Novell, Inc.
NMAS is a trademark of Novell, Inc.
Novell is a registered trademark of Novell, Inc., in the United States and other countries.
Novell Client is a trademark of Novell, Inc.
Novell Directory Services and NDS are registered trademarks of Novell, Inc., in the United States and other
countries.
Ximiam is a registerd trademark of Novell, Inc., in the United States and other countries.
ZENworks is a registered trademark of Novell, Inc., in the United States and other countries.
Third-Party Materials
All third-party trademarks are the property of their respective owners.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://
This guide describes how to manage and configure Novell® eDirectoryTM 8.8.
Chapter 1, “Understanding Novell eDirectory,” on page 19
Chapter 2, “Designing Your Novell eDirectory Network,” on page 73
Chapter 3, “Managing Objects,” on page 93
Chapter 4, “Managing the Schema,” on page 121
Chapter 5, “Managing Partitions and Replicas,” on page 133
Chapter 6, “Novell eDirectory Management Utilities,” on page 145
Chapter 7, “Offline Bulkload Utility,” on page 191
Chapter 8, “Using Novell iMonitor 2.4,” on page 197
Chapter 9, “Merging Novell eDirectory Trees,” on page 223
Chapter 10, “Encrypting Data In eDirectory,” on page 239
Chapter 11, “Repairing the Novell eDirectory Database,” on page 263
novdocx (en) 11 July 2008
Chapter 12, “WAN Traffic Manager,” on page 289
Chapter 13, “Understanding LDAP Services for Novell eDirectory,” on page 321
Chapter 14, “Configuring LDAP Services for Novell eDirectory,” on page 349
Chapter 16, “Backing Up and Restoring Novell eDirectory,” on page 421
Chapter 17, “SNMP Support for Novell eDirectory,” on page 493
Chapter 18, “Maintaining Novell eDirectory,” on page 537
Chapter 19, “DHost iConsole Manager,” on page 577
Chapter 20, “The eDirectory Management Toolbox,” on page 587
Appendix A, “NMAS Considerations,” on page 601
Appendix B, “Novell eDirectory Linux and UNIX Commands and Usage,” on page 607
Appendix C, “Configuring OpenSLP for eDirectory,” on page 615
Appendix D, “How Novell eDirectory Works with DNS,” on page 619
Appendix E, “Configuring GSSAPI with eDirectory,” on page 621
Audience
The guide is intended for network administrators.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.
About This Guide17
Documentation Updates
For the most recent version of this guide, see Novell eDirectory 8.8 Administration Guide (http://
www.novell.com/documentation/edir88/index.html).
Additional Documentation
For eDirectory installation instructions, see the Novell eDirectory 8.8 Installation Guide (http://
www.novell.com/documentation/edir88/index.html).
For documentation on the eDirectory management utility, see the Novell iManager 2.6
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items
within a cross-reference path.
®
A trademark symbol (
, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
novdocx (en) 11 July 2008
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux and UNIX*, should use forward slashes as required by your software.
18Novell eDirectory 8.8 Administration Guide
1
Understanding Novell eDirectory
In simplest terms, Novell® eDirectoryTM is a list of objects that represent network resources, such as
network users, servers, printers, print queues, and applications. Novell eDirectory is a highly
scalable, high-performing, secure directory service. It can store and manage millions of objects,
such as users, applications, network devices, and data. Novell eDirectory offers a secure identity
management solution that runs across multiple platforms, is internet-scalable, and extensible.
Novell eDirectory provides centralized identity management, infrastructure, Net-wide security, and
scalability to all types of applications running behind and beyond the firewall. Novell eDirectory
includes Web-based and wireless management capabilities, allowing you to access and manage the
directory and users, access rights, and network resources from a Web browser and a variety of
handheld devices.
Novell eDirectory natively supports the directory standard Lightweight Directory Access Protocol
(LDAP) 3 and provides support for TLS/SSL services based on the OpenSSL source code. For more
information on the eDirectory engine, see eDirectory Process Requests (http://developer.novell.com/
Figure 1-1 shows a few of the objects as viewed in the Novell iManager management utility.
Figure 1-1 eDirectory Objects in iManager
Some object classes might not be available, depending on the actual schema configured on the
eDirectory server and the operating system running eDirectory.
For more information on objects, see Section 1.2, “Object Classes and Properties,” on page 23.
If you have more than one eDirectory server on the network, the directory can be replicated on
multiple servers.
This chapter includes the following information:
Section 1.1, “Ease of Management through Novell iManager,” on page 20
Section 1.2, “Object Classes and Properties,” on page 23
Section 1.3, “Context and Naming,” on page 42
Section 1.4, “Schema,” on page 45
Section 1.5, “Partitions,” on page 52
Understanding Novell eDirectory
19
Section 1.6, “Replicas,” on page 55
Section 1.7, “NetWare Bindery Emulation,” on page 59
Section 1.8, “Server Synchronization in the Replica Ring,” on page 59
Section 1.9, “Access to Resources,” on page 60
Section 1.10, “eDirectory Rights,” on page 60
1.1 Ease of Management through Novell
iManager
Novell eDirectory allows for easy, powerful, and flexible management of network resources. It also
serves as a repository of user information for groupware and other applications. These applications
access your directory through the industry-standard Lightweight Directory Access Protocol
(LDAP).
eDirectory ease-of-management features include a powerful tree structure, an integrated
management utility, and single login and authentication.
Novell iManager lets you manage the directory and users, and access rights and network resources
within the directory, from a Web browser and a variety of handheld devices. The eDirectory plug-ins
to iManager give you access to basic directory management tasks, and to the eDirectory
management utilities you previously had to run on the eDirectory server, such as DSRepair,
DSMerge, and Backup and Restore.
novdocx (en) 11 July 2008
For more information, see the Novell iManager 2.6 Administration Guide (http://www.novell.com/
documentation/imanager26/index.html).
1.1.1 Powerful Tree Structure
Novell eDirectory organizes objects in a tree structure, beginning with the top Tree object, which
bears the tree's name.
®
Whether your eDirectory servers are running NetWare
resources can be kept in the same tree. You won’t need to access a specific server or domain to
create objects, grant rights, change passwords, or manage applications.
The hierarchical structure of the tree gives you great management flexibility and power. These
benefits primarily result from the following two features:
“Container Objects” on page 20
“Inheritance” on page 21
Container Objects
Container objects allow you to manage other objects in sets, rather than individually. There are three
common classes of container objects, as seen in Figure 1-2:
Figure 1-2 Common Classes of Container Objects
, Linux*, UNIX*, or Windows*, all
20Novell eDirectory 8.8 Administration Guide
Description: Tree object icon The Tree object is the top container object in the tree. It usually
contains your company’s Organization object.
Description: Organization object icon Organization is normally the first container class under
the Tree object. The Organization object is typically named after your company. Small companies
keep management simple by having all other objects directly under the Organization object.
Description: Organizational Unit object icon Organizational Unit objects can be created under
the Organization to represent distinct geographical regions, network campuses, or individual
departments. You can also create Organizational Units under other Organizational Units to further
subdivide the tree.
Other classes of container objects are Country and Locality, which are typically used only in
multinational networks.
Description: Domain icon The Domain object can be created under the Tree object or under
Organization, Organizational Unit, Country, and Locality objects.
You can perform one task on the container object that applies to all objects within the container.
Suppose you want to give a user named Amy complete management control over all objects in the
Accounting container. (See Figure 1-3.)
novdocx (en) 11 July 2008
Figure 1-3 Container Object
To do this, right-click the Accounting object, select Trustees of This Object, then add Amy as a
trustee. Next, select the rights you want Amy to have, then click OK. Now Amy has rights to
manage the Database application, the Bookkeepers group, the LaserPrinter printer, and the users
Amy, Bill, and Bob.
Inheritance
Another powerful feature of eDirectory is rights inheritance. Inheritance means that rights flow
down to all containers in the tree. This allows you to grant rights with very few rights assignments.
For example, suppose you want to grant management rights to the objects shown in Figure 1-4 on
page 21.
Figure 1-4 Sample eDirectory Objects
Understanding Novell eDirectory21
You could make any of the following assignments:
If you grant a user rights to Allentown, the user can manage only objects in the Allentown
container.
If you grant a user rights to East, the user can manage objects in the East, Allentown, and
Yorktown c o n t a iners.
If you grant a user rights to YourCo, the user can manage any objects in any of the containers
shown.
For more information on assigning rights, see Section 1.10, “eDirectory Rights,” on page 60.
1.1.2 Web-Based Management Utility
iManager is a browser-based tool used for administering, managing, and configuring eDirectory
objects. iManager gives you the ability to assign specific tasks or responsibilities to users and to
present the user with only the tools (with the accompanying rights) necessary to perform those sets
of tasks.
To run iManager, you will need a workstation with Microsoft* Internet Explorer 6.0 SP1 or later
(recommended), Mozilla* 1.7 or later, or Mozilla Firefox* 0.9.2.
novdocx (en) 11 July 2008
IMPORTANT: While you might be able to access iManager through a Web browser not listed, we
do not guarantee full functionality.
You can use iManager to perform the following supervisory tasks:
Configure LDAP- and XML-based access to eDirectory
Create objects representing network users, devices, and resources
Define templates for creating new user accounts
Find, modify, move, and delete network objects
Define rights and roles to delegate administrative authority
Extend the eDirectory schema to allow custom object types and properties
Partition and replicate the eDirectory database across multiple servers
Run eDirectory management utilities such as DSRepair, DSMerge, and Backup and Restore
You can use iManager to perform other management functions based on plug-ins that have been
loaded into iManager. The following eDirectory plug-ins are installed with iManager 2.6:
eDirectory Backup and Restore
eDirectory Log Files
eDirectory Merge
eDirectory Repair
eDirectory Service Manager
eGuide Content
iManager Base Content
Import Convert Export Wizard
Index Management
22Novell eDirectory 8.8 Administration Guide
iPrint
LDAP
Universal Password Enforcement
Priority Sync
Encrypted Attributes
Encrypted Replication
NLS
NMAS
PKI/Certificate
Filtered Replica Configuration Wizard
SNMP
WAN Traffic Manager
For more information on installing, configuring, and running iManager, Novell iManager 2.6
With eDirectory, users log in to a global directory, so you don’t need to manage multiple server or
domain accounts for each user, and you don’t need to manage trust relationships or pass-through
authentication among domains.
A security feature of the directory is authentication of users. Before a user logs in, a User object
must be created in the directory. The User object has certain properties, such as a name and
password.
When the user logs in, eDirectory checks the password against the one stored in the directory for
that user and grants access if they match.
1.2 Object Classes and Properties
The definition of each type of eDirectory object is called an object class. For instance, User and
Organization are object classes. Each class of object has certain properties. A User object, for
example, has First Name, Last Name, and many other properties.
The schema defines the object classes and properties, along with the rules of containment (what
containers can contain which objects). eDirectory ships with a base schema that you, or the
applications you use, can extend. For more information about schemas, see Section 1.4, “Schema,”
on page 45.
Container objects contain other objects and are used to divide the tree into branches, while leaf
objects represent network resources.
1.2.1 List of Objects
The following tables list eDirectory object classes. Added services can create new object classes in
eDirectory that are not listed below.
Understanding Novell eDirectory23
eDirectory Container Object Classes
novdocx (en) 11 July 2008
iManager Icon
Container Object
(Abbreviation)
Description
TreeRepresents the beginning of your tree. For more
information, see “Tree” on page 25.
Country (C)Designates the countries where your network resides and
organizes other directory objects within the country. For
more information, see “Country” on page 28.
License Container (LC)Created automatically when you install a license certificate
or create a metering certificate using Novell Licensing
Services (NLS) technology. When an NLS-enabled
application is installed, it adds a License Container
container object to the tree and a License Certificate leaf
object to that container.
Organization (O)Helps you organize other objects in the directory. The
Organization object is a level below the Country object (if
you use the Country object). For more information, see
“Organization” on page 26.
Organizational Unit (OU)Helps you to further organize other objects in the directory.
The Organizational Unit object is a level below the
Organization object. For more information, see
“Organizational Unit” on page 27.
Domain (DC)Helps you to further organize other objects in the directory.
The Domain object can be created under the Tree object or
under Organization, Organizational Unit, Country, and
Locality objects. For more information, see “Domain” on
page 28.
eDirectory Leaf Object Classes
iManager Icon Leaf ObjectDescription
AFP ServerRepresents an AppleTalk* Filing Protocol server that operates as a
node on your eDirectory network. It usually also acts as a NetWare
router to, and the AppleTalk server for, several Macintosh*
computers.
AliasPoints to the actual location of an object in the directory. Any
directory object located in one place in the directory can also
appear to be in another place in the directory by using an Alias. For
more information, see “Alias” on page 40.
ApplicationRepresents a network application. Application objects simplify
administrative tasks such as assigning rights, customizing login
scripts, and launching applications.
ComputerRepresents a computer on the network.
Directory MapRefers to a directory in the file system. For more information, see
“Directory Map” on page 41.
24Novell eDirectory 8.8 Administration Guide
iManager Icon Leaf ObjectDescription
GroupAssigns a name to a list of User objects in the directory. You can
assign rights to the group instead of to each user; then the rights
transfer to each user in the group. For more information, see
“Group” on page 32.
License CertificateUse with NLS technology to install product license certificates as
objects in the database. License Certificate objects are added to the
Licensed Product container when an NLS-aware application is
installed.
Organizational Role Defines a position or role within an organization.
Print QueueRepresents a network print queue.
Print ServerRepresents a network print server.
PrinterRepresents a network printing device.
ProfileRepresents a login script used by a group of users who need to
share common login script commands. The users don’t need to be
in the same container. For more information, see “Profile” on
page 42.
novdocx (en) 11 July 2008
ServerRepresents a server running any operating system. For more
information, see “Server” on page 29.
TemplateRepresents standard User object properties that can be applied to
new User objects.
UnknownRepresents an object for which iManager has no custom icon.
UserRepresents the people who use your network. For more
information, see “User” on page 31.
VolumeRepresents a physical volume on the network. For more
information, see “Volume” on page 30.
1.2.2 Container Object Classes
“Tree” on page 25
“Organization” on page 26
“Organizational Unit” on page 27
“Country” on page 28
“Domain” on page 28
Tree
Description: Tree object icon The Tree container, formerly [Root], is created when you first
install eDirectory on a server in your network. As the top-most container, it usually holds
Organization objects, Country objects, or Alias objects.
What Tree Represents
Tree represents the top of your tree.
Understanding Novell eDirectory25
Usage
Tree is used to make universal rights assignments. Because of inheritance, any rights assignments
you make to Tree as the target apply to all objects in the tree. See Section 1.10, “eDirectory Rights,”
on page 60. The [Public] trustee has the Browse right and Admin has the Supervisor right to Tree by
default.
Important Properties
The Tree object has a Name property, which is the tree name you supply when installing the
first server. The tree name is shown in the hierarchy of iManager.
Tree name cannot exceed 32 characters.
Organization
Description: Organization object icon An Organization container object is created when you first
install eDirectory on a server in your network. As the top-most container under Tree, it usually holds
Organizational Unit objects and leaf objects.
The User object named Admin is created by default in your first Organization container.
novdocx (en) 11 July 2008
What an Organization Object Represents
Normally the Organization object represents your company, although you can create additional
Organization objects under Tree. This is typically done for networks with distinct geographical
districts or for companies with separate eDirectory trees that have merged.
Usage
The way you use Organization objects in your tree depends on the size and structure of your
network. If the network is small, you should keep all leaf objects under one Organization object.
For larger networks, you can create Organizational Unit objects under the Organization to make
resources easier to locate and manage. For example, you can create Organizational Units for each
department or division in your company.
For networks with multiple sites, you should create an Organizational Unit for each site under the
Organization object. That way, if you have (or plan to have) enough servers to partition the
directory, you can do so logically along site boundaries.
For easy sharing of company-wide resources such as printers, volumes, or applications, create
corresponding Printer, Volume, or Application objects under the Organization.
26Novell eDirectory 8.8 Administration Guide
Important Properties
The most useful properties for Organization are listed below. Only the Name property is required.
For a complete list of properties, select an Organization object in iManager. To display a description
for each page of properties, click Help.
Name
Typically, the Name property is the same as your company’s name. Of course, you can shorten
it for simplicity. For instance, if the name of your company is Your Shoe Company, you might
use YourCo.
The Organization name becomes part of the context for all objects created under it.
Login Script
The Login Script property contains commands that are executed by any User objects directly
under the Organization. These commands are run when a user logs in.
Organization name can be 64 characters long.
Organizational Unit
novdocx (en) 11 July 2008
Description: Organizational Unit object icon You can create Organizational Unit (OU) container
objects to subdivide the tree. Organizational Units are created with iManager under an Organization,
Country, or another Organizational Unit.
Organizational Units can contain other Organizational Units and leaf objects such as User and
Application objects.
What an Organizational Unit Object Represents
Normally the Organizational Unit object represents a department, which holds a set of objects that
commonly need access to each other. A typical example is a set of Users, along with the Printers,
Volumes, and Applications that those Users need.
At the highest level of Organizational Unit objects, each Organizational Unit can represent each site
(separated by WAN links) in the network.
Usage
The way you use Organizational Unit objects in your tree depends on the size and structure of your
network. If the network is small, you might not need any Organizational Units.
For larger networks, you can create Organizational Unit objects under the Organization to make
resources easier to locate and manage. For example, you can create Organizational Units for each
department or division in your company. Remember that administration is easiest when you keep
User objects together in the Organizational Unit with the resources they use most frequently.
For networks with multiple sites, you can create an Organizational Unit for each site under the
Organization object. That way, if you have (or plan to have) enough servers to partition the
directory, you can do so logically along site boundaries.
Understanding Novell eDirectory27
Important Properties
The most useful properties for the Organizational Unit are listed below. Only the Name property is
required. For a complete list of properties, select an Organizational Unit object in iManager. To
display a description for each page of properties, click Help.
Name
Typically, the Name property is the same as the department name. Of course, you can shorten it
for simplicity. For instance, if the name of your department is Accounts Payable, you can
shorten it to AP.
The Organizational Unit name becomes part of the context for all objects created under it.
Login Script
The Login Script property contains commands that are executed by any User objects directly
under the Organizational Unit. These commands are run when a user logs in.
Organizational Unit name can be 64 characters long.
Country
novdocx (en) 11 July 2008
Description: Country object icon You can create Country objects directly under the Tree object
using iManager. Country objects are optional and required only for connection to certain X.500
global directories.
What a Country Object Represents
The Country object represents the political identity of its branch of the tree.
Usage
Most administrators do not create a Country object, even if the network spans countries, since the
Country object only adds an unnecessary level to the tree. You can create one or many Country
objects under the Tree object, depending on the multinational nature of your network. Country
objects can contain only Organization objects.
If you do not create a Country object and find that you need one later, you can always modify the
tree to add one.
Important Properties
The Country object has a two-letter Name property. Country objects are named with a standard
two-letter code such as US, UK, or DE.
Country name cannot exceed 2 characters.
Domain
Description: Domain icon You can create Domain objects directly under the Tree object using
iManager. You can also create them under Organization, Organization Unit, Country, and Location
objects.
What a Domain Object Represents
The Domain object represent DNS domain components. Domain objects let you use your Domain
Name System location of services resource records (DNS SRV) to locate services in your tree.
28Novell eDirectory 8.8 Administration Guide
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.
novdocx (en) 11 July 2008
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.
Understanding Novell eDirectory29
What a Server Object Represents
The Server object represents a server running eDirectory or a bindery-based (NetWare 2 or NetWare
3) server.
Usage
The Server object serves as a reference point for replication operations. A Server object that
represents a bindery-based server allows you to manage the server’s volumes with iManager.
Important Properties
The Server object has a Network Address property, among others. The Network Address property
displays the protocol and address number for the server. This is useful for troubleshooting at the
packet level
For a complete list of properties, select a Server object in iManager. To display a description for
each page of properties, click Help.
Volume
novdocx (en) 11 July 2008
Description: Volume object icon When you create a physical volume on a server, a Volume object
is automatically created in the tree. By default, the name of the Volume object is the server’s name
with an underscore and the physical volume’s name appended (for example, YOSERVER_SYS).
Volume objects are supported only on NetWare. Linux and UNIX file system partitions cannot be
managed using Volume objects.
What a Volume Object Represents
A Volume object represents a physical volume on a server, whether it is a writable disk, a CD, or
other storage medium. The Volume object in eDirectory does not contain information about the files
and directories on that volume, although you can access that information through iManager. File and
directory information is retained in the file system itself.
Usage
In iManager, click the Vo lu m e icon to manage files and directories on that volume. iManager
provides information about the volume’s free disk space, directory entry space, and compression
statistics.
You can also create Volume objects in the tree for NetWare 2 and NetWare 3 volumes.
Important Properties
In addition to the required Name and Host Server properties, there are other important Volume
properties.
Name
This is the name of the Volume object in the tree. By default, this name is derived from the
name of the physical volume, though you can change the object name.
Host Server
This is the server that the volume resides on.
Ve r si o n
30Novell eDirectory 8.8 Administration Guide
Loading...
+ 604 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.