Review the following sections to plan your installation:
If you have more than one eDirectory tree in your network, decide which tree you want to use for managing Policy and Distribution Services objects. These objects will be created in the tree you select for installation.
Because Tiered Electronic Distribution (TED), a component of ZfS, uses IP addresses and DNS names for identifying servers, the TED objects can be easily associated with their servers, whether they are NetWare servers whose NCPTM Server objects reside in the installation tree or in other network trees, or on Windows servers contain ed in domains. This lets you manage the TED objects for your entire network from one eDirectory tree.
IMPORTANT: Two points concerning tree-to-tree Distributions:
1. For the File Distribution, if you are maintaining trustee rights in a tree, you cannot automatically maintain those rights for tree-to-tree Distributions. For servers where their NCP Server objects are in different trees than the corresponding Policy and Distribution Services objects, and users are different between the trees, the user's trustee rights cannot be automatically maintained. You will need to assign the trustee rights manually. For more information on the File Distribution, see "Selecting Your Distributions" under "Planning Your Distribution System" in "Configuring Policy and Distribution Services" in "Policy and Distribution Services" in the Administration guide.
2. For the Desktop Application Distribution, you can only distribute between trees using the External Subscriber object, and the Subscriber and Server NCP objects of the receiving server must reside on the same tree. For example, Distributor A on Tree A can use an External Subscriber object on Tree A to send a Desktop Application Distribution to Server B on Tree B, but only if Server B's Subscriber object and NCP object both reside on Tree B.
The installation program requires an eDirectory context for placing Subscriber objects. If you add a Windows server from a Microsoft* domain that does not have an eDirectory object, in another installation page you will be asked to browse and select an eDirectory context where the Subscriber object can be created and associated with the Windows server.
However, if you only intend for this Windows server to be used as an External Subscriber, do not install the Subscriber object and software at that time. Instead, you can later install the Subscriber software locally on that machine (which will not have a Subscriber object), then create the External Subscriber object for it in ConsoleOne. For more information, see "Out-of-Tree Distributions" in "Configuring Policy and Distribution Services" in "Policy and Distribution Services" in the Administration guide.
Although you can install Policy and Distribution Services objects to only one tree at a time, you can install Policy and Distribution Services software to all of the servers in your network in one run of the installation program. Therefore, you can set up the roles for each of your ZfS servers during installation.
You can also install Policy and Distribution Services software to any server when running the installation program, regardless of the server's eDirectory tree or Microsoft domain, because you can browse both trees and domains during installation.
Policy and Distribution Services software can even be installed to servers that are not in a tree or domain by inserting the Program CD on that server and installing directly.
There are two TED objects that define the role of a server. The role you select determines what software is installed on the server. The objects are:
The Distributor server does much of the distribution work. It compiles software and policy packages and distributes them to other servers.
To initially install Policy and Distribution Services, choose one server that exceeds the minimum server requirements to be the Distributor server. This can be either a NetWare or Windows server (see Policy and Distribution Services Minimum Requirements for NetWare Servers or Policy and Distribution Services Minimum Requirements for Windows Servers).
You are not required to always use this server as a Distributor, because it will also have the Subscriber software installed on it. Therefore, you can simply select any server that exceeds the minimum server requirements for first-time installation purposes.
IMPORTANT: Because Distributions belong exclusively to their Distributors, you will not be able to transfer the Distributions to another Distributor should you later change your mind about using your selected server as the Distributor. The Distributions would need to be re-created from scratch for another Distributor. For more information, see "Deleting a Distributor Object and How Its Distributions Are Affected" under "TED Issues" in "Understanding Tiered Electronic Distribution" in "Tiered Electronic Distribution" in the Administration guide.
The Subscriber servers receive distributions of policies and software. You can manage your network's servers by installing the Subscriber software on every server.
Make a note of all servers that you want to manage with Policy and Distribution Services. You will need to install the Subscriber software on each of these servers.
For large or complex networks, we recommend that you install Subscriber software incrementally to groups of servers. For example, you might want to roll out Policy and Distribution Services in phases.
To install Subscriber software to your servers incrementally, determine installation groupings for your servers. You will install to the first group of servers using the instructions in this Installation guide.
You can install to the other groups of servers later using the instructions in "Configuring Policy and Distribution Services" in the Administration guide.
If you want to encrypt Distributions for Windows, Linux, or Solaris servers, you will need to install NICI 2.4 on those servers. However, you should do this after initially installing ZfS. Installing NICI 2.4 is documented as part of the configuration process described in the Administration guide.
For more information, see "Installing NICI 2.4" under "Setting Up Additional Distribution Security" in "Configuring Your Distribution System" in "Configuring Policy and Distribution Services" in "Policy and Distribution Services" in the Administration guide.
Plan to accept all defaults when running the installation program, except as noted in information contained within an installation step in Installing Policy and Distribution Services.