{TemplateInclude "Default" "HelpNav"}

Parent Objects

Parent objects enable administrators to collectively manage agent services and user settings for specific sets of users. This functionality enables the administrator to sub-divide a single messaging system into configuration sub-units. For example, by creating separate Parent objects for each domain, administrators can manage every domain as if it were a separate messaging system.

In addition to being a collective management tool, the Parent object offers other significant advantages. The configuration options in the Parent object allow administrators to selectively grant access to messaging services. This means that although an agent is running on the messaging server, not everyone can access the agent’s services. Instead, the administrator can enable or disable different agent services for each Parent object. Parent objects can also be used to distribute administrative tasks. Selected users can be given rights to create, delete, modify, or import user accounts in specific Internet domains.

For more information, see Creating Parent Objects and Configuring Parent Objects.

 

Parent Container

The Parent container is created in Internet Services during installation. This container is the centralized location for Parent objects. NetMail® Agents reference the Parent container when looking up user configuration information.

IMPORTANT: Every Parent object must be represented in the Parent container in order for the NetMail Agents to find it. If a Parent object is created elsewhere in the tree, it must be represented by an Alias object in the Parent container.

If the Parent container is deleted, it can only be recreated by re-running NIMSEXT.

NOTE: For information on running the NIMSEXT utility, see the Novell® NetMail Administration Guide at http://www.novell.com/documentation.

 

A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For more information, see Legal Notices.