11 Version 6.5 or Later Policy and Distribution Services
11.2 Upgrading Using a Server Software Package
11.2.3 Upgrading Policy and Distribution Services with the Server Software PackageServer Software Package
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:
1. “Creating and Sending the Server Software Package Distribution” on page 180 2. “Determining If the Software Package Was Installed Successfully” on page 181 3. “Verifying that the Services Have Started” on page 182
4. “Installing the Snap-ins and Plug-ins” on page 182
5. “Verifying That the Servers Have Been Upgraded” on page 183 6. “Repeating for Server Groups” on page 183
n) 16 April 2010 Creating and Sending the Server Software Package Distribution
1 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 2 Write down where you copied zsm7_polydist.cpk on the Distributor server for when you
create its Server Package Distribution.
3 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.
4 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 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.
5 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.
6 To set up a Channel for this Distribution:
6a Create a Channel specifically for this software package upgrade.
6b 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.
6c Associate the Distribution with this Channel so that it is sent based on the Channel’s Send schedule.
7 Associate the Subscribers that you identified in Step 3 with the Channel.
8 Send the Distribution.
16 April 2010 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 Refresh Distributor.
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.
9 Set the Channel used to send the upgrade software package to Inactive, so that this upgrade won’t be sent again to these Subscribers.
10 Continue with “Determining If the Software Package Was Installed Successfully” on page 181.
Determining If the Software Package Was Installed Successfully
1 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
n) 16 April 2010 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.
2 Continue with “Verifying that the Services Have Started” on page 182.
Verifying that the Services Have Started
1 Verify that the Policy and Distribution Services is running on NetWare servers:
1a On each target server’s console, press Ctrl+Esc to view the services.
1b Check whether the following services are listed:
ASA 8.0.3 ... (Sybase database)
ZENworks (for Policy and Distribution Services)
1c If any service is missing, that component was not successfully started.
For steps to start a service, see “On NetWare Servers” on page 173.
1d After successfully starting the services, continue with Step 2.
2 Verify that the Policy and Distribution Services is running on Windows servers:
2a On each Windows server, open the Control Panel, double-click Admin Tools, then click Services.
2b Determine if the following services are running:
Novell Database - Sybase
Novell ZENworks Service Manager
2c If any service is not running, that component was not successfully started.
For steps to start a service, see “On Windows Servers” on page 173.
2d After successfully starting the services, continue with Step 3.
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
4 Continue with “Installing the Snap-ins and Plug-ins” on page 182.
Installing the Snap-ins and Plug-ins
1 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,” on page 159, then continue with Step 2.
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” on page 167.
3 Continue with “Verifying That the Servers Have Been Upgraded” on page 183.
16 April 2010 Verifying That the Servers Have Been Upgraded
“Using iManager” on page 183
“On a NetWare Server” on page 183
“On a Windows Server” on page 183 Using iManager
1 Log in to iManager.
2 Under the ZENworks Server Management role, select Remote Web Console.
3 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.
4 In the Display field, select Policy/Package Agent from the drop-down list.
5 Under the Configuration tab, review the version information.
“ZENworks 7 Server Management with SP1” should be displayed.
6 Repeat these steps for each upgraded server.
7 If the version is correct, continue with “Repeating for Server Groups” on page 183.
On a NetWare Server
1 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
2 View the current Server Management version information.
If version 7 was upgraded to correctly, it should read:
ZENworks Server Management - 7 3 Repeat these steps for each upgraded server.
4 If the version is correct, continue with “On a Windows Server” on page 183 or “Repeating for Server Groups” on page 183.
On a Windows Server
1 On the Windows server, run \zenworks\zfsversion.bat. This creates a zfsversion.log file in the \zenworks directory.
2 Open the log file to view the current Server Management version information.
3 Repeat these steps for each upgraded server.
4 If the version is correct, continue with “Repeating for Server Groups” on page 183.
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” on page 180 through “Verifying That the Servers Have Been Upgraded” on page 183.
n) 16 April 2010
12
16 April 2010
12