Setting up and managing NDS objects

Renaming leaf and container objects

You may want to rename objects to make the names more descriptive or to reflect your changing environment. For example, you may want to rename a printer from ``LASER IN BLDG D'' to ``LASER IN BLDG A'', or an Organizational Unit from ``SALES'' to ``ACCOUNTS''.

When you rename an object, NetWare Directory Services changes all references to the renamed object.

Renaming a leaf object changes only the object's common name, which is the name that is displayed in the Directory tree. It does not change the object's context. However, renaming a container object changes the object's common name as well as its context.

When renaming a container object, you should seriously consider creating an Alias object that points to the container object you are renaming. Then users can continue logging in to the network and can see the container object's original name.


NOTE: If you rename a container object and do not create an alias, users who are unaware of the object's new name will not easily find the object in the Directory tree, since they will look for its original name.

Also, users may not be able to log in if the name context in their configuration file (NET.CFG file) references the renamed container.


To automatically update users' NET.CFG files with a new name context after you rename a container object, you can place a command in the renamed container's login script that will run the NCUPATE utility.


© 1999 The Santa Cruz Operation, Inc. All rights reserved.
UnixWare 7 Release 7.1.1 - 5 November 1999