The definition of each type of NDS object is called an object class. For instance, User and Organization are object classes. Each class of object has certain properties. A User object, for example, has Login Name, Password, Last Name, and many other properties.

List of Objects

Table 14.

Table 15.

Container Object Classes

Tree

The Tree container, formerly [Root], is created when you first install NDS on a server in your network. As the top-most container, it usually holds Organization objects, Country objects, or Alias objects.

What Tree Represents

Tree represents the top of your tree.

Usage

Important Properties

The Tree object has a Name property, which is the tree name you supplied when installing the first server. The tree name is shown in the hierarchy of ConsoleOne.

Organization

An Organization container object is created when you first install NDS on a server in your network. As the top-most container under Tree, it usually holds Organizational Unit objects and leaf objects.

The User object named Admin is created by default in your first Organization container.

What an Organization Object Represents

Normally the Organization object represents your company, although you can create additional Organization objects under Tree. This is typically done for networks with distinct geographical districts or for companies with separate NDS trees that have merged.

Usage

The way you use Organization objects in your tree depends on the size and structure of your network. If the network is small, you should keep all leaf objects under one Organization object.

For larger networks, you can create Organizational Unit objects under the Organization to make resources easier to locate and manage. For example, you can create Organizational Units for each department or division in your company.

For networks with multiple sites, you should create an Organizational Unit for each site under the Organization object. That way, if you have (or plan to have) enough servers to partition the directory, you can do so logically along site boundaries.

For easy sharing of company-wide resources, such as printers, volumes, or applications, create corresponding Printer, Volume, or Application objects under the Organization.

Important Properties

The most useful properties for Organization are listed below. Only the Name property is required. For a complete list of properties, select an Organization object in ConsoleOne. To display a description for each page of properties, click Help.

• Name

  Typically, the Name property is the same as your company's name. Of course, you can shorten it for simplicity. For instance, if the name of your company is Your Shoe Company, you might use YourCo.

  The Organization name becomes part of the context for all objects created under it.

• Login Script

  The Login Script property contains commands that are executed by any User objects directly under the Organization. These commands are run when a user logs in.

You can create Organizational Unit (OU) container objects to subdivide the tree. Organizational Units are created with ConsoleOne under an Organization, Country, or another Organizational Unit.

Organizational Units can contain other Organizational Units and leaf objects such as User and Application objects.

What an Organizational Unit Object Represents

Normally the Organizational Unit object represents a department, which holds a set of objects that commonly need access to each other. A typical example is a set of Users, along with the Printers, Volumes, and Applications that those Users need.

At the highest level of Organizational Unit objects, each Organizational Unit can represent each site (separated by WAN links) in the network.

Usage

The way you use Organizational Unit objects in your tree depends on the size and structure of your network. If the network is small, you probably don't need any Organizational Units.

For larger networks, you can create Organizational Unit objects under the Organization to make resources easier to locate and manage. For example, you can create Organizational Units for each department or division in your company. Remember that administration is easiest when you keep User objects together in the Organizational Unit with the resources they use most frequently.

For networks with multiple sites, you can create an Organizational Unit for each site under the Organization object. That way, if you have (or plan to have) enough servers to partition the directory, you can do so logically along site boundaries.

Important Properties

The most useful properties for the Organizational Unit are listed below. Only the Name property is required. For a complete list of properties, select an Organizational Unit object in ConsoleOne. To display a description for each page of properties, click Help.

• Name

  Typically, the Name property is the same as the department name. Of course, you can shorten it for simplicity. For instance, if the name of your department is Accounts Payable, you can shorten it to AP.

  The Organizational Unit name becomes part of the context for all objects created under it.

• Login Script

  The Login Script property contains commands that are executed by any User objects directly under the Organizational Unit. These commands are run when a user logs in.

You can create Country objects directly under the Tree object using ConsoleOne. Country objects are optional and only required for connection to certain X.500 global directories.

What a Country Object Represents

The Country object represents the political identity of its branch of the tree.

Usage

Most administrators do not create a Country object, even if the network spans countries, since the Country object only adds an unnecessary level to the tree. You can create one or many Country objects under the Tree object, depending on the multinational nature of your network. Country objects can only contain Organization objects.

If you do not create a Country object and find that you need one later, you can always modify the tree to add one.

Important Properties

