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 7 Server Management with SP1 using the Server Software Package upgrade method. The zsm7_polydist.cpk upgrade file is provided on the Novell ZENworks 7 with Support Pack 1 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 Novell ZENworks 7 Server Management with Support Pack 1 Program CD.
After a ZENworks for Servers 3.0.2 Distributor is converted to ZENworks 7 Server Management with SP1, before it sends any of its Distributions, it converts them to ZENworks 7 Server Management with SP1 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:
When upgrading, the password used by the Subscriber is reset in both the Subscriber object and in the Tiered Electronic Distribution software installed on the Subscriber server.
Because you must upgrade the Subscriber objects first using the GUI upgrade program, until the Server Management software is upgraded on the Subscriber servers using the .cpk file, the Subscriber passwords do not match.
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 the 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 TID 2968433 in the Novell Support Knowledgebase.
Maintains all working directories, so that Distributions created in ZENworks for Servers 3.0.2 can be upgraded and used in version 7.
Upgrades to the ZENworks 7 Server Management with SP1 software using the installation paths where ZENworks for Servers 3.0.2 was installed.
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 7 needs to be replaced with the older-dated version 7 files in order to have the correct files for version 7.
The ZENworks for Servers 3.0.2 Policy Package Agent is automatically upgraded to the ZENworks 7 Server Management with SP1 Policy/Package Agent.
Upgrades the ConsoleOne® snap-ins on the Subscriber servers where ConsoleOne is installed.
In summary, the software package upgrades the objects and installs the software on all Subscriber servers where you send the Software Package Distribution.
Distributors cannot be upgraded using the software package. This must be done first using the GUI installation program.
This upgrade software package does not upgrade the ZENworks for Servers 3.0.2 Novell eDirectory™ Subscriber objects to version 7. You must use the GUI upgrade program to upgrade the objects.
The software package does not upgrade to ZENworks 7 Server Management with SP1 on servers where ZENworks for Servers 3.0.2 was not installed. It only upgrades existing ZENworks for Servers 3.0.2 Subscriber objects and software.
The schema is not automatically extended. In order to have an upgraded Distributor for sending the Software Package Distribution containing the upgrade .cpk file, you would have already extended the schema using the GUI installation program.
IMPORTANT:Server Software Packages do not check to see whether the schema has been properly upgraded. The installation of the .cpk files will complete without error; however, the software will not run correctly because of the missing schema extensions. We recommend that you extend the schema before upgrading using the .cpk files; however, you can do this immediately after upgrading.
The ZENworks 7 Server Management with SP1 snap-ins for ConsoleOne are not installed to the local machine during upgrading. You must do this with the installation program after you have exited the upgrade program. You may have already done this when upgrading the Distributors. This task is covered in the upgrade steps.
The ZENworks 7 Server Management with SP1 plug-ins for iManager are not installed during upgrading. You must do this with an installation program menu option after you have exited the upgrade program. You may have already done this when upgrading the Distributors. This task is covered in the upgrade steps.
In summary, the upgrade program does not install ZENworks 7 Server Management with SP1 where ZENworks for Servers 3.0.2 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 zsm7_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:
The Subscriber software resides on the shared volume of the cluster
Files such as sys:\system\zenworks.properties must be updated on each node in the cluster
Most Server Management files are updated on the cluster’s shared volume
The active server node in the cluster runs the Subscriber software from the shared volume
Only one node can be running the Subscriber software at a time (the one that is actively representing the cluster)
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 does not reinstall the files on the cluster’s shared volume. Only the node currently running the Subscriber software is updated.
Bring the 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 Remote Web Console as the Subscriber, click the tab, click the tab, select the Distribution that contains the .cpk file, click , then click .
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 does not reinstall the files on the cluster’s shared volume. Only the node currently running the Subscriber software is updated.
Bring the 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.
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 thinks that it has already been received and doesn’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.0.2 servers that you have targeted for upgrading at this time:
Fulfill the server requirements in Section 5.0, Server Requirements
Upgrade all of the ZENworks for Servers 3.0.2 Distributors’ objects and software using the graphical interface program option (see Section 12.1, Upgrade Using the Program CD)
Upgrade each Subscriber 3 or 3.0.1 server to version 3.0.2 (see the Novell ZENworks for Servers 3.0.2 documentation)
Upgrade each upgraded Subscriber 3.0.2 server to Interim Release 2 (see TID 2968433 in the Novell Support Knowledgebase)
Upgrade all of the ZENworks for Servers 3.0.2 servers to Interim Release 1 Subscriber objects using the graphical interface program option (see Section 12.1, Upgrade Using the Program CD)
If you upgrade the software on any Windows servers, make sure that you have closed the Services window on each Windows server to be upgraded.
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 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 the Server Software Package (zsm7_polydist.cpk):
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:
Compaion 3 CD\zenworks server management - software pkgs\pds
Make a note of where you copied zsm7_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 .
While a Subscriber server is being upgraded, no Distribution activity should be taking place on that server.
After the upgrade software package is sent and extracted, you can reset these Channels back to in Step 8.
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, and/or the Subscriber is a parent and is 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 are temporarily halted until Java is 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 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 .
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 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 .
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 finished upgrading to ZENworks 7 with SP1.
For each Channel that was set to for this Distribution process, reset it to .
Set the Channel used to send the upgrade software package to , so that the upgrade won’t be sent again to these Subscribers.
Determine which components of the software package are installed successfully by using one of the following methods:
Use the Tiered Electronic Distribution view in iManager to see information for every software package that was installed.
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.
Use the \zenworks\zfs-startup.log file contained on the Subscriber Servers to verify the success or failure.
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 are successfully installed, not necessarily all.
Because several components could fail to install, and the Software Package installation still appears 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.
Verify that the services have started:
Verify that the Policy and Distribution Services agents are loaded on NetWare servers:
On the target server’s console, press Ctrl+Esc to view the loaded software programs.
If the ZENworks Server Management service is not displayed, review the \zenworks\zfs-startup.log file, which contains information about why the agent did not start. Zfs-startup.log is used to log startup problems only.
If the ASA 8.0.2 service is not displayed, review the \zenworks\zfs-startup.log file, which contains information about why the Sybase engine database did not start.
Repeat 1 through 3 as necessary for each NetWare server that was upgraded.
Verify that the Policy and Distribution Services agents are loaded on Windows servers:
On the target server, open the Control Panel, double-click > , then determine if the and services are running.
If the services are not displayed, do the following:
Close the Services window.
Click , click , then enter the following command:
zenworks\pds\bin\dservices.bat
This stops the ZENworks Server Management services and unregisters them. This is done to make sure clean state exists for registering the services.
Click , click , then enter the following command:
zenworks\pds\bin\sservices.bat
This registers the ZENworks Server Management services.
Open the Control Panel, double-click > , then start the services by right-clicking them and selecting .
Repeat 1 and 2 for each Windows server that was upgraded.
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 7 with SP1, follow the instructions under Section 6.1.2, Web-Based Management for Policy and Distribution Services.
Otherwise, you have completed upgrading Policy and Distribution Services.