Preparing to Install

1. Make sure you have fulfilled all of the necessary requirements for your target Distributor and Subscriber servers.

2. If Java has not been unloaded on the target NetWare servers, unload JAVA.NLM.

   For example, at each NetWare server's console prompt, enter:

   java -exit

3. Select the workstation you will use to install the ZfS Distributors and Subscribers.

4. If you have not already done so, log in to the eDirectory tree where you will be creating the ZfS objects (worksheet item 1).

   This should be the same tree where you extended the schema for ZfS 3.0.2.

   You will automatically be authenticated to all of the NetWare target servers in this tree during installation. You will be able to select those servers, as well as servers in other trees or domains, for installing the Policy and Distribution Services software. However, this is the tree where all of the ZfS objects will be installed for each of the selected servers.

Starting the Installation Program

1. On the installation workstation, insert the ZENworks for Servers Program CD or the ZENworks 6 Server Management Program CD.

   The startup screen is displayed. If the startup screen is not automatically displayed after inserting the CD, you can start it by running WINSETUP.EXE at the root of the CD.

   IMPORTANT:  Installation from a CD in a remote server is not supported unless there is a drive mapped on the workstation to that remote server. For example, if you place the CD in a Windows NT/2000 server CD drive, then run the installation from a workstation, you must have a drive mapped on the workstation to the CD drive of that NT/2000 server.

2. Click the Policy-Enabled Server Management option.

   This begins the installation program.

3. If you agree with the Software License Agreement, click Accept > Next.

4. On the Installation Type page, click New Installation > click Next.

5. On the Components to Install page, click the Tiered Electronic Distribution, Server Policies, and Server Software Packages check box > click Next.

6. On the Installation Options page, make sure both the Create and Install check boxes are checked.

7. On the eDirectory Tree for Creating Objects page, select the tree (worksheet item 1).

   This is the tree where you initially created ZfS objects.

Selecting and Configuring the Distributor and Subscriber Servers

1. On the Server Selection page, click Add Server > browse for the Distributor (worksheet item 2) and Subscriber (worksheet item 3) servers > click OK.

2. For each Distributor server, click the check box in the Distributor column.

   Uncheck the box under the Subscriber/Policies column only if you are sure you do not want the Subscriber and Server Policies software installed on that Distributor server.

3. For each Subscriber server, click the check box in the Subscriber/Policies column.

4. If you plan to install a database on a Distributor server (worksheet item 4), for one of the servers, click the check box in the Database column > click Next.

   You can install only one database per run of the installation program. Therefore, click the Database column for just one of the Distributors.

5. On the Installation Paths and Options page, for each Distributor server, edit the installation path if you do not want to use the default (worksheet item 5).

   If you want all Distributor servers to have the same installation path, select all of the servers, then edit the path.

6. For each Subscriber server, edit the installation path if you do not want to use the default (worksheet item 6).

   If you want all Subscriber servers to have the same installation path, select all of the servers, then edit the path.

7. To launch Policy and Distribution Services components on server startup, click the check box.

8. On the Distributor Object Properties page, edit the properties as necessary (worksheet item 7) > click Next.

9. On the Subscriber Object Properties page, edit the properties as necessary (worksheet item 8) > click Next.

10. For the Distributor server where you selected to install the database, do the following:

    • Edit the database file's path if you do not want to use the default (worksheet item 9).

      Because the database file can become very large, we recommend that you change the default NetWare volume from SYS: to another volume on that server.

    • Edit the Database object's name, if desired (worksheet item 10).
    • Change the Database object's container, if desired (worksheet item 11).

11. Click Next.

    The Summary page is displayed.

Completing the Installation

1. To save the current installation configuration for future use in installing Distributors, on the Summary page click the Save the Following check box > enter a path and filename for the template file.

   If you attempt to quit the installation program without clicking Finish, you will be prompted to save your current installation configuration to an installation template file.

   You can reuse this template to speed up filling in installation pages in subsequent installations of Distributors or Subscribers.

2. Click Finish to begin the installation process.

3. After the installation program has finished, review the installation log file to determine whether any components failed to install.

   The log file is located at:

   C:\TEMP\_RESNumber.TXT

   where Number is increased incrementally each time a new installation log is created.

4. If necessary, rerun the installation program.

   Select only the components that failed to install.

5. Rerun the installation program once for each additional database that needs to be installed (worksheet item 4).

   On the Server Selection page add only one of the Distributors where you planned to have a database installed, but have not installed it yet. Then, click only the Database column for that database's Distributor server and fill in the applicable information on the remaining installation pages.

Setting Up Inter-Server Communications Security

