Overview

This chapter describes management procedures for setting up and maintaining bindery services (also called bindery emulation) when you implement the NetWare® Directory Services™ (NDS) technology on your network.

The following topics are discussed on the indicated pages:

Some applications and services which run in the NetWare 4™ environment do not currently take full advantage of NDS™ technology. Novell created bindery services to allow users in these environments access to NetWare 4 services.

With bindery services, NDS imitates a flat structure for leaf objects within an Organization or Organizational Unit object. Thus, when bindery services is enabled, all objects within the specified container can be accessed by NDS objects and by bindery-based servers and client workstations.

	CAUTION: Bindery services applies only to leaf objects in the specified container object.

The container object where bindery services is set is called the bindery context. To enable bindery services, you can use the SAM utility or the nwcm command line utility (see "nwcm" in Utilities Reference).

The following figure illustrates bindery services when an Organizational Unit object is specified as the bindery context.

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.

You cannot disable bindery services if someone is logged in via bindery services, and bindery objects are always available unless bindery services is disabled.