Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP 9000 Networking: NetWare Directory Services > Chapter 4 Understanding Bindery Services

Planning Bindery Services

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

When you plan and implement bindery services, you need to consider the following.

Created Objects

Keep these guidelines in mind as you plan bindery services:

  • If you require the user GUEST or GROUP EVERYONE or if you use a service that requires GUEST, you must create such a user in the NDS database.

  • During installation, a bindery object SUPERVISOR is created but is not used with NDS. The NDS utilities do not display this object. This object is intended to be used with bindery services and to enable access to the server via a bindery login. Once bindery services is enabled, you can use this object to log in to the server, providing you log in as a bindery object.

    You can create an NDS User object SUPERVISOR and assign ADMIN- equivalent rights to it in NDS. However, the bindery object and the NDS object are unique and separate objects even though they are identified by the same name.

  • After installing NetWare Services, you can use a migration utility to convert bindery user accounts to NDS User and Group objects. If you do, all users except SUPERVISOR and all groups are updated to NDS objects. The user SUPERVISOR is migrated, but with supervisory rights for that server's file system and bindery context only. The supervisor does not appear as an NDS object.

Inaccessible Information

Some NDS information is not available to users through bindery services. This information includes, but is not limited to, the following items:

  • E-mail name

  • Phone number

  • Print job configurations

  • Aliases

  • Profiles

  • NDS login scripts

Limited Partitioning

The bindery context for a server can be set to a container that is part of a partition stored on a different server. But, before you can use bindery services, you must place a writable replica of the partition that includes the bindery context on the bindery services-enabled server.

If you set the bindery context for a server to a container object that is not part of a writable replica on that server, users will not be able to log in via bindery services.

Changing Contexts

Avoid changing a server's bindery context once you set it. Changing a server's bindery context leaves users in the original context without access to bindery services. Changing the server's bindery context can also cut off access to print queues.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1996 Hewlett-Packard Development Company, L.P.