If you will be distributing to servers outside your secured network (worksheet item 13), see Security for Inter-Server Communication Across Non-Secured Connections for detailed instructions on setting up security for inter-server communications.

Installing NICI 2.4

If you need Distribution encryption support for certain NetWare, Windows, Linux, and Solaris Subscriber servers, a newer version of NICI (2.4) provides this support. A NICI update is contained on the ZENworks Companion CDs. The NICI24CPK.EXE file on the CD is a self-extracting file that contains the NICI24.CPK software package file.

This software package updates NICI to the 2.4 version. Because NetWare 5.1/6 servers automatically have this version of NICI installed, you only need to install the NICI24.CPK software package to the Windows, Linux, and Solaris Subscriber servers where you are using the encryption feature of TED.

IMPORTANT:  All servers that will be sending or receiving encrypted Distributions must be running the same version of NICI. Otherwise, encrypted Distributions to any of those servers will fail.

When you install NICI24.CPK, it will not check to see if NICI is already installed. It will simply install NICI to all Subscribers subscribed to the Channel that you select for the software package used to distribute NICI.

The NICI24.CPK file is the same software package file that was provided with ZfS 3 SP1. If you previously updated your servers to NICI 2.4 using SP1, you can skip this section.

1. On a Windows workstation, insert the ZENworks for Servers Companion CD or the ZENworks 6 Companion 1 CD.

2. Copy the NICI24CPK.EXE file from a Companion CD (CD_drive:\NICI or CD_drive:\ZENWORKSFORSERVERS\NICI) to a directory on the Windows workstation.

3. From the directory where you saved the NICI24CPK.EXE file, run this .EXE file to extract the NICI24.CPK and README_NICI24CPK.TXT files.

4. Follow the installation instructions in the Readme file under "Installing NICI 2.4 with ZfS 3.0.2."

   In Step 6 of the Readme, select the servers that you planned to update to NICI 2.4 (worksheet item 14).

Starting the Agents

1. On a NetWare server where you installed the software for the Distributor (worksheet item 2) or Subscriber (worksheet item 3), at the server's console prompt, enter:

   sys:\zenworks\pds\smanager\zfs.ncf

   If you used a different volume, or added other path information before the ZENWORKS directory, replace the SYS: portion with the alternate path information.

   After you have started ZfS in this manner, and after the server has rebooted once, the full path will no longer be needed for start the software---you will only need to enter zfs thereafter. By entering the path the first time you run ZFS.NCF, or by rebooting the server after installing ZfS, you enable the server to learn that path.

   IMPORTANT:  If you edited the TED.NCF file for a Distributor that already has ZfS running (as instructed in Configuring Distributors in a Mixed eDirectory Environment), bring the ZfS Agent down and restart it on that server.

   TED.NCF and ZWS.NCF are started automatically by the ZFS command. The database is automatically started by the installation program.

2. Repeat Step 1 for each NetWare server in your network where you have installed the Distributor or Subscriber software.

3. On a Windows server where you installed the software for the Distributor (worksheet item 2) or Subscriber (worksheet item 3), do the following:

   1. Open the Control Panel.

   2. Do the applicable tasks:

      On Windows NT, double-click Services.

      or

      On Windows 2000, double-click Admin Tools > double-click Services.

   3. Start the Novell ZfS Policies service.

      This will also start the Novell ZfS Distribution service, and the Novell ZfS Web Server service. The Novell Sybase* Database service is automatically started by the installation program.

4. Repeat Step 3 for each Windows server in your network where you have installed the Distributor or Subscriber software.

5. At the server console or in an Xterm window on a Linux or Solaris server where you installed the software for the Distributor (worksheet item 2) or Subscriber (worksheet item 3), enter:

   /etc/init.d/zfs start

6. Repeat Step 5 for each Linux or Solaris server in your network where you have installed the Distributor or Subscriber software.

Verifying That the Policy and Distribution Services Agents Are Loaded

To verify that the Policy and Distribution Services agents are running on the target servers:

• Verifying on NetWare Servers
• Verifying on Windows Servers
• Verifying on Linux or Solaris Servers

Configuring the Distributor Routing Hierarchies

1. In ConsoleOne, right-click a Distributor object (worksheet item 2) > click Properties.

