When you create or rename an NDS* object, you must fill in a name field. The name you enter is used as the official name of the object in the NDS tree. It corresponds to the CN, O, or OU value in typeful name specifications like CN=DJONES and O=XYZ_CORP. Here are some guidelines you should follow when creating an official object name.
Uniqueness
The name should be unique within the container. For example, users Debra Jones and Daniel Jones can't both be named DJONES if they are in the same container.
Special Characters
You can use special characters, but plus (+) and equals (=) must be preceded by a backslash (\) if used. In fully distinguished names, plus (+), equals (=), and period (.) are displayed with a preceding backslash.
Uppercase and Lowercase
Uppercase, lowercase, underscores, and spaces will be displayed as you first enter them, but they aren't distinguished by the system. For example, the names Manager_Profile and MANAGER PROFILE are considered identical. If you use spaces in the name, users will have to enclose the name in quotes when entering it on the command line or in login scripts.
Multilingual Networks
If users will view the object in different languages, you might want to limit the name to characters that are viewable in all those languages. For example, a name entered in Japanese can contain characters that aren't viewable in Western languages.
Bindery-based Networks
If users will access the object through bindery-based (NetWare* 2 or NetWare 3*) client software, spaces in the name will be replaced with underscores and the name will be truncated to 47 characters (bytes). In addition, the following characters are not supported in bindery environments:
Related Topics
Web Links
* Novell trademark. ** Third-party trademark. For more information, see Trademarks.