Using the ZENworks 6.5 Server Management Program CD, you can upgrade the following Server Inventory components from ZENworks for Servers 3.x to ZENworks 6.5 Server Management: Inventory server, Inventory database, Inventory Agent, and the ZENworks 6.5 Server Management snap-ins for ConsoleOne.
However, to automate installation to multiple Subscriber servers, we recommend upgrading these servers using the Server Software Package method (see Upgrading the Server Inventory Components Using a Server Software Package).
To upgrade Server Inventory from ZENworks for Servers 3.x to ZENworks 6.5 Server Management, perform the following tasks in the order listed:
After reviewing the facts mentioned in Pre-Upgrade Considerations, you must perform the following tasks before you upgrade the Server Inventory components from ZENworks for Servers 3.x to ZENworks 6.5 Server Management:
Stop the Inventory service.
NOTE: If you do not want the Sybase database to be stopped automatically when you stop the Inventory services, comment the Unload dbsrv8.nlm line in the sys:\system\invstop.ncf file.
Stop the Inventory database.
To stop the Sybase Inventory database:
Stop the ZENworks web server:
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 made and 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 6.5 Server Inventory system requirements are met. For more information, see 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 6.5. For more information on how to upgrade Policy and Distribution Services to ZENworks 6.5, see Policy and Distribution Services.
Make sure that the schema has been migrated to ZENworks 6.5. You can migrate the schema by using the ZENworks 6.5 Server Management installation program. For more information on how to migrate the schema, see Extending the Schema in Installation on NetWare and Windows in Policy-Enabled Server Management Installation.
If you have a ZENworks for Servers 3.x database running Oracle, you must perform the following tasks before the migration:
In inventory_database_installation_path\init.ora_path\init.ora, set the value of db_block_buffers to obtain a net value of approximately 128 MB for the database buffer cache.
If the db_block_size is 4096 then the minimum value must be 32768. This allocates 128 MB of database cache for the Inventory database. If the existing value of db_block_buffers is greater than 128 MB, do not change the value.
We recommend you to set the Oracle's Shared Global (SGA) memory to 30-40% or above during the database migration.
Ensure that the Inventory database is up and running.
You must have a larger rollback segment because the database migration and the storage of further data will not succeed due to ORA-01555 and other rollback segment related issues.
To increase the value of rollback segment, execute the following sql script to add an additional data file to rollback segment (rbs) and to add a Redo log group:
connect internal;
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;
During the ZENworks 6.5 Server Management 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 Yes, then the existing database will be overwritten by the new ZENworks 6.5 Server Management database files. If you choose No, the database will be migrated when the Inventory service starts for the first time.
IMPORTANT: If you are upgrading a ZENworks for Server 3 NetWare Inventory server, on which ZENworks for Servers 3 SP2 has been installed using the server software package, to ZENworks 6.5 Server Management, the ZENworks 6.5 Server Management installation fails to detect the Inventory database installed on the ZENworks for Servers 3 SP2 Inventory server. Consequently, the Inventory Database check box is not automatically selected during the ZENworks 6.5 Server Management installation. To install the ZENworks 6.5 Inventory database, you must manually select the Inventory database 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 ("-c" parameter) is set to 25% or above of the server's memory.
If you have a ZENworks for Servers 3.x database running MS SQL, ensure that the value of fixed memory is 40% or above.
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 6.5 Server Management Server Inventory snap-ins installed, click Tools, click ZENworks Inventory, then click Inventory Migration.
Click Browse 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 the subcontainers within the selected container, select the Search SubContainers check box.
The Search SubContainers check box is available only if you select a container in Search Context.
Select the Search for Database Objects 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 Search Context. By default, this option is selected.
Click Find.
All the ZENworks for Servers 3.x database objects that are found within the specified context are displayed in the Report panel.
Click Migrate.
Click Close.
In ConsoleOne, right-click the database object, then click Properties, then click the ZENworks Database tab.
Ensure that the following database object options have the specified values mentioned depending on the Inventory database:
Click Apply, then click Close.
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 6.5 Server Management Inventory server if the server where you want to install the ZENworks 6.5 Server Management Inventory server meets the installation requirements. For more information on how to install the ZENworks 6.5 Server Management Inventory server, see Policy-Enabled Server Management Installation. The ZENworks 6.5 Server Management 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 6.5 Server Management, 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 6.5 Server Management, you must upgrade the associated component to ZENworks 6.5 Server Management (the ZENworks for Servers 3.x Inventory services should not interact with ZENworks 6.5 Server Management 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 6.5 Server Management, you must also upgrade all the associated ZENworks for Servers 3.x Inventory servers.
The ZENworks 6.5 Server Management installation program automatically migrates only the ZENworks for Servers 3.x Inventory Service object to ZENworks 6.5 Server Management. Before starting the Inventory service, you must manually migrate the existing ZENworks for Servers 3.x policies to ZENworks 6.5 Server Management 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 has been installed using the server software package, to ZENworks 6.5 Server Management, the ZENworks 6.5 Server Management 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 6.5 Server Management installation. To install the ZENworks 6.5 XML Proxy, you must manually select the Inventory Proxy Server check box during the Server Management installation.
In ConsoleOne with ZENworks 6.5 Server Management Server Inventory snap-ins installed, click Tools > ZENworks Inventory > Inventory Migration.
Click Browse 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 the subcontainers within the selected container, select the Search SubContainers check box.
The Search SubContainers check box is available only if you select a container in Search Context.
Select the Search for Policies 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 Search Context. By default, this option is selected.
Click Find.
All the ZENworks for Servers 3.x Inventory policies that are associated with the Inventory Service object and are found within the specified context are displayed in the Report panel.
Click Migrate.
Click Close.
The ZENworks 6.5 Inventory agents obtain the software scan configuration rules from the private dictionary and the general dictionary, instead from the Server Inventory policy. But the ZENworks for Servers 3.x Inventory agents would 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 6.5 Server Management, you must perform the following tasks:
Start the ZENworks 6.5 Server Management 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 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.
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.
When the ZENworks 6.5 Inventory Agent is installed on the inventoried server, the existing ZENworks for Servers 3.x Inventory Agent is uninstalled. If the existing ZENworks for Servers 3.x Inventory Agent is not uninstalled, you need to manually uninstall it. For more information about uninstalling the ZENworks for Servers 3.x Inventory Agent, review the following sections:
Stop the ZENworks for Servers 3.x Inventory Agent service.
In the Windows NT Control Panel, double-click Services, select ZFS Policies, then click Stop.
In the Windows 2000 Control Panel, double-click Administrative Tools > Services, select ZFS Policies, then click Stop.
Note the value of the InvAgentPath and the PDSPath key in the HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZenWorks registry entry. The InvAgentPath key contains the Inventory Agent installation directory and the PDSPath contains the Policy and Distribution service installation directory.
Delete the Inventory Agent installation directory identified in the InvAgentPath key.
Delete invagentnt.jar from the plug-ins directory, which is located in the directory identified in the PDSPath key.
You can upgrade the Server Inventory ConsoleOne snap-ins of ZENworks for Servers 3.x to ZENworks 6.5 using the ZENworks 6.5 Server Management installation program if the machine where you want to install the ZENworks 6.5 Server Management ConsoleOne snap-ins meets the installation requirements. For more information about the installation requirements, see Installation Machine and Management Workstation Requirements. For more information on how to install the ZENworks 6.5 Server Management ConsoleOne snap-ins, see Installation on NetWare and Windows in Policy-Enabled Server Management Installation.
After migration is complete and the Storer is able to process files, do the following:
Stop the Inventory service.
If your Inventory database is running Oracle, 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
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 ZENworks 6.5 Companion 2 CD\database\oracle8i\common directory.
For more information on how to improve the performance of the Inventory database, see "Performance Tips" in the Novell ZENworks 6.5 Server Management Administration Guide.
If the Inventory database is running MS SQL, 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 logins:
For more information on how to improve the performance of the Inventory database, see "Performance Tips" in the Novell ZENworks 6.5 Server Management Administration Guide.
Start the Inventory services.