NetWare Directory Services

7-8
Planning NetWare Directory Services Implementation
First Steps
NOTE: Use familiar naming conventions, such as users’ E-mail names, to ensure that each
user has a unique common name.
Naming standards detail the conventions you will use for naming Directory
objects, including users, printers, print queues, and servers. Standards
should also specify how you will enter property values (telephone numbers,
addresses, etc.) for the objects.
If you will use bindery services, make sure the names are compatible with
standards for bindery-based versions of NetWare. (See Appendix C, “NDS
Object Classes and Properties.)
Consistency
Consistent naming standards provide a guideline for network supervisors
who will be adding file servers, creating users, modifying and moving
objects, etc. Consistent standards also make it easy for users to identify the
resources available to them in the Directory tree.
NOTE: Although a consistent naming standard for the corporate network is important, you
do not need to have it perfected before you implement NDS because leaf objects can
be renamed later. See Chapter 9, “Managing NetWare Directory Services. for more
information.
Name Length
Make sure naming schemes are short, yet as descriptive as possible. For
example, “Software Engineering” could be shortened to “SWEng.”
All Directory object names can contain up to 64 characters in their Name
property (the name given when an object is created). The Distinguished
Name of an object is limited to 256 characters (including name types,
periods, and equal signs).
However, concise (short) Organizational Unit names that are meaningful
make it easier to use the Directory tree. Keeping names short reduces the
amount of data going across the wire, simplifies logins, and makes names
easier to remember.