Upgrade to Linux OES2 Can Remove GroupWise Agent and Startup Files

Upgrading a server from Linux OES 1 ot Linux OES 2 can cause GroupWise 7x Agents or ConsoleOne to be deleted because of package conflicts unless care is taken to prevent it from happening.

NOTE: Linux OES 2 is an unsupported platform for running GroupWise 6.5

If the GroupWise Agents or ConsoleOne is accidently removed, run the appropriate install from the software distribution directory.

The instructions listed below for the upgrade process can also be found in the GroupWise 7.0 SP3 Readme when the service pack becomes available.

When you upgrade from Open Enterprise Server (OES) 1 to OES 2 with GroupWise installed on
your OES server, you encounter package conflicts that must be resolved. A pop-up message appears
immediately before the Installation Settings screen that informs you that the Delete Unmaintained
Packages option is selected under Update Options. OES 2 considers GroupWise an"unmaintained
package.” This means that, by default, your GroupWise software will be deleted as part of the
upgrade process, unless you follow the instructions below.

1Read the pop-up warning carefully, then click OK to close the pop-up.
The pop-up describes three possible actions you can take to resolve the GroupWise status as an
unmaintained package. This procedure steps you through the second of the three possible
actions. This alternative works most efficiently for preserving your GroupWise installation.

2When ConsoleOne®is installed on the server:

The following message displays below the Packages link on the Installation Settings screen:

"Cannot solve all conflicts. Manual intervention is required."

2aClick the Packages link.

The upgrade process checks for package conflicts, then displays the following message:

"NOVLc1-1.3.6-1.i386 is locked and cannot be uninstalled."

2bSelect Keep NOVLc1, then click OK - Try Again.

The upgrade process checks again for conflicts for NOVLc1 and displays one or more
package-related warnings, providing you with alternatives for how to handle each conflict.
The specific warnings you receive depend on the packages installed on the server you are
upgrading. Therefore, warnings vary. Here are some examples:

"NOVLc1-1.3.6-1.i386 cannot be installed due to missingdependencies."
"novell-eguide-2.1.32.noarch cannot be installed due tomissing dependencies."

The messages fall into two categories of problems:

Missing dependencies for ConsoleOne (the NOVLc1 package)Missing dependencies for some other product package besides ConsoleOne (forexample, eGuide)

The following steps help you decide which action to take for each type of message.

2cIf the message indicates missing dependencies for ConsoleOne (NOVLc1), select Ignore This Requirement Just Here.

2dIf the message indicates missing dependencies for some other product package besides
ConsoleOne, and you are sure that you do not want that product package, select Delete>.

WARNING:ConsoleOne is dependent on a variety of packages. Delete packages only when you are certain that they are not required by ConsoleOne. If in doubt, select Keep .

2eWhen you have selected an action for each conflict message, click OK - Try Again.

The upgrade process checks again for conflicts for NOVLc1. Additional messages might
be displayed for you to select actions to resolve the conflicts. This cycle repeats until all
conflicts have been resolved, then you successfully reach the Packages page.

3On the Packages page, select Search in the Filter field.

4Search for the GroupWise packages that are installed on the server by typing the following in
the Search field:

novell-groupwise

5Click Search.

Depending on what GroupWise components are installed on the server, the search results
include some of the following packages:

novell-groupwise-admin
novell-groupwise-agents
novell-groupwise-dbcopy
novell-groupwise-gwcheck
novell-groupwise-gwha
novell-groupwise-gwia
novell-groupwise-gwinter
novell-groupwise-gwmon
novell-groupwise-monitor
novell-groupwise-webaccess

6Right-click the first GroupWise package in the list, then click All in This List > Keep.

This changes the status of each GroupWise package from Delete to Keep.

7Search for the NOVLc1 package.

The NOVLc1 and NOVLc1Linuxjre packages should be listed and marked as locked. This
means that they will not be deleted.

8If these packages are marked with a Delete status, change their status to Keep.

9Click Accept on the Packages page.

10If you are presented with a font License Agreement, click Accept.

11Click Continue to return to the Install Settings page.

12Verify that the package conflict message is now gone from under the Packages link, then
continue with the upgrade process.

13After you have finished the upgrade, reinstall the NDSbase RPM that was originally installed
with ConsoleOne.

The upgrade process removed it, but it is still needed by ConsoleOne.

13aIn a Linux terminal window, log in as root, then change to the directory where you
originally extracted the ConsoleOne files.

13bChange to the Linux subdirectory.

13cUse the following command to reinstall the NDSbase RPM:

rpm -ivh NDSbase-8.7.3.7-38.i386.rpm