2.2 Platform-Dependent Information

The following sections provide the information you need to know that is specific to a component and its installation method on the supported platforms:

2.2.1 Information for Installing Policy-Enabled Server Management on NetWare and Windows Servers

You need to know the following information before running the installation program:

Table 2-2 Information Needed before Running the Installation Program

Information Needed

Explanation

eDirectory containers for the ZENworks objects

We recommend that you create containers to enhance your ability to manage the ZENworks objects. You learn about the recommended containers in Section 3.3, eDirectory Container Requirements, and instructions for creating the containers are provided in Section 3.3.2, Creating the ZENworks Containers.

Distributor servers

You need at least one server to have the Distributor software installed on it. See Section 1.1.1, Policy and Distribution Services Server Roles for information to help you determine where you want to install Distributors.

2.2.2 Information for Installing Policy and Distribution Services on Linux and Solaris Servers

You need to know the following information before running the installation script:

Table 2-3 Information Needed before Running the Installation Script

Information Needed

Explanation

Server DNS name

The installation script must be able to authenticate to a server that holds a replica of the eDirectory tree where you want Distributor and/or Subscriber objects created. This could be a Linux, Solaris, NetWare, or Windows server. You must know either the fully qualified DNS hostname or the IP address of the server in order for the installation script to identify it in your network. For example:

Server1.Servers.novell.com

Username

To enable the installation script to authenticate to the eDirectory server, you must know the fully distinguished username and password for a user with Admin-equivalent rights to the tree. For example:

admin.novell

Object contexts

You need to determine the eDirectory context where you want the installation script to create Distributor and Subscriber objects. You can only use an existing container. Therefore, you might want to create a container before running the installation script. For example:

Distributors.ZENworks.Novell
Linux.Subscribers.ZENworks.Novell
Solaris.Subscribers.ZENworks.Novell

If you have already installed Policy and Distribution Services on NetWare or Windows servers, the eDirectory tree might already have the necessary containers for the Distributor and Subscriber objects.

Distributor object name

If the Linux or Solaris server where you are installing Policy and Distribution Services will function as a Distributor, you must choose a unique name for the Distributor object. The name you choose should retain the Linux or Solaris server’s identity. For example:

Distributor-Linux-01

Subscriber object name

If the Linux or Solaris server where you are installing Policy and Distribution Services will function as a Subscriber, you must choose a unique name for the Subscriber object. The name you choose should retain the Linux or Solaris server’s identity. For example:

Subscriber-Solaris-02

Database object’s DN

If you want a Distributor that you are installing to write to a database, you need to know the database object’s DN, such as:

database.novell

When providing object names during installation, you need to include the object’s context with the object name. For example:

Distributor-Linux-01.Distributors.ZENworks.Novell

IMPORTANT:Do not use double-byte or extended characters in the object names or object contexts.