Novell ZENworks for Servers 3 Support Pack 2

August 15, 2003

Novell® ZENworks® for Servers (ZfS) 3 Support Pack 2 (SP2) contains updates for all components contained in the ZfS 3 product. SP2 includes all fixes from SP1.

If the Support Pack 2 file is downloaded, it must be extracted at the root of the drive because it contains directory paths that could exceed the DOS limits.

(New) ZENworks for Servers 3 SP2 supports NetWare 6.5 when you apply the latest ZENworks update. See the ZENworks for Servers 3.0.2 Update for NetWare 6.5 Readme for information about obtaining the update and other information about using ZENworks for Servers with NetWare 6.5. The update files can be obtained from TID 10083888 on the Novell Support Web site.

Installing this Support Pack updates ZfS 3 or ZfS 3 SP1 to the same version of ZfS that is on the ZENworks for Servers Program CD or the ZENworks 6 Server Management Program CD. You can use either this Support Pack or the upgrade option on the Program CD for updating ZfS 3 or ZfS 3 SP1. Therefore, all ZfS 3.0.2 documentation on the Novell Documentation Web site applies to your ZfS software after you update with SP2.

The purpose of this Support Pack is to provide a bundle of ZfS 3 fixes that have all been tested together. These files have undergone component testing, core OS testing, and integration testing with other Novell products.

This Support Pack includes all fixes from previous Support Packs; therefore, you do not need to install earlier Support Packs before installing this Support Pack. Do not install individual files from the Support Pack, except as outlined in this Readme.

ZfS 3 SP2 is also available in Novell Consolidated Support Pack 9 (CSP9). For information on the latest Consolidated Support Pack issues, see TID 10077724 at the Support Connection Web site.


Readme Updates

Items in this Readme that are marked (New) have been added to this version of the Readme after the Program CD was created. The Readme was updated in the following sections on the dates indicated:

April 15, 2003 = 9.2.3; 9.2.4
June 27, 2003 = 9.2.5; 9.3.5


Table of Contents

1.0 Overview
1.1 Documentation
1.2 The Purpose of Support Pack 2
1.3 Support Pack Contents
2.0 Management and Monitoring Services
2.1 Management Site Services (ZFS3SP2SITESVR.CPK)
2.2 Management Agent (ZFS3SP2MGMTAGNT.CPK)
2.3 LANalyzer Agent (ZFS3SP2LANZAGNT.CPK)
3.0 Policy and Distribution Services
3.1 NICI Update (NICI24.CPK)
3.2 Policy and Distribution Services (ZFS3SP2POLYDIST.CPK)
4.0 Server Inventory
4.1 Inventory Server and Server Inventory ConsoleOne (ZFS3SP2INVREM.CPK)
4.2 Inventory Agent (ZFS3SP2INVSPAGN.CPK)
5.0 Remote Management
5.1 Remote Management ConsoleOne (ZFS3SP2INVREM.CPK)
5.2 Remote Management (ZFS3SP2REMMGMT.CPK)
6.0 Installing the Support Pack
6.1 Installation Issues and Guidelines
6.2 Automatic Installation
6.3 Manual Installation
6.4 Installing Snap-Ins and Plug-Ins
6.5 Installation Log Files
6.6 Variables Used by NCF and BAT Files for Installing Manually
7.0 New Features
7.1 Policy and Distribution Services New Features
7.2 Server Inventory New Features
7.3 Remote Management New Features
8.0 Resolved Issues
8.1 Management and Monitoring Services Resolved Issues
8.2 Policy and Distribution Services Resolved Issues
8.3 Inventory Agent Resolved Issues
8.4 Remote Management Resolved Issues
9.0 Known Issues
9.1 Management and Monitoring Services Known Issues
9.2 Policy and Distribution Services Known Issues (New entries)
9.3 Inventory Agent Known Issues
10.0 Documentation Conventions
11.0 Legal Information


1.0 Overview

The following sections provide an overview of ZfS 3 SP2.


1.1 Documentation

This Readme is the only documentation provided for the SP2 download. Installation and usage instructions for the SP2 udpates are contained in the Readme sections.

The documentation for ZfS 3.0.2 at the Novell documentation Web site has been updated to reflect the changes made with installation of this support pack.

This Readme is also included on the documentation Web site, and can be updated at any time.


1.2 The Purpose of Support Pack 2

SP2 provides updates and bug fixes for ZfS 3 and ZfS 3 SP1. It includes all the fixes that were released with ZfS 3 SP1 plus additional fixes for SP2.

The support pack is contained in two self-extracting files, ZFS3SP2.EXE and NICI24CPK.EXE, that are downloaded separately. The ZFS3SP2.EXE file contains this Readme and the .CPK, .ZIP, and .EXE files you need for updating ZfS 3 to SP2. The NICI24CPK.EXE file contains the NICI24.CPK file and Readme needed if you are using the encryption feature of Tiered Electronic Distribution (TED).


1.2.1 Updates and Bug Fixes

ZfS 3 SP2 provides updates or bug fixes for:


1.2.2 Where to Find Information

You can individually update the ZfS components that you have installed in your system. For more information on these components, see Sections 4 through 11.

For installation instructions, see 6.0 Installing the Support Pack.


1.3 Support Pack Contents

The following sections describe the content of the support pack.


1.3.1 Extracted File Organization

The following file and directory structure is placed in the temporary directory where you extract the ZFS3SP2.EXE file:

TEMP\
   |__README_ZFS3SP2.TXT (this Readme file in ASCII format)
   |__README_ZFS3SP2.HTML (this Readme file in HTML format)
   |__INVREMMGMT\
       |__InvRem_StandAlonePacPro.zip
       |__ZFS3SP2C1Snap_Inv.zip
       |__ZFS3SP2C1Snap_RemMgmt.zip
       |__ZFS3SP2InvRem.cpk
       |__ZFS3SP2InvSPAgn.cpk
       |__ZFS3SP2RemMgmt.cpk
   |__MGMTMON\
       |__MgmtMon_StandAlonePacPro.zip
       |__ZFS3SP2C1Snap_MgmtMon.zip
       |__ZFS3SP2LanzAgnt.cpk
       |__ZFS3SP2MgmtAgnt.cpk
       |__ZFS3SP2SiteSvr.cpk
   |__POLYDIST\
       |__ExtSch32.exe
       |__nici24.cpk (from a separate download)
       |__PolyDist_StandAlonePacPro.zip
       |__ZFS3SP2.sch
       |__zfs3SP2polydist.cpk
       |__ZFS3SP2PolyDistPlugins.zip
       |__ZFS3SP2PolyDistSnapins.zip


1.3.2 Server Software Package Files

Each of the seven Server Software Packages (files with the .CPK extension) included in this support pack contains software updates for a group of ZfS 3 components as defined below.

Installation of a software package requires that the ZfS 3 component that it is updating be present on the server. For example, if you are updating the Inventory Agent using ZFS3SP2INVSPAGN.CPK, the software package will fail if it does not find the ZfS 3 Inventory Agent on the server.

The software packages contained in the support pack update the following ZfS components:


1.3.3 Other Files

SP2 contains the following files in addition to the software packages:


2.0 Management and Monitoring Services

The following software packages install the various components of Management and Monitoring Services:


2.1 Management Site Services (ZFS3SP2SITESVR.CPK)

The following sections list the information you need to install the Management Site Services update (ZFS3SP2SITESVR.CPK) from this support pack.


2.1.1 Management Site Services Prerequisites

Fulfill the following prerequisites before installing ZFS3SP2SITESVR.CPK.

Stopping Various Services

To prepare your system for installing the software packages:

  1. Close ConsoleOne on the client workstation if it is running; if ConsoleOne and the ZfS console components are installed on the ZfS server, close all ConsoleOne sessions invoked from this server.

  2. Shut down the Management Site Server by entering the following at the server prompt:

    UNMW

  3. Shut down the Java* Naming Server program by entering the following at the server prompt:

    mmsnaming -exit

    The above shutdown processes can take up to a minute depending on your server configuration. See "Stopping and Starting Management and Monitoring Services" in the ZfS 3.0.2 Administration guide for more information.

Modifying Variables

The Standalone Package Processor uses variables for installation options that can be unique to each server on which the update is being installed. The variables are set to the default value in the .BAT or .NCF file. The default must be modified if the value for the variable on the server where you are installing differs from the default value.

See 6.6 Variables Used by NCF and BAT Files for Installing Manually for a complete list of variables used by the various software packages. See "Using Variables" under "Policy and Distribution Services" in the ZfS 3.0.2 Administration guide for details on defining variables in Subscriber objects.

To prepare for using variables during software package installation:

  1. You must modify the ZFS3SP2SITESVR.NCF file and change the MMSPATH variable so that it lists the correct directory. By default, MMSPATH is set to DATA:\ZENWORKS\MMS.

    IMPORTANT:  You must enclose the values for the directory location within double quotes if the directory name contains white space. For example: 

       MMSPATH "SYS:\ZFS SERV\ZENWORKS\MMS"


2.1.2 Installing the Management Site Services Software Package

To install ZFS3SP2SITESVR.CPK:

  1. Choose whether to install ZFSSP2SITESVR.CPK automatically or manually.

    For automatic installation, follow the instructions in 6.2 Automatic Installation. You do not need to continue with the remaining steps.

    For manual installation, follow the instructions in 6.3 Manual Installation, then continue with Step 2.

  2. Restart the Management Site Server component.

  3. Restart ConsoleOne to access the updated Management console.


2.2 Management Agent (ZFS3SP2MGMTAGNT.CPK)

The following sections list the information you need to install the Management Agent update (ZFS3SP2MGMTAGNT.CPK) from this support pack.


2.2.1 Management Agent Prerequisites

Ensure that you install ZFS3SP2POLYDIST.CPK before installing ZFS3SP2MGMTAGNT.CPK.


2.2.2 Installing the Management Agent Software Package

  1. Choose whether to install ZFS3SP2MGMTAGNT.CPK automatically or manually.

    For automatic installation, follow the instructions in 6.2 Automatic Installation. You do not need to continue with Step 2.

    For manual installation, follow the instructions in 6.3 Manual Installation, then continue with Step 2.

  2. If you have installed the Management Agent in a directory other than the default, do the following:

    • For a NetWare server, edit the ZFS3SP2MGMTAGNT.NCF file to change the NMAPATH variable so that the file lists the correct directory.
    • For a Windows server, edit the ZFS3SP2MGMTAGNT.BAT file to change the ZFS3AGENTPATH variable so that the file lists the correct directory.


