NetWare Directory Services

4-5
Understanding Bindery Services
Planning Bindery Services
Planning Bindery Services
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.