Automatically Installing the Inventory Server CPK

Using the Tiered Electronic Distribution component of ZENworks 6.5 Server Management, you can automatically distribute and install the Inventory server .cpk file 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. Also, ensure that the Inventory server and the Inventory Agent Distributions are not simultaneously sent to the server using the same Channel. You must first send the Inventory server Distribution and after it is complete, you must send the Inventory Agent Distribution. This is because each software package unloads the JVM on NetWare, which prevents concurrent processing of multiple software packages.

To automatically install the Inventory Server .cpk file:

1. Copy zsm65_invsrv.cpk from ZENworks 6.5 Companion CD 2\ zenworks server management - software pkgs\invrm to a temporary directory on a Distributor server you will use to install the software package.

2. Set the Subscriber's Extract schedule.

   If the schedule is set to Run Immediate, you will probably interrupt the sending of the Distribution to Subscribers because the update process involves unloading Java. With Java unloaded, Distributions are 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 continue from where they left off after Java is started again.

3. 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 ZENworks 6.5 Server Management 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.

   Make sure to set the Distribution's Build schedule.

   The Distribution containing ZENworks 6.5 Server Management must be built, sent, extracted, and installed before sending any other Distributions containing other ZENworks 6.5 Server Management software packages.

   For detailed instructions on creating Distributions, see "Tiered Electronic Distribution" in the Novell ZENworks 6.5 Server Management Administration Guide.

4. Associate the Distribution with a Channel so that it is sent based on the channel schedule.

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

   The ZENworks 6.5 Server Management 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 ZENworks 6.5 Server Management software packages simultaneously (such as by processing them at the same time in a given Channel), it is probable that one or more of the Software Package Distributions will fail on installation.

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

6. Send the Distribution.

   For example, refresh the Distributor to build Distribution so that it can be sent and extracted. For detailed information on sending distributions, see "Tiered Electronic Distribution" in the Novell ZENworks 6.5 Server Management Administration Guide.

   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.

7. Review the following log files to verify the success or failure of the .cpk file installation:

   • On a NetWare server: sys:\etc\cpk65logs\cpk65_invsrv.log, sys:\etc\cpk65logs\invsrv_nw_files.log, and sys:\etc\cpk65logs\cpk_ndsupdate.log
   • On a Windows server: %windir%\cpk65logs\cpk65_invsrv.log, %windir%\cpk65logs\invsrv_win_files.log, and %windir%\cpk65logs\cpk_ndsupdate.log

   If the .cpk file has been successfully installed, the Inventory service is automatically started. The Upgrade Service automatically migrates the database schema and the inventory data to a ZENworks 6.5 Server Management database. The data migration process might take a significant amount of time. On the Inventory server screen, messages indicating that the database has been successfully migrated and initialized are displayed

   After the database is migrated, the Inventory ConsoleOne utilities (Query, Summary, Inventory Report, and Database Export) and the Storer can access the database.

8. Create and configure the Dictionary Update policy to get the latest version of the dictionary for ZENworks 6.5 Inventory Agent.

   For more information on how to create the Dictionary Update policy, see "Configuring the Dictionary Update Policy" in the Novell ZENworks 6.5 Server Management Administration Guide.

Manually Installing the Inventory Server CPK

If you are installing the Inventory server .cpk file to servers that are not running Subscriber software and the Policy/Package Agent, you must use the Standalone Package Processor included in the software package download to manually install the Inventory server .cpk file.

The Standalone Package Processor is required where Policy and Distribution Services agents are not running for both NetWare and Windows servers. However, it can be used on servers where Policy and Distribution Services agents are running.

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.

The following instructions should be repeated for each NetWare or Windows server where you will manually install the Inventory server .cpk file:

1. (Conditional) If you are installing the .cpk file on a Windows Inventory server, make sure that users have not logged into eDirectory from that Inventory server.

2. Copy invrem_standalonepacpro.zip from ZENworks 6.5 Companion CD 2\zenworks server management - software pkgs\invrm to a temporary directory on a NetWare or Windows Inventory server where you will install the software package.

3. Extract invrem_standalonepacpro.zip to the following appropriate location:

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

   Invrem_standalonepacpro.zip contains a directory structure that includes temp as the first directory. The Standalone Package Processor files are unzipped into a TEMP directory at the root of the server's file system.

4. Copy zsm65_invsrv.cpk to the temporary directory where the associated .bat or .ncf file exists. For example:

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

5. If you are installing the .cpk file on a NetWare server, edit the zsm65_invsrv.ncf, which is associated with the software package, to set the values of the following variables:

   • envset ZFSHOMEDIR = Inventory_server_installation_path

     For example, envset ZFSHOMEDIR = sys:\zenworks

   • envset CPKTEMP = path where you have extracted invrem_standalonepacpro.zip

     For example, envset CPKTEMP = sys:\temp\zfs65

   • SEARCH ADD path where you have extracted invrem_standalonepacpro.zip\NETWARE

     For example, SEARCH ADD sys:\temp\zfs65\netware

6. If you are installing the .cpk file on a Windows server, edit the zsm65_invsrv.bat associated with the software package to set the value of following variables:

   • set ZFSHOMEDIR = Inventory_server_installation_path

     For example, set ZFSHOMEDIR = c:\zenworks

   • set CPKTEMP = path where you have extracted invrem_standalonepacpro.zip

     For example, set CPKTEMP = c:\temp\zfs65

7. 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\zfs65\netware\zsm65_invsrv.ncf

   • On Windows, run c:\temp\zfs65\win\zsm65_invsrv.bat

8. Review the following log files to verify the success or failure of the .cpk file installation:

   • On a NetWare server: sys:\etc\cpk65logs\cpk65_invsrv.log, sys:\etc\cpk65logs\invsrv_nw_files.log, and sys:\etc\cpk65logs\cpk_ndsupdate.log
   • On a Windows server: %windir%\cpk65logs\cpk65_invsrv.log, %windir%\cpk65logs\invsrv_win_files.log, and %windir%\cpk65logs\cpk_ndsupdate.log

   If the .cpk file has been successfully installed, the Inventory service is automatically started. The Upgrade Service automatically migrates the database schema and the inventory data to a ZENworks 6.5 Server Management database. The data migration process might take a significant amount of time. On the Inventory server screen, messages indicating that the database has been successfully migrated and initialized are displayed

   After the database is migrated, the Inventory ConsoleOne utilities (Query, Summary, Inventory Report, and Database Export) and the Storer can access the database.

9. Create and configure the Dictionary Update policy to get the latest version of the dictionary for ZENworks 6.5 Inventory Agent.

   For more information on how to create the Dictionary Update policy, see "Configuring the Dictionary Update Policy" in the Novell ZENworks 6.5 Server Management Administration Guide.