2.3 LANalyzer Agent (ZFS3SP2LANZAGNT.CPK)

The following sections list the information you need to install the LANalyzer Agent update (ZFS3SP2LANZAGNT.CPK) from this support pack.


2.3.1 LANalyzer Agent Prerequisites

Ensure that you install ZFS3SP2POLYDIST.CPK before installing ZFS3SP2LANZAGNT.CPK.


2.3.2 Installing the LANalyzer Agent Software Package

  1. Choose whether to install ZFS3SP2LANZAGNT.CPK automatically or manually.

    For automatic installation, follow the instructions in 6.2 Automatic Installation. You do not need to continue with Step 2.

    For manual installation, follow the instructions in 6.3 Manual Installation, then continue with Step 2.

  2. If you have installed the LANalyzer Agent in a directory other than the default, do the following:

    • For a NetWare server, edit the ZFS3SP2LANZAGNT.NCF file to change the LANZPATH variable so that the file lists the correct directory.
    • For a Windows server, edit the ZFS3SP2LANZAGNT.NCF file to change the NTLANZPATH variable so that the file lists the correct directory.


3.0 Policy and Distribution Services

The following software packages install the various components of Policy and Distribution Services:


3.1 NICI Update (NICI24.CPK)

The NICI24.CPK file is compressed in a NICI24CPK.EXE file that you can download.

This software package updates NICI to a newer version (2.4), which supports encryption for NetWare, Windows, Solaris, and Linux servers. Because NetWare servers automatically have NICI installed, you only need to install NICI24.CPK to Windows, Linux, and Solaris servers if you are using the encryption feature of TED.

Previous to NICI 2.4, NICI encryption was not available for Linux and Solaris servers. To provide encryption for Linux and Solaris servers, continue with this section. However, the NICI24.CPK file is the same software package file that was provided with ZfS 3 SP1. Therefore, if you previously updated all of your servers to NICI 2.4 using SP1, you can skip this section.

IMPORTANT:  All servers that will be sending or receiving encrypted Distributions must be running the same version of NICI.

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.

To install NICI24.CPK:

  1. Choose to install NICI24.CPK automatically.

    For automatic installation, follow the instructions in 6.2 Automatic Installation. This .CPK file cannot be installed manually.

  2. After installation, review the ZFSINIT.LOG file to ensure that the installation was successful.


3.2 Policy and Distribution Services (ZFS3SP2POLYDIST.CPK)

This software package updates the Policy and Distribution Services components of ZfS 3. The following sections list the information you need to install the Policy and Distribution Services update (ZFS3SP2POLYDIST.CPK) from this support pack.


3.2.1 Cluster Installation Issues

If you are installing ZFS3SP2POLYDIST.CPK to servers in a clustered environment, you must install the support pack .CPK file individually for each node in the cluster so that any support pack files that need to be written to a SYS: volume can be updated.

For example, the following information is known:

Then, you have two ways to update the cluster's nodes: through iManager or by renaming the Distribution.

Updating Through iManager

To update all cluster nodes:

  1. Update the active node's server by sending a Distribution containing the .CPK file to it.

    For support pack installation steps, see 3.2.5 Installing the Policy and Distribution Services Software Package.

    This will update any support pack files that need to be copied to a SYS: volume. It will also update the TED and policies software, such as the .NCF files that are installed on a cluster's volume.

    Because filenames and dates are checked during software package installation, running this .CPK file repeatedly will not reinstall the files on the cluster's shared volume. Only the node currently running the Subscriber software will be updated.

  2. Bring currently active node's server down to create a cluster failover condition.

    This will cause the next node in the predefined sequence to start the Subscriber software and take over for the cluster.

  3. In iManager, access the ZfS/Remote Web Console as the Subscriber > click the Distributions tab > click the Received Distributions tab > select the Distribution that contains the .CPK file > click OK > click Extract.

  4. Repeat Step 2 through Step 3 until all nodes have been updated.

  5. Restart each of the servers in the cluster that were downed.

    The primary node's server should take over again.

Updating by Renaming the Distribution

Alternatively, to update all cluster nodes:

  1. Update the active node's server by sending a Distribution containing the .CPK file to it.

    For support pack installation steps, see 3.2.5 Installing the Policy and Distribution Services Software Package.

    This will update any support pack files that need to be copied to a SYS: volume. It will also update the TED and policies software, such as the .NCF files that are installed on a cluster's volume.

    Because filenames and dates are checked during software package installation, running this .CPK file repeatedly will not reinstall the files on the cluster's shared volume. Only the node currently running the Subscriber software will be updated.

  2. Bring the currently active node's server down to create a cluster failover condition.

    This will cause the next node in the predefined sequence to start the Subscriber software and take over for the cluster.

  3. Rename the Distribution that you sent in Step 1.

    If you do not rename the Distribution when it is resent, the Subscriber software on the cluster volume being used by the current node will think that it has already been received and won't receive and extract it again.

  4. Send the Distribution.

    This updates the current node with the support pack.

  5. Repeat Step 2 through Step 4 until all nodes within the cluster have been updated.

  6. Restart each of the servers in the cluster that were downed.

    The primary node's server should take over again.


3.2.2 Policy and Distribution Services Prerequisites

Fulfill the following prerequisites before installing the Policy and Distribution Services CPK:


3.2.3 Extending the Schema

Before installing the ZFS3SP2POLYDIST.CPK, you must first extend the schema on the Novell eDirectoryTM trees where you previously extended the schema for ZfS 3. However, if you extended the schema when installing SP1, you can skip this section.

This schema extension removes the limitation on how many files and folders you can select for a File type of Distribution. It adds the new zentedXMLAgentData2 attribute to the schema.

The EXTSCH32.EXE file is placed in the temporary directory when you extract the ZFS3SP2.EXE file.

To extend the schema:

  1. Authenticate to the tree as Admin.

  2. Open a DOS window.

  3. Run the EXTSCH32.EXE file using the following syntax:

    EXTSCH32.EXE Tree_Name ZFS3SP2.SCH

3.2.4 Updating a Server for Large Distribution Support

To have support for Distributions larger than 4 GB on NetWare servers, your servers must have one of the following versions of NetWare installed:


3.2.5 Installing the Policy and Distribution Services Software Package

To install the ZFS3SP2POLYDIST.CPK file, it is easier to use the automatic installation option (see 6.2 Automatic Installation), because you already are running the TED and Distributor components required for this installation method.

To install the Policy and Distribution Services support pack:

  1. Choose to install ZFS3SP2POLYDIST.CPK automatically or manually.

    For automatic installation, follow the instructions in 6.2 Automatic Installation, then continue with the Step 2.

    IMPORTANT:   If ZfS 3 Policy and Distribution Services has been installed to a server running ZfD 4.0.1 Workstation Inventory, Policy and Distribution Services will not work until you apply ZfS 3 SP2. You cannot use the automatic installation method to install the ZFS3SP2POLYDIST.CPK file on the servers. You must use the manual installation method described in 6.3 Manual Installation of this Readme.

    For manual installation, follow the instructions in 6.3 Manual Installation, then continue with the Step 2.

  2. You must upgrade your Distributors first, then upgrade your Subscribers.

    You can send Distributions from a ZfS 3 SP2 Distributor to ZfS 3 or ZfS 3 SP1 Subscribers. However, ZfS 3 SP2 Subscribers cannot receive Distributions from a ZfS 3 (non-SP2) Distributor. The reason is that during extraction, this software package unloads all Java processes. This interrupts the Distributor’s sending of the .CPK file to its Subscribers, as well as any Subscriber's forwarding of it on to subordinate Subscribers (when acting as a parent Subscriber).

    If the Distributor is not upgraded first, you will receive an ArrayIndexOutOfBoundsException on the ZfS 3 SP2 Subscribers receiving Distributions from a ZfS 3 or ZfS 3 SP1 Distributor.

    Each Distributor has a Subscriber running on the same server. To upgrade the Distributor first, incorporate the following sequence of events into your use of the automatic installation steps:

    1. Create a Distribution for the ZFS3SP2POLYDIST.CPK file.

    2. Add the Distributor’s Subscriber by itself in a new Channel.

    3. Associate the Distribution with this Channel.

    4. Send the Distribution.

      This upgrades both the Distributor and Subscriber software on the Distributor server.

    5. Add all other Subscribers to the same Channel.

    6. Resend the Distribution.

      The Distribution will not try to upgrade the Distributor again because its Subscriber will know that it’s already received it.

    This process will ensure that the Distributor server is upgraded first.

    If you have multiple Distributors, repeat this process for each Distributor. However, you will not need to include any Subscribers that are shared by the Distributors if those Subscribers have been already upgraded.

  3. Restart Management and Monitoring Services if you unloaded it to install ZFS3SP2POLYDIST.CPK.

  4. If Server Inventory was running on the server, you might need to restart it.


3.2.6 Restarting Java Services After the Policy and Distribution Services Installation

If Server Inventory and Remote Management are installed to the same server as Policy and Distribution Services, after installing the Policy and Distribution services .CPK file, you must manually restart Server Inventory and Remote Management services.


4.0 Server Inventory

The following software packages install the various components of Server Inventory:


4.1 Inventory Server and Server Inventory ConsoleOne (ZFS3SP2INVREM.CPK)

The following sections list the information you need to install the Inventory Server and Server Inventory ConsoleOne update (ZFS3SP2INVREM.CPK) from this support pack.

IMPORTANT:  ZFS3SP2INVREM.CPK updates the Inventory Server and ConsoleOne for both Server Inventory and Remote Management. Therefore, if you have already installed ZFS3SP2INVREM.CPK for Remote Management (see 5.1 Remote Management ConsoleOne (ZFS3SP2INVREM.CPK)), you do not need to reinstall it for Server Inventory, and you can skip to 4.2 Inventory Agent (ZFS3SP2INVSPAGN.CPK).


4.1.1 Prerequisites

Do the following for these components before updating them with their respective software packages.

Updating ConsoleOne for Server Inventory and Remote Management

To prepare for updating ConsoleOne with the ZfS snap-ins:

  1. Close all ConsoleOne sessions.

    If ConsoleOne and ZfS console components are installed on the ZfS server, close all ConsoleOne sessions invoked from this server.

  2. Close all Remote Control sessions.

Updating Inventory Server and ConsoleOne for Server Inventory

