NetWare Directory Services

4-3
Understanding Bindery Services
Overview
Figure 4-1 Bindery Services in a Directory Tree
A writable replica of the partition that includes the container object to be set
as the bindery context must be stored on each server you want bindery
services enabled on. However, by default, only the first three servers
installed on a partition receive a replica of the partition during the
installation process and subsequently support bindery services.
You can add replicas to other servers if needed for bindery services. If a
read/write or master replica is not present, use the Partition Manager utilities
to add one to the server. See chapter 9, “PARTMGR” for information and
procedures.
NOTE: If a bindery context is not set, NDS cannot support bindery services.
Bindery services allows NetWare 4 servers to emulate earlier versions of
NetWare and is, therefore, server-centric. For instance, if a client
workstation requests a bindery login, bindery services directs the default
server to use the bindery login script found in the user’s mail directory on
the SYS volume instead of using the user’s global NDS login script.
Changes to the bindery login script are kept locally and are not distributed to
other servers.
Leaf objects
Bindery context is
set here.
All of these objects
appear as a bindery
to NetWare 2 and 3
clients.
Server object
Server object
User object
requiring
bindery serices
Read/Write
replica of this
partition stored
on each server
in this context.
[ROOT]
[ROOT]
OrganizationOrganizationOrganization
Organizational
Unit
Organizational
Unit