Before upgrading, do the following:
Make sure that all of the installation requirements outlined in Section II, Preparation are met.
Review the facts in Section 13.1.1, Pre-Upgrade Considerations.
To upgrade the following Server Inventory components from ZENworks for Servers 3.x to ZENworks 7 Server Management with SP1 using the Novell ZENworks 7 Server Management with Support Pack 1 Program CD, see Section 13.1.2, Upgrading the Server Inventory Components Using the Program CD:
Inventory database
Inventory server
Inventory Agent
Server Inventory ConsoleOne® snap-ins
You can automate the upgrading of the Inventory Agent from ZENworks for Servers 3.0.2 or ZENworks for Servers 3 SP2 to ZENworks 7 Server Management with SP1 using a Server Software Package. For detailed information, see Section 13.1.3, Upgrading the Inventory Agent Using a Server Software Package.
Before you upgrade Server Inventory to ZENworks 7 Server Management with SP1 either using the Novell ZENworks 7 Server Management with Support Pack 1 Program CD or the Server Software Package, review the facts in the following sections:
ZENworks for Servers 3.x Inventory servers can roll up the inventory data to a ZENworks 7 Server Management with SP1 Inventory server, but a ZENworks 7 Server Management with SP1 Inventory server cannot roll up the inventory data to a ZENworks for Servers 3.x Inventory server.
Server Inventory in ZENworks 7 Server Management with SP1 supports backward compatibility with ZENworks for Servers 3.x Inventory servers residing on the same Novell eDirectory tree.
ZENworks for Servers 3.x Inventory servers must be upgraded to ZENworks 7 Server Management with SP1 in a top-down order. If you perform roll-up of your inventory data, the Root Server must be upgraded first, then the Intermediate Servers, and lastly the Leaf Servers.
A ZENworks 7 Server Management with SP1 Inventory server cannot send its inventory data to a ZENworks for Servers 3.x Inventory server.
A ZENworks 7 Server Management with SP1 Inventory server can process the .str files of the ZENworks for Servers 3.x inventoried servers. The ZENworks for Servers 3.x Inventory agents can send the inventory data to a ZENworks 7 Server Management with SP1 Inventory server.
A ZENworks 7 Server Management with SP1 Inventory server can process the .zip files of the ZENworks for Servers 3.x Inventory servers.
The ZENworks for Servers 3.x Inventory server and a ZENworks 7 Server Management with SP1 Inventory server can use a ZENworks for Servers 3.x Roll-Up policy that is migrated to ZENworks 7 Server Management with SP1.
Upgrading a ZENworks for Servers 3.x Inventory server to ZENworks 7 Server Management with SP1 does not change the role of the Inventory server.
You can use ZENworks 7 Server Management with SP1 ConsoleOne snap-ins to administer both ZENworks for Servers 3.x and ZENworks 7 with SP1 inventory data and inventory objects (such as Inventory Service object, database objects, Server Inventory policy, Roll-Up policy and Database Location policy).
Do not delete the ZENworks for Servers 3.x .str and .zip files in a ZENworks for Servers 3.x Inventory server’s SCANDIR and its subdirectories after you’ve upgraded the Inventory server to ZENworks 7 with SP1.
Do not have a ZENworks for Servers 3.x Inventory server and a ZENworks 7 with SP1 Inventory server store inventory data directly to the same Inventory database.
The ZENworks for Servers 3.x Inventory agent can send inventory data to a ZENworks 7 with SP1 Inventory server, which means the data can be stored in a ZENworks 7 with SP1 Inventory database.
The ZENworks 7 with SP1 Inventory agent cannot send the inventory data to a ZENworks for Servers 3.x Inventory server, which means the data cannot be stored in a ZENworks for Servers 3.x Inventory database.
Do not upgrade to the ZENworks 7 with SP1 Inventory Agent until you’ve upgraded your Inventory servers and databases.
A ZENworks for Servers 3.x or ZENworks 7 Server Management with SP1 Inventory Agent can use a ZENworks for Servers 3.x Inventory policy that is upgraded to ZENworks 7 Server Management with SP1, or they can use a newly created ZENworks 7 Server Management with SP1 Inventory policy.
If the ZENworks for Servers 3.x Inventory Agent and the ZENworks for Servers 3.x Policy and Distribution Services are installed on the same machine, and if you upgrade Policy and Distribution Services to ZENworks 7 Server Management with SP1, you must upgrade the Inventory Agent also to ZENworks 7 Server Management with SP1.
You can use ZENworks 7 Server Management with SP1 ConsoleOne snap-ins to administer both ZENworks for Servers 3.x and ZENworks 7 with SP1 inventory data and inventory objects (such as Inventory Service object, database objects, Server Inventory policy, Roll-Up policy, Dictionary Update policy, and Database Location policy).
You cannot use the ZENworks for Servers 3.x ConsoleOne snap-ins to administer ZENworks 7 Server Management with SP1 inventory data and inventory objects.
Do not use both ZENworks for Servers 3.x and ZENworks 7 Server Management with SP1 consoles to configure the same ZENworks for Servers 3.x Inventory objects.
The ZENworks 7 with SP1 Server Inventory installation program automatically upgrades an existing ZENworks for Servers 3.x ConsoleOne snap-ins to ZENworks 7 with SP1. For more information on installing ZENworks 7 with SP1 Server Inventory, see Section 6.0, Policy-Enabled Server Management Installation.
Using the Novell ZENworks 7 Server Management with Support Pack 1 Program CD, you can upgrade the following Server Inventory components from ZENworks for Servers 3.x to ZENworks 7 Server Management with SP1: Inventory server, Inventory database, Inventory Agent, and the ZENworks 7 Server Management with SP1 snap-ins for ConsoleOne.
To upgrade Server Inventory from ZENworks for Servers 3.x to ZENworks 7 Server Management with SP1, perform the following tasks in the order listed:
Perform the tasks explained in Tasks To Be Performed Before Upgrade and Database Migration
Upgrading the Server Inventory ConsoleOne Snap-Ins Using the Program CD
Perform the tasks explained in Post Database Migration Tasks
After reviewing the facts mentioned in Section 13.1.1, Pre-Upgrade Considerations, you must perform the following tasks before you upgrade the Server Inventory components from ZENworks for Servers 3.x to ZENworks 7 Server Management with SP1:
Stop the Inventory service.
On a NetWare Inventory server: At the server console prompt, enter:
sys:\system\invstop.ncf
NOTE:If you do not want the Sybase database to be stopped automatically when you stop the Inventory services, comment the Unload dbsrv8.nlmline in the sys:\system\invstop.ncf file.
On a Windows 2000/2003 Inventory server: In the Control Panel, double-click , double-click , select , then click .
To stop the Sybase Inventory database:
On NetWare: At the Sybase console prompt, press the q key.
On Windows 2000/2003: In the Control Panel, double-click , double-click , right-click , then click .
To stop the ZENworks web server:
On Windows 2000 Server: In the Control Panel, double-click , double-click , right-click , then click .
If Java has not been unloaded on the target NetWare servers, unload java.nlm (at the server console, enter java -exit).
IMPORTANT:This command stops all Java processes running on the server. Verify that all Java processes can be stopped while you are installing Server Management.
On the target Windows servers, close the Services window.
Make sure that you have archived a reliable backup of the ZENworks for Servers 3.x database.
Before upgrading the Inventory server, make sure that you have upgraded its associated database server.
Make sure that the ZENworks for Servers 3.x database is not accessed from ConsoleOne.
Make sure that the recommended ZENworks 7 with SP1 Server Inventory system requirements are met. For more information, see Section 5.0, Server Requirements.
If ZENworks_installation_path\zenworks\inv\server\wminv\ properties\inventoryremoval.properties has been modified after the ZENworks for Servers 3.x installation, take a reliable backup of inventoryremoval.properties.
Make sure that the Policy and Distribution Services have been upgraded to ZENworks 7 with SP1.
For more information on how to upgrade Policy and Distribution Services to ZENworks 7 with SP1, see Section 12.0, Version 3.0.2 Policy and Distribution Services.
Make sure that the schema is migrated to ZENworks 7 with SP1.
You can migrate the schema by using the ZENworks 7 Server Management with SP1 installation program. For more information on how to migrate the schema, see Extending the Schema.
If you have a ZENworks for Servers 3.x Oracle Inventory database, you must perform the following tasks before the migration:
Ensure that the Oracle’s version is 9.2.0.6 or later.
In inventory_database_installation_path\init.ora_path\init.ora, set the values of the following parameters as shown:
You can increase the cache size and shared pool to have Shared Global Area (SGA) to 30-40% physical RAM size.
Ensure that the Inventory database is up and running.
Because you must have a larger rollback segment because the database migration and the storage of further data cannot succeed because of ORA-01555 and other rollback segment-related issues, to increase the value of the rollback segment, execute the following SQL script to add an additional data file to the rollback segment (RBS) and to add a Redo log group:
connect / as sysdba;
alter tablespace rbs add datafile ’Inventory_database_installation_path\rbs2.ora’ size 40M autoextend on next 50K maxsize 60M;
alter rollback segment rb0 storage (maxextents unlimited);
alter rollback segment rb1 storage (maxextents unlimited);
ALTER DATABASE ADD LOGFILE GROUP 3 (’Inventory_database_installation_path\log3.ora’) SIZE 50M;
Stop the Inventory database.
Ensure that the value of the compatible parameter in inventory_database_installation_path\path_to_init.ora\init.ora is set to 9.1.3.0.0 or later.
If the size of any data file is about to exceed 4096 MB, you must add extra data files to the corresponding tablespace.
Extract the appropriate platform-specific atlasperf_altertablespace.sql from ZENworks_installation_directory\zenworks\inv\server\wminv\properties\sql.zip to C:.
If Oracle is running on Windows, extract atlasperf_altertablespace.sql from the oracle\winntspecific directory within sql.zip.
If Oracle is running on UNIX, extract atlasperf_altertablespace.sql from the oracle\unixspecific directory within sql.zip.
Edit atlasperf_altertablespace.sql to set the value of MAXSIZE for all data files to the nearest multiple of 4 GB.
For example, if the size of CIM8.ora is 5 GB, then set the value of MAXSIZE to 8192 MB.
Ensure that the file path of all data files listed in atlasperf_altertablespace.sql is correct.
Restart the Inventory database.
Execute altaslperf_altertablespace.sql.
During the ZENworks 7 Server Management with SP1 installation, if you choose to install Sybase and you do not choose to overwrite the database files, the server installation program automatically upgrades the existing ZENworks for Servers 3.x database engine only. During the Sybase database upgrade, a message indicating that the existing database can be migrated is displayed. If you choose , then the existing database is overwritten by the new ZENworks 7 Server Management with SP1 database files. If you choose , the database is migrated when the Inventory service starts for the first time.
IMPORTANT:If you are upgrading a ZENworks for Servers 3 NetWare Inventory server (on which ZENworks for Servers 3 SP2 is installed using the Server Software Package) to ZENworks 7 Server Management with SP1, the ZENworks 7 Server Management with SP1 installation fails to detect the Inventory database installed on the ZENworks for Servers 3 SP2 Inventory server. Consequently, the check box is not automatically selected during the ZENworks 7 Server Management with SP1 installation. To install the ZENworks 7 with SP1 Inventory database, you must manually select the check box during the Server Management installation.
However, you must perform the following tasks:
If you have a ZENworks for Servers 3.x Oracle database object, or if you have manually created Sybase database objects, you must manually migrate the database object using the Inventory Migration tool. For more information, see Manually Migrating the ZENworks for Servers 3.x Database Objects.
If you have a ZENworks for Servers 3.x database running Sybase, ensure that the value of Sybase cache (the -c parameter) is set to 25% or higher than the server’s memory.
To change the database cache size on a NetWare database server:
Close all connections to the Inventory database.
Quit the Sybase server.
Open the mgmtdbs.ncf file in the sys:\system directory.
Modify the -c parameter. For example, -c 128M sets the cache size to 128 MB.
Save the file.
On the server console, to load the Inventory database, enter MGMTDBS.
To change the database cache size on a Windows database server:
Stop the Sybase service:
On Windows NT, in the Control Panel, double-click , right-click , then click .
On Windows 2000 Server, in the Control Panel, double-click > double-click , right-click , then click .
On the database server, run the ntdbconfig.exe file from the \dbengine directory.
Ntdbconfig.exe is a ZENworks database configuration utility for the ZENworks database using Sybase on Windows NT/2000 servers. This utility enables you to reconfigure the Sybase service.
Modify the -c parameter.
Click .
Restart the Sybase service:
On Windows NT, in the Control Panel, double-click , right-click , then click .
On Windows 2000 Server, in the Control Panel, double-click , double-click , right-click , then click .
If you have a ZENworks for Servers 3.x database running MS SQL, ensure that the value of fixed memory is 40% or higher.
IMPORTANT:You can upgrade multiple Inventory servers and database servers at the same time by running the Server Management installation program.
However, you must manually migrate the existing ZENworks for Servers 3.x Server Inventory policy, Database Location policy, and Roll-Up policy. If you have manually created the database object, you must also migrate the database object. For more information on how to manually migrate the policies, see Manually Migrating the ZENworks for Servers 3.x Database Objects.
In ConsoleOne with ZENworks 7 Server Management with SP1 Server Inventory snap-ins installed, click > > .
Click to browse for and select the database object to be migrated or the container that has the database object.
If you selected a container in Step 2, do the following:
If you want to search for the database object in all of the subcontainers within the selected container, select the check box.
The check box is available only if you select a container in .
Select the check box to search for the database objects within the selected container to be migrated.
This option is available only if you select a container in . By default, this option is selected.
Click .
All the ZENworks for Servers 3.x database objects that are found within the specified context are displayed in the Report panel.
Click .
Click .
In ConsoleOne, right-click the database object, click , then click the tab.
Ensure that the following database object options have the specified values mentioned depending on the Inventory database:
Click , then click .
Before upgrading the ZENworks for Servers 3.x Inventory server, make sure that you have upgraded the associated database server.
You can upgrade the ZENworks for Servers 3.x Inventory server by installing ZENworks 7 Server Management with SP1 Inventory server if the server where you want to install the ZENworks 7 Server Management with SP1 Inventory Server meets the installation requirements. For more information on how to install the ZENworks 7 Server Management with SP1 Inventory Server, see Section 6.0, Policy-Enabled Server Management Installation.
The ZENworks 7 Server Management with SP1 Inventory server supports the same set of roles as ZENworks for Servers 3.x. Therefore, when you upgrade from ZENworks for Servers 3.x to ZENworks 7 Server Management with SP1, the role of the Inventory server is retained.
IMPORTANT:If you have a ZENworks for Servers 3.x Inventory server attached to a ZENworks for Servers 3.x database, and if you upgrade either the Inventory server or the database to ZENworks 7 Server Management with SP1, you must upgrade the associated component to ZENworks 7 Server Management with SP1 (the ZENworks for Servers 3.x Inventory services should not interact with ZENworks 7 Server Management with SP1 compliant database, and vice versa).
If you have multiple ZENworks for Servers 3.x Inventory servers connected to a ZENworks for Servers 3.x database server, and if you upgrade the database server to ZENworks 7 Server Management with SP1, you must also upgrade all of the associated ZENworks for Servers 3.x Inventory servers.
The ZENworks 7 Server Management with SP1 installation program automatically migrates only the ZENworks for Servers 3.x Inventory Service object to ZENworks 7 Server Management with SP1. Before starting the Inventory service, you must manually migrate the existing ZENworks for Servers 3.x policies to ZENworks 7 Server Management with SP1 policies using the ZENworks Inventory Migration tool. For more information, see Manually Migrating the ZENworks for Servers 3.x Inventory Policies.
IMPORTANT:If you are upgrading a ZENworks for Server 3 NetWare Inventory server (on which ZENworks for Servers 3 SP2 is installed using the server software package) to ZENworks 7 Server Management with SP1, the ZENworks 7 Server Management with SP1 installation fails to detect the XML Proxy server installed on the ZENworks for Servers 3 SP2 Inventory server. Consequently, the Inventory Proxy Server check box is not automatically selected during the ZENworks 7 Server Management with SP1 installation. To install the ZENworks 7 with SP1 XML Proxy, you must manually select the check box during the Server Management installation.
In ConsoleOne with ZENworks 7 Server Management with SP1 Server Inventory snap-ins installed, click > > .
Click to browse for and select the Inventory Service object or the container that has the Inventory Service object.
If you selected a container in Step 2, do the following:
If you want to search for the Inventory Service object in all of the subcontainers within the selected container, select the check box.
The check box is available only if you select a container in .
Select the check box to search for the Inventory policies associated with the Inventory Service object within the selected container.
This option is available only if you select a container in . By default, this option is selected.
Click .
All of the ZENworks for Servers 3.x Inventory policies associated with the Inventory Service object that are found within the specified context are displayed in the Report panel.
Click .
Click .
The ZENworks 7 with SP1 Inventory agents obtain the software scan configuration rules from the private dictionary and the general dictionary, instead from the Server Inventory policy. However, the ZENworks for Servers 3.x Inventory agents continue to use the Server Inventory policy for software configuration.
After migrating the policies, perform the following tasks:
(Conditional) If you upgrade a ZENworks for Servers 3.0.2 NetWare database server with ZENworks for Servers 3.0.2 Interim Release 2 (IR 2) installed to ZENworks 7 Server Management with SP1, you must perform the following tasks:
Edit sys:\system\autoexec.ncf to add the following line:
sys:\system\mgmtdbs.ncf
Manually start the database server.
Start the ZENworks 7 Server Management with SP1 Inventory services.
When you start the Inventory service, the Upgrade Service automatically migrates the ZENworks for Servers 3.x database schema and the inventory data to a ZENworks 7 Server Management with SP1 database. The data migration process might take a significant amount of time. On the Inventory server screen, messages indicating that the database is 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.
Create and configure the Dictionary Update policy to obtain the latest version of the dictionary for ZENworks 7 with SP1 Inventory Agent. For more information on how to configure the Dictionary Update policy, see Configuring the Dictionary Update Policy
in the Novell ZENworks 7 Server Management Administration Guide.
If the machine where you want to install the ZENworks 7 Server Management with SP1 Inventory Agent meets the installation requirements, you can upgrade the Inventory Agent of ZENworks for Servers 3.x to ZENworks 7 with SP1 using the ZENworks 7 Server Management with SP1 installation program. For more information about the installation requirements, see Section II, Preparation.
If the machine where you want to install the ZENworks 7 Server Management with SP1 ConsoleOne snap-ins meets the installation requirements, you can upgrade the Server Inventory ConsoleOne snap-ins of ZENworks for Servers 3.x to ZENworks 7 with SP1 using the ZENworks 7 Server Management with SP1 installation program.
For more information about the installation requirements, see Section 4.0, Installation Machine and Management Workstation Requirements. For more information on how to install the ZENworks 7 Server Management with SP1 ConsoleOne snap-ins, see Section 6.1, Installation on NetWare and Windows Servers.
After migration is complete and the Storer is able to process files, do the following:
Stop the Inventory service.
On an Oracle Inventory database, do the following to improve the database performance:
In the inventory_database_installation_path\_start.sql file, delete the existing entries and add the following entries:
SET ECHO ON
CONNECT INTERNAL
SET ECHO OFF
STARTUP PFILE=
inventory_database_installation_path\path_to_init.ora\init.ora
SET NUMWIDTH 20
SET CHARWIDTH 40
SET ECHO ON
connect mw_dba;
SET ECHO OFF
alter table cim.t$product cache;
SET ECHO ON
connect internal
SET ECHO OFF
@<path to oracle home directory>/rdbms/admin/dbmspool
call sys.dbms_shared_pool.keep(‘zenworks.zenpin', ‘P');
EXIT
Extract atlasperf_alterfreelist.sql from ZENworks_installation_directory\zenworks\inv\server\wminv\properties\sql.zip and execute it at the SQLPLUS prompt.
Execute the oracle\common\oracle_perf.sql and oracle\common\oracle_perf2.sql files from Inventory_server_installation_path\zenworks\inv\server\wminv\properties\sql.zip to add performance enhancing indexes to the database.
Execute oracle_dbexport_perf.sql from the Novell ZENworks 7 with Support Pack 1 Companion 2 CD’s \database\oracle9i\common directory.
For more information on how to improve the performance of the Inventory database, see Performance Tips
in the Novell ZENworks 7 Server Management Administration Guide.
On a MS SQL Inventory database, use the MS SQL Query Analyzer to execute the following scripts from Inventory_server_installation_path\zenworks\inv\server\wminv\properties\sql.zip using the appropriate user login:
Log in as “CIM” and execute mssql_perf_cim.sql.
Log in as “mw_dba” and execute mssql_perf_mw_dba.sql.
Log in as “zenworks” and execute msswl_perf_zenworks.sql.
For more information on how to improve the performance of the Inventory database, see Performance Tips
in the Novell ZENworks 7 Server Management Administration Guide
Start the Inventory services.
You can also upgrade the Inventory Agent from ZENworks for Servers 3.0.2 or ZENworks for Servers 3 SP2 to ZENworks 7 Server Management with SP1 using a Server Software Package upgrade file contained on the Novell ZENworks 7 with Support Pack 1 Compaion 3 CD.
This method allows you to automatically upgrade the Inventory Agent installed on NetWare 5.1 SP7 or later, and Windows 2000 Server.
To upgrade the Inventory Agent, perform the following tasks in the order listed:
Review the Section 13.1.1, Pre-Upgrade Considerations.
Upgrade Policy and Distribution Services to ZENworks 7 with SP1.
For more information on how to upgrade Policy and Distribution Services to ZENworks 7 with SP1, see Section 12.0, Version 3.0.2 Policy and Distribution Services.
You can automatically install the Inventory Agent .cpk file.
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 Agent .cpk file:
Copy zsm7_inv_agnt.cpk from the Novell ZENworks 7 with Support Pack 1 Compaion 3 CD’s zenworks server management - software pkgs\invrm directory to a temporary directory on the Distributor server you use to install the software package.
Set the Subscriber’s Extract schedule.
If the schedule is set to , you might interrupt the sending of the Distribution to Subscribers because the update process involves unloading Java. With Java unloaded, Distributions are temporarily halted until Java is 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 permitted when distributing the ZENworks 7 Server Management with SP1 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 you set the Distribution’s Build schedule.
The Distribution containing ZENworks 7 Server Management with SP1 must be built, sent, extracted, and installed before sending any other Distributions containing other ZENworks 7 Server Management with SP1 software packages.
For detailed instructions on creating Distributions, see Tiered Electronic Distribution
in the Novell ZENworks 7 Server Management Administration Guide.
Associate the Distribution with a Channel so that it is sent based on the Channel’s schedule.
You might need to create the Channel. Be sure to set the Channel’s Send schedule.
The ZENworks 7 Server Management with 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 ZENworks 7 Server Management with SP1 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.
Associate the Subscribers that you want to receive this software package with the Channel.
Send the Distribution.
For example, refresh the Distributor to build the Distribution so that it can be sent and extracted. For detailed information on sending distributions, see Tiered Electronic Distribution
in the Novell ZENworks 7 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 is extracted according to the Subscriber server’s Extract schedule.
Review the following log files to verify the success or failure of the Inventory Agent .cpk file installation:
NetWare: sys:\etc\cpk7logs\cpk7_invagnt.log
Windows: %windir%\cpk7logs\cpk7_invagnt.log
If the .cpk file is successfully installed, the ZENworks service is automatically started.
NOTE:During the NetWare Inventory agent upgrade, all of the Java services, including the ZENworks service, are automatically terminated. After the upgrade, only the ZENworks service is automatically started; you must manually start all of the other Java services.
If you have installed the ZENworks 7 with SP1 Inventory Agent on the inventoried server using the Novell ZENworks 7 Server Management with Support Pack 1 Program CD, and now you want to reinstall the ZENworks 7 with SP1 Inventory Agent using the software package, you must do the following:
Ensure that the value of InvAgentPath in sys:\system\zenworks.properties is volume_name:\zenworks\inv\agent.
Follow the steps explained in Upgrading the Inventory Agent Using the Software Package.
NOTE:During the NetWare Inventory agent upgrade, all of the Java services, including the ZENworks service, are automatically terminated. After the upgrade, only the ZENworks service is automatically started; you must manually start all of the other Java services.