The Standalone Package Processor uses variables for installation options that can be unique to each server on which the update is being installed. The variables are set to the default value in the .BAT or .NCF file. The default must be modified if the value for the variable on the server where you are installing differs from the default value.

See 6.6 Variables Used by NCF and BAT Files for Installing Manually for a complete list of variables used by the various software packages. See "Using Variables" under "Policy and Distribution Services" in the ZfS 3.0.2 Administration guide for details on defining variables in Subscriber objects.

To prepare for using variables during software package installation:

  1. If you are automatically installing the software package, create and initialize the following package processor variables:

    • On NetWare servers: CONSOLE_INSTALL_PATH_NW package processor variable.

    • On Windows NT/2000 servers: CPK_WORKING_DRIVE_NT and CONSOLE_INSTALL_PATH_NT package processor variables.

  2. If you are manually installing the software package, do the following:

    • On NetWare servers, in the INVRMSP2.NCF file, edit the default value of the CONSOLE_INSTALL_PATH_NW package processor variable: 
      java -ns -noclassgc -classpath $zfspaths com.novell.application.servman.services.software 
      package.PackageProcessor SYS:\TEMP\ZFS3SP2\ZFS3SP2INVREM.CPK 5 CONSOLE_INSTALL_PATH_NW SYS:\PUBLIC\MGMT\CONSOLEONE\1.2
    • On Windows NT/2000 servers, in the INVRMSP2.BAT file, edit the default values of the CPK_WORKING_DRIVE_NT and CONSOLE_INSTALL_PATH_NT package processor variables: 
      java -cp %zfspaths% com.novell.application.servman.services.software 
      package.PackageProcessor C:\TEMP\ZFS3SP2\ZFS3SP2INVREM.CPK 5 CONSOLE_INSTALL_PATH_NT C:\NOVELL\CONSOLEONE\1.2 CPK_WORKING_DRIVE_NT C:


4.1.2 Installing the Inventory Server Software Package

You must install ZFS3SP2INVREM.CPK on the ZfS console and all ZfS servers. You must also upgrade ZfS servers and ConsoleOne snap-ins.

  1. Choose whether to install ZFS3SP2INVREM.CPK automatically or manually.

    For automatic installation, follow the instructions in 6.2 Automatic Installation, then continue with Step 2.

    For manual installation, follow the instructions in 6.3 Manual Installation, then continue with Step 2.

  2. Restart ConsoleOne.

IMPORTANT:  After installing the Policy and Distribution Services .CPK, you must manually restart the Server Inventory services.


4.2 Inventory Agent (ZFS3SP2INVSPAGN.CPK)

The following sections list the information you need to install the Inventory Agent update (ZFS3SP2INVSPAGN.CPK) from this support pack. Also included in this section is a list of software issues resolved by this component.


4.2.1 Installing the Inventory Agent Software Package

  1. Choose to install ZFS3SP2INVSPAGN.CPK automatically.

    For automatic installation, follow the instructions in 6.2 Automatic Installation.

    ZFS3SP2INVSPAGN.CPK cannot be installed manually.


5.0 Remote Management

The following software packages install the various components of Remote Management:


5.1 Remote Management ConsoleOne (ZFS3SP2INVREM.CPK)

The following sections list the information you need to install the Remote Management ConsoleOne update (ZFS3SP2INVREM.CPK) from this support pack.

IMPORTANT:  ZFS3SP2INVREM.CPK updates the Inventory Server and ConsoleOne for both Server Inventory and Remote Management. Therefore, if you have already installed ZFS3SP2INVREM.CPK for Server Inventory (see 4.1 Inventory Server and Server Inventory ConsoleOne (ZFS3SP2INVREM.CPK)), you do not need to reinstall it for Remote Management, and you can skip to 5.2 Remote Management (ZFS3SP2REMMGMT.CPK).


5.1.1 Prerequisites

Do the following for these components before updating them with their respective software packages.

Updating ConsoleOne for Server Inventory and Remote Management

To prepare for updating ConsoleOne with the ZfS snap-ins:

  1. Close all ConsoleOne sessions.

    If ConsoleOne and ZfS console components are installed on the ZfS server, close all ConsoleOne sessions invoked from this server.

  2. Close all Remote Control sessions.

Updating Inventory ConsoleOne for Remote Management

The Standalone Package Processor uses variables for installation options that can be unique to each server on which the update is being installed. The variables are set to the default value in the .BAT or .NCF file. The default must be modified if the value for the variable on the server where you are installing differs from the default value.

See 6.6 Variables Used by NCF and BAT Files for Installing Manually for a complete list of variables used by the various software packages. See "Using Variables" under "Policy and Distribution Services" in the ZfS 3.0.2 Administration guide for details on defining variables in Subscriber objects.

To prepare for using variables during software package installation:

  1. If you are automatically installing the software package, create and initialize the following package processor variables:

    • On NetWare servers: CONSOLE_INSTALL_PATH_NW package processor variable.

    • On Windows NT/2000 servers: CPK_WORKING_DRIVE_NT and CONSOLE_INSTALL_PATH_NT package processor variables.

  2. If you are manually installing the software package, do the following:

    • On NetWare servers, in the INVRMSP2.NCF file, edit the default value of the CONSOLE_INSTALL_PATH_NW package processor variable: 
      java -ns -noclassgc -classpath $zfspaths com.novell.application.servman.services.software 
      package.PackageProcessor SYS:\TEMP\ZFS3SP2\ZFS3SP2INVREM.CPK 5 CONSOLE_INSTALL_PATH_NW SYS:\PUBLIC\MGMT\CONSOLEONE\1.2
    • On Windows NT/2000 servers, in the INVRMSP2.BAT file, edit the default values of the CPK_WORKING_DRIVE_NT and CONSOLE_INSTALL_PATH_NT package processor variables: 
      java -cp %zfspaths% com.novell.application.servman.services.software 
      package.PackageProcessor C:\TEMP\ZFS3SP2\ZFS3SP2INVREM.CPK 5 CONSOLE_INSTALL_PATH_NT C:\NOVELL\CONSOLEONE\1.2 CPK_WORKING_DRIVE_NT C:


5.1.2 Installing the Remote Management ConsoleOne Software Package

You must install ZFS3SP2INVREM.CPK on the ZfS console and all ZfS servers. You must also upgrade ZfS servers and ConsoleOne snap-ins.

  1. Choose whether to install ZFS3SP2INVREM.CPK automatically or manually.

    For automatic installation, follow the instructions in 6.2 Automatic Installation, then continue with Step 2.

    For manual installation, follow the instructions in 6.3 Manual Installation, then continue with Step 2.

  2. Restart ConsoleOne.


5.2 Remote Management (ZFS3SP2REMMGMT.CPK)

The following sections list the information you need to install the Remote Management update (ZFS3SP2REMMGMT.CPK) from this support pack. Also included in this section is a list of new features and software issues resolved by this component.


5.2.1 Remote Management Prerequisites

The Standalone Package Processor uses variables for installation options that can be unique to each server on which the update is being installed. The variables are set to the default value in the .BAT or .NCF file. The default must be modified if the value for the variable on the server where you are installing differs from the default value.

See 6.6 Variables Used by NCF and BAT Files for Installing Manually for a complete list of variables used by the various software packages. See "Using Variables" under "Policy and Distribution Services" in the ZfS 3.0.2 Administration guide for details on defining variables in Subscriber objects.

To prepare for using variables during software package installation:

  1. If you are installing the ZFS3SP2REMMGMT.CPK automatically on Windows NT/2000 servers, you must create and initialize the ZFS3_RMINSTALL_PATH variable.

  2. For manual installation of ZFS3SP2REMMGMT.CPK only, you must edit the following parameters in its .BAT or .NCF file:

    1. On NetWare, if you installed the ZFS3SP2REMMGMT.CPK in a directory other than the default SYS:\TEMP\ZFS3SP2, you must modify the following line in the ZFS3REMMGMT.NCF file to specify the new path:

      java -ns -noclassgc -classpath $zfspaths com.novell.application.servman.services.software 
      package.PackageProcessor SYS:\TEMP\ZFS3SP2\ZFS3SP2REMMGMT.CPK 6 FORCE 0

    2. On Windows, you must modify the following line in the ZFS3SP2REMMGMT.BAT file to specify the new path:

      jre -noasyncgc -cp %zfspaths%com.novell.application.servman.services.softwarepackage.PackageProcessor C:\TEMP\ZFS3SP2\ZFS3SP2REM MGMT.CPK 6 ZFS3_RMINSTALL_PATH C:\ZENWORKS FORCE 0

  3. You must initialize the ZFS3_RMINSTALL_PATH variable in the path where you have installed ZfS 3 Remote Management (for example, C:\ZENWORKS).


5.2.2 Installing the Remote Management Software Package

  1. Choose whether to install ZFS3SP2REMMGMT.CPK automatically or manually.

    For automatic installation, follow the instructions in 6.2 Automatic Installation.

    For manual installation, follow the instructions in 6.3 Manual Installation.


6.0 Installing the Support Pack

The following sections provide detailed instructions for installing the software packages, the ConsoleOne snap-ins, and iManager plug-ins.

IMPORTANT:  During the software package installation process, the rollback feature is disabled. Therefore, you cannot uninstall the support packs after they are installed.

The three installation options for installing the updates included in this support pack are:


6.1 Installation Issues and Guidelines

The following sections provide important information about installing SP2:

6.1.1 General Installation Issues for SP2


6.1.2 Guidelines for Using the Automatic Installation Method

For more information on the automatic method, see 6.2 Automatic Installation.


6.1.3 Guidelines for Installing the ZfS 3 ConsoleOne Snap-Ins

It does not matter whether the SP2 software packages (.CPK files) or the SP2 ConsoleOne snap-ins are installed first. However, the ZfS 3 SP2-updated software can only be managed by the ZfS 3 SP2 snap-ins to ConsoleOne. Therefore, if you install the software packages first, you should install the snap-ins before attempting to use ZfS 3 SP2.

There are no issues with the order of installing the various ZfS 3 SP2 snap-ins to ConsoleOne that are provided in this support pack. However, for Server Inventory the following issues exist:


6.1.4 Server Inventory Issues with Installing and Using SP2

Performing a top-down deployment of Server Inventory:

The following list highlights the important issues for interoperability of ZfS 3 Server Inventory with ZfS 3 SP2 Server Inventory:


