Upgrading Using a Server Software Package

You can use the server software package to upgrade only the following agents of Management and Monitoring Services. Following are the agents you can upgrade:

The following sections provide detailed instructions for installing the software packages on Management and Monitoring Services agents and Installation Log Files:


Automatically Installing Software Packages

Using the TED component of ZENworks for Servers 6.5, 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.

To automatically install the Management and Monitoring Services Agent .cpk file:

  1. Make sure that your server meet the general ZENworks 6.5 Server Management requirements and Policy and Distribution Services is installed on your servers.

  2. Copy the .cpk files at ZENworks Server Management - Software Pkgs \ MMS. Note where they are located, you will need the information when you create the associated Distribution.

  3. Set the Subscriber's Extract schedule.

  4. Create a Distribution for this software package and set the Distribution's Build schedule.

  5. Associate the Distribution with a Channel so that it is sent based on the channel schedule. You might need to create the Channel and set the Channel's Send schedule.

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

  7. For the zfs65_mms_mgmtagnt.cpk file, create and initialize the following package processor variables in the Subscriber objects' properties:

    • On NetWare servers:

      Variable = OLDNMAPATH. For Example, sys:\zfs_agnt

      Function = Defines the path of the older version of the agent is installed.

      Variable = TARGETIP. For Example, 127.0.0.1

      Function = Defines the IP address where you want to send the traps

    • On Windows servers:

      Variable = MMSAGENTPATH. For example, c:\zenworks

      Function = Defines the path to install the agents.

      Variable = REPLACEHOSTMIB. For example, 0

      Function = Defines if Microsoft* hostmib implementation is to be replaced by Novell hostmib implementation (1=Yes, 0=No)

      Variable = TARGETIP. For example, 127.0.0.1

      Function = Defines the IP address where you want to send the traps.

  8. For the zfs65_mms_lanzagnt.cpk file, create and initialize the following package processor variables in the Subscriber objects' properties:

    • On NetWare servers:

      Variable = MMSAGENTPATH. For Example, sys:\zfs_agnt

      Function = Defines the location where the Traffic Analysis agent is installed.

      Variable = TARGETIP. For Example, 127.0.0.1

      Function = Defines the IP address where you want to send the traps

    • On Windows servers:

      Variable = MMSAGENTPATH. For example, c:\zenworks

      Function = Defines the path to install the agents.

      Variable = GTRENDPATH. For example, c:\winnt

      Function = The subdirectory under the Windows directory (c:\winnt) where the Gtrend files are saved.

      Variable = TARGETIP. For example, 127.0.0.1

      Function = Defines the IP address where you want to send the traps.

  9. For the zfs65_mms_trendagnt.cpk file, create and initialize the following package processor variables in the Subscriber objects' properties:

    • On NetWare servers:

      Variable = MMSAGENTPATH. For Example, sys:\zfs_agnt

      Function = Defines the location where the Advanced Trending agent is installed.

      Variable = TARGETIP. For Example, 127.0.0.1

      Function = Defines the IP address where you want to send the traps

    • On Windows servers:

      Variable = MMSAGENTPATH. For example, c:\zenworks

      Function = Defines the path to install the agents.

      Variable = GTRENDPATH. For example, c:\winnt

      Function = The subdirectory under the Windows directory (c:\winnt) where the Gtrend files are saved.

      Variable = TARGETIP. For example, 127.0.0.1

      Function = Defines the IP address where you want to send the traps.

  10. Send the Distribution.

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

  11. Review the log file contained in the Subscriber Servers to verify the success or failure of the installation.

    Several components might fail to install, and the Software Package installation still appears as successful, so you should review the success or failure of each component of the software package to ensure that the components needed on a specific server were installed successfully.


Manually Installing Software Packages

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

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

The following package-specific .bat and .ncf files are available from these three .zip files to launch the Standalone Package Processor:

