NetWare Directory Services

2-24
Understanding NetWare Directory Services
Context and Names
Object Naming Rules
Apply the following rules when naming NDS objects:
• The name should be unique in the branch (container) of the Directory tree where
the object is located.
• The name can be up to 64 characters in length.
• You can use special characters. But, if the object needs to be accessed from a
workstation running the NetWare Client shell (NETX), you should avoid using
special characters.
For a list of these special characters, see “Naming Restrictions for Bindery
Services” in this chapter.
• Object names are displayed with uppercase and lowercase letters as they are first
entered, but they are not case-sensitive. Therefore, “ManagerProfile” and
“MANAGERPROFILE” are considered identical names.
• Spaces and underscores can be used and are displayed as spaces. Therefore,
“Manager_Profile” and “Manager Profile” are considered identical names.
If you use a space in a name, you must place quotation marks around that text
string whenever you use a command line utility that includes that text string. For
this reason, spaces are not recommended.
• Country objects can have only two-character names. For example, the United
States is US.
CAUTION: If you anticipate managing objects created from different code pages, you must limit
object names and properties to those characters common to all the applicable code
tables.
Nondisplayable Unicode* characters for your code page are represented by an ASCII
3 character (a “heart” symbol). For more information, see “Unicode” in Concepts.
Naming Restrictions for NetWare Server Objects
The following restrictions apply when naming Server objects:
• When you install NetWare 4, an NDS NetWare Server object is created for the
server in the container object you specify.
• If you create a Server object for a server other than a NetWare 4 server, you must
use the server name for the object, because NDS searches for the server to verify
its existence.