6.1.5 Interoperability of the ZfS 3 Inventory Agent with ZfS 3 SP2 Inventory Server

Inventory Agents of one version of ZfS 3 can send scans to Inventory servers of the other version of ZfS 3:


6.1.6 Determining Whether SP2 Is Installed on a Server

Except as noted, the ZfS 3 or ZfS 3 SP2 software does not need to be running on the server in order to determine which version has been installed using the methods described in this section.


6.2 Automatic Installation

Using the TED component of ZfS 3, you can automatically distribute and install the software packages to all servers that are running the Subscriber and Policy Package software.

IMPORTANT:  You cannot combine software packages into the same Distribution. You must create a separate Distribution object for each software package. This is because each software package unloads the JVM on NetWare, which prevents concurrent processing of multiple software packages. Also, the order of installing some software packages is important. See 6.2.2 Automatic Installation Order for more information.

The software packages for the following cannot be installed manually. You must install them automatically:

All other software packages can be installed automatically, but only if their servers are running the Subscriber and Policy Package software.


6.2.1 Automatic Installation Prerequisites


6.2.2 Automatic Installation Order

For the software packages that you plan to install, we recommend that they be installed in the following order:

  1. NICI24.CPK

    This software package is only required if you will encrypt your Distributions for Windows, Solaris, or Linux servers. However, if you installed this file with SP1, you do not need to re-install it for SP2.

  2. ZFS3SP2POLYDIST.CPK

    This software package must be installed before the software packages listed in item 3 below, because ZFS3SP2POLYDIST.CPK contains a fix for TED that is required for these files to be installed successfully.

    Also, you must update all the Distributor servers to SP2 before updating the Subscriber servers to SP2.

  3. ZFS3SITESVR.CPK, ZFS3MGMTAGNT.CPK, and ZFS3SP2REMMGMT.CPK

    The order for installing these three software packages does not matter. However, they each require that ZFS3SP2POLYDIST.CPK is installed first to update the Subscriber software on the server so that TED can be used to install those software packages.

  4. Any of the other software packages.

    The order for installing the remaining software package files does not matter.

    The remaining software packages do not require that ZFS3SP2POLYDIST.CPK be installed first.


6.2.3 Automatic Installation Procedure

To install a specific software package automatically:

  1. Download the self-extracting ZFS3SP2.EXE file to a temporary directory on a Windows workstation you will use to install the support pack.

  2. Run ZFS3SP2.EXE to extract the support pack software files into the temporary directory.

    See 1.3.1 Extracted File Organization for information on the directory structure that is created where the files are extracted.

  3. Copy each of the .CPK files you want to install to the Distributor's file system and make a note where they are located for when you create the associated Distribution.

  4. Set the Subscriber's Extract schedule.

    Use care in setting your Subscriber's Extract schedule.

    If the schedule is set to Run Immediate and either the Subscriber is running on the same server as a Distributor, and/or the Subscriber is a parent and will be forwarding the Distribution on to subordinate Subscribers, you will likely interrupt the sending of the Distribution to Subscribers because the update process involves unloading Java. With Java unloaded, Distributions will be temporarily halted until Java has been reloaded and the Channel's Send schedule fires.

    If the Subscriber is a parent that is sending the Distribution to subordinate Subscribers, it will be in the process of sending the Distribution when the software package tries to unload Java. However, the Distributions will continue from where they left off after Java is started again.

    For the NICI24.CPK file only, determine which Subscriber servers you want to upgrade with NICI 2.4. The NICI24.CPK file can upgrade all supported platforms using just one Distribution.

  5. Create a Distribution for this software package.

    You can have only one software package per Distribution object. Although the software allows more than one software package to be selected in a single Distribution object, this is not allowed when distributing the ZfS 3 SP2 software packages. The reason is that installing a software package unloads and reloads Java, which can prevent the remaining software packages from being successfully processed from a single Distribution object.

    Be sure to set the Distribution's Build schedule.

    IMPORTANT:  The Distribution containing ZFS3SP2POLYDIST.CPK must be built, sent, extracted, and installed before sending any other Distributions containing other ZfS 3 SP2 software packages.

    For the NICI24.CPK Distribution, make sure that all existing instances of NICI are the same version; otherwise, Distribution encryption will not work if there are two different versions of NICI in your Policy and Distribution Services system.

    For detailed instructions on creating Distributions, see "Policy and Distribution Services" in the ZfS 3.0.2 Administration guide.

  6. Associate the Distribution with a Channel so that it will be sent based on the channel schedule.

    You might need to create the Channel. Be sure to set the Channel's Send schedule.

    IMPORTANT:  ZfS 3 SP2 software packages unload and restart Java as part of the installation process. Therefore, you must process each software package individually. If you attempt to process multiple ZfS 3 SP2 software packages simultaneously (such as by processing them at the same time in a given Channel), it is likely that one or more of the Software Package Distributions will fail on installation. Therefore, add one software package to the Channel, wait until it has been successfully received and extracted by all Subscribers, then add the next software package, and so on.

  7. Associate the Subscribers that you want to receive this software package with the Channel.

  8. For the ZFS3SP2SITESVR.CPK file only, create and initialize the following package processor variables in the Subscriber objects' properties:

    • On NetWare servers: MMSPATH package processor variable.

      MMSPATH is the installation path for Management Site Services on a NetWare server. For example, DATA:\ZENWORKS\MMS.

    IMPORTANT:  You must create and initialize the Management Site Services variable for the ZFS3SP2SITESVR.CPK installation to be successful.

    See "Using Variables" under "Policy and Distribution Services" in the ZfS 3.0.2 Administration guide for details on defining variables in Subscriber objects.

  9. For the ZFS3SP2MGMTAGNT.CPK file only, create and initialize the following package processor variables in the Subscriber objects' properties:

    • On NetWare servers: NMAPATH package processor variable.

      NMAPATH is the installation path of the Management Agent on a NetWare server. For example, SYS:\ZFS_AGNT.

    • On Windows NT/2000 servers: ZFS3AGENTPATH package processor variable.

      ZFS3AGENTPATH is the installation path of the Management Agent on a Windows NT/2000 server. For example, C:\ZENWORKS.

    IMPORTANT:  You must create and initialize the Management Agent variables for the ZFS3SP2MGMTAGNT.CPK installation to be successful.

    See "Using Variables" under "Policy and Distribution Services" in the ZfS 3.0.2 Administration guide for details on defining variables in Subscriber objects.

  10. For the ZFS3SP2LANZAGNT.CPK file only, create and initialize the following package processor variables in the Subscriber objects' properties:

    • On NetWare servers: LANZPATH package processor variable.

      LANZPATH is the installation path of the LANalyzer Agent on a NetWare server. For example, SYS:\ZFS_AGNT.

    • On Windows NT/2000 servers: NTLANZPATH package processor variable.

      NTLANZPATH is the installation path of the LANalyzer Agent on a Windows NT/2000 server. For example, C:\ZENWORKS.

    IMPORTANT:  You must create and initialize the LANalyzer Agent variables for the ZFS3SP2LANZAGNT.CPK installation to be successful.

    See "Using Variables" under "Policy and Distribution Services" in the ZfS 3.0.2 Administration guide for details on defining variables in Subscriber objects.

  11. Send the Distribution.

    For example, refresh the Distributor to get the Distribution built so that it can be sent and extracted.

    See Policy and Distribution Services in the ZfS 3.0.2 Administration guide for detailed instructions on sending Distributions.

    The Distribution will be automatically created when the Distribution's Build schedule starts. The Distribution will automatically be sent when the Channel's Send schedule starts. It will be extracted according to the Subscriber server's Extract schedule.

  12. Determine which components of the software package were installed successfully by using one of the following methods:

    1. Use the Tiered Electronic Distribution view in iManager to see information for every software package that was installed.

    2. If you use TED for installation, use ZfS reporting to verify the success or failure of individual components of a software package.

    3. Use the log files contained on the Subscriber Servers to verify the success or failure.

      For a list of the log files and their locations, see 6.5 Installation Log Files.

    Each software package can consist of several components. It is possible that some of these components can succeed in installing and others fail. Therefore, success for the software packages included in the ZfS3 support pack installation means that one or more components were successfully installed.

    Several components could fail to install, and the Software Package installation will still appear as successful. Therefore, we recommend that you review the success or failure of each component of the software package to verify that the components needed on a specific server were installed successfully.

IMPORTANT:  All ConsoleOne snap-ins installed on the server will be updated during the automatic installation process. However, if you installed ConsoleOne snap-in components on local workstations, you must upgrade those workstations manually using the manual process outlined under 6.4.1 Installing the ConsoleOne Snap-Ins to a Workstation or Windows Server.


6.3 Manual Installation

If you are installing the support packs to servers that are not running Subscriber software and the Policy/Package Agent, you must use the Standalone Package Processor included in the support pack download to manually install the software packages.

You also have the option to use the Standalone Package Processor to manually install a software package to a server that is running Subscriber software and the Policy/Package Agent.

The following software packages can be manually installed in any order:

The following .ZIP files contain the .BAT and .NCF files and other Standalone Package Processor software:

The following package-specific .BAT and .NCF files are available from these three .ZIP files to launch the Standalone Package Processor:


6.3.1 Manual Installation Prerequisites


6.3.2 Manual Installation Order

Software packages that you plan to install manually can be installed in any order.


6.3.3 Manual Installation Procedure

The following instructions should be repeated for each NetWare or Windows server where you will manually install the support pack.

