This method allows you to automate the upgrading of Subscriber servers on all supported platforms where the Subscriber software is installed, including NetWare, Windows, Linux, and Solaris.
You can upgrade ZENworks for Servers 3.0.2 Interim Release 1 Subscriber servers to ZENworks 6.5 Server Management using the Server Software Package upgrade method. The zfs65_polydist.cpk upgrade file is provided on the ZENworks 6.5 Companion 2 CD for creating 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:
You must first upgrade all of your Distributor servers using the Policy and Distribution Services Upgrade menu option in the GUI installation program that is run from the ZENworks 6.5 Server Management Program CD.
After a ZENworks for Servers 3.x Distributor has been converted to ZENworks 6.5 Server Management, before it sends any of its Distributions, it converts them to ZENworks 6.5 Server Management Distributions when it builds them.
The Server Software Package upgrade method does not upgrade the Subscriber objects. You must do this first using the GUI upgrade program.
The following conditions exist when you upgrade using the Server Software Package method:
Because the Subscriber passwords are not matched during the time interval between when you upgrade the objects and upgrade the software, the following Server Management functionality does not work:
Both of these require eDirectory access, which is the purpose of the Subscriber password.
Therefore, we recommend that you plan your upgrade so that a minimal amount of time will exist between when you upgrade the objects and software.
IMPORTANT: If you are upgrading incrementally, do not upgrade all of your Subscriber objects at the same time. Only upgrade the Subscriber objects in conjunction with when you plan to upgrade their servers' software.
The Interim Release 2 software update for ZENworks for Servers 3.0.2 (or 3 SP2) is required to be installed on a Subscriber server that you want to update using the Server Software Package method.
For instructions, see Technical Information Document 2968433.
Files are always copied in the ZENworks directories, replacing both older and newer files with the upgrade files. Files copied to other locations outside of the ZENworks directories are replaced only if they are older. The reason for replacing both older and newer files in the ZENworks directories is that version 3.0.2 files from a support pack that is more recent than the release of version 6.5 would need to be replaced with the older-dated version 6.5 files in order to have the correct files for version 6.5.
In summary, the software package upgrades the objects and installs the software on all Subscriber servers where you send the Software Package Distribution.
In summary, the upgrade program does not install ZENworks 6.5 Server Management where ZENworks for Servers 3.x was not installed. ZENworks Subscriber objects are necessary for identifying where to send the Software Package Distribution containing the .cpk upgrade file.
You can upgrade Subscriber servers on multiple trees, because you can send Software Package Distributions to Subscribers on multiple trees.
If you are installing zfs65_polydist.cpk to servers in a clustered environment, you must install the .cpk file individually for each node in the cluster so that any files that need to be written to the sys: volume can be updated.
For example, the following information is known:
Then, you have two ways to update the cluster's nodes: through iManager or by renaming the Distribution:
To update all cluster nodes:
Update the active node's server by sending a Distribution containing the .cpk file to it.
This updates any support pack files that need to be copied to the sys: volume. It also updates the Tiered Electronic Distribution and policies software, such as the .ncf files that are installed on a cluster's volume.
Because filenames and dates are checked during software package installation, running this .cpk file repeatedly will not reinstall the files on the cluster's shared volume. Only the node currently running the Subscriber software will be updated.
Bring currently active node's server down to create a cluster failover condition.
This causes the next node in the predefined sequence to start the Subscriber software and take over for the cluster.
In iManager, access the ZfS/Remote Web Console as the Subscriber > click the Distributions tab > click the Received Distributions tab > select the Distribution that contains the .CPK file > click OK > click Extract.
Repeat Step 2 through Step 3 until all nodes have been updated.
Restart each of the servers in the cluster that were downed.
The primary node's server should take over again.
Alternatively, to update all cluster nodes:
Update the active node's server by sending a Distribution containing the .cpk file to it.
This updates any support pack files that need to be copied to the sys: volume. It also updates the Tiered Electronic Distribution and policies software, such as the .NCF files that are installed on a cluster's volume.
Because filenames and dates are checked during software package installation, running this .cpk file repeatedly will not reinstall the files on the cluster's shared volume. Only the node currently running the Subscriber software will be updated.
Bring the currently active node's server down to create a cluster failover condition.
This will cause the next node in the predefined sequence to start the Subscriber software and take over for the cluster.
Rename the Distribution that you sent in Step 1.
If you do not rename the Distribution when it is resent, the Subscriber software on the cluster volume being used by the current node will think that it has already been received and won't receive and extract it again.
Send the Distribution.
This updates the current node with the support pack.
Repeat Step 2 through Step 4 until all nodes within the cluster have been updated.
Restart each of the servers in the cluster that were downed.
The primary node's server should take over again.
Make sure you have done the following to prepare the ZENworks for Servers 3.x servers that you have targeted for upgrading at this time:
The software package upgrade automatically stops all ZENworks Server Management services. However, the Server Management services cannot be registered if the Services window is left open when upgrading the server.
Using the Tiered Electronic Distribution component of ZENworks 6.5 Server Management, 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 the Server Software Package (zfs65_polydist.cpk):
Select a ZENworks 6.5 Distributor server and copy zfs65_polydist.cpk to the Distributor's file system.
The .cpk file is located in:
ZENWorks 6.5 Companion CD 2\zenworks server management - software pkgs\pds
Make a note of where you copied zfs65_polydist.cpk on the Distributor server for when you create its Server Package Distribution.
To set up the Subscribers, do the following:
Determine which Subscriber servers you want to upgrade with the software package.
Make sure any Channel that services these Subscribers is set to Inactive.
While a Subscriber server is being upgraded, no Distribution activity should be taking place on that server.
After the upgrade software package has been sent and extracted, you can reset these Channels back to Active in Step 8.
Set each Subscriber's Extract schedule.
Use care in setting your Subscriber's Extract schedule.
If the schedule is set to Run Immediate and either the Subscriber is running on the same server as the Distributor, and/or the Subscriber is a parent and will be forwarding the Distribution on to subordinate Subscribers, 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.
Therefore, 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 zfs65_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 zfs65_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 "Policy and Distribution Services" in the Novell ZENworks 6.5 Server Management Administration Guide.
To set up a Channel for this Distribution:
Associate the Subscribers that you identified in Step 3 with the Channel.
Send the Distribution.
For example, refresh the Distributor to get the Distribution built 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, right-click the Distributor object in ConsoleOne and select Refresh Distributor.
For detailed instructions on sending Distributions, see "Policy and Distribution Services" in the Novell ZENworks 6.5 Server Management Administration Guide.
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. At that point, the Subscriber server should be upgraded to ZENworks 6.5.
For each Channel that was set to Inactive for this Distribution process, reset it to Active.
Set the Channel used to send the upgrade software package to Inactive, so that the upgrade won't be sent again to these Subscribers.
Determine which components of the software package were installed successfully by using one of the following methods:
Each software package can consist of several components. It is possible that some of these components can succeed in installing and others fail. For example, a server platform might exist for one of the servers to receive the Distribution, which 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 were successfully installed.
Because several components could fail to install, and the Software Package installation will 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 were installed successfully.
Verify that the services have started:
Verify that the Policy and Distribution Services agents are loaded on NetWare servers:
Verify that the Policy and Distribution Services agents are loaded on Windows servers:
If you have instances of ConsoleOne that need the snap-ins upgraded, follow the instructions in Upgrade the ConsoleOne Snap-Ins, then continue with Step 13.
If you have Novell iManager 2.0.2 installed on a server in your network, and you need to upgrade the iManager plug-ins to ZENworks 6.5, follow the instructions under Web-Based Management for Policy and Distribution Services.
Otherwise, you have completed upgrading Policy and Distribution Services.