Naming leaf objects

The object naming rules described in ``Object naming rules'' apply to most leaf objects. Special rules applying to NetWare Server objects and objects viewed through bindery services are described in separate topics. For rules about naming container objects, see ``Naming container objects''.

Object naming rules

Remember these rules when naming an object:

• The name must be unique in the branch (container) of the Directory tree where the object is located.

• The object name can be up to 64 characters in length.

• You can use any special characters. But if the object needs to be accessed from a client running a version of NetWare earlier than NetWare 4, you should avoid using special characters (see ``Object name restrictions for bindery services'').

• You can enter object names in either uppercase or lowercase. Object names are displayed with uppercase and lowercase letters as they were first entered, but they are not case sensitive. Therefore, ``ManagerProfile'' and ``MANAGERPROFILE'' are considered to be identical names.

• You can use both spaces and underscores, but they are both considered spaces. Therefore, ``Manager_Profile'' and ``Manager Profile'' are considered to be 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.

  ---

  NOTE: 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).

  ---

Object name restrictions for bindery services

When you create objects to be accessed from a client running a version of NetWare earlier than NetWare 4, the names of the objects must follow bindery naming rules or else the pre-NetWare 4 client does not recognize them. Object names in bindery services are interpreted as the following:

• Spaces in object names are replaced by underscores.

• Object names longer than 47 characters are cut off after the 47th character.

/

slash

\

backslash

:

colon

,

comma

asterisk

?

question mark

Naming restrictions for NetWare server objects

The first NetWare Server object for a NetWare 4.1 server must be created with Directory Services Install. The object is given the same name as the physical server. Rules for naming physical servers appear in Help of Directory Services Install.

If you create a NetWare Server object for a non-NetWare 4.1 server, you must use the physical server name as well, because NetWare Directory Services must search for the server on the network to verify its existence.

For example, if you create a Server object for a NetWare 3 server whose physical name on the network is SURFBOY, you must name the Server object SURFBOY.

Because of these restrictions, you can never rename a NetWare Server object, even if you have the Supervisor object right to it.