IMPORTANT:  Use the manual installation instructions only in conjunction with the installation instructions contained in the individual software package sections in this Readme, because the various prerequisites for the software packages are documented in those sections.

  1. Download the self-extracting ZFS3SP2.EXE file to a temporary directory on a Windows workstation.

  2. For installation to a NetWare server, run ZFS3SP2.EXE to extract the support pack software files to a temporary directory at the root of the SYS: volume.

    You must have a drive mapped to the NetWare server for this operation.

    You cannot manually install to a Linux or Solaris server.

    See 1.3.1 Extracted File Organization for information on the directory structure that is created where the files are extracted.

    IMPORTANT:  For NetWare 4.2 servers, there are no ZfS 3 SP2 updates. For NetWare 5.0 servers, there is a Management Agent update containing the ZFS3SP2MGMTAGNT.CPK file. However, you cannot install ZfS 3 SP2 to a NetWare 5.0 server. The Management Agent update for NetWare 5.0 servers is contained in a .ZIP file, which you can obtain from the Novell Support Connection Web site. See TID 10074783 for the download and installation instructions.

  3. For installation to a Windows server:

    1. Copy the self-extracting ZFS3SP2.EXE file to the Windows server where you will install the support pack.

    2. Run ZFS3SP2.EXE to extract the support pack software files to a temporary directory at the root of the C: drive.

    See 1.3.1 Extracted File Organization for information on the directory structure that is created where the files are extracted.

  4. Before manually installing the ZFS3SP2INVREM.CPK, ZFS3SP2MGMTAGNT.CPK, ZFS3SP2LANZAGNT.CPK, or ZFS3SP2REMMGMT.CPK files, do the following as applicable before manually installing any of these .CPK files:

    1. If for some reason JRE 1.3.1 is not installed on the target Windows server (JRE 1.3.1 is usually installed when you install ZfS 3 to a server), do the following:

      • Download JRE 1.3.1 from Sun*.
      • Install the JRE.
      • Continue with Step b.

    2. Do the following on each target Windows server where JRE 1.3.1 is installed:

      • For the .BAT files corresponding to the ZFS3SP2MGMTAGNT.CPK and ZFS3SP2LANZAGNT.CPK files, edit the .BAT files to set the JRE path to: 
        JRE_installation_path\JRE\BIN
      • For the .BAT files corresponding to the ZFS3SP2INVREM.CPK and ZFS3SP2REMMGMT.CPK files, edit the .BAT files to set the JRE path to: 
        JRE_installation_path\JRE

  5. Locate and unzip the INVREM_STANDALONEPACPRO.ZIP, MGMTMON_STANDALONEPACPRO.ZIP, or POLYDIST_STANDALONEPACPRO.ZIP file to the following appropriate location:

    • Windows server: C:\

    • NetWare server: SYS:\

    These .ZIP files contain a directory structure that includes TEMP as the first directory.

    The Standalone Package Processor files will be unzipped into a TEMP directory at the root of the server's file system.

  6. Copy the .CPK file to be manually installed to the temporary directory where the associated .BAT or .NCF file exists. For example:

    • Windows server: C:\TEMP\ZFS3SP2

    • NetWare server: SYS:\TEMP\ZFS3SP2

    For the location of the .CPK file, see 1.3.1 Extracted File Organization.

    For the location of the .BAT or .NCF files, see Step 4 above.

  7. From the temporary directory, run the .BAT or .NCF file associated with the software package you want to install:

    • ZFS3SP2REMMGMT.CPK:

      On NetWare, enter the following at the server prompt:

      SYS:\TEMP\ZFS3SP2\NETWARE\ZFS3SP2REMMGMT.NCF

      On Windows, run the following:

      C:\TEMP\ZFS3SP2\WIN\ZFS3SP2REMMGMT.BAT

      NOTE:  If you have installed ZFS3SP2REMMGNT.CPK on a path other than the default on Netware or Windows, you must specify the new path while running ZFS3SP2REMMGMT.CPK as mentioned above.

    • ZFS3SP2INVREM.CPK:

      On NetWare, enter the following at the server prompt:

      SYS:\TEMP\ZFS3SP2\NETWARE\INVRMSP2.NCF

      On Windows, run the following:

      C:\TEMP\ZFS3SP2\WIN\INVRMSP2.BAT

    • ZFS3SP2SITESVR.CPK:

      SYS:\TEMP\ZFS3SP2\NETWARE\ZFS3SP2SITESVR.NCF

      You must modify the ZFS3SP2SITESVR.NCF file and change the MMSPATH variable so that it lists the correct directory. By default, MMSPATH is set to DATA:\ZENWORKS\MMS.

      IMPORTANT:  You must enclose the values for the directory location within double quotes if the directory name contains white space. For example: 

      MMSPATH "SYS:\ZFS SERV\ZENWORKS\MMS"

    • ZFS3SP2LANZAGNT.CPK:

      On NetWare, enter the following at the server prompt:

      SYS:\TEMP\ZFS3SP2\NETWARE\ZFS3SP2LANZAGNT.NCF

      On Windows, run the following:

      C:\TEMP\ZFS3SP2\WIN\ZFS3SP2LANZAGNT.BAT

    • ZFS3SP2MGMTAGNT.CPK:

      On NetWare, enter the following at the server prompt:

      SYS:\TEMP\ZFS3SP2\NETWARE\ZFS3SP2MGMTAGNT.NCF

      On Windows, run the following:

      C:\TEMP\ZFS3SP2\WIN\ZFS3SP2MGMTAGNT.BAT

    • ZFS3SP2POLYDIST.CPK:

      On NetWare, enter the following at the server prompt:

      SYS:\TEMP\ZFS3SP2\NETWARE\ZFS3SP2POLYDIST.NCF

      On Windows, run the following:

      C:\TEMP\ZFS3SP2\WIN\ZFS3SP2POLYDIST.BAT

  8. Determine which components of the software package were installed successfully by reviewing the log file created by the package processor to ensure that the installation was successful.

    For a list of the log files and their locations, see 6.5 Installation Log Files.

IMPORTANT:  Before starting another software package installation, you must ensure that the previous installation is complete. Processing a new software package before the previous one is complete could cause the second software package installation to fail.


6.4 Installing Snap-Ins and Plug-Ins

To install the SP2-updated ConsoleOne snap-ins to instances of ConsoleOne on workstations or the ZfS 3 plug-ins to iManager, you must do this manually using the .ZIP files supplied for each set of snap-ins or plug-ins.

For guidelines on installing the ZfS 3 ConsoleOne snap-ins, see 6.1.3 Guidelines for Installing the ZfS 3 ConsoleOne Snap-Ins.

The following .ZIP files contain ZfS snap-ins or plug-ins for SP2:


6.4.1 Installing the ConsoleOne Snap-Ins to a Workstation or Windows Server

This section applies only to the following .ZIP files:

TEMP\MGMTMON\ZFS3SP2C1SNAP_MGMTMON.ZIP
TEMP\POLYDIST\ZFS3SP2POLYDISTSNAPINS.ZIP
TEMP\INVREMMGMT\ZFS3SP2C1SNAP_REMMGMT.ZIP
TEMP\INVREMMGMT\ZFS3SP2C1SNAP_INV.ZIP

To install the snap-ins to ConsoleOne on a workstation:

  1. Close ConsoleOne.

    The instance of ConsoleOne where you want to install the snap-ins cannot be running.

  2. Open a .ZIP file in WinZip or other file extraction program.

  3. Unzip the file in the following location:

    C:\Novell\ConsoleOne\1.2

    The .ZIP files contain the directory structure for all snap-in files beginning in the 1.2 directory.

IMPORTANT:  When prompted to overwrite the existing files of the same name in the destination directories, regardless of differences in file dates, choose "Yes to ALL."

For the Server Inventory and Remote Management ConsoleOne snap-ins functionality to work, ensure that ZFS3SP2POLYDISTSNAPINS.ZIP is installed.


6.4.2 Modifying QUERY.PROPERTIES for Interoperability of ZfS 3 SP2 and ZfD 4.0.1

After installing the ConsoleOne snap-ins using the ZFS3SP2C1SNAP_REMMGMT.ZIP or ZFS3SP2C1SNAP_INV.ZIP file to Windows or NetWare servers, you need to perform the following tasks on each of these servers in order for ZfS 3 SP2 to work with ZfD 4.0.1:

  1. Modify the INSVER parameter in the ConsoleOne_installation_path\BIN\QUERY.PROPERTIES file to contain any of the following values:

    zfs (default): Inventory ConsoleOne will have only ZfS snap-in functionality
    zfd: Inventory ConsoleOne will have only ZfD snap-in functionality
    both: Inventory ConsoleOne will have both ZfS and ZfD snap-in functionality

  2. Modify the RMVER parameter in the ConsoleOne_installation_path\BIN\QUERY.PROPERTIES file to contain any of the following values:

    zfs (default): Remote Management ConsoleOne will have only ZfS snap-in functionality
    zfd: Remote Management ConsoleOne will have only ZfD snap-in functionality
    both: Remote Management ConsoleOne will have both ZfS and ZfD snap-in functionality


6.4.3 Installing the iManager Plug-Ins for Management of the Policy and Distribution Services Components

This section applies only to the TEMP\POLYDIST\ZFS3SP2POLYDISTPLUGINS.ZIP file.

The ZfS 3 SP2 iManager plug-ins require iManager 1.5.1 or later. Previously, the ZfS 3 and ZfS 3 SP1 iManager plug-ins worked with iManager 1.2. To obtain the iManager 1.5.1 update, see the Novell Web site.

ZFS3SP2POLYDISTPLUGINS.ZIP contains all of the iManager files for ZfS 3 SP2. A prior installation of the ZfS plug-ins is not needed. In fact, when you install iManager 1.5.1 on a server where iManager 1.2 was installed, the old ZfS plug-ins are removed.

iManager plug-ins are not supported on NetWare 5.1.

To install the plug-ins to iManager on the Web server:

  1. Map a drive to the Web server where Tomcat and your iManager plug-ins are installed.

    On a Windows server, you can perform this installation locally, so a drive mapping is not needed.

  2. Stop Tomcat.

  3. Open ZFS3SP2POLYDISTPLUGINS.ZIP in WinZip or other file extraction program.

  4. Unzip the file where you previously installed the plug-ins under the Tomcat directory. For example:

    %TOMCAT_HOME%\WEBAPPS\EMFRAME

    The .ZIP files contain the directory structure for all plug-in files beginning in the EMFRAME directory on the Web server.

  5. Restart Tomcat.


6.5 Installation Log Files

A log file, created by the package processor, can be found in the following locations:


6.6 Variables Used by NCF and BAT Files for Installing Manually

This section lists the variables used by the .BAT and .NCF files during manual installation of a support pack software package.

The following variables are grouped under the software package headings for the applicable .BAT and .NCF files.

IMPORTANT:  Only one variable name is maintained for the ConsoleOne directory in the software package. If you need to install to more than one platform, you must edit the value for the corresponding platform in the .BAT or .NCF file.


6.6.1 ZFS3SP2REMMGMT.CPK

This software package for Remote Management uses variables for the following .BAT or .NCF files:

ZFS3SP2REMMGMT.BAT

Variable = ZFS3_RMINSTALL_PATH
Default Value = C:\ZENWORKS
Function = Defines the path to which the Remote Management Agent is installed on Windows NT/2000 Servers.


