This method allows you to automatically upgrade Subscriber servers on all supported platforms where the ZENworks 6.5 Subscriber software is installed, including NetWare, Windows, Linux, and Solaris.
For Server Inventory, this method only upgrades the Inventory Agent on NetWare and Windows servers. Management and Monitoring Services cannot be upgraded using a Server Software Package.
When you upgrade ZENworks 6.5 Policy-Enabled Server Management to version 7 using the Server Software Package upgrade method, you use the zsm7_polydist.cpk upgrade file contained on the Novell ZENworks Companion 3 CD to create the Software Package Distribution. Then you send it to all of the Subscriber servers that you want to upgrade.
Review the following to understand what the upgrading does, and to understand the issues involved:
Upgrades the ZENworks 6.5 Server Management software to version 7 using the installation paths where ZENworks 6.5 was installed.
Automatically stops and restarts the services for all supported platforms (NetWare, Windows, Linux, and Solaris).
IMPORTANT:The ZENworks Server Management service must be running in order for the Subscriber to receive and extract the Software Package Distribution containing the upgrade .cpk file. The services on the Subscriber are then stopped during upgrading.
Always copies files to the ZENworks directories, whether the existing files are new newer or older than the upgrade files. However, files copied to locations outside of the ZENworks directories are replaced only if they are older.
Upgrades the ConsoleOne snap-ins on the Subscriber servers where the ZENworks 6.5 snap-ins to ConsoleOne are installed.
The Software Package Distribution is not delivered to the Subscriber server if the ZENworks Server Management service is not running.
The software package does not install new software on ZENworks 6.5 Server Management servers where it was not originally installed. Only existing software is upgraded.
The software package does not upgrade ZENworks for Servers 3.0.2 servers to ZENworks 6.5.
ZENworks eDirectory objects are not upgraded because there are no changes to them between ZENworks 6.5 and 7.
The ZENworks 6.5 Server Management snap-ins for ConsoleOne are not installed to the local machine during upgrading. You must do this with the wizard. This task is covered in Section 11.1.3, Upgrading Policy-Enabled Server Management on NetWare and Windows Servers.
The ZENworks 6.5 Server Management plug-ins for iManager are not installed during upgrading. You must do this with a wizard menu option after you have finished upgrading with the server package. This task is covered in Upgrading the Novell iManager Plug-Ins.
You can upgrade Subscriber servers on multiple trees, because you can send Software Package Distributions to Subscribers on multiple trees.
You can upgrade all ZENworks 6.5 servers to version 7 in one distribution of the .cpk file, or incrementally (such as geographical locations) by setting up different Channels for each Subscriber grouping, but using the same Distribution.
Make sure you have done the following to prepare the ZENworks 6.5 servers that you have targeted for upgrading to version 7:
Review the Novell ZENworks 7 Server Management with Support Pack 1 Readme on the ZENworks 7 Web site for any last-minute information concerning upgrading.
Make sure that ZENworks 6.5 Server Management is installed on the servers you want to upgrade to version 7.
Make sure you have fulfilled all of the installation requirements listed in Section II, Preparation.
Extend the schema to ZENworks 7 Server Management with SP1 in the tree where objects for the servers you are upgrading reside.
For information on extending the schema, see Extending the Schema.
Make sure the ZENworks services are running on the Subscriber server so that it can receive and extract the Software Package Distribution containing the zsm7_polydist.cpk file that is used to upgrade the server.
The services are automatically stopped during upgrading and restarted after the upgrade has finished.
Using the Tiered Electronic Distribution component of ZENworks 7 Server Management with SP1, you can automatically distribute and install the software packages to all Subscriber servers that are running the Subscriber and Policy/Package Agent software.
To upgrade using a Server Software Package, do the following in order:
Select a ZENworks 7 with SP1 Distributor server and copy zsm7_polydist.cpk to the Distributor’s file system.
The .cpk file is located in:
Program_CD\zenworks7\zenworks server management - software pkgs\pds
Write down where you copied zsm7_polydist.cpk on the Distributor server for when you create its Server Package Distribution.
Determine which Subscriber servers you want to upgrade with the software package.
If you created a list during preparation, continue with Step 4.
Distributor servers’ software are upgraded to version 7 when their Subscribers are upgraded.
Set each Subscriber’s Extract schedule.
Use care in setting your Subscriber’s Extract schedule. If the schedule is set to and either the Subscriber is running on the same server as the Distributor, or the Subscriber is a parent and is forwarding the Distribution on to subordinate Subscribers, 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 is 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.
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 zsm7_polydist.cpk. 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.
Be sure to set the Distribution’s Build schedule.
IMPORTANT:The Distribution containing zsm7_polydist.cpk must be built, sent, extracted, and installed before sending any other Distributions containing other software packages for upgrading other Server Management components.
For detailed instructions on creating Distributions, see Tiered Electronic Distribution
in the Novell ZENworks 7 Server Management Administration Guide.
To set up a Channel for this Distribution:
Create a Channel specifically for this software package upgrade.
Set the Channel’s Send schedule to .
If you want to wait and not immediately send the upgrade, you can set it to until you are ready to send it, then set it to .
Associate the Distribution with this Channel so that it is sent based on the Channel’s Send schedule.
Associate the Subscribers that you identified in Step 3 with the Channel.
Send the Distribution.
For example, refresh the Distributor to build the Distribution so that it can be sent and extracted. You do not need to set or change the Distributor’s Refresh schedule if you refresh the Distributor manually.
To refresh the Distributor manually, in ConsoleOne right-click the Distributor object and select .
For detailed instructions 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 sent when the Channel’s Send schedule starts. It is extracted according to the Subscriber server’s Extract schedule. At that point, the Subscriber server should be upgraded to ZENworks 7 with SP1.
Set the Channel used to send the upgrade software package to , so that this upgrade won’t be sent again to these Subscribers.
Continue with Determining If the Software Package Was Installed Successfully.
Determine which components of the software package are installed successfully by using one of the following methods:
iManager: Use the Tiered Electronic Distribution view in iManager to see information for every software package that was installed.
Reports: If you use Tiered Electronic Distribution for installation, use Server Management reporting to verify the success or failure of individual components of a software package.
Log files: Use the log files contained on the Subscriber Servers to verify the success or failure:
For file copying messages:
For general log file messages:
Linux: Enter the following command:
rpm -q novell-zen-zfs
This should return:
novell-zen-zfs-6.5-1
Solaris: Enter the following command:
pgkinfo -l novlzfs
This should return:
VERSION: 6.5-1
Each software package can consist of several components. It is possible that some of these components can be successfully installed and others fail. For example, a server platform might exist for one of the servers to receive the Distribution, but the platform is not contained in the requirements for the software package. Therefore, success for the software packages included in the installation means that one or more components are successfully installed.
Because several components could fail to install, and the Software Package installation might still appear as successful, 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 are installed successfully.
Continue with Verifying that the Services Have Started.
Verify that the Policy and Distribution Services is running on NetWare servers:
On each target server’s console, press Ctrl+Esc to view the services.
Check whether the following services are listed:
If any service is missing, that component was not successfully started.
For steps to start a service, see On NetWare Servers.
After successfully starting the services, continue with Step 2.
Verify that the Policy and Distribution Services is running on Windows servers:
On each Windows server, open the Control Panel, double-click , then click .
Determine if the following services are running:
If any service is not running, that component was not successfully started.
For steps to start a service, see On Windows Servers.
After successfully starting the services, continue with Step 3.
To verify that Policy and Distribution Services is running on Linux or Solaris servers, enter in an XTerm window on each server:
/etc/init.d/novell-zfs status
Continue with Installing the Snap-ins and Plug-ins.
If you have instances of ConsoleOne that need the snap-ins upgraded, follow the instructions in Section 11.1.3, Upgrading Policy-Enabled Server Management on NetWare and Windows Servers, then continue with Step 2.
If you have Novell iManager 2.0.2 or 2.5 installed on a server in your network, and you need to upgrade the iManager plug-ins, follow the instructions under Upgrading the Novell iManager Plug-Ins.
Continue with Verifying That the Servers Have Been Upgraded.
Log in to iManager.
Under the role, select .
Identify a server (any supported platform), then click .
You can either enter the IP address or DNS name, or browse for the server’s ZENworks object.
In the field, select from the drop-down list.
Under the tab, review the version information.
“ZENworks 7 Server Management with SP1” should be displayed.
Repeat these steps for each upgraded server.
If the version is correct, continue with Repeating for Server Groups.
At the NetWare server’s main console prompt, enter the following command:
zfsversion
The zfsversion command also writes a listing of ZENworks .jar files and their dates to:
volume:\zenworks\zfsversion.log
View the current Server Management version information.
If version 7 was upgraded to correctly, it should read:
ZENworks Server Management - 7
Repeat these steps for each upgraded server.
If the version is correct, continue with On a Windows Server or Repeating for Server Groups.
On the Windows server, run \zenworks\zfsversion.bat.
This creates a zfsversion.log file in the \zenworks directory.
Open the log file to view the current Server Management version information.
Repeat these steps for each upgraded server.
If the version is correct, continue with Repeating for Server Groups.
For each incremental grouping of servers to be upgraded, repeat the procedures from Creating and Sending the Server Software Package Distribution through Verifying That the Servers Have Been Upgraded.