This page is provided to update the GroupWise 8 Upgrade Guide in between major announced releases.Subscribe to our blog's rss feed to get notified immediately when there is a change to the errata page.

The following changed have been made since version 1.0.07:

GroupWise 8.01 on SLES11

GroupWise 8.01 adds support for SLES11. While for the most part everything will run exactly the same, some items (such as ncpfs) are only available on the SDK DVD, so you might have to go hunting for files.

Additionally, if you are running ConsoleOne on SLES11, you may run into Java errors. TID 7004506 on the Novell Support site has instructions on installing Java 1.6 and modifying the JREHome Path in the ConsoleOne script on that server. It has also been reported that if you are running ConsoleOne as a non-root user, you may need to change the permissions of the ConsoleOne script to 666.

GroupWise 8/8.01 POA on NetWare

The GroupWise Document Converter Agent is intended to provide indexing capabilities for document types that are not supported by the QuickFinder process running at the Post Office Agent. For example, the DCA can index PDFs, docx files OpenOffice files and other types not previously supported. This allows for both attachments in the GroupWise system and documents in the GWDMS to be indexed and included in searches in the GroupWise client. However, on NetWare there is no viewer for Acrobat files, and when the DCA attempts to index a PDF the DCA process crashes.

Problems with the GWDCA running on NetWare still persist (and by some accounts are worse in GroupWise 8.01 than on GroupWise 8 shipping code). If you are running a Post Office Agent on NetWare, there are two ways to address this:

• Disable the DCA altogether: If you have no need for the DCA at all, then put the /nodca switch in your POA startup file. This will effectively remove the functionality of the DCA and return your NetWare post office to the same indexing functionality of GroupWise 7.
• In order to simply remove the attempts at indexing PDFs, add /dcafilter-"pdf,img" to your post office startup file. While this is the preferred method (because it allows for indexing of other new document types), if you run into any additional problems with the DCA crashing after enabling this switch, the final solution is to add the /nodca switch as indicated above. Note that all file types indicated in this switch will be skipped during the indexing.

On November 21, 2008 we released version 1.0 of the Upgrade Guide. And of course we immediately found small changes :) If you have a version earlier than 1.0.07, the changes made, and needed to be documented are as follows:

1.0.07 additions:

Added to Chapter 6 - Web Access

At the bottom of page 92, after Step 17:

NOTE: Occasionally the NetWare installation will seem to stall when it comes time to copy the files to the server. This can be avoided by leaving Apache2 and Tomcat loaded, and allowing the installation routine to shut these components down during the installation.

1.0.06 additions:

Added to Chapter 1 - Preparing

The following section was inadvertantly left out of the guide.

GroupWise Client Requirements

For the GroupWise client, a few things have changed that are important.

Windows

GroupWise 7 was no longer supported on Win9x machines. GroupWise 8 is no longer supported on Windows 2000 machines. In fact, for many sites who have tested it, even installing on Windows 2000 has failed. If you still have PCs in your environment running Windows 2000, you should use the GroupWise 7 client. Here are the specifics:

• Windows XP on a 300 MHz or higher workstation with at least 128 MB of RAM
• Windows 2003 on a 350 MHz or higher workstation with at least 256 MB of RAM
• Windows 2003 R2 on a 350 MHz or higher workstation with at least 256 MB of RAM
• Windows Vista* on a 1 GHz or higher workstation with at least 1 GB of RAM
  

  200 MB of free disk space on each user’s workstation is recommended to install the Windows client.

It is VERY important that you notice that Windows 2000 is no longer supported. The problem is that the installation routine will happily attempt to upgrade a Windows 2000 workstation, and then you will be faced with a bit of cleanup. DO NOT enable Auto-Update for your post office if you have WIndows 2000 users, without a bit of pre-planning. We will discuss this more in Chapter 8.

Linux

For Linux, the only supported platform is SuSE Linux Enterprise Desktop 10. We have tested the client on various OpenSuSE versions, and it seems to perform properly. That said, however, remember that the only supported platform is SLED 10. The client will run with either KDE or GNOME.

Mac