6.6.2 ZFS3SP2MGMTAGNT.CPK

This software package for the Management Agent uses variables for the following .BAT or .NCF files:

ZFS3SP2MGMTAGNT.BAT

Variable = ZFS3AGENTPATH
Default Value = C:\ZENWORKS
Function = Defines the complete path to the install agents.

ZFS3SP2MGMTAGNT.NCF

Variable = NMAPATH
Default Value = SYS:\ZFS_AGNT
Function = Defines the install folder name on NetWare.


6.6.3 ZFS3SP2LANZAGNT.CPK

This software package for LANalyzer Agent uses variables for the following .BAT or .NCF files:

ZFS3SP2LANZAGNT.NCF

Variable = LANZPATH
Default Value = SYS:\ZFS_AGNT
Function = Defines the install folder name NetWare Servers.

ZFS3SP2LANZAGNT.BAT

Variable = NTLANZPATH
Default Value = C:\ZENWORKS
Function = Defines the complete path of the install agents.


6.6.4 ZFS3SP2SITESVR.CPK

This software package for Site Management Server uses variables for the following .NCF file:

ZFS3SP2SITESVR.NCF

Variable = MMSPATH
Default Value = DATA:\ZENWORKS\MMS
Function = Defines the path to which the Site Management Server is installed on NetWare servers.


6.6.5 ZFS3SP2INVREM.CPK

This software package for Inventory Server, Inventory ConsoleOne, and Remote Management ConsoleOne uses variables for the following .BAT or .NCF files:

INVRMSP2.BAT

Variable = CONSOLE_INSTALL_PATH_NT
Default Value = C:\NOVELL\CONSOLEONE\1.2
Function = Defines the path to which ConsoleOne is installed on the local machine.
   
Variable = CPK_WORKING_DRIVE_NT
Default Value = C:
Function = Defines the working drive used for software package execution.

INVRMSP2.NCF

Variable = CONSOLE_INSTALL_PATH_NW
Default Value = SYS:\PUBLIC\MGMT\CONSOLEONE\1.2
Function = Defines the path to which ConsoleOne is installed on NetWare servers.

7.0 New Features

The following sections list the new features provided in ZfS 3 SP1 and SP2.


7.1 Policy and Distribution Services New Features

The following sections list the new features provided after installing ZFS3SP2POLYDIST.CPK.


7.1.1 Ability to Create Desktop Application Distributions in iManager

You can now create Desktop Application types of Distributions in iManager.


7.1.2 Interoperability Between TED and ZfD 4.0.1

Desktop Application type Distributions created in ZfS 3 SP2 will work with ZfD 4.0.1.


7.1.3 Ability to Revoke an Individual Policy

You can now revoke an individual policy using an option in iManager.


7.1.4 Support for Distributions Greater than 4 GB

NetWare 6 SP2 or later, and NetWare 5.1 SP6 or later each contain the JVM update that provides support for 64-bit I/O, which allows you to create and send Distributions greater than 4 GB.

For more information, see 3.2.4 Updating a Server for Large Distribution Support.


7.1.5 Encryption Support Added for Linux and Solaris Platforms

The NICI 2.4 included in SP2 provides encryption capability for the Windows, Solaris, and Linux platforms. This is new in SP2 for the Linux and Solaris platforms. For more information, see 3.1 NICI Update (NICI24.CPK).


7.1.6 No Limit to the Number of Files and Folders in a Distribution

The previous limit of approximately 240 files/folders that could be selected for a File type of Distribution has been removed in SP2.


7.2 Server Inventory New Features

The following lists the Server Inventory-related new features:


7.3 Remote Management New Features

Remote Management has the following new features:


8.0 Resolved Issues

(SP1) and (SP2) are used at the beginning of an entry to indicate in which support pack the issue was resolved.


8.1 Management and Monitoring Services Resolved Issues

The following sections list the software issues that are resolved in the Management and Monitoring Services support packs (ZFS3SP1SITESVR.CPK or ZFS3SP2SITESVR.CPK).


8.1.1 Network Discovery Resolved Issues


8.1.2 Atlas Management Resolved Issues


8.1.3 Alarm Management Resolved Issues


8.1.4 Server Management Resolved Issues


8.1.5 Reports Resolved Issues


8.1.6 MIB Browser Resolved Issues


8.1.7 MIB Compiler Resolved Issues


8.1.8 Traffic Analysis Agent Resolved Issues


8.1.9 Other Resolved Issues


8.2 Policy and Distribution Services Resolved Issues

The following sections list the software issues that are resolved in the Policy and Distribution Services support packs (ZFS3SP1POLYDIST.CPK or ZFS3SP2POLYDIST.CPK).


8.2.1 (SP1) One-Hour File Time Change After Distribution

After you install the JVM that comes with NetWare 6 SP2, file times are no longer off by one hour after the files have been distributed during Daylight Saving Time (DST).


8.2.2 (SP1) Software Package Status Problem Resolved

Prior to ZFS 3 SP2, when a software package was processed that required rebooting the server (for example, a NetWare support pack software package), the package status would stay at "Processing" even though it had finished. This has been fixed.


8.2.3 (SP1) Converting ZfS 2 Software Packages to ZfS 3

ZfS 2 software packages cannot be used in ZfS 3 until they have been converted to ZfS 3 format. A utility for converting these software packages has been provided as a menu option in ConsoleOne.


8.2.4 (SP1) Using the Euro Symbol in Distributions

Certain characters in the DOS 850 code page, such as the euro symbol, will no longer cause TED Distributions to fail when used in filenames. Any unmapped characters found in filenames will be replaced with a question mark (?).


8.2.5 (SP1) E-Mail Addresses for Service Location Packages

When defining an e-mail address for logging notification in the Messaging tab for the Tiered Electronic Distribution policy in the Service Location Package, the correct e-mail addresses now display in the Distributor and Subscriber objects' properties.


8.2.6 (SP1) Changing SET Parameter Values

Previously, you could not delete a SET parameter value, such as Maximum Pending TCP Connection Request, so that you could enter a new value. This has been fixed.


8.2.7 (SP1) Quotation Mark Characters in Distinguished Names

TED object names with single quotation marks can now be written to the Sybase* database.


8.2.8 (SP1) Trustees Not Being Synchronized for Distributions

When a File or Software Package type of Distribution is set to Synchronize, the trustees are now synchronized. In other words, if any trustees are removed from the source, the target has the trustees also removed.

Also, when you change a trustee's properties, this will trigger new versions of the Distributions associated with the trustee to be sent.


8.2.9 (SP1) Local File Copying and Software Package Failure

Previously, if a Local File Copy component in a software package failed, the entire component did not fail. Now, the failure of a Local File Copy action will cause the entire component to fail.


8.2.10 (SP1) Starting Order for ZfS 3.0.2 and ZfD 4.0.1

After installing SP2, the ZfS 3.0.2 and ZfD 4.0.1 software can be started in any order.


8.2.11 (SP1) Using Special Characters in Distinguished Names

Special characters, such as the ampersand (&), are now handled correctly by the iManager plug-ins.


8.2.12 (SP1) Distributing Two RPM Packages in One Distribution

You can now list two RPM packages in one Distribution that is being sent to a Red Hat 7.2 Subscriber server. Previously, only the first RPM package listed in the Distribution would be installed when the Subscriber extracted the Distribution.


8.2.13 (SP1) Deleting Old Log File Information

Log files are now updated by having older entries deleted when you specify to delete entries older than nnn days in the ZFS Policy.


8.2.14 (SP1) Multiple DNS Names or IP Addresses and the -hosts Switch

When a server is known by multiple DNS names or IP addresses, you need to use the -hosts switch during installation of ZfS to that server so that the configuration file will be updated with all of the addresses. Otherwise, Policy and Distribution Services will not start up the next time the server is brought down and back up. The -hosts switch for all platforms has been documented in the ZfS 3.0.2 Installation guide.


8.2.15 (SP1) Status Buttons for TED Events

For Tomcat 3.3 running on NetWare 6 with the latest eMFrame.zip, the Status buttons are now displayed for the TED events in iManager, such as for viewing the Distributor or Subscriber Event Log.


8.2.16 (SP1) GMT Offset File Time Change After Distribution

When installing a software package to a Windows Server, the file time stamps were all off by that machine's offset from GMT. For example, if you are in New York (-6 GMT) and a software package contained a file with a time stamp of 3:00 pm, the time stamp of the file would have been 9:00 pm. This has been fixed.


8.2.17 (SP1) Compilation Times for Server Software Packages Improved

Compilation time for software packages has been improved dramatically when large numbers of files are used.


8.2.18 (SP1) Selecting Server Software Package Options for Windows

You can now set the version and major or minor attributes in a software package for the Windows platform.


8.2.19 (SP1) Corrupted Paths to Executables for Desktop Application Distributions

The second time a Desktop Application Distribution was sent, the Path to Executable field was being corrupted. This has been fixed.


8.2.20 (SP1) Adding/Deleting Rights for Desktop Application Distributions

Previously, the second time a Desktop Application type of Distribution was sent, distribution rights were being deleted instead of added. This has been fixed.


8.2.21 (SP1) ConsoleOne Snap-Ins for ZfS 3 Overwriting ZfD 3.2 Snap-Ins

ConsoleOne snap-ins for ZfS 3 were causing UI information for ZfD 3.2 snap-ins to be lost. For example, you would see a message stating "Policies enabled on this page will be applied only on workstations that have been upgraded to ZfD 4.0.1.

To set policies for workstations using earlier versions of ZfD, please us the Windows NT-2000-XP tab. However, the ZfS 3 snap-ins were not allowing this tab to be displayed. This has been fixed.


8.2.22 (SP1) Installation Parameters for RPM Distributions

Previously, after an RPM Distribution was saved, you could not edit the Distribution and add installation parameters. This has been fixed.


8.2.23 (SP1) Installing Red Hat RPMs with Parameters

When using parameters with RPM Distributions, the Distributions are now extracted and installed successfully.


8.2.24 (SP1) Event Icons Now Display

When displaying the event log in iManager, the icons to the left are now displayed. Previously, the default graphic for missing icons was displayed.


8.2.25 (SP1) Registry Value Comparisons Added to Software Packages

When processing a software package with a registry requirement, the package generated a false positive, meaning that the registry requirement passed, and the package or component was processed when it should have failed. This has been fixed.


8.2.26 (SP2) iManager Lists Alphabetized

In iManager, lists of objects are now alphabetized for ease of finding specific items in the list.


