You can upgrade the ZENworks Desktop Management components on the various supported platforms to ZENworks 7 Desktop Management with SP1 using the available CPKs. See the information in the following sections:
Section 34.4.1, Upgrading with a Distribution
Using the Tiered Electronic Distribution component of ZENworks 7 Server Management with SP1, you can distribute and automatically install the CPKs to all Subscriber servers that are running the Subscriber and Policy/Package Agent software.
Section 34.4.2, Upgrading with the Standalone Package Processor
Using the Standalone Package Processor, you can upgrade to ZENworks 7 Server Management with SP1 by using the CPKs on any server where the Desktop Management software to be upgraded exists. The Server Management Tiered Electronic Distribution software is not required, and you must upgrade each server individually.
To upgrade the ZENworks Desktop Management components to SP1 by using Software Package Distributions to send the CPKs, complete the steps in the following sections in the order listed:
IMPORTANT:Make sure you have fulfilled the prerequisites outlined in Section 34.3, Upgrade Prerequisites Checklist.
Select a ZENworks 7 Server Management with SP1 Distributor server and copy all of the .cpk files to the Distributor’s file system.
This Distributor server can be used to send all of the CPKs to Subscriber servers of different platforms.
See Step 1 for the locations of the CPK files.
Make a note of where you copied the CPK files so that you have the information when you create the related Software Package Distributions.
For each of your Desktop Management servers, determine which software components need to be updated using the second column in the following table:
Table 34-2 CPK Upgrade Distribution Matrix
For each CPK to be installed on a server, that server needs to have a separate Software Package Distribution sent and extracted on it (except as noted in footnote 1 below). Use the preceding table to determine which Distributions you need to create (which CPKs to upgrade with), determine their Software Package Distribution names (examples in column one), then determine which Subscribers need which Distributions.
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.
1 You can combine the two start CPKs into one Distribution, and the two stop CPKs into another Distribution. It doesn’t matter which is executed first between the Inventory and Wake-on-LAN CPKs. Examples: ZDM7SP1upgr_stop_NW65 and ZDM7SP1upgr_start_NW65.
Continue with Defining Subscriber Variables.
Each Subscriber server being upgraded must have the applicable variables defined in its ConsoleOne properties in order to receive its Distributions and install the CPKs.
If you are upgrading servers that have Inventory Service objects associated with them, use ConsoleOne to create an admin-equivalent user specifically for this CPK upgrade.
This provides password security by not having your Administrator’s DN and password viewable in each Subscriber object’s tab properties. A later step instructs you to disable or remove this admin-equivalent user, or the variable definitions that expose the administrator’s DN and password.
In ConsoleOne, select a Subscriber object.
To save time, you can do one of the following:
Select multiple Subscriber objects and make the same tab entries for all of them.
Create a Service Location Package, add the variables, then associate the package with the eDirectory container where your Subscriber objects reside. This causes the Include Policy option to be displayed on the Subscriber object’s tab.
For more information, see Creating a Policy Package
and Tiered Electronic Distribution
in the Novell ZENworks 7 Server Management Administration Guide.
If only some Subscriber servers have the Inventory Service object associated with them, you can define their variables (see Step 3) separately from the other Subscribers. However, it doesn’t matter if you define those Inventory Service-specific variables on the other Subscriber servers.
Select the tab and fill in the fields for the following variables:
Include policy: If it is displayed, select this option to use the Service Location Package variables that you defined in Step 2.
Assigned Variables: Define the necessary variables ( is optional) for the applicable platforms as listed in the following tables.
IMPORTANT:Where actual values are given in the following tables, these are the ZENworks defaults. Otherwise, the column displays placeholders in italics for the values that are needed. Make sure that the values you enter are correct for your installation.
Table 34-3 NetWare and OES NetWare Variables
1 The other NetWare CPKs do not require variable definitions.
2 Include the colon and backslash. For example, sys:\.
3 These variables are only required for Subscriber servers that have an Inventory Service object associated with them.
Table 34-4 NetWare Cluster Variables
1 The other NetWare CPKs do not require variable definitions.
2 Include the colon and backslash. For example, cluster_vol:\.
3 These variables are only required for Subscriber servers that have an Inventory Service object associated with them.
Table 34-5 Windows Variables
1 Include the colon and backslash. For example, C:\.
2 These variables are only required for Subscriber servers that have an Inventory Service object associated with them.
Table 34-6 OES Linux Variables
1 zdl7mbcksp1.cpk does not require variable definitions.
2 This instance of ConsoleOne must be run from a Windows workstation that has a drive mapped to this path because ConsoleOne uses Windows DLLs.
Repeat Step 3 until all of the applicable variables are defined in the Subscriber properties of the NetWare and Windows servers.
Click to accept the changes and close the Subscriber’s properties.
Repeat Step 2 through Step 5 as necessary until all of the Subscriber servers that are to receive the Distributions have had the necessary variables defined.
Continue with Creating the Distributions.
For more information on creating Distributions, see Distributions
in the Novell ZENworks 7 Server Management Administration Guide.
To create a Software Package Distribution, in ConsoleOne, select the container where you want the Distribution to be created, click > > , select the type, then click .
Specify a Distribution name (see Table 34-2 for examples).
This is only the object name for the Distribution. The Distribution’s files are automatically generated by ZENworks.
If you combine the two start CPKs into one Distribution, or the two stop CPKs into another Distribution, specify an applicable Distribution name, such as ZDM7SP1upgr_stop_NW65 and ZDM7SP1upgr_start_NW65. It doesn’t matter which is executed first or second between the Inventory and Wake-on-LAN CPKs.
IMPORTANT:Periods (.) are not allowed in Distribution names. Instead, use dashes (-) or underscores (_) as word separators. If you use a period in the Distribution name, the Distribution is not sent, and the Distributor is not reloaded after it has been exited.
To assign the Distribution to a Distributor, browse for and select the Distributor object, select , then click .
The Distribution object’s properties are displayed.
Click > and fill in the following fields (for all other fields, accept the defaults):
Active: Required. In order to make a Distribution available to Subscribers, it must be active.
Description: Provide useful details about the Distribution, such as the name of the CPK, the purpose of the CPK, the variables used by the CPK, and so on. (You need to use the scroll bar to access the field.)
Click > and select a platform restriction.
Platform restrictions: To select specific operating system versions as a prerequisite to receiving this Distribution, deselect and select the desired operating system version. You can select from the following options:
No Restrictions NetWare All NetWare 4.x (earlier versions of ZfS supported these platforms) NetWare 5.0 (earlier versions of ZfS supported this platform) NetWare 5.1 NetWare 5.x (earlier versions of ZfS supported these platforms) NetWare 6.x Windows Server Solaris Linux
IMPORTANT:For updating ZENworks Desktop Management, if the target server requires a platform-specific CPK, make sure you restrict this Distribution to that platform.
Selecting the check box means that the Distribution can be sent to any platform.
If you select , you do not need to select any of the individual NetWare platforms.
Select the tab and use the drop-down list to choose the type in the field.
Click , browse for and select a .cpk file, then click .
You might need to change the file viewing selection to , because .spk is the default.
The CPK is inserted in the list box on the tab. Select from the following CPKs:
Table 34-7 NetWare and OES NetWare Servers
|
stopinv.cpk 1 |
zdn7bksp1.cpk |
|
stopwol.cpk 1 |
zdn7midsp1.cpk |
|
startinv.cpk 1 |
c1-zen7-snap.cpk |
|
startwol.cpk 1 |
language-agent.cpk |
1 You can combine the two start CPKs into one Distribution, and the two stop CPKs into another Distribution. It doesn’t matter which is executed first between the Inventory and Wake-on-LAN CPKs.
Table 34-8 Clustered NetWare and OES NetWare Servers
|
stopinv.cpk 1 |
zdnc7bksp1.cpk |
|
stopwol.cpk 1 |
c1-zen7-snap.cpk |
|
startinv.cpk 1 |
language-agent.cpk |
|
startwol.cpk 1 |
|
1 You can combine the two start CPKs into one Distribution, and the two stop CPKs into another Distribution. It doesn’t matter which is executed first between the Inventory and Wake-on-LAN CPKs.
When you are creating Distributions for the language-agent.cpk files, if you will use the same path for the different languages, you can include multiple language CPKs in one Distribution. Also, these language CPKs only copy the MSI files so that they are accessible when needed.
Click .
If you are creating a Distribution for the zdw7midsp1.cpk file, if any of the ZENworks services are disabled on a Windows target server, you must enable those services.
The CPK that upgrades a ZENworks service requires that it is enabled in order to upgrade it. Otherwise, the CPK fails to complete.
If you are creating a Distribution for the zdl7mbcksp1.cpk file and at least one of the servers you are upgrading is a ZENworks imaging server, the novell-tftp, novell-zmgprebootpolicy, and novell-proxydhcp daemons must not be running on it during upgrading; therefore, do the following so that the CPK upgrade can complete successfully on an imaging server:
Click the tab and select .
In the field next to the button, click the list arrow, select , then click .
Rename the default Script to something like PXEstop.
Enter the following script text in the field:
#!/bin/bash if [ -x /etc/init.d/novell-tftp ]; then /etc/init.d/novell-tftp stop fi if [ -x /etc/init.d/novell-zmgprebootpolicy ]; then /etc/init.d/novell-zmgprebootpolicy stop fi if [ -x /etc/init.d/novell-proxydhcp ]; then /etc/init.d/novell-proxydhcp stop fi
Click .
Click the tab and select .
This is a temporary setting. In Setting Up the Schedules, you can configure all of the schedules.
If this is the first time for resolving certificates, click , then select to resolve the certificates; otherwise, it is optional whether you resolve certificates at this time.
For NetWare and Windows servers, this copies the security certificates from the Distributor to Subscriber subscribed to the Channel. For Linux servers (if you do not have drives mapped to them), you might need to resolve the certificates manually.
For more information, see Resolving Certificates
in the Novell ZENworks 7 Server Management Administration Guide.
Repeat Step 1 through Step 12 for each CPK that needs a Distribution created for it.
Continue with Setting Up the Distribution Channels.
In ConsoleOne, right-click a Channels OU, then select > .
Select , then click .
Specify a Channel name, click , then click .
Channels need to be created for each of the following Distributions that you intend to use. Following are suggested Channel names:
NetWare Server
Chnl_ZDM7SP1upgr_stopinv_NW65 (stopinv.cpk)
Chnl_ZDM7SP1upgr_stopwol_NW65 (stopwol.cpk)
Chnl_ZDM7SP1upgr_DMS_NW65 (zdn7bksp1.cpk)
Chnl_ZDM7SP1upgr_startinv_NW65 (startinv.cpk)
Chnl_ZDM7SP1upgr_startwol_NW65 (startwol.cpk)
Chnl_ZDM7SP1upgr_MTS_NW65 (zdn7midsp1.cpk)
Chnl_ZDM7SP1upgr_C1snap (c1-zen7-snap.cpk)
Chnl_ZDM7SP1upgr_LangAgentMSI (language-agent.cpk)
NetWare Server Cluster
Chnl_ZDM7SP1upgr_stopinv_NW65 (stopinv.cpk)
Chnl_ZDM7SP1upgr_stopwol_NW65 (stopwol.cpk)
Chnl_ZDM7SP1upgr_DMS_NW65_Cluster (zdnc7bksp1.cpk)
Chnl_ZDM7SP1upgr_startinv_NW65 (startinv.cpk)
Chnl_ZDM7SP1upgr_startwol_NW65 (startwol.cpk)
Chnl_ZDM7SP1upgr_C1snap (c1-zen7-snap.cpk)
Chnl_ZDM7SP1upgr_LangAgentMSI (language-agent.cpk)
Windows Server
Chnl_ZDM7SP1upgr_DMS_Win (zdw7bksp1.cpk)
Chnl_ZDM7SP1upgr_MTS_Win (zdw7midsp1.cpk)
Chnl_ZDM7SP1upgr_C1snap (c1-zen7-snap.cpk)
Chnl_ZDM7SP1upgr_LangAgentMSI (language-agent.cpk)
OES Linux Server
Chnl_ZDM7SP1upgr_OES-Linux (zdl7mbcksp1.cpk)
Chnl_ZDM7SP1upgr_C1snap (c1-zen7-snap.cpk)
Chnl_ZDM7SP1upgr_LangAgentMSI (language-agent.cpk)
(Optional) In the field, enter useful information.
Click the tab, click , browse for and select the appropriate Distribution, then click to add it into the list box.
To associate the Subscribers that you identified in Step 3 with the current Channel, click the tab, click , browse for and select all of the Subscribers that are applicable to this Channel’s Distribution (upgrade CPK), then click to add them to the list.
IMPORTANT:If you want to test the Distributions on your test servers before sending them into your production environment, select only your test Subscriber servers at this time.
Click the tab and select .
This is a temporary setting. In Setting Up the Schedules, you can configure all of the schedules.
Click to close and save your changes to the new Channel object.
Repeat Step 1 through Step 8 for each Channel that you need to create.
Continue with Setting Up the Schedules.
Use the timing information that you gathered in Step 9 (test server steps) with the following CPK information (example Distribution names with CPK filenames) to determine the best schedules for building, sending, and extracting each of the Distributions. Be sure to write down these decisions; you will implement these schedules later in this procedure.
You need to set up your Build, Send, and Extract schedules to send and extract the Distributions in the following order, and to have the Subscriber servers extract them at a time most convenient for their workload.
NetWare Server
ZDM7SP1upgr_stopinv_NW65 (stopinv.cpk)
ZDM7SP1upgr_stopwol_NW65 (stopwol.cpk)
ZDM7SP1upgr_DMS_NW65 (zdn7bksp1.cpk)
ZDM7SP1upgr_startinv_NW65 (startinv.cpk)
ZDM7SP1upgr_startwol_NW65 (startwol.cpk)
ZDM7SP1upgr_MTS_NW65 (zdn7midsp1.cpk)
ZDM7SP1upgr_C1snap (c1-zen7-snap.cpk)
ZDM7SP1upgr_LangAgentMSI (language-agent.cpk)
IMPORTANT:For the zdn7bksp1.cpk file, the two stop-process helper Distributions (stopinv.cpk and stopwol.cpk) should be sent and extracted immediately. The zdn7bksp1.cpk can be extracted when you can accommodate a service disruption on the NetWare servers (you noted the length of time in Step 9). After that time has elapsed, send and immediately extract the two start-process helper Distributions (startinv.cpk and startwol.cpk).
NetWare Server Cluster
ZDM7SP1upgr_stopinv_NW65 (stopinv.cpk)
ZDM7SP1upgr_stopwol_NW65 (stopwol.cpk)
ZDM7SP1upgr_DMS_NW65_Cluster (zdnc7bksp1.cpk)
ZDM7SP1upgr_startinv_NW65 (startinv.cpk)
ZDM7SP1upgr_startwol_NW65 (startwol.cpk)
ZDM7SP1upgr_C1snap (c1-zen7-snap.cpk)
ZDM7SP1upgr_LangAgentMSI (language-agent.cpk)
IMPORTANT:For the zdnc7bksp1.cpk file, the two stop-process helper Distributions (stopinv.cpk and stopwol.cpk) should be sent and extracted immediately. The zdnc7bksp1.cpk can be extracted when you can accommodate a service disruption on the NetWare servers (you noted the length of time in Step 9). After that time has elapsed, send and immediately extract the two start-process helper Distributions (startinv.cpk and startwol.cpk).
Windows Server
ZDM7SP1upgr_DMS_Win (zdw7bksp1.cpk)
ZDM7SP1upgr_MTS_Win (zdw7midsp1.cpk)
ZDM7SP1upgr_C1snap (c1-zen7-snap.cpk)
ZDM7SP1upgr_LangAgentMSI (language-agent.cpk)
OES Linux Server
ZDM7SP1upgr_OES-Linux (zdl7mbcksp1.cpk)
ZDM7SP1upgr_C1snap (c1-zen7-snap.cpk)
ZDM7SP1upgr_LangAgentMSI (language-agent.cpk)
In ConsoleOne, select a Software Package Distribution object, select the tab, then select a type for the Build schedule.
Build schedule for Software Package Distributions: The Build schedule determines how often the Distributor builds a new version of the Distribution.
This type builds new versions of the Distribution each time the Build schedule starts, regardless of whether the Distribution has changed. It sends this new version to the Subscribers.
When sending a Distribution, the sender retries every 2 minutes for 30 minutes, then stops. It does not begin sending again until the Channel schedule starts again.
The following options allow you to override the Channel’s Send and Subscriber’s Extract schedules:
Send Distribution immediately after building: Overrides the Channel’s Send schedule, allowing you to immediately send the Distribution, rather than wait for the Channel’s Send schedule to start. However, the Subscriber’s Extract schedule determines when it is actually extracted for use.
Extract Distribution immediately after receiving: Overrides the Subscriber’s Extract schedule, allowing the Distribution to be immediately extracted, rather than wait for the Subscriber’s Extract schedule to start. This is useful for Distributions that need to be extracted immediately, such as your Desktop Management upgrade Distributions.
Repeat Step 2 for each upgrade Distribution object.
For each target Subscriber object, select the tab and select a type for the Extract schedule.
Use care in setting the Subscriber Extract schedules. If the schedule is set to and the Subscriber is a parent and is forwarding the Distribution 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 starts.
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.
For more information on the Tiered Electronic Distribution processes, see Tiered Electronic Distribution
in the Novell ZENworks 7 Server Management Administration Guide.
For each Channel object, click the tab and select .
Continue with Sending the Distributions.
To send the Distributions, do one of the following:
Refresh the Distributor Manually: To refresh the Distributor manually, go to ConsoleOne, right-click the Distributor object, then select . This causes the Distribution to be automatically built.
Wait for the Distributor’s Schedule to Start: The Distribution is automatically built when the Distributor’s Refresh schedule starts, which triggers the Build schedule.
The Distribution is automatically sent when the Channel’s Send schedule starts, and is extracted according to the Subscriber server’s Extract schedule, unless you chose to override those schedules when creating the Distribution object. In that case, the Distribution is sent and extracted immediately after it is built.
At that point, the Subscriber servers should be upgraded to ZENworks 7 with SP1 for that CPK’s Desktop Management component.
IMPORTANT:For the Software Package type of Distributions, if a target file is found to be locked during extraction, the Subscriber throws an exception stating that the file could not be copied. The Distributor receives this information from the Subscriber and logs the failure in the reporting database.
For detailed instructions on sending Distributions, see Sending the Distributions
in the Novell ZENworks 7 Server Management Administration Guide.
After the Distribution has been sent and received by the Subscriber servers (it doesn’t need to be extracted yet), set the Channel used to send the upgrade software package to so that this upgrade won’t be sent again to these Subscribers.
For a NetWare cluster, make another node the resource and repeat Step 1 through Step 3.
Repeat Step 2 until all nodes have been upgraded.
If you previously disabled any ZENworks services, then enabed them so they could be upgraded (see Step 9), disable those services again.
Do one of the following:
If you used the administrator DN and password, remove those definitions from each Subscriber objects’ properties.
For information on which Subscribers this applies to, see Step 2.
If you created an admin-equivalent user for this upgrade (see Step 1), either disable or remove the user object.
This secures the DN and password of this temporary admin-equivalent object.
Continue with Section 34.5, Determining if the Upgrade Was Successful.
To use the Standalone Package Processor to upgrade the ZENworks Desktop Management components to SP1 on individual servers, repeat the following tasks for each server:
IMPORTANT:Make sure you have fulfilled the prerequisites outlined in Section 34.3, Upgrade Prerequisites Checklist.
To provide access to the necessary files for upgrading with the Standalone Package Processor:
Select a network location for copying the .cpk and .zip files.
If you copy these files to the following locations, you do not need to edit their paths in the .ncf, .bat, or .sh files:
sys:\temp\cpk\
c:\temp\cpk\
/usr/temp/
Copy all of the .cpk and the .zip or .tar.gz files from the Novell ZENworks 7 with Support Pack 1 Companion 3 CD (OES Linux CPKs) and the Novell ZENworks 7 with Support Pack 1 Companion 4 CD (NetWare and Windows CPKs) to the location determined in Step 1.
Do not copy any files from the \ZENworks Server Management - Software Pkgs directory on the Companion 3 CD; those are only for Server Management use.
If you know the specific components that you want to upgrade and their platforms, you can copy just those .cpk files, including the .zip file from the CD.
To unzip or untar the files:
NetWare/Windows CPKs: Unzip standalone_zdm7sp1_n-w.zip to the root of the server (sys:\ volume or C:\ drive).
This creates or uses an existing \temp directory for the files contained in the ZIP file. The files are placed into subdirectories named \cpk\zdm7sp1\java, \cpk\zdm7sp1\netware, and \cpk\zdm7sp1\windows.
OES Linux CPKs: Untar standalone_zdm7sp1_linux.tar.gz to the root of the server (/).
This creates or uses an existing /usr/tmp directory for the files contained in the ZIP file. The files are placed into subdirectories named zdm7sp1/java and zdm7sp1/linux.
Continue with Determining Which CPKs to Use.
To determine which CPKs you need, use the following table to identify a Desktop Management software component that needs to be upgraded, along with the server’s platform:
Copy the necessary .cpk file to the \temp\cpk directory on the Windows or NetWare server or to the /usr/tmp/zdm7sp1 directory on the Linux server.
Edit the following files as necessary:
NetWare or NetWare Cluster: In a NetWare or Windows-based text editor, open the .ncf file contained in the \temp\cpk\zdm7sp1\netware directory that corresponds to the CPK you want to use and follow instructions in the .bat file concerning values for the variables that need to be defined.
Windows: In a Windows-based text editor, open the .bat file contained in the \temp\cpk\zdm7sp1\windows directory that corresponds to the CPK you want to use and do the following:
Change the existing JREROOT variable path to JRE_installation_path\jre\bin.
where JRE_installation_path matches the path were JRE 1.4.2 is installed (see Section 34.3, Upgrade Prerequisites Checklist).
Follow instructions in the .bat file concerning values for other variables that need to be defined.
OES Linux: In a Linux-based text editor, open the scripts contained in the /usr/tmp/zdm7sp1/linux directory that correspond to the CPKs you want to use and follow the instructions concerning values for the variables that need to be defined.
You can also edit the Linux scripts in a Windows-based text editor:
In a terminal console, enter the following command for each script to be edited:
dos2unix script_filename
where script_filename is the full name of the script to be edited.
If necessary, copy the scripts to your Windows workstation.
Open the scripts in your Windows-based text editor and perform the necessary edits, saving the edited files.
If necessary, copy the edited scripts back to the Linux server.
In a terminal console, enter the following command for each script that you edited:
chmod +RWX script_filename
where script_filename is the script that was edited in the Windows environment.
This is necessary to make the scripts executable in a Linux environment.
Save the .ncf, .bat, or .sh file and exit the editor.
Repeat Step 1 through Step 4 for each server that is to be individually upgraded.
Continue with Upgrading the Server.
If you are upgrading with the zdw7midsp1.cpk file and if any of the ZENworks services are disabled on a target Windows server, you must enable those services.
The CPK that upgrades a ZENworks service requires that it is enabled in order to upgrade it. Otherwise, the CPK fails to complete.
On the server to be upgraded:
NetWare server: At the server’s command prompt, enter
sys:\temp\zdm7sp1\netware\CPK_batchfile_name.ncf
where CPK_batchfile_name corresponds to the NCF file for the CPK being used to upgrade the server.
Repeat this command for each NetWare CPK to be run (for the order, see Setting Up the Schedules).
NetWare cluster: At the resource server’s command prompt, enter
sys:\temp\zdm7sp1\netware\CPK_batchfile_name.ncf
where CPK_batchfile_name corresponds to the NCF file for the CPK being used to upgrade the server.
Repeat this command for each NetWare CPK to be run (for the order, see Setting Up the Schedules).
Reset the resource to another node, then repeat this step, doing so until all nodes have been upgraded.
Windows server: Open a command prompt window and enter
sys:\temp\zdm7sp1\windows\CPK_batchfile_name.bat
where CPK_batchfile_name corresponds to the BAT file for the CPK being used to upgrade the server.
Repeat this command for each NetWare CPK to be run (for the order, see Setting Up the Schedules).
OES Linux server: In a terminal console, stop the following daemons, which must not be running while upgrading, by entering the following commands:
/etc/init.d/novell-tftp stop
/etc/init.d/novell-zmgprebootpolicy stop
/etc/init.d/novell-proxydhcp stop
To upgrade the Desktop Management Server and Middle Tier Server, enter:
/usr/temp/zdm7sp1/linux/sadmlbkmd.sh
(The stopped daemons must not be running while upgrading.)
(Optional) To upgrade the ConsoleOne snap-ins, enter:
/usr/temp/zdm7sp1/linux/sac1snap.sh
(Optional) To copy the language MSI files, enter:
/usr/temp/zdm7sp1/linux/sadmagnt.sh
After the upgrade process has finished, run the following script to restart the imaging server:
/usr/temp/zdm7sp1/linux/sadmlimage.sh
(Optional) To restart the Proxy DHCP service, run the following script where applicable:
/usr/temp/zdm7sp1/linux/sadmlproxy.sh
If you previously disabled any ZENworks services, then enabed them so they could be upgraded (see Step 1), disable those services again.
Continue with Repeating the Upgrade Process.
For each Desktop Management component that you want to upgrade on a particular server using the Standalone Package Processor, repeat all of the steps in Determining Which CPKs to Use and Upgrading the Server.
After upgrading all servers, continue with Section 34.5, Determining if the Upgrade Was Successful.