Interestingly, the Mac client seems to run on the most diverse versions of the operating system than either Windows or Linux! You can run the GroupWise 8 Mac client on:

• Mac OS 10.4 (Tiger)
• Mac OS 10.5 (Leopard)
• Mac OS X for Intel
• Mac OS X for PowerPC

Changed in Chapter 8 - Upgrading Clients

• The fourth bullet on page 108 was changed as follows:

The setup.cfg file is used to define whether or not clients should auto-update their software when all of the conditions of update are met.

• Step 2 in the first half of page 108 was changed as follows:

  Next the setup.cfg that is contained in the /client directory of the SDD is configured to perform the auto-update, and this file is copied into the /client/win32 directory of the SDD. In reality, the default of the setup.cfg is to perform the auto-update, so if you wish to prevent auto-update after performing Step 3 following, you should change the AutoUpdate value to Enabled=No.

• Step 4 in the bottom half of page 108 was changed as follows:

  The client then looks in the setup.cfg, and if the Auto-Update value is set to “Enabled=Yes”, the client upgrades. Since the default for the Auto-Update is “Enabled=Yes” and occurs even if you do not configure the setup.cfg, if you wish to prevent the Auto-Update from occurring once you associate a GroupWise 8 SDD to your post office, you must place the setup.cfg file into the <sdd>/client/win32 directory, and change the Auto-Update Enabled value to No.

• A Note was added on page 110

  NOTE: If you want to enable Auto-Update, and at the same time prevent Windows 2000 users from upgrading, you can change the BuildNumber value in HKEY_LOCAL_MACHINE\SOFTWARE\Novell\GroupWise\BuildNumber to the same value as the software.inf file (shipping version this is 4100). Make sure this is in decimal format.

• Added at end of Chapter 8

Configuration Settings of Note

Here are a few things that you might be interested in as you upgrade the clients:

Sent Items Folder Issues:

Renamed Sent Items Folder: The first time a former GroupWise 6.0 and earlier user logs into the GroupWise 8 post office, the POA will convert the Sent Items folder into a new system level folder, rather than the former search folder that was the Sent Items folder in earlier versions. This will generally be transparent to the users. However, if the user has in the past deleted the Sent Items search folder and then recreated it, the user may find that there is now both a Sent Items folder, and an “Old Sent Items” folder just above the Sent Items folder. The “Old Sent Items” is also a search folder, and can be deleted without removing any messages.
No Sent Items In a GroupWise 5.5x or 6.0x Client: If as in the above case, the new Sent Items folder is created, but your users continue to access GroupWise with an older 5.5x or 6.0x client, it will not recognize the new Sent Items folder, and will not appear to have a Sent Items folder at all. You can recreate the Sent Items query folder if necessary. Of course it’s better to just upgrade the client if possible!

GroupWise 8 Home View (thanks to Scott Campbell and Herb Parsons for this tip)

In GroupWise 7, Novell introduced the new Home View. The first time a new GroupWise 8 user clicks on the Home folder, he will see a “Welcome” screen that explains the home view usage. However, if your upgrade is from GroupWise 7, the user has already been confronted with this welcome screen before, and if the “Do not show this screen again” box has been checked, it will not appear when opening the Home View with the GroupWise 8 client. This s a registry setting found here:

HKEY_CURRENT_USER\Software\Novell\GroupWise\Client\Setup\Show Home Folder Help

Change this key entry to “1” (for yes) and the Home View Welcome will reappear.

1.0 - 1.0.05

Various typos, formatting issues and general editing. We apologize for the problems. Danita was tired!

The following section was added to both Chapter 2 and Chapter 3:

Running More Than One MTA on the Same Server

The new GroupWise 8 MTA opens a SOAP connection (for administrative purposes) on
port 7161. If you intend to run more than one MTA on any particular server, you must set a
unique SOAP port for the additional MTAs. This cannot be done in ConsoleOne, but must be
configured in your MTA startup file. The default port is 7161. For each additional MTA you
should set an alternative port. For example:

• NetWare/Windows: /soapport-7162
• Linux: -- soapport 7162