8.2.27 (SP2) iManager 1.5.1 required for SP2

iManager 1.5.1 is now required for use with the iManager plug-ins that are installed with ZfS 3.0.2 or ZfS 3 SP2. This is the same version of iManager that is included in CSP9.

IMPORTANT:  iManager 2.0 is not supported by the plug-ins included in ZfS 3.0.2 or ZfS 3 SP2.


8.2.28 (SP2) Using the NICI24.CPK File to Upgrade Multiple Servers

A compressed file (NICI24CPK.EXE) containing the NICI24.CPK file is available from the Novell Web site with ZfS 3 SP2, and also on the ZENworks for Servers 3.0.2 Companion CD or ZEnworks 6 Companion 1 CD (see \NICI\NICI24CPK.EXE) for upgrading Windows, Linux, and Solaris servers to NICI 2.4. NICI24.CPK must be used in a Distribution.

The NICI24.CPK file can be used to update servers on any supported platform using one Distribution.

NICI 2.4 is automatically installed with the versions of NetWare supported by ZfS 3 SP2 or ZfS 3.0.2, so you do not need to install NICI to NetWare servers.


8.2.29 (SP2) Default Value for the Connection Timeout Field Corrected

In the Service Location Package for the TED policy's properties, the Connection Timeout field's limitation of 60 has been increased to 60,000. This matches the existing setting of 60,000 for the Connection Timeout for the Subscriber object's properties.


8.2.30 (SP2) High CPU Utilization Fixed

High CPU utilization for a File type of Distribution that interfered with users logging into the network has been fixed.


8.2.31 (SP2) The No Restrictions Check Box Retains Previous Values

Previously, the No Restrictions box was automatically unchecked when you modified multiple Distributions, regardless of its previous value (checked or unchecked). This has been fixed so that the field now retains its previous value.


8.2.32 (SP2) Windows NT Server and Null Pointer Exception Fixed

ZfS now correctly handles an occasional null pointer exception error that could be received during the extraction of a File type Distribution on Windows NT servers.


8.2.33 (SP2) User Group Trustee Assignments Are Now Replicated Properly

The Desktop Application type of Distribution was not previously replicating the User Group Trustee assignments, such as Read and Compare rights. This has been fixed.


8.2.34 (SP2) Daylight Saving Time Offset Corrected

The Daylight Saving time offset is now being correctly set from a SET parameter.


8.2.35 (SP2) TRAPTARG.CFG File Now Updated Properly

The TRAPTARG.CFG file is now properly being updated when an IP address or DNS name is removed from the SNMP Trap Target policy.


8.2.36 (SP2) Desktop Application Distributions Now Correctly Resolves Cluster Information

When a Desktop Application is distributed to a Subscriber on a cluster, the application path in the NAL object was referencing the cluster node that was currently running the Subscriber process, instead of referencing the Cluster object. When a failover occurred, the Application object no longer worked. Now, the Application object will use the cluster's DNS name, IP address, or object name as contained in the NAL object path.


8.2.37 (SP2) CPU Utilization by Subscriber Fixed

During the extraction process of a File type of Distribution, a list of all the files was built in the destination directory of the Subscriber. It was during the generation of this list that the server utilization was reaching 100%. A ZfS 3 Subscriber will no longer cause 100% CPU utilization during software package processing.


8.2.38 (SP2) % Symbols Now Allowed in Directory Paths

Directory paths can now contain % symbols in path names. They are no longer misinterpreted as variable symbols.


8.2.39 (SP2) Distributions No Longer Fail When Using More Space Than Is Free on the Subscriber Server

The Disk Space Desired To Be Free option in a Windows, Linux, or Solaris Subscriber server’s properties allows you to control the condition for when a Distribution is larger than the space that is free on a given Subscriber server. For example, you can specify a value large enough that should the Subscriber server’s free disk space be less than that value, it will prevent the Distributor from trying to send a Distribution.

If you do not enable the Disk Space Desired To Be Free option, the Distributor now receives notification that the Subscriber server may not have sufficient free disk space to receive the Distribution, so the Distributor stops sending the Distribution data. Previously, the Distributor would continue sending the Distribution data, because only the Subscriber was receiving notification that it was running out of disk space.


8.3 Inventory Agent Resolved Issues

The following list indicates the resolved software issues that are provided in the Server Inventory support packs (ZFS3SP1INVSPAGN.CPK or ZFS3SP2INVSPAGN.CPK).


8.4 Remote Management Resolved Issues

The following sections list the resolved software issues that are provided in the Remote Management support packs (ZFS3SP1REMMGMT.CPK and ZFS3SP1INVREM.CPK or ZFS3SP2REMMGMT.CPK and ZFS3SP2INVREM.CPK).


9.0 Known Issues

The following sections list the software issues that are unresolved in ZfS 3 SP2.


9.1 Management and Monitoring Services Known Issues

The following sections list the software issues that are unresolved in the ZFS3SP2MGMTAGNT.CPK and ZFS3SP3SITESVR.CPK provided in this support pack. These issues are new to ZfS 3 as a result of SP2.


9.1.1 The SNMP service stops abruptly but successfully when the Traffic Analysis agent is installed on Windows 2000, Windows .NET servers

You attempted to stop the SNMP services while it was running. When you attempted to stop the services, some of the Traffic Analysis agent .DLL files did not unload completely. However, this is an informational message and does not require any troubleshooting.


9.1.2 For NetWare IP and IPX routers, which use unnumbered links, Discovery fails to create a topology correctly involving NetWare

On NetWare IP and IPXTM routers that are configured with unnumbered addresses, discovery fails to create a correct topology.

To work around this problem, try using the Database Object Editor to manually create the correct topology linking the routers.


9.1.3 The Summary view of the storage instance displays a column mismatch

A column mismatch is displayed in the Summary view of the Storage Instance. To resolve the column mismatch, rename the MWPARTITIONVIEW_SUMMARY.CONTROL and the NWPARTITIONVIEW_SUMMARY.DATA files in the CONSOLEONE\SAVEDVIEWS directory.


9.1.4 The Trend view is not displayed correctly in ConsoleOne for unnamed volumes

The information in the Trend view is not displayed correctly in ConsoleOne for unnamed volumes. To resolve this issue:

On a Windows NT Server:

  1. From the desktop console, click Start > Programs > Administrative Tools > Disk Administrator.

  2. Right-click an unnamed primary partition or an unnamed logical drive, then click Assign Drive Letter.

  3. Select the Assign drive letter option.

  4. Select a drive letter from the drop-down list.

  5. Click OK.

  6. Repeat Step 2 through Step 5 for all unnamed primary partitions or logical drives.

On a Windows 2000 or Windows .NET server:

  1. From the desktop console, click Start > Settings > Control Panel.

  2. Double-click Administrative Tools > click Computer Management.

  3. Click Storage > Disk Management.

  4. Right-click an unnamed primary partition or an unnamed logical drive > click Change Drive Letter and Paths.

  5. Add a drive letter.

  6. Click OK.

  7. Repeat Step 4 through Step 6 for all unnamed primary partitions or logical drives.


9.2 Policy and Distribution Services Known Issues

The following sections list the software issues that are unresolved in the ZFS3SP2POLYDIST.CPK file provided in this support pack. These issues are new to ZfS 3 as a result of SP2.


9.2.1 Cannot Associate Multiple SP2 Distribution Objects Containing Server Software Packages to the Same Channel

ZfS 3 SP2 software packages unload and restart Java as part of the installation process. Therefore, you must process each software package individually.

If you attempt to process multiple ZfS 3 SP2 software packages simultaneously (such as by associating them with the same Channel), it is likely that one or more of the Software Package Distributions will fail on installation.


9.2.2 Unloading Java Disrupts Sending Other Distributions When a Subscriber Is on the Same Server As the Distributor

If a Distributor server is also a Subscriber, the Distributor cannot send any Distributions to other Subscriber servers while the Distributor server is updating its Subscriber software to SP2 from a Software Package Distribution.

This is applicable only to Distributions created for installing SP2 components, because the SP2 Server Software Packages are designed to automatically stop and restart Java.

Therefore, do not send a Distribution containing an SP2 update to other Subscriber servers while the Distributor server is processing a Distribution that is updating the Distributor's Subscriber to SP2. When Java is stopped on the Distributor server, unprocessed Distributions for other servers will be stopped and not restarted.

Also, do not include a Software Package Distribution for an SP2 update in the same Channel that is used to send that SP2 Distribution to other Subscriber servers. Again, when Java is stopped on the Distributor server, unprocessed SP2 Distributions for other servers will be stopped and not restarted.


9.2.3 (New) Error Caused by Use of a DNS Short Name on NetWare 5.1 SP6 Servers

If the ETC\HOSTS file on a server contains only the short version of the DNS name (such as Server1), the TED component of ZfS 3 SP2 will not start after installing NetWare 5.1 SP6. The 105 error is given stating that the DNS name couldn’t be resolved, and TED is exited.

To fix this, edit the HOSTS file on the NetWare 5.1 SP6 server and change the DNS short name to its fully-qualified DNS name (such as Server1.Provo.Novell). Then the TED component will be able to resolve the DNS name and start.

This is not an issue for NetWare 6 SP3 because fully-qualified DNS names are required.


9.2.4 (New) Distribution Entryption Not Working if JVM 1.3.1_06 Is Installed

TED is unable to generate its ephemeral keys on NetWare 5.1 SP6 and NetWare 6 SP3 servers when either operating system has the JVM 1.3.1_06 that is installed with SP6 or SP3. This inability to generate ephemeral keys means no encrypted Distribution support is possible.

To fix this, see TID 10081994, which provides the JNINICI.NLM file that sovles this problem.


9.2.5 (New) ZfS 3 Desktop Application Distributions Need to be Rebuilt for SP2

The following is only applicable if you are upgrading from ZfS 3 to ZfS 3 SP2 or ZfS 3.0.2. It does not apply if you are upgrading from ZfS 3 SP1.

All Desktop Application Distributions that were built by a ZfS 3 (not SP1) Distributor before SP2 was installed must be rebuilt after the Distributor and Subscribers have been updated to SP2. Otherwise, the Subscriber will receive a null pointer exception error when extracting the Desktop Application Distribution.

In order to force a rebuild of a Desktop Application Distribution to make it an SP1 version, you must delete the directory containing the name of the Desktop Application Distribution, then refresh the Distributor.