The Country object has a two-letter Name property. Country objects are named with a standard two-letter code such as US, UK, or DE.

Leaf Object Classes

Server

A Server object is created in the tree automatically whenever you install NDS on a server. The object class can be any server running NDS.

You can also create a Server object to represent a NetWare 2 or NetWare 3 bindery server.

What a Server Object Represents

The Server object represents a server running NDS, or a bindery-based (NetWare 2 or NetWare 3) server.

Usage

The Server object serves as a reference point for replication operations. A Server object that represents a bindery-based server allows you to manage the server's volumes with ConsoleOne.

Important Properties

The Server object has a Network Address property, among others. For a complete list of properties, select a Server object in ConsoleOne. To display a description for each page of properties, click Help.

• Network Address

  The network address property displays the protocol and address number for the server. This is useful for troubleshooting at the packet level.

When you create a physical volume on a server, a Volume object is automatically created in the tree. By default, the name of the Volume object is the server's name with an underscore and the physical volume's name appended (for example, YOSERVER_SYS).

Volume objects are supported only on NetWare. UNIX file system partitions cannot be managed using Volume objects.

What a Volume Object Represents

A Volume object represents a physical volume on a server, whether it is a writable disk, a CD, or other storage medium. The Volume object in NDS does not contain information about the files and directories on that volume, though you can access that information through ConsoleOne. File and directory information is retained in the file system itself.

Usage

In ConsoleOne, click the Volume icon to manage files and directories on that volume. ConsoleOne provides information about the volume's free disk space, directory entry space, and compression statistics.

You can also create Volume objects in the tree for NetWare 2 and NetWare 3 volumes.

Important Properties

In addition to the required Name and Host Volume properties, there are other important Volume properties.

• Name

  This is the name of the Volume object in the tree. By default, this name is derived from the name of the physical volume, though you can change the object name.

• Host Server

  This is the server on which the volume resides.

• Version

  The Version property gives the NetWare or NDS version of the server hosting the volume.

• Host Volume

  This is the physical volume name. Since the actual Volume object name does not need to reflect the physical volume name, this property is necessary to associate the Volume object with the physical volume.

A User object is required for logging in. When you install the first server into a tree, a User object named Admin is created. Log in as Admin the first time.

You can use the following methods to create or import User objects:

A User object represents a person who uses the network.

Usage

You should create User objects for all users who need to use the network. Although you can manage User objects individually, you can save time by:

• Using Template objects to set default properties for most User objects. The Template applies automatically to new Users you create (not to already-existing ones).
• Creating Group objects to manage sets of Users.
• Assigning rights using the container objects as trustees when you want that assignment to apply to all User objects in the container.
• Selecting multiple User objects by Shift-clicking or Ctrl-clicking. When you do, you can change property values for all selected User objects.

User objects have over 80 properties. For a complete list of properties, select a User object in ConsoleOne. To display a description for each page of properties, click Help.

The Login Name and Last Name properties are required. These and some of the most useful properties are listed below.

• Account Expiration Date: This property lets you limit the life of a user account. After the expiration date, the account is locked so the user cannot log in.

• Account Disabled: This property has a system-generated value that indicates a lock on the account so the user cannot log in. The lock might occur if the account has expired or because the user has given too many incorrect passwords in succession.

• Force Periodic Password Changes: This property lets you enhance security by requiring the user to change passwords after a specified interval.

• Group Memberships: This property lists all the Group objects that include the User as a member.

• Home Directory: The Home Directory property refers to a NetWare volume and file system path for the user's own files. Most administrators like to create such a directory so that a user's working files can be kept on the network.

  The directory referred to in this property can be created automatically when you create the User object.

• Last Login: This is a system-generated property that lists the date and time that the user last logged in.

• Last Name: The Last Name property, although required, is not used directly by NDS. Applications that take advantage of the NDS name base can use this property, along with other identification properties such as Given Name, Title, Location, and Fax Number.

• Limit Concurrent Connections: This property lets you set the maximum number of sessions a user can have on the network at any given time.

• Login Name: This is the name shown in ConsoleOne by the User icon. It is also the name supplied by the user when logging in.

  NDS does not require that login names be unique throughout the network, only in each container. However, you might want to keep login names unique across the company to simplify administration.

  Typically, login names are a combination of first and last names, such as STEVET or STHOMAS for Steve Thomas.

