Developing an Integration Strategy for Bindery Services

When planning a hierarchical Directory tree, consider applications and users that still rely on bindery services.

Bindery-based users can access any object in the Directory tree by using multiple accounts. But this can result in significantly more work for the network supervisor (especially if numerous users need several accounts).

Although multiple accounts might still be necessary in your Directory tree, thoughtful planning can reduce the number of accounts you need to create.

Bindery services users should be grouped within a few container objects (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.

Managing Bindery Services

Once NDS is installed, ADMIN can use the NETADMIN or NetWare Administrator utility to manage the Directory tree from a client workstation.

Using the NetWare DOS Requester™ software, your DOS-based client workstations can take full advantage of the NDS functionality and access the NDS administration tools, such as NETADMIN and NetWare Administrator, for managing bindery services.

See "Managing the NetWare Directory Services Tree," in Supervising the Network for more information.

Changing Bindery Context

You can use the System Administration Manager (SAM) or the nwcm command line utility to set a server's bindery context.

For example, suppose you want to change a server's bindery context to the Organizational Unit MFG under the Organization object ACME. At the server, use the following command:

nwcm -s ds_bindery_context="OU=MFG.O=ACME"

Changes made with SAM or nwcm are not effective until the NetWare server is restarted.

Changing Directory Tree Structure

You should always think about bindery services users when making changes to the Directory tree. A change in the structure of the tree could prevent some bindery services users from accessing the network or network objects.

Moving Bindery Contexts

If users are using bindery services within a specific container and that container is moved, you need to reset the bindery context on the servers users are logging in to.