Items marked (New) have been added to this version of the Readme after ZfS 3 SP1 was released. The Readme was updated in the following sections on the dates indicated:
October 21, 2002 = 6.6.4
November 11, 2002 = 2.1.3 (steps 9 and 10)
November 20, 2002 = 2.3.3
1.0 Overview
1.1 Documentation
1.2 The Purpose of Support Pack 1
1.3 Installation Issues and Guidelines
2.0 Installation
2.1 Automatic installation of software packages
2.2 Manual installation of software packages
2.3 Installation of snap-ins and plug-ins
3.0 Management Site Services (ZFS3SP1SITESVR.CPK)
4.0 Management Agent (ZFS3SP1MGMTAGNT.CPK)
6.0 Policy and Distribution Services (ZFS3SP1POLYDIST.CPK)
7.0 Inventory Server, Server Inventory ConsoleOne, and Remote Management ConsoleOne (ZFS3SP1INVREM.CPK)
8.0 Inventory Agent (ZFS3SP1INVSPAGN.CPK)
9.0 Remote Management (ZFS3SP1REMMGMT.CPK)
10.0 Variables Used by NCF and BAT Files for Installing Manually
The following sections provide an overview of the Novell® ZENworks® for Servers (ZfS) 3 Support Pack 1 (SP1).
This Readme is the only documentation provided with the SP1 download. Installation and usage instructions for the SP1 udpates are contained in the Readme's sections.
The documentation for ZfS 3 at www.novell.com/documentation/lg/zfsi/index.html has been updated to reflect the changes made with installation of this support pack.
This SP1 Readme also exists at the above URL, and can be updated at any time.
SP1 provides updates and bug fixes for ZfS 3 and interoperability with ZENworks for Desktops (ZfD) 4.
The support pack is contained in two self-extracting files, ZFS3SP1.EXE and NICI24CPK.EXE, that are downloaded separately. The ZFS3SP1.EXE file contains this Readme and the .CPK, .ZIP, and .EXE files you need for updating ZfS 3 to SP1. The NICI24CPK.EXE file contains the NICI24.CPK file needed to update encryption.
ZfS 3 SP1 provides updates and bug fixes for:
Management and Monitoring Services
Remote Management
Policy and Distribution Services, including:
Server Inventory, including:
The following are reasons why ZfS 3 SP1 is necessary for interoperability between ZfS 3 and ZfD 4:
To resolve this issue, you must install ZfS 3 SP1 on the ZfS 3 Inventory server.
You can individually update the ZfS components that you have installed in your system. For more information on these components, see Sections 3 through 9.
For installation instructions, see Section 2.
The following sections provide important information about installing SP1:
Installation Methods: You can install the software packages contained in the support pack either using Tiered Electronic Distribution (TED) or the Standalone Package Processor (included in the support pack), depending on whether you have Policy and Distribution Services running on the target Subscriber servers.
For more information, see Section 2.
Installing ZfS with ZfD: ZfS 3 SP1 provides enhanced interoperability with ZfD 4. The two products must be installed in a certain order so that the two products will work together. For important information concerning the installation order for ZfS 3, ZfS 3 SP1, and ZfD 4, see "Interoperability Between ZENworks for Servers and ZENworks for Desktops" in the Installation guide.
Installing ZfS 3 SP1 on ZfS 3 Cluster Nodes: All the ZfS 3 nodes in a clustered environment must be upgraded to ZfS 3 SP1.
For more information on the automatic method, see Section 2.1.
Distributor Servers First: You must update all Distributor servers to SP1 before updating the Subscriber servers, because ZfS 3 SP1 Subscribers cannot receive Distributions from ZfS 3 (non-SP1) Distributors.
Installation Order of Support Pack Contents: Some software packages must be installed before others when using the automatic installation method. For more information, see Section 2.1.2.
Single .CPK File per Distribution Object: Because the software packages unload Java*, they cannot be combined into one Distribution object. Java would need to be running for each software package to be installed. This information is covered in the steps.
Processing Software Packages Sequentially: A software package must have completed its installation before you can begin the installation of the next software package. Again, this is because of Java being unloaded and reloaded. Therefore, SP1's Software Package Distributions cannot be processed at the same time in a given Channel. This information is covered in the steps.
It does not matter whether the SP1 software packages (.CPK files) or the SP1 ConsoleOne snap-ins are installed first. However, the ZfS 3 SP1-updated software must be managed by the ZfS 3 SP1 snap-ins.
The following issues relate to the order for installing the ConsoleOne snap-ins for the ZfS 3, ZfD 4, and ZfS 3 SP1 products:
ZfS 3 First (preferred installation order): If you installed the ZfS 3 snap-ins, then the ZfD 4 snap-ins, nothing will be broken in ZfS 3, except that you will not be able to manage ZfS 3 Server Inventory. However, Server Inventory will continue to work according to its configuration before installing ZfD 4, because a ZfD 4 installation allows the ZfS 3 Server Inventory and ZfD 4 Workstation Inventory functionalities to coexist on the same server. For the interoperability between ZfS 3 and ZfD 4 that SP1 provides, and to be able to manage Server Inventory, you must install the ZfS 3 SP1 snap-ins.
ZfD 4 First (scenario A): If you installed the ZfD 4 snap-ins, then installed the ZfS 3 snap-ins, you will not be able to set policies or view data relating to ZfD 4. Therefore, you must install the ZfS 3 SP1 snap-ins to restore that functionality, and to add the new interoperability between ZfS 3 and ZfD 4.
ZfD 4 First (scenario B): If you installed the ZfD 4 snap-ins, but did not install the ZfS 3 snap-ins during installation of ZfS 3, you can add the new interoperability between ZfS 3 and ZfD 4 by simply installing the ZfS 3 SP1 snap-ins after updating ZfS 3 to SP1. The ZfS 3 SP1 snap-ins contain all of the functionality and files of the ZfS 3 snap-ins, plus the bug fixes and interoperability for ZfS 3 and ZfD 4.
There are no issues with the order of installing the various ZfS 3 SP1 snap-ins to ConsoleOne that are provided in the support pack.
Performing a top-down deployment of Server Inventory:
The following highlight the important issues for interoperability of ZfS 3 Server Inventory with ZfS 3 SP1 Server Inventory:
However, you can use ConsoleOne with just ZfS 3 Server Inventory snap-ins to configure only ZfS 3 Inventory policies and to access only the ZfS 3 Inventory database. You cannot use this instance of ConsoleOne to configure the ZfS 3 SP1 Inventory policies or to access the ZfS 3 SP1 Inventory database.
Inventory Agents of one version of ZfS 3 can send scans to Inventory servers of the other version of ZfS 3:
Except as noted, the ZfS 3 or ZfS 3 SP1 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.
Management and Monitoring Services:
SiteServer:
Access the NetWare® registry.
NMA: Access the NetWare registry.
NTMA: Access the Windows* registry.
Policy and Distribution Services:
The first method can be used for all servers where Policy and Distribution Services is running. The other two methods will work where Policy and Distribution Services is not running.
All Platforms: NetWare, Windows, Linux, and Solaris Servers:
This method works for all servers where Policy and Distribution Services is running. You perform it using iManager.
Policy and Distribution Services must be running on Linux and Solris servers in order to determine which version of ZfS 3 is currently installed.
Using the ZfS Management role in iManager, do the following:
"Support Pack 1" will be displayed in the information for the Version field if SP1 has been installed.
HINT: This method will work for servers of any supported platform where Policy and Distribution Services is running.
NetWare Servers: At the server's console prompt, enter: installation_path\ZENWORKS\ZFSVERSION TED
where installation_path is the location you used to install ZfS, such as SYS:. If SP1 is installed, one of the lines will read: If SP1 is not installed, the line will read: If Policy and Distribution Services is running on the server, enter VERSION at the ZfS console prompt. If SP1 is installed, the first line will read:VERSION: 3.0 SUPPORT PACK: 1
VERSION: 3 SUPPORT PACK: 0
ZENworks for Servers 3 Support Pack 1
Windows Servers: Access the Windows registry.
For ZfS 3 only, the registry key stops at ZENworks and does not include a Version entry.
Inventory Server:
NetWare Servers:
Access the NetWare registry.
Windows Servers: Access the Windows registry.
Inventory Agent:
Remote Management:
NetWare Servers:
Access the NetWare registry.
Windows Servers: Access the Windows registry.
The following sections describe the content of the support pack.
The following file and directory structure will be placed in the temporary directory where you extract the ZFS3SP1.EXE file. For example:
TEMP\
|__README_ZFS3SP1.TXT (this Readme file in .TXT format)
|__README_ZFS3SP1.HTML (this Readme file in .HTML format)
|__INVREMMGMT\
|__InvRem_StandAlonePacPro.zip
|__ZFS3SP1C1Snap_Inv.zip
|__ZFS3SP1C1Snap_RemMgmt.zip
|__ZFS3SP1InvRem.cpk
|__ZFS3SP1InvSPAgn.cpk
|__ZFS3SP1RemMgmt.cpk
|__MGMTMON\
|__MgmtMon_StandAlonePacPro.zip
|__ZFS3SP1C1Snap_MgmtMon.zip
|__ZFS3SP1MgmtAgnt.cpk
|__ZFS3SP1SiteSvr.cpk
|__POLYDIST\
|__ExtSch31.exe
|__nici24.cpk (from a separate download)
|__PolyDist_StandAlonePacPro.zip
|__ZFS3SP1.sch
|__zfs3sp1polydist.cpk
|__ZFS3SP1PolyDistPlugins.zip
|__ZFS3SP1PolyDistSnapins.zip
Each of the seven Server Software Packages 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 ZFS3SP1INVSPAGN.CPK, the software package will fail if it does not find that the ZfS 3 Inventory Agent exists on the server.
IMPORTANT: During the software package installation process, the rollback feature is disabled. Therefore, you cannot uninstall the support packs after they are installed.
The software packages contained in the support pack update the following ZfS components:
ZFS3SP1SITESVR.CPK
Contains the Support Pack update for the Management Site Server. For more
information, see Section 3.0.
ZFS3SP1MGMTAGNT.CPK
Contains the Support Pack update for the Management Agent. For more information,
see Section 4.0.
NICI24.CPK
Contains an update of the NICI software for enhanced encryption capability
with ZfS 3 SP1. You need to install this software package only if you
want to encrypt your Distributions for Solaris or Linux servers. For more
information, see Section 5.0. This is a separate
download.
ZFS3SP1POLYDIST.CPK
Contains the Support Pack update for the Policy and Distribution Services
component. For more information, see Section 6.0.
ZFS3SP1INVREM.CPK
Contains the Support Pack update for the Server Inventory component and
the ConsoleOne snap-ins for the Server Inventory and Remote Management components.
For more information, see Section 7.0.
ZFS3SP1INVSPAGN.CPK
Contains the Support Pack update for the Inventory Agent on NetWare and
Windows NT*/2000 servers. For more information, see Section
8.0.
ZFS3SP1REMMGMT.CPK
Contains the Support Pack update for the Remote Management Agent on NetWare
and Windows NT/2000 servers. For more information, see Section
9.0.
SP1 contains the following files in addition to the software packages:
These are provided as an option for installing the software packages manually per server, rather than to use TED to distribute them. The Standalone Package Processor is required where Policy and Distribution Services agents are not running for both NetWare and Windows NT/2000. However, it can be used on servers where Policy and Distribution Services agents are running to manually install the software packages. Note that the Standalone Package Processor cannot be used to install the ZFS3SP1INVSPAGN.CPK file. This software package requires distribution using TED. It is also recommended that NICI24.CPK be installed using TED.
The following sections provide detailed instructions for installing the software packages, the ConsoleOne snap-ins, and iManager plug-ins.
The three installation methods for installing the updates included in this support pack are:
Automatic installation
of software packages (see Section 2.1)
Use this method to have TED distribute the software packages containing ZfS 3 SP1 to multiple servers that are running the Policy and Distribution Services software.
You must use this method for installing software packages to Linux or Solaris severs, because TED is required for installing to those servers. You must also use this method for installing NICI and the Inventory Agent.
Manual installation of
software packages (see Section 2.2) You cannot use this method for the NICI24.CPK and ZFS3SP1INVSPAGN.CPK files. You also cannot use this method for Linux or Solaris servers, because TED is required for installing to those servers.
Use this method to install a software package to individual servers that do not have the Subscriber (TED) software installed. It uses the Standalone Package Processor utility provided in the support pack to install the software package.
Installation of snap-ins
and plug-ins (see Section 2.3)
Use WinZip or another file extraction utility to install the ZfS 3 SP1 ConsoleOne snap-ins from .ZIP files to instances of ConsoleOne on workstations, or to install the ZfS 3 SP1 iManager plug-ins from the .ZIP file to a Web server.
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 Section 2.1.2 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.
For the software packages that you plan to install, we recommend that they be installed in the following order:
This software package is only required if you will encrypt your Distributions for Solaris or Linux servers.
IMPORTANT: This software package must be installed before the software packages listed in item 3 below, because ZFS3SP1POLYDIST.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 SP1 before updating the Subscriber servers to SP1.
The order for installing these three software packages does not matter. However, they each require that ZFS3SP1POLYDIST.CPK is installed first to update the Subscriber software on the server so that TED can be used to install those software packages.
The order for installing the remaining software package files does not matter.
The remaining software packages do not require that ZFS3SP1POLYDIST.CPK be installed first.
To install a specific software package automatically:
Download the self-extracting ZFS3SP1.EXE file to a temporary directory on a Windows workstation you will use to install the support pack.
Run ZFS3SP1.EXE to extract the support pack software files into the temporary directory.
See Section 1.4.1 for information on the directory structure that is created where the files are extracted.
Copy the .CPK files to the Distributor's file system and make a note where they are located for when you create the associated Distribution.
Set the Subscriber's Extract schedule.
Use care in setting your Subscriber's Extract schedule.
If the schedule is set to Run Immediate, 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.
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 SP1 software packages. The reason is that installation of 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 the ZFS3SP1POLYDIST.CPK must be built, sent, extracted, and installed before sending any other Distributions containing other ZfS 3 SP1 software packages.
For the NICI24.CPK Distribution, make sure in addition to installing NICI to Solaris or Linux servers that you also update all existing instances of NICI; 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 Administration guide.
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 SP1 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 SP1 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.
Associate the Subscribers that you want to receive this software package with the Channel.
For the ZFS3SP1INVSPAGN.CPK file only, create and initialize the following package processor variables in the Subscriber objects' properties:
INVPATH is the installation path of the Inventory Agent on a NetWare server. For example, SYS:\ZENWORKS\INV.
WININVPATH is the installation path of the Inventory Agent
on a Windows NT/2000 server. For example, C:\ZENWORKS\INV.
IMPORTANT: You must create and initialize the Inventory Agent variable for the ZFS3SP1INVSPAGN.CPK installation to be successful.
See "Using Variables" under "Policy and Distribution Services" in the ZfS 3 Administration guide for details on defining variables in Subscriber objects.
(New) For the ZFS3SP1SITESVR.CPK file only, create and initialize the following package processor variables in the Subscriber objects' properties:
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 ZFS3SP1SITESVR.CPK installation to be successful.
See "Using Variables" under "Policy and Distribution Services" in the ZfS 3 Administration guide for details on defining variables in Subscriber objects.
(New) For the ZFS3SP1MGMTAGNT.CPK file only, create and initialize the following package processor variables in the Subscriber objects' properties:
NMAPATH is the installation path of the Management Agent on a NetWare server. For example, ZFS_AGNT.
TARGETIP is the IP address for where to send traps. For example, 127.0.0.1..
VOLUMENAME is the installation volume of the Management Agent on a NetWare server. For example, SYS.
ZFS3AGENTPATH is the installation path of the Management
Agent on a Windows NT/2000 server. For example, C:\. TEMPDIR defines the Windows TEMP directory path of the
Management Agent on a Windows NT/2000 Server. For example, C:\TEMP.
IMPORTANT: You must create and initialize the Management Agent variables for the ZFS3SP1MGMTAGNT.CPK installation to be successful.
See "Using Variables" under "Policy and Distribution Services" in the ZfS 3 Administration guide for details on defining variables in Subscriber objects.
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 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.
Determine which components of the software package were installed successfully by using one of the following methods:
You can use the Tiered Electronic Distribution view in iManager to see information for every software package that was installed.
If you use TED for installation, you can use ZfS reporting to verify the success or failure of individual components of a software package.
You can use log files contained on the Subscriber Servers to verify the success or failure.
For a list of the log files and their locations, see Section 2.4.
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. If, however, you installed ConsoleOne snap-in components on local workstations, you must upgrade those workstations manually using the manual process outlined under Section 2.3.
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:
Requirements: Your servers must meet the general ZfS 3 requirements for the component to be updated. See the Readme sections 3 through 9 corresponding to the software package you are installing. Also, you cannot manually install the support pack to Linux or Solaris servers, because TED is required for installing to those servers.
Installed Components: 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 ZFS3SP1INVSPAGN.CPK, the software package will fail if it does not find the ZfS 3 Inventory Agent on the server.
Variables: You must have configured the variables required for the component. See the applicable Section (3 through 9) for your component for instructions on setting its variables.
IMPORTANT: If you have installed the ZfS Management and Monitoring Services software in a different directory other than the default SYS:\ZENWORKS directory, modify the ZFS3SP1SITESVR.NCF file to contain the new directory information.
Software packages that you plan to install manually can be installed in any order.
The following instructions should be repeated for each NetWare or Windows server where you will install the support pack manually.
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.
Download the self-extracting ZFS3SP1.EXE file to a temporary directory on a Windows workstation.
For installation to a NetWare server, run ZFS3SP1.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 install manually to a Linux or Solaris server.
See Section 1.4.1 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 SP1 updates. For NetWare 5.0 servers, there is a Management Agent update contained the ZFS3SP1MGMTAGNT.CPK file. However, you cannot install ZfS 3 SP1 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. See TID 10074783 for the download and installation instructions.
For installation to a Windows server:
Copy the self-extracting ZFS3SP1.EXE file to the Windows server where you will install the support pack.
Run ZFS3SP1.EXE to extract the support pack software files to a temporary directory at the root of the C: drive.
See Section 1.4.1 for information on the directory structure that is created where the files are extracted.
Before manually installing the ZFS3SP1INVREM.CPK, ZFS3SP1MGMTAGNT.CPK, or ZFS3SP1REMMGMT.CPK files, do the following as applicable:
If JRE 1.3 was previously installed on the Windows server (such as when you originally installed ZfS 3 to the server): Before manually installing any CPK, edit the corresponding .BAT file to set the JRE path to JRE_installation_path\JRE\BIN.
If JRE 1.3 has not been installed on the Windows server: Do the following before manually installing any CPK:
JRE_installation_path\JRE\BINLocate and unzip the INVREM_STANDALONEPACPRO.ZIP, MGMTMON_STANDALONEPACPRO.ZIP, or POLYDIST_STANDALONEPACPRO.ZIP file to the following appropriate location:
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.
Copy the .CPK file to be manually installed to the TEMP\ZFS3SP1 directory. For example:
For the location of the .CPK file, see Section 1.4.1.
For the location of the .BAT or .NCF files, see Step 4 above.
IMPORTANT: For the ZFS3SP1REMMGMT.CPK file, initialize the ZFS3_RMINSTALL_PATH variable contained in the ZFS3SP1REMMGMT.BAT file on the server. For more information, see Section 10.1.
From the temporary directory, run the .BAT or .NCF file associated with the software package you want to install:
On NetWare, enter the following at the server prompt:
SYS:\TEMP\ZFS3SP1\NETWARE\ZFS3SP1REMMGMT.NCF
On Windows, run the following:
C:\TEMP\ZFS3SP1\WIN\ZFS3SP1REMMGMT.BAT
NOTE: If you have installed the ZFS3SP1REMMGNT.CPK on a path other than the default on Netware or Windows, you must specify the new path while running the ZFS3SP1REMMGMT.CPK as mentioned above.
On NetWare, enter the following at the server prompt: SYS:\TEMP\ZFS3SP1\NETWARE\INVRMSP1.NCF
On Windows, run the following: C:\TEMP\ZFS3SP1\WIN\INVRMSP1.BAT
SYS:\TEMP\ZFS3SP1\NETWARE\ZFS3SP1SITESVR.NCF
You must modify the ZFS3SP1SITESVR.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"
On NetWare, enter the following at the server prompt: SYS:\TEMP\ZFS3SP1\NETWARE\ZFS3SP1MGMTAGNT.NCF
On Windows, run the following: C:\TEMP\ZFS3SP1\WIN\ZFS3SP1MGMTAGNT.BAT
On NetWare, enter the following at the server prompt: SYS:\TEMP\ZFS3SP1\NETWARE\ZFS3SP1POLYDIST.NCF
On Windows, run the following: C:\TEMP\ZFS3SP1\WIN\ZFS3SP1POLYDIST.BAT
After installing the software package, review 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 Section 2.4.
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.
To install the SP1-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 gidelines on installing the ZfS 3 ConsoleOne snap-ins, see Section 1.3.3.
The following .ZIP files contain ZfS snap-ins or plug-ins for SP1:
TEMP\MGMTMON\ZFS3SP1C1SNAP_MGMTMON.ZIP
ConsoleOne snap-ins for Management and Monitoring Services to be installed on a Windows workstation.
TEMP\POLYDIST\ZFS3SP1POLYDISTSNAPINS.ZIP
ConsoleOne snap-ins for Policy and Distribution Services to be installed on a Windows workstation.
TEMP\POLYDIST\ZFS3SP1POLYDISTPLUGINS.ZIP
Updated iManager plug-ins for Policy and Distribution Services to be installed
on the Web server.
TEMP\INVREMMGMT\ZFS3SP1C1SNAP_INV.ZIP
ConsoleOne snap-ins for Server Inventory to be installed on a Windows workstation.
TEMP\INVREMMGMT\ZFS3SP1C1SNAP_REMMGMT.ZIP
ConsoleOne snap-ins for Remote Management to be installed on a Windows workstation.
This section applies only to the following .ZIP files:
To install the snap-ins to ConsoleOne on a workstation:
Close ConsoleOne.
The instance of ConsoleOne where you want to install the snap-ins cannot be running.
Open a .ZIP file in WinZip or other file extraction program.
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 ZFS3SP1POLYDISTSNAPINS.ZIP is installed.
After installing the ConsoleOne snap-ins using the ZFS3SP1C1SNAP_REMMGMT.ZIP or ZFS3SP1C1SNAP_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 SP1 to work with ZfD 4:
Modify the insver parameter in QUERY.PROPERTIES to contain any of the following values:
Modify the rmver parameter in QUERY.PROPERTIES to contain any of the following values:
This section applies only to the TEMP\POLYDIST\ZFS3SP1POLYDISTPLUGINS.ZIP file.
iManager plug-ins are not supported on NetWare 5.1.
(New) IMPORTANT: You must install the plug-ins to iManager contained in this zip file over the plug-ins that were installed from the ZENworks for Servers 3 product CD. The ZFS3SP1POLYDISTPLUGINS.ZIP file only contains the plug-in files that were updated for SP1.
To install the plug-ins to iManager on the Web server:
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 that a drive mapping is not needed.
Stop Tomcat.
Open ZFS3SP1POLYDISTPLUGINS.ZIP in WinZip or other file extraction program.
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.
Restart Tomcat.
A log file, created by the package processor, can be found in the following locations:
ZFS3SP1INVREM.CPK (for Inventory Server only):
SYS:\ETC\INVSVR.LOG
or
%WINDIR%\INVSVR.LOG
where %WINDIR% typically resolves to C:\WINNT.
If you have installed the Inventory Server only, the INVSVR.LOG file provides details about the success or failure of the support pack installation.
ZFS3SP1INVREM.CPK (for Inventory Server and ConsoleOne snap-ins for Server Inventory and Remote Management): or where%CPK_WORKING_DRIVE_NT% typically resolves to C:. The ZENCPK.LOG file provides information about the existing installation on which the software package is being executed.SYS:\INVTEMP\ZENCPK.LOG
%CPK_WORKING_DRIVE_NT%\INVTEMP\ZENCPK.LOG
ZFS3SP1INVSPAGN.CPK (for Inventory Agent): or This file provides detailed information about the success of the Inventory Agent installation.SYS:\ETC\INVUPDT.LOG
C:\WINNT\INVUPDT.LOG
ZFS3SP1MGMTAGNT.CPK (for Management Agent): or This file contains detailed information about the success of the Management Agent installation.SYS:\ETC\ZFS3SP1MGMTAGNT.LOG
C:\WINNT\ZFS3SP1MGMTAGNT.LOG
ZFS3SP1POLYDIST.CPK (for Policy and Distribution Services): or This file contains detailed information about the success of the Policy and Distribution Services installation.SYS:\TEMP\ZFS3SP1\NETWARE\UPGRADE.LOG
C:\TEMP\ZFS3SP1\WIN\UPGRADE.LOG
ZFS3SP1REMMGMT.CPK (for Remote Management Agent): or This file contains detailed information about the success of the Remote Management installation.SYS:\ETC\REMUPDT.LOG
C:\WINNT\REMUPDT.LOG
ZFS3SP1SITESVR.CPK (for Management Site Server): This file contains detailed information about the success of the Management Site Server installation.SYS:\ETC\SITESERVER.LOG
The following sections list the information you need to install the Management Site Services update component (ZFS3SP1SITESVR.CPK) of this support pack.
Fulfill the following prerequisites before installing the ZFS3SP1SITESVR.CPK.
To prepare your system for installing the software packages:
Close ConsoleOne on the Novell ClientTM 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.
Shut down the Management Site Server by entering the following at the server prompt:
UNMW
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 Administration guide for more information.
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 Section 10.0 for a complete list of variables used by the various software packages. See "Using Variables" under "Policy and Distribution Services" in the ZfS 3 Administration guide for details on defining variables in Subscriber objects.
To prepare for using variables during software package installation:
You must modify the ZFS3SP1SITESVR.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"
To install the ZFS3SP1SITESVR.CPK:
Choose whether to install ZFSSP1SITESVR.CPK automatically or manually.
For automatic installation, follow the instructions in Section 2.1. You do not need to continue with the remaining steps.
For manual installation, follow the instructions in Section 2.2, then continue with the Step 2.
Restart the Management Site Server component.
Restart ConsoleOne to access the updated Management console.
The following sections list the resolved software issues that are provided in the ZFS3SP1SITESVR.CPK support pack.
The following sections list the information you need to install the Management Agent update component (ZFS3SP1MGMTAGNT.CPK) of this support pack.
Ensure that you install the ZFS3SP1POLYDIST.CPK before installing the ZFS3SP1MGMTAGNT.CPK.
Choose whether to install ZFSSP1SP1MGMTAGNT.CPK automatically or manually.
For automatic installation, follow the instructions in Section 2.1. You do not need to continue with Step 2.
For manual installation, follow the instructions in Section 2.2, then continue with Step 2.
If you have installed the Management Agent in a directory other than the default, do the following:
This software package updates NICI to a newer version that provides encryption for Solaris and Linux servers.
You only need to install NICI24.CPK if you are encrypting Distributions for Solaris and Linux servers.
IMPORTANT: Make sure you update all servers where NICI was previously installed. If you install NICI24.CPK only to Solaris and Linux servers and still have the older version of NICI installed on NetWare or Windows servers, encryption will not work. All instances of NICI in your network must be the same version.
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 this software package.
To install NICI24.CPK:
Choose to install NICI24.CPK automatically.
For automatic installation, follow the instructions in Section 2.1. This .CPK file cannot be installed manually.
After installation, review the ZFSINIT.LOG file to ensure that the installation was successful.
The following sections list the information you need to install the Policy and Distribution Services update component (ZFS3SP1POLYDIST.CPK) of this support pack.
Fulfill the following prerequisites before installing the Policy and Distribution Services CPK:
Before installing the ZFS3SP1POLYDIST.CPK, you must first extend the schema on the Novell eDirectoryTM trees where you previously extended the schema for ZfS 3.
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 EXTSCH31.EXE file is placed in the temporary directory when you extract the ZFS3SP1.EXE file.
Open a DOS window.
Run the EXTSCH31.EXE file using the following syntax:
EXTSCH31.EXE Tree_Name ZFS3SP1.SCHTo install the ZFS3SP1POLYDIST.CPK file, you must use the automatic installation option (see Section 2.1), because you already are running the TED and Distributor components required for this installation method.
If you have a Subscriber running on the same server as the Distributor, do not include this Subscriber in the same Channel as subordinate Subscribers. If the Subscriber is running on the same server as the Distributor, this Subscriber will receive the Distribution and never forward it. Another work around is to set the Extract schedule on this Subscriber to "Never" so that you can process the .CPK file manually after it has already sent the Distribution to the other subordinate Subscribers.
After installing the Policy and Distribution services .CPK file, you must manually restart Server Inventory and Remote Management services.
The version of the JVM that shipped with NetWare 6 SP2 is required if you want to create and distribute Distributions larger than 4 GB.
This newer JVM uses 64-bit I/O that provides self-updating capability. This allows you to have Distributions larger than 4 GB.
Distributions greater than 4 GB are not supported on NetWare 5.1.
This JVM is not shipped with ZfS 3 SP1. You must obtain it and other required operating system changes for the JVM by installing NetWare 6 SP2.
Choose to install ZFS3SP1POLYDIST.CPK automatically or manually.
For automatic installation, follow the instructions in Section 2.1, then continue with the Step 2.
IMPORTANT: If ZfS 3 Policy and Distribution Services has been installed to a server running ZfD 4 Workstation Inventory, Policy and Distribution Services will not work until you apply ZFS 3 SP1. You cannot use the automatic installation method to install the ZFS3SP1POLYDIST.CPK file on the servers. You must use the manual installation method described in Section 2.2 of this Readme.
For manual installation, follow the instructions in Section 2.2, then continue with the Step 2.
If you will be using a Software Package type of Distribution and you have upgraded your Subscribers to SP1, you must also upgrade your Distributors to SP1 before sending Software Package Distributions.
If the Distributor is not upgraded, you will receive an ArrayIndexOutOfBoundsException on the Subscribers receiving the Software Package Distribution.
Restart Management and Monitoring Services if you unloaded it to install ZFS3SP1POLYDIST.CPK.
If Server Inventory was running on the server, you might need to restart it.
The following sections list the new features provided after installing the ZFS3SP1POLYDIST.CPK.
You can now create Desktop Application types of Distributions in iManager.
Desktop Application type Distributions created in ZfS 3 SP1 will work with ZfD 4.
You can now revoke an individual policy using an option in iManager.
NetWare 6 SP2 contains the JVM update that provides support for 64-bit I/O, which allows SP1 to provide support for Distributions greater than 4 GB on NetWare 6 servers.
For more information, see Section 6.3.1.
The new NICI (version 2.4) included in SP1 provides encryption capability for the Solaris and Linux platforms. For more information, see Section 5.0.
The previous limit of approximately 240 files/folders that could be selected for a File type of Distribution has been removed in SP1.
The following sections list the software issues that are resolved in the ZFS3SP1POLYDIST.CPK provided in this support pack.
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).
Prior to ZFS 3 SP1, 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.
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.
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 (?).
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.
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.
TED object names with single quotation marks can now be written to the Sybase database.
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.
Previously, if a Local File Copy component in a software package failed, the entire component should have failed. Now, the failure of a Local File Copy action will cause the entire component to fail.
After installing SP1, the ZfS 3 and ZfD 4 software can be started in any order.
Special characters, such as the ampersand (&), are now handled correctly by the iManager plug-ins.
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.
Log files are now updated by having older entries deleted when you specify to delete entries older that nnn days in the ZFS Policy.
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. Use of the -hosts switch for all platforms has been documented in the ZfS 3 Installation guide.
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.
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.
Compilation time for software packages has been improved dramatically when large numbers of files are used.
You can now set the version and major or minor attributes in a software package for the Windows platform.
The second time a Desktop Application Distribution was sent, the Path to Executable field was being corrupted. This has been fixed.
Previously, the second time a Desktop Application type of Distribution was sent, distribution rights were being deleted instead of added. This has been fixed.
ConsoleOne snap-ins for ZfS 3 were causing UI information for ZfD 3.2 snap-ins to be lost. For example, a message stating "Policies enabled on this page will be applied only on workstations that have been upgraded to ZENworks for Desktops 4. To set policies for workstations using earlier versions of ZENworks for Desktops, 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.
Previously, after an RPM Distribution had been saved, you could not edit the Distribution and add installation parameters. This has been fixed.
When using parameters with RPM Distributions, the Distributions are now extracted and installed successfully.
When displaying the event log in iManager, the icons to the left are now displayed. Previously, the default graphic for missing icons was displayed.
When processing a software package with a registry requirement, the package would generate a false positive, meaning that the registry requirement passed, and the package or component would be processed when it should have failed. This has been fixed.
The following sections list the software issues that are unresolved in the ZFS3SP1POLYDIST.CPK provided in this support pack. These issues are new to ZfS 3 as a result of SP1.
The ZfS 3 SP1 software packages unload and restart Java as part of the installation process. However, on a NetWare 6 SP2 server with Policy and Distribution Services and Server Inventory components installed, if Server Inventory is running when ZFS3SP1POLYDIST.CPK is installed, it might not be restarted after the ZFS3SP1POLYDIST.CPK installation has completed.
You can manually restart Server Inventory after the ZFS3SP1POLYDIST.CPK installation has completed. Or, you can avoid this problem by updating your JVM to the latest JVM 1.3.1, which is available for download from the Novell Support Connection by searching for TID 2963237.
ZfS 3 SP1 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 SP1 software packages simultaneously (such as by associating them with the same Channel), it is likely that one or more of the Software Package Distributions may fail on installation.
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 SP1 from a Software Package Distribution.
This is applicable only to Distributions created for installing SP1 components, because the SP1 Server Software Packages are designed to automatically stop and restart Java.
Therefore, do not send a Distribution containing an SP1 update to other Subscriber servers while the Distributor server is processing a Distribution that is updating the Distributor's Subscriber to SP1. 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 SP1 update in the same Channel that is used to send that SP1 Distribution to other Subseriber servers. Again, when Java is stopped on the Distributor server, unprocessed SP1 Distributions for other servers will be stopped and not restarted.
All Desktop Application Distributions that were built by a Distributor before SP1 was installed must be rebuilt after the Distributor and Subscribers have been updated to SP1. 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.
The following sections list the information you need to install the Inventory Server, the Server Inventory ConsoleOne, and the Remote Management ConsoleOne update component (ZFS3SP1INVREM.CPK) of this support pack.
Do the following for these components before updating them with their respective software packages.
You must follow the certain procedures for the installation order of ZfS 3, ZfS 3 SP1, and ZfD 4. For more information, see "Interoperability Between ZfS 3 SP1 and ZfD 4" under "Interoperability Between ZENworks for Servers and ZENworks for Desktops" in the Installation guide.
To prepare for updating ConsoleOne with the ZfS snap-ins:
Close all ConsoleOne sessions.
If ConsoleOne and ZfS console components are installed on the ZfS server, close all ConsoleOne sessions invoked from this server.
Close all Remote Control sessions.
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 Section 10.0 for a complete list of variables used by the various software packages. See "Using Variables" under "Policy and Distribution Services" in the ZfS 3 Administration guide for details on defining variables in Subscriber objects.
To prepare for using variables during software package installation:
If you are automatically installing the software package, create and initialize the following package processor variables:
If you are manually installing the software package, do the following:
java -ns -noclassgc -classpath $zfspaths com.novell.application.servman.services.softwarepackage.PackageProcessor SYS:\TEMP\ZFS3SP1\ZFS3SP1INVREM.CPK 5 CONSOLE_INSTALL_PATH_NW SYS:\PUBLIC\MGMT\CONSOLEONE\1.2java -cp %zfspaths% com.novell.application.servman.services.softwarepackage.PackageProcessor C:\TEMP\ZFS3SP1\ZFS3SP1INVREM.CPK 5 CONSOLE_INSTALL_PATH_NT C:\NOVELL\CONSOLEONE\1.2 CPK_WORKING_DRIVE_NT C:
You must install ZFS3SP1INVREM.CPK on the ZfS console and all ZfS servers. You must also upgrade ZfS servers and ConsoleOne snap-ins.
Choose whether to install ZFS3SP1INVREM.CPK automatically or manually.
For automatic installation, follow the instructions in Section 2.1, then continue with Step 2.
For manual installation, follow the instructions in Section 2.2, then continue with Step 2.
Restart ConsoleOne.
IMPORTANT: After installing the Policy and Distribution Services .CPK, you must manually restart the Server Inventory services.
The following lists the Server Inventory-related new features:
The following sections list the information you need to install the Inventory Agent update component (ZFS3SP1INVSPAGN.CPK) of this support pack. Also included in this section is a list of software issues resolved by this component.
Before you automatically install this software package, create and initialize the following package processor variables in the Subscriber objects' properties:
The INVPATH is the installation path of the Inventory Agent on a NetWare server. For example, SYS:\ZENWORKS\INV.
The WININVPATH is the installation path of the Inventory Agent on a Windows NT/2000 server. For example, C:\ZENWORKS\INV.
IMPORTANT: You must create and initialize the Inventory Agent variable for the ZFS3SP1INVSPAGN.CPK installation to be successful.
See "Using Variables" under "Policy and Distribution Services" in the ZfS 3 Administration guide for details on defining variables in Subscriber objects.
Choose to install ZFS3SP1INVSPAGN.CPK automatically.
For automatic installation, follow the instructions in Section 2.1.
ZFS3SP1INVSPAGN.CPK cannot be installed manually.
The following lists the resolved software issues that are provided in the ZFS3SP1INVSPAGN.CPK support pack:
The following section lists the software issues that are unresolved in the ZFS3SP1INVSPAGN.CPK provided in this support pack.
If the execution of the ZFS3SP1INVSPAGN.CPK fails due to a problem in unloading Java, the following error will be 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.
To work around this problem, do the following:
Upgrade your JAVA.NLM by doing the following:
Download JVM131SP1.EXE (dated 08-08-2002 and is 49 MB in size), which you can obtain from the Novell Support Connection by searching for TID 2963237.
Also see TID 2962994 for information on installing the new JVM more quickly (10 minutes versus 4 hours) when you must install remotely across a slow WAN link.
Unload Java on the inventoried server.
Upgrade JAVA.NLM on the inventoried server by running JVM131SP1.EXE.
We recommend that you restart the server after upgrading JAVA.NLM.
Reinstall ZFS3SP1INVSPAGN.CPK.
For more information on how to install ZFS3SP1INVSPAGN.CPK, see the ZfS 3 SP1 Readme on the ZENworks for Servers 3 documentation Web site.
Review SYS:\ETC\INVUPDT.LOG to ensure that ZFS3SP1INVSPAGN.CPK has been successfully reinstalled.
If you do not apply the fix to the JVM 1.3.1, do the following:
At the server console prompt, enter java -killall.
At the server console prompt, enter unload java.
Before unloading Java, unload other referenced NLM (NetWare Loadable Module), if any.
If Java has been successfully unloaded, do the following:
Reinstall ZFS3SP1INVSPAGN.CPK.
For more information on how to install ZFS3SP1INVSPAGN.CPK, see the ZfS 3 SP1 Readme on the ZENworks for Servers 3 documentation Web site.
Review SYS:\ETC\INVUPDT.LOG to ensure that ZFS3SP1INVSPAGN.CPK has been successfully reinstalled.
If Java has not been successfully unloaded, do the following:
Upgrade your JAVA.NLM by doing the following:
Also see TID 2962994 for information on installing the new JVM more quickly (10 minutes versus 4 hours) when you must install remotely across a slow WAN link.
Restart the inventoried server.
Reinstall ZFS3SP1INVSPAGN.CPK.
For more information on how to install ZFS3SP1INVSPAGN.CPK, see the ZfS 3 SP1 Readme on the ZENworks for Servers 3 documentation Web site.
Review SYS:\ETC\INVUPDT.LOG to ensure that ZFS3SP1INVSPAGN.CPK has been successfully reinstalled.
(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.
The following sections list the information you need to install the Remote Management update component (ZFS3SP1REMMGMT.CPK) of this support pack. Also included in this section is a list of new features and software issues resolved by this component.
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 Section 10.0 for a complete list of variables used by the various software packages. See "Using Variables" under "Policy and Distribution Services" in the ZfS 3 Administration guide for details on defining variables in Subscriber objects.
To prepare for using variables during software package installation:
If you are installing the ZFS3SP1REMMGMT.CPK automatically on Windows NT/2000 servers, you must create and initialize the ZFS3_RMINSTALL_PATH and FORCE variables.
For manual installation of ZFS3SP1REMMGMT.CPK only, you must edit the following parameters in its .BAT or .NCF file:
On NetWare, if you installed the ZFS3SP1REMMGMT.CPK in a directory other than the default SYS:\TEMP\ZFS3SP1, 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.softwarepackage.PackageProcessor SYS:\TEMP\ZFS3SP1\ZFS3SP1REMMGMT.CPK 6 FORCE 0You must initialize the ZFS3_RMINSTALL_PATH variable in the path where you have installed ZfS 3 Remote Management (for example, C:\ZENWORKS).
If you reinstall the ZfS 3 SP1 Remote Management Agent, you must initialize the FORCE variable to 1.
The default value of the FORCE variable is 0.
Choose whether to install ZFS3SP1REMMGMT.CPK automatically or manually.
For automatic installation, follow the instructions in Section 2.1.
For manual installation, follow the instructions in Section 2.2.
Remote Management has two new features:
For more information, see "Installing ZfS 3, ZfS 3 SP1, and ZfD 4" under "Interoperability Between ZfS 3 SP1 and ZfD 4" in "Interoperability Between ZENworks for Servers and ZENworks for Desktops" in the Installation guide.
The following sections list the resolved software issues that are provided in the ZFS3SP1REMMGMT.CPK and ZFS3SP1INVREM.CPK support pack:
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.
This software package for Remote Management uses variables for the following .BAT or .NCF files:
ZFS3SP1REMMGMT.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.
- Variable = FORCE
- Default Value = 0
- Function = If you want to reinstall the Remote Management Agent, set the value to 1.
ZFS3SP1REMMGMT.NCF
- Variable = FORCE
- Default Value = 0
- Function = If you want to reinstall the Remote Management Agent, set the default value to 1.
This software package for the Management Agent uses variables for the following .BAT or .NCF files:
ZFS3SP1MGMTAGNT.BAT
- Variable = ZFS3AGENTPATH
- Default Value = C:
- Function = Defines the complete path to the install agents.
- Variable = TEMPDIR
- Default Value = C:\TEMP
- Function = Defines the Windows TEMP directory path.
ZFS3SP1MGMTAGNT.NCF
- Variable = NMAPATH
- Default Value = ZFS_AGNT
- Function = Defines the install folder name on NetWare.
- Variable = TARGETIP
- Default Value = 127.0.0.1
- Function = Defines the IP address to send traps to.
- Variable = VOLUMENAME
- Default Value = SYS
- Function = Defines the install volume on NetWare.
This software package for Site Management Server uses variables for the following .NCF file:
ZFS3SP1SITESVR.NCF
- Variable = MMSPATH
- Default Value = DATA:\ZENWORKS\MMS
- Function = Defines the path to which the Site Management Server is installed on NetWare servers.
This software package for Inventory Server, Inventory ConsoleOne, and Remote Management ConsoleOne uses variables for the following .BAT or .NCF files:
INVRMSP1.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.
INVRMSP1.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.
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 © 2002 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, and ZENworks are registered trademarks of Novell, Inc. in the United States and other countries.
eDirectory, NLM, and Novell Client are trademarks of Novell, Inc.
All third-party trademarks are the property of their respective owners.