2. Click the Routing tab > do the following:

   1. Click Add > browse for your first tier Subscriber servers (worksheet item 15) > click Select > click OK.

      This sets up your first tier of Subscriber servers. These will receive Distributions directly from the Distributor.

   2. Click one of the Subscriber servers in the first tier of the routing tree > click Add > browse for your next tier of Subscriber servers to go under that fist tier Subscriber (worksheet item 15) > click Select > click OK.

      This sets up a second tier of Subscriber servers for the one Subscriber that you selected. These second-tier Subscribers will receive Distributions indirectly from the Distributor via the Subscriber server above them in the hierarchy.

   3. Repeat Step 2.b for each of the first-tier Subscribers until you have selected all of the second-tier Subscribers for this part of the hierarchy.

   4. Click one of the Subscriber servers in the second tier of the routing tree > click Add > browse for your next tier of Subscriber servers to go under that Subscriber (worksheet item 15) > click Select > click OK.

   5. Repeat Step 2.d for each of the second tier Subscribers until you have selected all of the third-tier Subscribers for this part of the hierarchy.

   6. Repeat this process, tier by tier, until you have completed your planned routing hierarchy for the current Distributor.

3. Repeat Step 1 through Step 2 for your other Distributors.

4. When you have finished building the routing hierarchy, click OK.

Configuring Parent Subscribers

All Subscribers should not receive their Distributions directly from a Distributor. The Distributor's routing hierarchy provides a way to minimize the Distributor's workload in sending Distributions.

For Subscriber servers to receive their Distributions using the routing hierarchy, you need to identify a parent Subscriber that is in the routing hierarchy for each end-node Subscriber (the Subscriber to receive the Distribution). This will allow an end-node Subscriber to receive its Distributions through the routing hierarchy, rather than directly from a Distributor.

A Subscriber that is in the Distributor's routing hierarchy does not need to have a parent Subscriber in order to receive a Distribution from that Distributor. Distributors check their routing hierarchies first, then check for parent Subscribers second.

To associate Subscribers with parent Subscribers:

1. In ConsoleOne, select a group of Subscriber objects for servers that you planned to have serviced by a particular parent Subscriber (worksheet item 16) > right-click the selected group > click Properties of Multiple Objects > in the Parent Subscriber field, browse for the parent Subscriber object > click OK > OK.

   Because you can do multiple editing of eDirectory objects, you can select all of the Subscribers that will be serviced by one parent Subscriber and edit the Parent Subscriber field once for all of them.

2. Repeat this process for all end-node Subscribers.

Configuring Subscriber Groups

To create and populate a Subscriber Group:

1. In ConsoleOne, select the container to hold the Subscriber Group object > click File > New > Object > TED Subscriber Group.

2. In the New TED Subscriber Group dialog box, enter a name for the Subscribe Group (worksheet item 17) > click Define Additional Properties > click OK.

3. In the General Settings tab, enter a description.

4. To populate the group with Subscribers, click the Members tab > do the following:

   1. Click Add > browse for and select the Subscriber objects (worksheet item 18) > click OK.

   2. To remove any Subscribers from the list, select the Subscribers > click Delete.

   3. To view the properties of any Subscriber, select the Subscriber > click Details.

5. Click OK when you have finished configuring the Subscriber Group object.

Creating and Configuring the Distribution

1. In ConsoleOne, locate the container where the TED objects were installed.

2. Right-click the container > click New > Object > select TED Distribution.

3. Enter a Distribution name (worksheet item 19).

   Name the Distribution so you can identify what it contains.

4. Browse to the Distributor object that will own this Distribution (worksheet item 19) > select it.

   Each Distribution is associated with a single Distributor. That Distributor is responsible for building and sending the Distribution.

5. Click the Define Additional Properties check box.

6. Click OK to create the object.

   The properties for the Distribution are now displayed.

7. Click the Type tab > in the Select Type drop-down box, click a Distribution type (worksheet item 19).

8. Configure the Distribution.

   For information on configuring the different Distribution types, see Distributions.

   Use the up and down arrow buttons to change the distribution order.

9. Click the Schedule tab.

   The Distribution's schedule determines how often the Distributor will attempt to build a new version of the Distribution. A new version is built only if there have been changes since the last version was built.

10. Select Run Immediate from the drop-down list.

    This will cause the Distributor to build the Distribution as soon as it re-reads eDirectory for the Distribution information.

11. Click OK at the bottom of the Distribution Properties dialog box to save all changes.

12. If you have not previously resolved certificates, click Yes when prompted to copy security certificates.

    For information on resolving certificates, see Resolving Certificates.

    The Distributor needs to have been run at least once so that its certificates can be minted (created).

    A Distributor needs to resolve its certificates only once per Subscriber.

    The Subscriber software does not need to be running on the server for security certificates to be resolved. The server only needs to be up.

    ConsoleOne will send security certificates to each Subscriber server that subscribes to the Channel that was selected in the Channel Tab. Each Subscriber must have a security certificate from the Distributor before it can receive Distributions from that Distributor.

    It can take several minutes to copy a security certificate to each Subscriber.

    IMPORTANT:  Certificate copying only needs to be done once for each Distributor/Subscriber relationship.