The following instructions should be repeated for each NetWare or Windows server where you will install the software package:

  1. Make sure your server meet the general ZENworks 6.5 Server Management requirements for the component to be updated.

  2. Unzip the zfs65_mgmtmon_standalonepacpro.zip file to one of the following appropriate location:

    • Windows server: c:\
    • NetWare server: sys:\

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

  3. 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\zfs65
    • NetWare server: sys:\temp\zfs65

    IMPORTANT:  You cannot install on a Linux server.

  4. If JRE 1.3.1 is not installed on the target Windows server, download the JRE and install it.

  5. In the .bat files corresponding to zfs65_mms_mgmtagnt.cpk, zfs65_mms_lanzagnt.cpk, or the zfs65_mms_trendagnt.cpk, change the JRE path to JRE_installation_path\JRE\BIN on each of the target Windows server where JRE 1.3.1 is installed.

  6. Install the agents.

    To install the zfs65_mms_mgmtagnt.cpk:

    • On NetWare, enter the following at the console prompt:

      sys:\temp\zfs65\netware\zfs65_mms_mgmtagnt.ncf

    • On Windows, enter the following at the command prompt:

      c:\temp\zfs65\win\zfs65_mms_mgmtagnt.bat

    To install the zfs65_mms_lanzagnt.cpk:

    • On NetWare, enter the following at the console prompt:

      sys:\temp\zfs65\netware\zfs65_mms_lanzagnt.ncf

    • On Windows, enter the following at the command prompt:

      c:\temp\zfs65\win\zfs65_mms_lanzagnt.bat

    To install the zfs65_mms_trendagnt.cpk:

    • On NetWare, enter the following at the console prompt:

      sys:\temp\zfs65\netware\zfs65_mms_trendagnt.ncf

    • On Windows, enter the following at the command prompt:

      c:\temp\zfs65\win\zfs65_mms_trendagnt.bat

  7. Determine which components of the software package were installed successfully by reviewing the log file created during installation.


Variables Used by NCF and BAT Files for Manual Installation

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.


zfs65_mms_mgmtagnt.cpk

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

  • zfs65_mms_mgmtagnt.ncf

    Variable = OLDNMAPATH where Default Value = sys:\zfs_agnt

    Function = Defines the path of the older version of the agent if installed.

    Variable = TARGETIP where Default Value = 127.0.0.1

    Function = Defines the IP address where you want to send the traps

  • zfs65_mms_mgmtagnt.bat

    Variable = MMSAGENTPATH where Default Value = c:\zenworks

    Function = Defines the complete path to install the agents.

    Variable = REPLACEHOSTMIB where Default Value = 0

    Function = Defines if Microsoft* hostmib implementation is to be replaced by Novell hostmib implementation (1=Yes, 0=No).


zfs65_mms_lanzagnt.cpk

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

  • zfs65_mms_lanzagnt.ncf

    Variable = MMSAGENTPATH where Default Value = sys:\zfs_agnt

    Function = Defines the location where the Traffic Analysis Agent is installed.

    Variable = TARGETIP where Default Value = 127.0.0.1

    Function = Defines the IP address where you want to send the traps

  • zfs65_mms_mgmtagnt.bat

    Variable = MMSAGENTPATH where Default Value = c:\zenworks

    Function = Defines the complete path to install the agents.

    Variable = GTRENDPATH where Default Value = GTREND

    Function = The sub-directory under the Windows directory (c:\winnt) where the Gtrend files are saved.

    Variable = TARGETIP where Default Value = 127.0.0.1

    Function = Defines the IP address where you want to send the traps.


zfs65_mms_trendagnt.cpk

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

  • zfs65_mms_mgmtagnt.ncf

    Variable = MMSAGENTPATH where Default Value = sys:\zfs_agnt

    Function = Defines the location where the Advanced Trending Agent is installed.

    Variable = TARGETIP where Default Value = 127.0.0.1

    Function = Defines the IP address where you want to send the traps

  • zfs65_mms_trendagnt.bat

    Variable = MMSAGENTPATH where Default Value = c:\zenworks

    Function = Defines the complete path to install the agents.

    Variable = TARGETIP where Default Value = 127.0.0.1

    Function = Defines the IP address where you want to send the traps.


Installation Log Files

A log file, created by the package processor, can be found in the following location for zfs65_mms_mgmtagnt.cpk, zfs65_mms_lanztagnt.cpk and zfs65_mms_trendagnt.cpk: