The following list describes in alphabetical order each leaf object you can create and when to use it:
Although an object appears both where it was actually created and where an alias referring to it was created, only one copy of the object really exists.
If you delete or rename an alias, the object it is pointing to is not affected.
Use this object to allow easier access to an object that is in another context.
For example, you can use an Alias to represent a resource, such as a special printer, that most users in the tree need to access.
Also, when you move or rename a container object in a Directory tree, you have the option of creating an alias in place of the moved or renamed object. If you select this option, NetWare Administrator automatically creates the alias for you and assigns it the same name as the original object.
Creating an alias in place of a moved or renamed container object allows users to continue logging in to the network and see the container objects (and the objects it contains) in its original Directory location.
Use this object to store information about a nonserver computer, such as its network address, its serial number, or the person to whom the computer is assigned.
This object has no effect on the operation of the network; it only stores information about the computer.
For example, if you have a directory that contains DOS 5.0, you will probably map a search drive to that directory in the login scripts you create. Later, if you upgrade to DOS 6.0 and rename the directory, you would have to change the mapping in every login script where that search mapping appears.
With a Directory Map object, you change only the information in that one object.
Use this object to avoid making changes to many login scripts when the location of applications changes.
For more information on Directory Map objects, see ``Loading operating systems and applications onto the network''.
Use this object to simplify sending mail.
For example, you could create a Distribution List object called Recreation Committee. Anyone wanting to send a message to all the members of the Recreation Committee can simply address the message to Recreation Committee, rather to each member.
If your messaging environment contains SMTP hosts, SNADS nodes, or X.400 MTAs, you might choose to add users and lists at these servers to your NetWare database as External Entities.
Adding these objects to the database as external entities adds them to the address books of your messaging applications.
Create a Group object when you have many User objects that need the same trustee assignments. Rather than making many trustee assignments, you make just one trustee assignment to a Group object for all users who belong to the group.
Create a Message Routing Group when you have two or more messaging servers that need to communicate with each other.
Stores information about the server in the NetWare Server object's properties, such as the server's address, the physical location of the server, and what services it provides.
The NetWare Server object affects the network in that it is referred to by several other objects.
Use the NetWare Server object to associate the physical server on the network with the Directory tree. Without this object, users cannot access filesystems that are on that server's volumes.
If you have a non-NetWare 4.1 server, you must create this object to be able to access non-NetWare 4.1 volumes. When you create a NetWare Server object for a non-NetWare 4.1 server, the non-NetWare 4.1 server must be running.
Create an Organizational Role object so that you can assign rights to a particular position rather than the person who occupies that position. The occupant may change frequently, but the responsibilities of that position do not.
You can assign any user to be an occupant of the Organizational Role object because every occupant receives the same rights that you granted to the Organizational Role object.
You must create a Print Queue object for every print queue on the network.
This object cannot be created with NETADMIN.
See Administering NetWare print services for more information.
You must create a Print Server object for every print server on the network.
This object cannot be created with NETADMIN.
See Administering NetWare print services for more information.
You must create a Printer object for every printer on the network.
This object cannot be created with NETADMIN.
See Administering NetWare print services for more information.
Create a Profile object for a set of users who need to share common login script commands but who are not located in the same container in the Directory tree, or who are a subset of users in the same container.
In the User object properties, you can set login restrictions, intruder detection limits, password and password restrictions, security equivalences, and so on.
You must create a User object for every user who needs to log in to the network. When you create a User object, you can create a home directory for that user. When you create User objects, you can also choose to apply a user template to the user that provides default property values.
For users who have NetWare 4.1 workstations, you can create the User objects anywhere in the Directory tree, but the users must know their context in order to log in. You should create User objects in the container where the users will typically log in.
For users who have non-NetWare 4.1 workstations, you must create the User objects in the container at which the bindery services context is set for the server that they need to log in to. (Bindery services is set by default for every NetWare 4.1 server that is installed.) Non-NetWare 4.1 users do not need to know their context because they log in to the server rather than to the Directory tree.
In the Volume object's properties, you can enter identification information, such as the host server, volume location, and so on. You can also set restrictions for use of the volume, such as space limits for users.
You should create a Volume object for every physical volume on the network. During installation of on a server, Volume objects are created for every physical volume on that server.
When you create a volume, you are prompted for the server name and the volume name on the server. That information is placed in the Volume object's properties.
You can use the Volume object to display the directories and files on that volume.