Creating Container Objects

You can create container objects using either NetWare Administrator or NETADMIN. Both of these methods are described in this section.

Considerations for naming container objects and suggestions for creating searchable objects are also described here.

Types of Container Objects

The kinds of container objects you can create are Country, Organization, and Organizational Unit. The top object, called Root, is created by default, and is placed at the top of the Directory tree when NetWare Services is installed.

Container objects form the top levels of the Directory tree. Use them to manage and organize the top level of the Directory tree.

For more information about planning the top levels of your Directory tree, see chapter 2, "Understanding NetWare Directory Services" in Introduction to NetWare Directory Services.

Figure 2-1 shows the hierarchy of container objects and leaf objects in NetWare Directory Services. (The icons represent the leaf objects as they appear in NetWare Administrator.)

Figure 2-1 Hierarchy of Objects

You can create leaf objects only under the Organization and Organizational Unit container objects.

Table 2-3 describes each container object you can create and when to use it.

Table 2-3 Container Objects You Can Create

Container object	Description	When to use it
Country	Designates the countries where your network resides and organizes other objects within the country. You must always include the name type of the object in complete names when you include the Country container object in your Directory tree. Even when you refer to objects located in the same container object, you must designate the name type (CN, OU, or O) of the object.	This object is optional. If you choose to create a Country object, you can use it to represent the country where your organization headquarters resides or, if you have a multinational network, to represent each country that is a part of your network. You can create a Country container object only under the Root object.
Organization	Allows you to organize other objects in the Directory, to set defaults in a login script, and to create a user template for User objects you create in this container.	You can use an Organization object to designate a corporation, or location, etc. The Organization object is mandatory. The Directory tree must include at least one of these containers. You can create an Organization object only under the Root or Country object.
Organizational Unit	Allows you to organize leaf objects in the Directory tree, to set defaults in a login script, and to create a user template for User objects you create in this container.	You can use an Organizational Unit object to designate a division, a business unit, or a project team. You can create multiple levels of Organizational Units. You can create Organizational Units in Organization objects and other Organizational Unit objects.

Naming Container Objects

Try to keep container object names short and simple. This makes it easier for users to change context and to remember their own context.

The following rules apply to most objects. For specific rules about naming leaf objects, see "Naming Leaf 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, except for Country objects, which are limited to two characters.
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.1, you should avoid using special characters. (For a list of these 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 spaces and underscores, but they are both considered spaces. Therefore, "Manager_Profile" and "Manager Profile" are considered to be identical names.




	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). For more information, see "Unicode" in Concepts.

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.1, the names of the objects must follow bindery naming rules or else the non-NetWare 4.1 client will 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.

You cannot use the following characters in an object name that must be accessed from a client running a version of NetWare earlier than NetWare 4.1:

/ slash

\ backslash

: colon

, comma

* asterisk

? question mark

Creating Searchable Container Objects

When you create a container object, you can enter various types of information about that object into its properties, such as location and telephone. If you enter data into the containers' properties in a consistent format, it is easier to search the Directory database for a particular type of information.

Many container object properties are optional; you are not required to enter information in order to create the object. However, information in objects' properties can help you track and manage container objects.

After you create container objects, you can use NetWare Administrator, NETADMIN, or NLIST to search for and list these objects. You can also search for their various properties.

Creating Container Objects Using Directory Services Installation

When you install a NetWare Services server on a host, you are required to type a context (the pathname from the container object to the Root) in which the NetWare Server object is placed.

If you create a new context, several events happen by default:

An Organization or Organizational Unit container object is created, depending on the context you create.
Bindery services is set for that container object, so that the server you installed in the container object is running bindery services.
A read/write replica of the Directory partition where the container object resides is stored on the server that you just installed.

For more information on how to create container objects using Directory Services Install (dsinstall), see the NetWare 4.1/9000 Installation and Administration Guide..

Creating Container Objects Using NetWare Administrator or NETADMIN

The first time the network supervisor logs in, the User object ADMIN must be used. This is the only object after installation that has rights to create and manage objects.

Before you can log in, you must first install a single workstation and run either NetWare Administrator or NETADMIN to start creating objects on your network.

You can install and customize other workstations later, using the respective client manual.

Creating Container Objects Using NetWare Administrator

Prerequisites

A 386 or later workstation and NetWare Administrator
The Create object right to the container that will contain the new container object

Procedure

From the Windows Program Manager, click on the "NetWare Administrator" icon.
Select the object that will contain the new container object.
For information on moving around in the browser and choosing objects, press <F1>.
Choose "Create" from the "Object" menu.
From the "New Object" dialog box, select the new container object class that you want.
If the container object class you want to create does not appear under "New Object," you cannot create that object in the selected container. Choose "Cancel" to return to the browser; then select a different container type.
Choose "OK."
The "Create Object" dialog box appears.
Type a name for the object in the box provided.
(Optional) Select "Define Additional Properties."
Select this option if you want to use the same default information in the new container as was present in the parent container. This default information is used whenever you create a new user.
The user default information for each container is stored in a User object named USER_TEMPLATE.
(Optional) Select "Define User Defaults."
Select this option if you want to use the same default information in the new container as was present in the parent container. This default information is used whenever you create a new user.
The user default information for each container is stored in a User object named USER_TEMPLATE.
Choose "Create."
(Optional) Choose "Yes" if you want user template properties to be inherited from the parent container, or "No" if you want to define a new user template.
(Optional) Add information to the object dialog pages.
If you chose "Define Additional Properties," add the information now. Press <F1> for help.
Choose "OK" to save the properties you have just entered in the dialog pages.

Additional Information

For more information about	Refer to
Objects	"Object" in Concepts
Rights	"Rights" in Concepts
Using NetWare Administrator	"NetWare Administrator" in Utilities Reference
Using object dialog pages in NetWare Administrator	"NetWare Administrator" in Utilities Reference

Creating Container Objects Using NETADMIN