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 a support pack using the Server Software Package upgrade method, you use the zsm65sp1_polydist.cpk or zsm65sp2_polydist.cpk upgrade file contained in the support pack download for creating the Software Package Distribution. Then you send it to all of the Subscriber servers that you want to upgrade to the support pack.
Review the following to understand what the upgrading does, and to understand the issues involved:
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.
Make sure you have done the following to prepare the ZENworks 6.5 servers that you have targeted for upgrading to the support pack:
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 to the support pack using a Server Software Package, do the following in order:
Select a ZENworks 6.5 Distributor server and copy zsm65sp1_polydist.cpk or zsm65sp2_polydist.cpk to the Distributor's file system.
The .cpk file is located on the ZENworks 6.5 SPx Companion CD download in:
download_location\zenworks65_sp1\zenworks server management - software pkgs\pds
or
download_location\zenworks65_sp2\zenworks server management - software pkgs\pds
For instructions on downloading the support pack file containing the .cpk file, see the ZENworks 6.5 Server Management Support Pack Readme on the ZENworks 6.5 Web site.
Make a note of where you copied zsm65sp1_polydist.cpk or zsm65sp2_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 are upgraded to the support pack 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 Run Immediate and either the Subscriber is running on the same server as the Distributor, or the Subscriber is a parent and will be forwarding the Distribution on to subordinate Subscribers, you will probably interrupt the sending of the Distribution to Subscribers because the update process involves unloading Java. With Java unloaded, Distributions are temporarily halted until Java has been 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 allowed when distributing zsm65sp1_polydist.cpk or zsm65sp2_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 zsm65sp1_polydist.cpk or zsm65sp1_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:
Create a Channel specifically for this software package upgrade.
Set the Channel's Send schedule to Immediate.
If you want to wait and not immediately send the upgrade, you can set it to Never until you are ready to send it, then set it to Immediate.
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, 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 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 6.5 SPx.
Set the Channel used to send the upgrade software package to Inactive, so that this a support pack upgrade won't be sent again to these Subscribers.
Continue with Creating and Sending the Server Software Package.
Determine which components of the software package were 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:
NetWare and Windows |
volume_or_drive\temp\zsm651_polydist.cpk\copylog.txt or volume_or_drive\temp\zsm652_polydist.cpk\copylog.txt |
For general log file messages:
Linux: Enter the following command:
rpm -q novell-zen-zfs
This should return:
novell-zen-zfs-6.5-1
or
novell-zen-zfs-6.5-2
Solaris: Enter the following command:
pgkinfo -l novlzfs
This should return:
VERSION: 6.5-1
or
VERSION: 6.5-2
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 were 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 were 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 Admin Tools, then click Services.
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 1.
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 to the support pack, follow the instructions in 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 to the support pack, follow the instructions under Upgrading the Novell iManager Plug-Ins.
Continue with Verifying That the Servers Have Been Upgraded to the Support Pack.
Log in to iManager.
Under the ZENworks Server Management role, select Remote Web Console.
Identify a server (any supported platform), then click OK.
You can either enter the IP address or DNS name, or browse for the server's ZENworks object.
In the Display field, select Policy/Package Agent from the drop-down list.
Under the Configuration tab, review the Version information.
"ZENworks 6.5 Server Management Support Pack x" should be displayed, where x is the current support pack version.
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
View the current Server Management version information.
If a support pack was applied correctly, it should read:
ZENworks Server Management - Support Pack x
where x is the current support pack version.
Repeat these steps for each upgraded server.
If the version is correct, continue with On a Windows Server or Repeating for Server Groups.
The zfsversion command also writes a listing of ZENworks .jar files and their dates to:
volume:\zenworkszfsversion.log
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 to the support pack, repeat the procedures from Creating and Sending the Server Software Package through Verifying That the Servers Have Been Upgraded to the Support Pack.
You can upgrade only the Inventory Agent component of Server Inventory using the server software package. 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; 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.
If the Inventory Agent is running on Distributor servers and Subscriber servers, you must first upgrade the Inventory Agent running on the Distributor servers before upgrading the Inventory Agent running on the Subscriber servers.
To automatically install the Inventory Agent .cpk file:
Select a ZENworks 6.5 Distributor server and copy zsm651_invagnt.cpk or zsm65sp2_invagnt.cpk to the Distributor's file system.
The .cpk file is located on the ZENworks 6.5 SPx Companion CD download in:
download_location\zenworks65_sp1\zenworks server management - software pkgs\invrm
or
download_location\zenworks65_sp2\zenworks server management - software pkgs\invrm
For instructions on downloading the support pack file containing the .cpk file, see the ZENworks 6.5 Server Management Support Pack Readme on the ZENworks 6.5 Web site.
Make a note of where you copied zsm651_invagnt.cpk or zsm65sp2_invagnt.cpk on the Distributor server for when you create its Server Package Distribution.
Set the Subscriber's Extract schedule.
If the schedule is set to Run Immediate, you will probably interrupt the sending of the Distribution to Subscribers because the update process involves unloading Java. With Java unloaded, Distributions are temporarily halted until Java has been 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 allowed when distributing the ZENworks 6.5 Server Management 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 to set the Distribution's Build schedule.
The Distribution containing ZENworks 6.5 Server Management must be built, sent, extracted, and installed before sending any other Distributions containing other ZENworks 6.5 Server Management software packages.
For detailed instructions on creating Distributions, see "Tiered Electronic Distribution" in the Novell ZENworks 6.5 Server Management Administration Guide.
Associate the Distribution with a Channel so that it is sent based on the channel schedule.
You might need to create the Channel. Be sure to set the Channel's Send schedule.
The ZENworks 6.5 Server Management 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 6.5 Server Management 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 6.5 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.
Review the following log files to verify the success or failure of the Inventory Agent .cpk file installation:
If the .cpk file has been successfully installed, the ZENworks service is automatically started.
The following sections provide detailed instructions for installing the software packages on Remote Management:
IMPORTANT: If you already have a hook driver installed on the machine where you are upgrading, the hook driver is uninstalled during the upgrade.
NOTE: You cannot set a password using a Server Software Package installation. However, if the password is already set on the server, the RConJ agent is loaded.
For loading the RConJ agent on a NetWare 6.5 cluster server, you must set the password by running the ZENworks 6.5 Server Management upgrade wizard followed by the ZENworks 6.5 Server Management a support pack installation.
Using the Tiered Electronic Distribution (TED) component of ZENworks 6.5 Server Management, you can automatically distribute and upgrade the software packages to all servers that are running the Subscriber and Policy Package software.
IMPORTANT: You cannot combine software packages into the same Distribution. You must create a separate Distribution object for each software package. This is because each software package unloads the JVM on NetWare, which prevents concurrent processing of multiple software packages.
Make sure you have completed the following prerequisites for automatic installation:
To automatically install the Remote Management Agent .cpk file:
Select a ZENworks 6.5 Distributor server and copy zsm651_remmgmt.cpk or zsm65sp2_remmgmt.cpk to the Distributor's file system.
The .cpk file is located on the ZENworks 6.5 SPx Companion CD download in:
download_location\zenworks65_sp1\zenworks server management - software pkgs\invrm
or
download_location\zenworks65_sp2\zenworks server management - software pkgs\invrm
For instructions on downloading the support pack file containing the .cpk file, see the ZENworks 6.5 Server Management Support Pack Readme on the ZENworks 6.5 Web site.
Make a note of where you copied zsm651_remmgmt.cpk or zsm65sp2_remmgmt.cpk on the Distributor server for when you create its Server Package Distribution.
Set the Subscriber's Extract schedule.
Create a Distribution for this software package and set the Distribution's Build schedule.
Associate the Distribution with a Channel so that it is sent based on the channel schedule. You might need to create the Channel and set the Channel's Send schedule.
Associate the Subscribers that you want to receive this software package with the Channel.
Send the Distribution.
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.
Review the log file contained in the Subscriber Servers to verify the success or failure of the installation.
Several components might fail to install, and the Software Package installation can still appear as successful, so you should review the success or failure of each component of the software package to ensure that the components needed on a specific server were installed successfully.
You must use the Standalone Package processor included in the software package download to manually upgrade the Remote Management Agent .cpk file on servers that are not running Subscriber software and the Policy/Package Agent.
Before you begin manual installation:
IMPORTANT: In order to use these files for upgrading to ZENworks 6.5 SP2, you will need to edit each file and change any zsm651_remmgmt.cpk references to zsm65sp2_remmgmt.cpk, which is covered in a step in the following procedure.
To manually install the Remote Management Agent .cpk file:
Unzip the RemStandAlonePacPro.zip file to an appropriate location:
Windows server: c:\
NetWare server: sys:\
The Standalone Package Processor files are unzipped into a TEMP directory at the root of the server's file system.
For instructions on downloading the support pack file containing the .zip file, see the ZENworks 6.5 Server Management Support Pack Readme on the ZENworks 6.5 Web site.
Copy the .cpk file to be manually installed to the temporary directory where the associated .bat or .ncf file exists. For example:
Windows server: c:\temp\zfs65
NetWare server: sys:\temp\zfs65
If JRE 1.3.1 is not installed on the target Windows server, download the JRE and install it.
For upgrading to ZENworks 6.5 SP2, open zsm651_remmgmt.bat and zsm651_remmgmt.ncf in a text editor and rename any occurrences of zsm651_remmgmt.cpk to zsm65sp2_remmgmt.cpk.
In the .bat files corresponding to zsm651_remmgmt.cpk or zsm65sp2_remmgmt.cpk, change the JREROOT variable path to JRE_installation_path\JRE\BIN on each of the target Windows servers where JRE 1.3.1 is installed.
Point the CPKTEMP variable in the batch file to the location of the installation directory. For example:
Windows server: CPKTEMP = c:\temp\zfs65
NetWare server: CPKTEMP = sys:\temp\zfs65
Install the agents.
To install the zsm651_remmgmt.cpk or zsm65sp2_remmgmt.cpk on a Windows server, enter the following at the command prompt:
c:\temp\zfs65\win\zsm651_remmgmt.bat
To install the zsm651_remmgmt.cpk or zsm65sp2_remmgmt.cpk on a NetWare server, enter the following at the command prompt:
sys:\temp\zfs65\NetWare\zsm651_remmgmt.ncf
Determine which components of the software package were installed successfully by reviewing the log file created during installation.
The following log files contain detailed information about the success of the Remote Management installation:
NetWare |
sys:\etc\cpk65logs\cpk65_rmagnt.log |
Windows |
%windir%\cpk65logs\cpk65_rmagnt.log |