The Desktop Application Distribution directory containing the Distribution is located in the Distributor's working directory. You do not need to delete the Distribution on the Subscriber's file system. It will be replaced when the rebuilt Distribution is sent.

If a Desktop Application Distribution is not rebuilt, the Subscriber successfully extracts the Distribution, then starts to build the Application object. At that point, a null pointer exception is thrown. The log file might look like the following:

2002.10.16 20:19:03 Package (App0) Component (): ? copied file ? Sys:\extra\1002.fil
2002.10.16 20:19:04 Package (App0) Component (): ? copied file ? Sys:\extra\1003.fil
2002.10.16 20:19:04 Package (App0) Component (): ? copied file ?
SYS:\ZENWORKS\PDS\TED\SUB\ff~appdist4.temp?servers.servers.glenmont.ff\1034813685475\App0\App0.xml
2002.10.16 20:19:04 Finished processing sucessfully software package : App0
2002.10.16 20:19:21 *** Exception: java.lang.NullPointerException
2002.10.16 20:19:21 java.lang.NullPointerException
     at com.novell.application.zenworks.nalted.application.ApplicationObject.copyApplicationObject(ApplicationObject.java, Compiled Code)
     at com.novell.application.zenworks.nalted.tedagent.TEDNalSequentialExtractAgent.buildAppObject(TEDNalSequentialExtractAgent.java, Compiled Code)

9.3 Inventory Agent Known Issues

The following section lists the software issues that are unresolved in the ZFS3SP2INVSPAGN.CPK provided in this support pack.


9.3.1 Unable to upgrade the ZfS3 Inventory Agent through using the Inventory Agent software package (ZFS3SP2INVSPAGN.CPK)

If the execution of ZFS3SP2INVSPAGN.CPK fails because of a problem in unloading Java, the following error is reported in SYS:\ETC\INVUPDT.LOG:

Java.nlm could not be unloaded, installation of ZFS3 upgrade will fail

This error occurs if there is a problem in executing the java -exit command.

You have two options for solving this problem: upgrading your JVM from a support pack, or manually unloading and loading Java.

Upgrade Your JVM Using the Correct Support Pack

  1. Upgrade your JAVA.NLM:

    1. Unload Java on the inventoried server.

    2. Upgrade JAVA.NLM on the inventoried server by installing NetWare 6 SP3 or NetWare 5.1 SP6 (which include the same JVM provided with CSP9).

  2. Reinstall ZFS3SP2INVSPAGN.CPK.

    For more information on how to install ZFS3SP2INVSPAGN.CPK, see 6.2 Automatic Installation.

  3. Review SYS:\ETC\INVUPDT.LOG to ensure that ZFS3SP2INVSPAGN.CPK has been successfully reinstalled.

Manually Unloading and Reloading Java

If you do not apply a fix to JVM 1.3.1:

  1. At the server console prompt, enter java -killall.

  2. At the server console prompt, enter unload java.

    Before unloading Java, unload other referenced NLM programs, if any.

  3. If Java has been successfully unloaded:

    1. Reinstall ZFS3SP2INVSPAGN.CPK.

      For more information on how to install ZFS3SP2INVSPAGN.CPK, see 6.2 Automatic Installation.

    2. Review SYS:\ETC\INVUPDT.LOG to ensure that ZFS3SP2INVSPAGN.CPK has been successfully reinstalled.

  4. If Java has not been successfully unloaded:

    1. Upgrade your JAVA.NLM:

      • Unload Java on the inventoried server.
      • Upgrade JAVA.NLM on the inventoried server by installing NetWare 6 SP3 or NetWare 5.1 SP6 (which include the same JVM provided with CSP9).

    2. Restart the inventoried server.

    3. Reinstall ZFS3SP2INVSPAGN.CPK.

      For more information on how to install ZFS3SP2INVSPAGN.CPK, see 6.2 Automatic Installation.

    4. Review SYS:\ETC\INVUPDT.LOG to ensure that ZFS3SP2INVSPAGN.CPK has been successfully reinstalled.

    5. (Recommended) Test the execution of the Inventory Agent when the ZENworks_for_Servers service is not running by entering sys:\system\InvAgentStop.ncf at the server console prompt. This command resets the Inventory Agent's internal references and prepares the Inventory Agent for the next invocation.

      If this command is successful, test the Inventory Agent scanning procedure by entering sys:\system\InvAgentStart.ncf at the server console prompt.

      Review SYS:\ETC\INVAGENT.LOG to ensure that the Inventory Agent's scanning has been successfully completed.

      If the log file reports the following message: "The Inventory Agent's scanning procedure successfully completed," it indicates that the scanning is successful, the Inventory Agent software package has been successfully installed, and the Inventory Agent is ready to be enforced by the ZENworks_for_Servers policy engine.

      If the log file reports the following message: "Failure in initialization of the inventory agent" or "Failure in the scanning procedure," refer to "Troubleshooting the Inventory Scanner or Inventory Agent on NetWare Servers" in Server Inventory in the Troubleshooting guide to troubleshoot the problem.


9.3.2 Unable to unload the ZfS 3 Inventory Agent ( INVAID.NLM, MPKSCAN.NLM) during the execution of the Inventory Agent software package ZFS3SP2INVSPAGN.CPK

Although the upgrade is successful, the helper applications could not be unloaded. This error will prevent the new versions from being loaded in the memory.

To resolve the failure:

  1. Unload Java on the inventoried server by entering the following at the command prompt:

    java -exit

    or

    java -killall

    java unload

  2. To test if the Inventory Agent executes when the ZENWORKS_FOR_SERVERS service is not running, at the command prompt enter:

    SYS:\SYSTEM\INVAGENTSTOP.NCF

    This command resets the internal references of the Inventory agent when you invoke the Inventory agent the next time.

  3. If the above command is successful, to test the Inventory Agent scanning procedure, at the command prompt enter:

    SYS:\SYSTEM\INVAGENTSTART.NCF

    Review the SYS:\ETC\INVAGENT.LOG file to ensure that the scanning of the Inventory Agent is successfully completed.

    If the log file reports the following message "The Inventory Agent's scanning procedure successfully completed," the scanning procedure is successful, the Inventory Agent software package has been successfully installed, and the Inventory Agent is ready to be enforced by the ZENWORKS_FOR_SERVERS policy engine.

    If the log file reports a "Failure in initializing of the inventory agent" or "Failure in the scanning procedure" message, see "Troubleshooting the Inventory Scanner or Inventory Agent on NetWare Servers" in the ZENworks for Desktops documentation Web site.


9.3.3 During the creation of the Inventory database or when loading the Inventory database, the "MGR-00072: Warning: Procedure Populate created with compilation errors" message is displayed

This error occurs when you are trying to create a new Inventory database or when you are trying to load the database without running the Inventory service manager. As a workaround, do the following:

  1. Run the Inventory service Manager.

  2. Restart the Inventory database.


9.3.4 The ZFS3SP2INVSPAGN.CPK installation fails if the Inventory agent is still running

If the ZFS3SP2INVSPAGN.CPK upgrade fails, it is probably because the Inventory agent did not stop within the default interval. Because the Inventory agent is still running, the ZFS3SP2INVSPAGN.CPK is unable to unload the ZENworks services.

Check whether the Inventory agent has completed execution and try installing ZFS3SP2INVSPAGN.CPK again. Use the following scenarios to help you resolve this problem.

Scenario 1: Is the Inventory agent execution stopped?

To check whether the Inventory agent has completed execution:

  1. Check the SYS:\ETC\INVAGENT.LOG for the following entries:

    Initiated a cheduled instance of the Inventory Agent

    The Inventory Agent's scanning procedure successfully completed.

  2. Check the SYS:\ETC\INVNATVE.LOG file for the following entry:

    Resetting mutual exclusion state for scanning procedure

  3. If you find the entries above, the scanner has completed execution and you can install the ZFS3SP2INVSPAGN.CPK again.

Scenario 2: The Inventory agent takes a long time to complete its execution

The Inventory agent takes a longer time to complete execution if you have enabled the software scanning option. Because the ZFS3SP2INVSPAGN.CPK update fails if the Inventory agent is running, turn off the scanning on the Windows .EXE version to complete the Inventory agent execution.

To turn off the scanning on the Windows .EXE version:

  1. Edit SYS:\SYSTEM\INVSETUP.INI to add the following entry:

    invSWScanMode=1

    This setting will turn off the scanning of Windows .EXE version information only if the software scan has been enabled. The Windows .EXE version information will not be reported in the software inventory results.

Scenario 3: Is the ZfS 3 SP2 installed for the Inventory agent?

  1. Verify the NetWare registry SOFTWARE\NOVELL\ZENWORKS\ZFS\INVENTORYAGENT for the version information.

    If the version number is 3.0.2, this indicates that the ZfS 3 SP2 is installed.


9.3.5 (New) DBExport fails to run in an isolated mode on Windows NT/2000 servers when other JREs are installed

When you install ZfS 3 SP2 Server Inventory on a Windows NT/2000 server, the installation program will automatically copy JRE 1.3.1 to the server. DBExport might not work if you have installed other JREs separately.

If DBExport fails to run in an isolated mode on Windows NT/2000 servers, do the following:

  1. Open the Windows Registry and note the value of the InvSvrPath as contained in:

    HKEY_LOCAL_MACHINE\Software\Novell\ZENworks

  2. Open the InvSrvPath\SERVER\MWINV\BIN\DBEXPORT.BAT file in a text editor.

  3. Remove the -xbootclasspath flag and its value in the Java command line and save the file.

  4. Open the InvSrvPath\SERVER\MWINV\BIN\JAVADIR.BAT file in a text editor.

  5. Append the following line and save the file:

    setpath=%java_dir%\bin;%java_dir%\njclv2\bin;%path%

  6. To run DBEXPORT.BAT, at the server console prompt enter:

    DBEXPORT configuration_filename.EXP csv_filename.CSV

    where configuration_filename.EXP is an existing file that contains the data export settings, csv_filename.CSV is the filename where the data exported from the database will be stored.


Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (®, TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.


Legal Information

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.

Copyright © 2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

U.S. Patent Nos. 5,910,803 and 6,067,093. US and Foreign Patents Pending.

Novell, NetWare, ConsoleOne, LANalyzer, and ZENworks are registered trademarks of Novell, Inc. in the United States and other countries.

eDirectory, IPX, and NLM are trademarks of Novell, Inc.

All third-party trademarks are the property of their respective owners.