13. If you receive an error when the Distributor tries to copy to an NT Subscriber, enter the following for the path:

    \\IP_Address\zen$\PDS\TED

    where IP_Address is the IP address of that NT Subscriber.

14. If you receive an error when the Distributor tries to copy to a Linux or Solaris Subscriber, or you cannot browse for the Server to select it for resolving certificates, you must map a drive to the server (such as through using Samba) and then repeat resolving certificates.

15. Repeat these steps for any other Distributions you want to create at this time (worksheet item 19).

Creating and Configuring the Channel

Channel objects are used to associate Subscribers with Distributions. When Subscribers subscribe to a Channel, they receive all of the Distributions associated with that Channel. Each Channel has a schedule that determines when the Distributions associated with it are to be sent to the Subscribers.

1. In ConsoleOne, locate the container where the TED objects reside (worksheet item 20).

   This container should already exist. It is where your Distributor and Subscriber objects were created.

   We suggest for ease of management that you use the same OU for all Channels.

2. Right-click the TED container > click New > Channel > OK.

3. Enter a name for the Channel (worksheet item 21) > click OK.

   You could name your Channels according to the Distributions you intend for them. For example, Channel - ZfS 3 Support Pack 2.

4. Right-click the new Channel object > click Properties.

5. Click the Distributions tab > click Add > browse for and select the Distributions for the Channel (worksheet item 22) > click OK.

   This associates the Distributions with the Channel. The Subscribers that are subscribed to this Channel will receive the current Distributions.

6. To set the Channel's Send schedule, click the Schedule tab > select Interval > specify the interval as every 5 minutes > click OK.

7. Repeat Step 1 through Step 5 for each Channel you have planned (worksheet item 21).

Setting Subscribers' Extract Schedules

Before a Subscriber can use a Distribution that is sent to it via TED, it must extract the Distribution. Therefore, the Subscriber's extraction schedule must be set before sending the Distributions.

1. In ConsoleOne, right-click the Subscriber object (worksheet item 23) for a server where you want to set the extraction schedule > > click Properties.

2. Click the Schedule tab > click the arrow for the drop-down box > click Run Immediately > click OK.

   This will cause the selected Subscriber to extract its Distributions as soon as they are received.

3. Repeat Step 1 and Step 2 as necessary until all Subscriber schedules have been set.

Subscribing to the Channels

Subscribers must subscribe to a Channel in order to receive the Distributions associated with that Channel. In the following steps, you will associate all of your Subscribers to the Channels created previously.

1. In ConsoleOne, right-click a Channel object (worksheet item 21) > click Properties.

2. Click the Subscribers tab > click Add > browse for each of the Subscriber or Subscriber Group (worksheet item 24) objects to be subscribed to this Channel > click Select > click OK.

3. Click the General tab > make sure the Active check box is checked.

4. Click OK to close the Channel object's properties and save the changes.

5. Click No when prompted to copy security certificates.

6. Repeat Step 1 through Step 5 for each Channel (worksheet item 21).

Scheduling and Refreshing the Distributor

1. In ConsoleOne, right-click the Distributor object (worksheet item 2).

2. On the Distribution object's Build Schedule tab, click Send Distribution Immediately After Building.

   The Distribution will be sent as soon as it is built, regardless of the Channel's Send schedule.

3. Click Refresh Distributor.

   This causes the Distributor to re-read eDirectory and obtain all of the changes that were made in eDirectory.

Building the Distribution will begin immediately (according to the Build schedule you set previously). The Distribution will be sent within five minutes (according to the Send schedule you set previously).

As soon as the Subscribers receive the entire Distribution, they will extract the contents to the Subscriber's working directory that you specified in the Subscriber object's properties.

Verifying That the Distribution Process Was Successful

There are a number of ways you can verify that your Distribution process has worked:

• Reporting: Run a report on the Distribution to see its status. For information on TED reporting, see Reporting.

• Log Files: Depending on the logging levels you are using, you can review the log files for distribution statuses. Log files (.LOG) can be found in the Distributors' and Subscribers' working directories.

• Distribution Files: Compare the Distribution file on the Distributor's file system (under ZENWORKS\PDS\TED\DIST) with the Subscriber's file system (under ZENWORKS\PDS\TED\SUB\individual_Distribution's_path) to see if it was received. The Distribution file uses the same name on both servers.