You can create Organizational Unit (OU) container objects to subdivide the NDS tree. Organizational Units are created with NWAdmin under an Organization, Country, or another Organizational Unit object.
Organizational Units can contain other Organizational Units and leaf objects such as User and Application objects.
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.
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 instance, you could 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 should create an Organizational Unit for each site under the Organization object. That way, if you have (or will have) enough servers to partition the Directory, you can do so logically along site boundaries.
The following properties (and many more) are available for the Organizational Unit object. Only the Name property is required. For a complete list of properties, select an Organizational Unit object in NWAdmin, then choose Object > Details. To display a description for each page of properties, click Help.
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.
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.
The Applications property lists all applications you have set up for this context. Users view and work with applications via the Novell Application Launcher (NAL) Window and NAL Explorer desktop software.
Applications are associated with an Organizational Unit from the Application object's Associations property page. When an application is associated with an Organization object, User objects in that Organization are (by default) presented the application through the NAL Window.
Use the Launcher Configuration properties to specify how users view and work with the Novell Application Launcher (NAL) Window and NAL Explorer desktop software. Use this property to allow users to inherit applications through multiple levels of the NDS tree.