'' is feasible.
Part of the process of developing the Directory tree maps is to determine names of objects. If there are standards in place for using NDS, then users can more fully navigate, use, and exploit the Directory tree.
Searching and browsing rely heavily on the ability to do a lookup in the Directory based on criteria from the user. If object names follow a standard, then searching is simpler.
For example, if all laser printers are named ``LJuniquename'',
where uniquename is more descriptive, then a search for all
printers named ``LJ'' is feasible.
See ``NDS objects and properties standards'' for more information.
Note that using familiar naming conventions, such as users' email names, ensures 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, and so on) for the objects.
If you will use bindery services, make sure the names are compatible with standards for bindery-based versions of NetWare. See ``NDS objects and properties standards'' for more information.
Consistent naming standards provide a guideline for network supervisors who will be adding file servers, creating users, modifying and moving objects, and son on. Consistent standards also make it easy for users to identify the resources available to them in the Directory tree.
Note that 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. Refer to ``Managing NDS'' for more information.
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.