Upgrading Using a Server Software Package

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

IMPORTANT:  If you already have a hook driver installed on the machine where you are upgrading, the hook driver will be uninstalled during the upgrade. If Mirror Driver is not selected during the ZENworks 6.5 installation, optimization is disabled for remote sessions and consequently, the performance of the remote session degrades.

NOTE:  Apply zfsrmir2.cpk through Hotpatch24, if you have upgraded to ZfS 3.0.2 from ZfS 3.0 using a Server Software Package. After applying Hotpatch24, you can upgrade to ZENworks 6.5 Server Management using a Server Software Package.You need not apply HotPatch24 before upgrading to ZENworks 6.5 Server Management using a Server Software Package if you have upgraded to ZENworks for Server 3.0.2 from ZENworks for Servres 3.0 using the program CD, or if you have a fresh installation of ZENworks for Servers 3.0.2. For more information, see TID 10096514 in the Novell Support Knowledgebase.


Automatically Installing Software Packages

Using the Tiered Electronic Distribution (TED) component of ZENworks for Servers 6.5, you can automatically distribute and upgrade 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.

Make sure you have completed the following prerequisites for automatic installation:

To automatically install the Remote Management Agent .cpk file:

  1. Copy the .CPK files at ZENworks Server Management - Software Pkgs \ InvRM. Note where they are located for when you create the associated Distribution.

  2. Set the Subscriber's Extract schedule.

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

  4. 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.

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

  6. On a Windows server, for the zsm65_remmgmt.cpk file, create and initialize the following package processor variable in the Subscriber objects' properties:

    Variable = MIRROR

    If the MIRROR variable value is set to YES, the MIRROR driver is installed, if the value is set to NO, it is not installed.

    IMPORTANT:  The Mirror driver (recommended) provides video adapter independence and co-existence with other Remote Control solutions. This is not yet signed by Microsoft. Installation will overrides any check for it and suppresses any message from Windows.

    For External Subscribers, put the variable in the tednode.properties file.

  7. Send the Distribution.

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

  8. 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 will 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 package to a server that is not running Subscriber and the Policy/Package Agent.

Before you begin manual installation:

To manually install the Remote Management Agent .cpk file:

  1. Unzip the InvRemStandAlonePacPro.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.

  2. 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

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

  4. In the .bat files corresponding to zsm65_remmgmt.cpk, change the JREROOT variable path to JRE_installation_path\JRE\BIN on each of the target Windows server where JRE 1.3.1 is installed.

  5. Point the CPKTEMP variable in the batch file to the location of the installation directory. For example:

    Windows server: CPKTEMP = c:\temp\zfs65

    NetWare server: CPKTEMP = sys:\temp\zfs65

  6. Install the agents.

    To install the zsm65_remmgmt.cpk on Windows server, enter the following at the command prompt: c:\temp\zfs\win\zfs65_mms_mgmtagnt.bat

    To install the zsm65_remmgmt.cpk on Windows server, enter the following at the command prompt: sys:\temp\zfs65\zfs65_mms_mgmtagnt.ncf

  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 variable is grouped under the software package headings for the applicable .bat and .ncf files:

zsm65_remmgmt.cpk

This software package for Server Management Agent uses variables for the following .bat or .ncf files:

zsm65_remmgmt.bat

Variable = MIRROR

If the MIRROR variable value is set to YES, the MIRROR driver is installed, if the value is set to NO, it is not installed.

IMPORTANT:  The Mirror driver (recommended) provides video adapter independence and co-existence with other Remote Control solutions. This is not yet signed by Microsoft. Installation will override any check for it and suppresses any message from Windows.


Installation Log Files

The following log files contain detailed information about the success of the Remote Management installation:

For Windows:

%WINDIR%\CPK65Logs\Cpk65_Agnt.LOG - Install /file changes log

For NetWare:

ted.log file in the TED_PATH/dist directory