Supervising the Network

2-69

Setting Up and Managing NetWare Directory Services Objects

Renaming Leaf and Container Objects

You may want to rename objects to make the names more descriptive or to

reﬂect 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.

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 ﬁnd 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

conﬁguration ﬁle (NET.CFG ﬁle) references the renamed container.

To automatically update users’ NET.CFG ﬁles 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.

Renaming Objects Using NetWare Administrator

Prerequisites

• A 386 or later workstation and NetWare Administrator

• The Rename object right to the object that you want to rename

Procedure

1 From the Windows Program Manager, click on the “NetWare Administrator”