• Login Script: The Login Script property lets you create specific login commands for a User object. When a user logs in, the container login script runs first. Then a profile login script runs if the User object has been added to the membership list of a Profile object. Finally, the user login script runs (if one exists).

  You should put most of the login commands in container login scripts to save administrative time. The user login script can be edited to manage unique exceptions to common needs.

• Login Time Restrictions: This property lets you set times and days when the user can log in.

• Network Addresses: This property contains system-generated values that list all the IPX^TM and/or IP addresses from which the user is logged in. These values are useful for troubleshooting network problems at the packet level.

• Require a Password: This property lets you control whether the user must use a password. Other related properties let you set common password constraints such as password length.

• Rights to Files and Directories: This property lists all rights assignments made for this user to the NetWare file system. Using ConsoleOne, you can also check a user's effective rights to files and directories, which include those inherited from other objects.

You can create Group objects to help you manage sets of User objects.

What a Group Object Represents

A Group object represents a set of User objects.

Usage

While container objects let you manage all User objects in that container, Group objects are for subsets within a container or in multiple containers.

Group objects have two main purposes:

• They allow you to grant rights to a number of User objects at once.
• They allow you to specify login script commands using the IF MEMBER OF syntax.

The most useful properties of the Group object are Members and Rights to Files and Directories. For a complete list of properties, select a Group object in ConsoleOne. To display a description for each page of properties, click Help.

• Members

  This property lists all User objects in the group. Rights assignments made to the Group object apply to all members of that group.

• Rights to Files and Directories

  This property lists all trustee assignments made for this Group to the NetWare file system.

You can create an Alias object that points to another object in the tree. Alias objects give users a local name for an object that lies outside their container.

When you rename a container, you have the option of creating an Alias in the former container's place that points to the new name. Workstations and login script commands that reference objects in the container can still access the objects without having the container name updated.

What an Alias Object Represents

An Alias object represents another object, which can be a container, User object, or any other object in the tree. An Alias object does not carry trustee rights of its own. Any trustee authority you grant to the Alias object applies to the object it represents. The Alias can be a target of a trustee assignment, however.

Usage

Create an Alias object to make name resolution easier. Since object naming is simplest for objects in the current context, you should create Alias objects there that point to any resources outside the current context.

Figure 7

Figure 8

The Alias object points to the original ColorQ object, so setting up printing for the users involves a local object.

Important Properties

Alias objects have an Aliased Object property, which associates the Alias object with the original object.

Directory Map

The Directory Map object is a pointer to a path in the server file system. It allows you to make simpler references to directories.

If your network has no NetWare volumes, you cannot create Directory Map objects.

What a Directory Map Object Represents

A Directory Map object represents a directory on a NetWare volume. (An Alias object, on the other hand, represents an object.)

Usage

Create a Directory Map object to make drive mapping simpler, particularly in login scripts. Using a Directory Map object allows you to reduce complex file system paths to a single name.

Figure 9

A command mapping drives to the Shared directory on volume SYS: would look like the following:

MAP N:=SYS.North.:Shared

If you created the Shared Directory Map object, the map command would be much simpler:

MAP N:=Shared

Important Properties

The Directory Map object has Name, Volume, and Path properties.

• Name

  The Name property identifies the object in the directory (for example, Shared) and is used in MAP commands.

• Volume

  The Volume property contains the name of the Volume object that the Directory Map object references, such as Sys.North.YourCo.

• Path

  The Path property specifies the directory as a path from the root of the volume, such as PUBLIC\WINNT\NLS\ENGLISH.

Profile objects help you manage login scripts.

What a Profile Object Represents

A Profile object represents a login script that runs after the container login script and before the user login script.

Usage

Create a Profile object if you want login script commands to run for only selected users. The User objects can exist in the same container or be in different containers. Once you have created the Profile object, you add the commands to its Login Script property. Then make the User objects trustees of the Profile object and add the Profile object to their Profile Membership property.

Important Properties

The Profile object has two important properties: Login Script and Rights to Files and Directories.

• Login Script

  The Login Script property contains the commands you want to run for users of the Profile.

• Rights to Files and Directories

  If you have INCLUDE statements in the login script, you need to give the Profile object rights to the files included with the Rights to Files and Directories property.