GroupWise 6.5 Support Pack 1

June 27, 2003

Overview

The information in this Readme file pertains to GroupWise® 6.5 Support Pack 1.

This Support Pack contains updates for all components contained in the GroupWise 6.5 product. You must have GroupWise 6.5 installed before you install Support Pack 1.

For information on the latest Support Pack issues, see TID 10084510 at the Novell Support Web site .

This Support Pack does not contain updates for GroupWise Messenger. GroupWise Messenger 1.0 Support Pack 1 is a separate download.

1.0 Support Pack Installation
1.1 GroupWise Version Information
1.2 Prerequisites
1.3 Downloading the Support Pack
1.3.1 Downloading the Regular Version
1.3.2 Downloading the ISO Version
1.4 Installing the Support Pack
2.0 Installation Issues
2.1 Recommendation for Overwriting Newer Files
2.2 WebAccess and Monitor on the Same Web Server
2.3 Wireless Device Support for WebAccess and Monitor
2.4 Windows 2000 Service Pack 2 or Later Required for Agents
2.5 Additional Installation Issues
3.0 Component Issues
3.1 Administration Issues
3.1.1 Directory Names and Filenames
3.1.2 Server Names
3.1.3 ConsoleOne on Windows NT
3.1.4 GWTSA and Duplicate Source Directories
3.1.5 Quotas on NSS Volumes
3.1.6 TurboFat Compatibility
3.2 Agent Issues
3.2.1 POA Slows Down
3.2.2 Potential CAP Port Conflict
3.3 Client Issues
3.3.1 NetWare 5.1 SP1 Compatibility for Client Installation
3.4 Internet Agent Issues
3.4.1 Address Resolution Change Since GroupWise 6
3.5 Monitor Issues
3.5.1 Restoring Monitor Settings after Reinstallation
3.6 WebAccess Issues
3.6.1 Unicode Support
3.6.2 Using the Latest Novell Client
3.6.3 Display Problems with Netscape 4.x
3.6.4 Installing to Non-Supported Web Servers
3.6.5 Configuring WebAccess to Use a Java Servlet Engine Other Than the Novell Servlet Gateway or Tomcat Servlet Engine
3.6.6 Login Page Reappears after Successful Login
3.6.7 Security Issue with WebAccess and Internet Explorer 5.0
3.6.8 Recommendation for Tomcat Memory Allocation (Heap Size)
4.0 International Issues
4.1 Double-Byte Characters in Directory Names and Filenames
4.2 Double-Byte Characters in Passwords
4.3 Euro Character in Subject Field
4.4 Print Calendar Language
4.5 RichWin and GroupWise 6.5
5.0 Defect Fixes
5.1 Address Book Fixes
5.2 Administration Fixes
5.3 Admin API Fixes
5.4 Agent Fixes
5.5 Client Fixes
5.6 Client API Fixes
5.7 Engine Fixes
5.8 GWCheck Fixes
5.9 Internet Agent Fixes
5.10 Monitor Fixes
5.11 WebAccess Fixes
6.0 Documentation
6.1 GroupWise 6.5 Readme Files
6.2 GroupWise 6.5 Installation Guide
6.3 GroupWise 6.5 Administration Guide
6.4 GroupWise 6.5 Help
7.0 Documentation Conventions
8.0 Legal Notices

1.0 Support Pack Installation


1.1 GroupWise Version Information

GroupWise 6.5 Support Pack 1 can be applied to the following GroupWise version in your software distribution directory:

When you update the software distribution directory, all GroupWise components should be updated to keep them at the same version level.


1.2 Prerequisites

Before installing GroupWise 6.5 Support Pack 1:


1.3 Downloading the Support Pack

GroupWise 6.5 Support Pack 1 is available in regular format for installing from a local or network driven and in ISO format for burning CDs. You can choose between multilingual and English-only downloads.


1.3.1 Downloading the Regular Version

The regular-format download is available as one self-extracting (.exe) file that includes both administrative and client files.

  1. In the list of Support Packs, click GroupWise 6.5 Admin/Client SP1.

  2. Click the filename (gw65sp1m.exe for multilingual or gw65sp1e.exe for English only), then follow the instructions to download the file into a temporary directory.

  3. Extract the .exe file into a directory at the root of your local drive or to a network server drive that can handle long pathnames.

    The compressed file contains directory paths that could exceed DOS limits.

  4. Continue with Section 1.4: Installing the Support Pack.


1.3.2 Downloading the ISO Version

The ISO-format download is available as two self-extracting (.exe) files, one for the GroupWise Administrator CD and one for the GroupWise Client CD.

  1. In the list of Support Packs, click GroupWise 6.5 Admin SP1 ISO for the GroupWise Administrator CD.

  2. Click the filename (gw65asp1m.exe for multilingual or gw65asp1e.exe for English only), then follow the instructions to download the file into a temporary directory.

  3. In the list of Support Packs, click GroupWise 6.5 Client SP1 ISO for the GroupWise Client CD.

  4. Click the filename (gw65csp1m.exe for multilingual or gw65csp1e.exe for English only), then follow the instructions to download the file into a temporary directory.

  5. Extract the administrator and client .exe files into two separate directories at the root of your local drive or to a network server drive that can handle long pathnames.

    The compressed files contain directory paths that could exceed DOS limits.

  6. Burn a separate CD for each directory.

  7. Continue with Section 1.4: Installing the Support Pack.


1.4 Installing the Support Pack

Use Windows to run the GroupWise setup.exe program extracted in the preceding section.

  1. Click Start > Run > Browse.

  2. Select the setup.exe file on the local or network drive.

    or

    Select the setup.exe file at the root of the GroupWise Administrator CD.

  3. Click OK to run the GroupWise Installation program.

  4. Follow the on-screen instructions provided in the GroupWise Installation program to update the software distribution directory and the administration, agent, and client software that is in production.

  5. After applying the Support Pack on NetWare® servers where GroupWise agents are running, restart the servers to ensure that all updated NLMTM programs are loaded.

    This will resolve any errors you might see during the update process.


2.0 Installation Issues


2.1 Recommendation for Overwriting Newer Files

When the gwpo.dc and ngwguard.dc files from the original GroupWise 6.5® release are installed, they receive the date and time when they are installed rather than retaining their original date and time. As a result, they might have a newer date and time than the gwpo.dc and ngwguard.dc files in Support Pack 1. If they do, you receive the following message:

"The files you are installing are older than the files on your system. Do you want to replace these files?"

Typically you should respond No to such a prompt, but in this case you should respond Yes so that the Support Pack version of the .dc files are installed. If necessary, you can manually copy these files from GroupWise 6.5 Support Pack 1 to the corresponding location in the software distribution directory:

\po\gwpo.dc
\domain\gwpo.dc
\po\ngwguard.dc
\client\win32\ngwguard.dc

You might also see this message if you are installing GroupWise 6.5 Support Pack 1 as an update to GroupWise 6 where Support Pack 3 or later has been installed. Again, respond yes to overwrite new newer files.

As an alternative, you can create a new software distribution directory for the GroupWise 6.5 Support Pack 1 files.


2.2 WebAccess and Monitor on the Same Web Server

The WebAccess Application, WebPublisher Application, and Monitor Application share a common library. If you plan to run these applications on the same Web server, you must update all three before any of them will work properly.


2.3 Wireless Device Support for WebAccess and Monitor

The GroupWise WebAccess and Monitor software included in GroupWise 6.5 Support Pack 1 supports the following wireless devices:

We are continually evaluating and adding support. As we add support for additional devices, we will post the updates at the Novell® GroupWise Wireless Web site. We encourage you to check this site frequently for updates and news.


2.4 Windows 2000 Service Pack 2 or Later Required for Agents

If the GroupWise Post Office Agent, Message Transfer Agent, Internet Agent, and WebAccess Agent are installed on Windows 2000 and the GroupWise domain and/or post office directories accessed by the agents are on NetWare® servers, you need to apply Windows 2000 Service Pack 2 or later on the Windows servers. You can download Windows 2000 Service Packs from Microsoft*.

NOTE:  If, as required with the initial release of GroupWise 6, you already installed Microsoft HotFix Q266066 on all Windows 2000 servers where GroupWise agents run, you do not need to apply Windows 2000 Service Pack 2 or later.


2.5 Additional Installation Issues

Installation issues for individual GroupWise components are located under the heading for each component.


3.0 Component Issues


3.1 Administration Issues


3.1.1 Directory Names and Filenames

All directory names in paths to GroupWise domains and post offices can consist of up to 8 characters.

Filenames can also consist of up to 8 characters, with extensions of up to 3 characters. Do not use long filenames for any files used by any GroupWise components. This requirement applies even to files that are not specific to GroupWise (such as SSL certificates and key files).


3.1.2 Server Names

When filling in a UNC Path field in ConsoleOne®, you must specify the server name. You cannot use an IP address or DNS host name.


3.1.3 ConsoleOne on Windows NT

If you will run ConsoleOne on Windows NT* 4, you must install NT 4 Service Pack 6 before you install ConsoleOne.


3.1.4 GWTSA and Duplicate Source Directories

GWTSA handles situations where the same directory names are used on different volumes to back up by numbering the instances. For example:

Original GWTSA:
GroupWise System/[Dom]Provo2:
GroupWise System/[Dom]Provo2:

Support Pack GWTSA:
GroupWise System/1[DOM]Provo2:
GroupWise System/2[DOM]Provo2:

Each instance is numbered and DOM is in all uppercase letters. After updating GWTSA with Support Pack 1, you must re-create your backup jobs because the path has changed.


3.1.5 Quotas on NSS Volumes

If you use NSS volumes with quotas turned on, then you must turn on quotas on all GroupWise directories. Otherwise, you will receive No Disk Space errors.


3.1.6 TurboFat Compatibility

If you see E811 errors on the POA or the GroupWise client, a possible cause is that TurboFat is corrupting GroupWise database pointers. The solution is to turn off TurboFat.

These NLMTM programs disable TurboFat at startup.


3.2 Agent Issues


3.2.1 POA Slows Down

If you are running the POA on NetWare 6.0 Support Pack 2 on a multiprocessor such as a Dell* 6650 PowerEdge* or an IBM* Netfinity, the POA might gradually slow down after a few hours or a day, depending on its load. GroupWise client users will also experience extremely slow response time from the POA. Update from NetWare 6.0 Support Pack 2 to Support Pack 3.


3.2.2 Potential CAP Port Conflict

By default, the POA uses 1026 for its CAP (Calendar Access Protocol) port. On some Windows 2000 servers, port 1026 is already used the Windows Task Scheduler or other Windows service. If this occurs, configure the POA to use a different CAP port in ConsoleOne.


3.3 Client Issues


3.3.1 NetWare 5.1 SP1 Compatibility for Client Installation

If you are using the AutoUpdate feature for installing the GroupWise 6.5 client, you might encounter an error if you are installing the client from a NetWare 5.1 server where a Support Pack has been installed. The setupip.exe program used during the AutoUpdate process might not run correctly.

To resolve the problem, you must modify the magnus.conf file located in the following directory:

sys:\novonyx\suitespot\http-web_server_name\config

by adding the following line:

MaximumFilesReturnedInIndex 500

Then run the client installation again.


3.4 Internet Agent Issues


3.4.1 Address Resolution Change Since GroupWise 6

In GroupWise 6 and its Support Packs, there was a problem with the address format used for sending to distribution lists and resources if you set Internet Addressing to one of the following formats (which are not appropriate for distribution lists and resources):

Messages to distribution lists and resources were initially undeliverable and were sent to the Internet Agent. The Internet Agent then successfully resolved the addresses and sent the messages back into the GroupWise system. Users did not notice the problem, but some administrators noticed unnecessary traffic through the Internet Agent.

In GroupWise 6.5, the address format problem for sending to distribution lists and resources was corrected. However, users who originally used GroupWise 6 have the erroneous address format for distribution lists and resources in their Frequent Contacts address books. If unnecessary traffic through the Internet Agent is a continuing problem, have users delete distribution lists and resources from their Frequent Contacts address books so that the correct address format is used for name completion in the future.


3.5 Monitor Issues


3.5.1 Restoring Monitor Settings after Reinstallation

Monitor settings are stored in the monitor.xml file in the Monitor installation directory. If you reinstall the Monitor software, the monitor.xml file is backed up as monitor.001. To restore previous Monitor settings, remove the newly installed monitor.xml file and rename monitor.001 to monitor.xml.


3.6 WebAccess Issues


3.6.1 Unicode Support

Unicode* support using UTF-8 encoding has been implemented in WebAccess to provide better support for international character sets. Unicode support enables users to intermix characters within the same message and have all character sets display correctly.

For Support Pack 1, Unicode support is not fully implemented for double-byte character set languages (CBCS languages). In order to correctly compose in a DBCS languages, users need to set their browser accept language to the desired DBCS language. And in Support Pack 1, intermixing two different DBCS languages is not supported. These limitations will be removed in the next version of WebAccess.

If you will update to Support Pack 1 in stages, update the WebAccess Agent first throughout your system, then update the WebAccess Application. If the update to Unicode support causes undesirable side effects for your particular languages or combination of languages, you can turn it off using the /utf8off startup switch with the WebAccess Agent. Then comment out the Charset.default setting in the webacc.cfg and webpub.cfg files. This procedure will not be necessary after Unicode support is fully supported for DBCS languages.


3.6.2 Using the Latest Novell Client

If you receive an error during installation indicating that the nvweb.dll file cannot be found, update the workstation to the latest Novell ClientTM. The Novell Client is available for download from the Novell Software Downloads site.


3.6.3 Display Problems with Netscape 4.x

If you experience display problems using Netscape* 4.x with WebAccess, update to a later version of Netscape.


3.6.4 Installing to Non-Supported Web Servers

The GroupWise WebAccess Installation program installs the WebAccess and WebPublisher Applications to the Web servers listed below. These are the Web servers for which Novell Technical ServicesSM will provide support.

If necessary, you can run the WebAccess and WebPublisher Applications on a non-supported Web server as long as the Web server supports a Java* servlet engine that is JSDK 2.0 and JDK* 1.1.6 compatible. However, the Installation program will not install the applications to other Web servers, which means you must manually install and configure them. When you run the Installation program, deselect the options to install the WebAccess Application and WebPublisher Application, install the WebAccess Agent, then complete the following steps to install the applications:

  1. Unzip webaccess.zip to the root of the network server volume where the Web server resides.

    The webaccess.zip file and the ZIP files referred to in the next three steps are in the \internet\webacces\other directory of GroupWise 6.5 Support Pack 1.

  2. Unzip webaccessdocs.zip to the Web server's document root directory.

  3. Unzip webaccessservlets.zip to the servlet root directory.

  4. Unzip webaccessjars.zip to a library or jar file directory on the network server (for example, you might want to create a \novell\lib directory), then add the jar files (ldapfilt.jar, ldapjdk.jar, njgwap.jar, njweb.jar, spellservlet.jar, xalan.jar, and xerces.jar) to the class path.

  5. Modify your Java engine's servlet properties file to include the settings shown in the sample WebAccess servlets.properties file.

    The WebAccess servlet.properties file is located in the \internet\webacces\other directory of GroupWise 6.5 Support Pack 1.

  6. Modify the Templates.path setting in the webacc.cfg and webpub.cfg files, located in the \novell\webaccess and \novell\webpublisher directories, to replace java/servlets with the path to the servlet root directory.

  7. If you created the \novell directory structure in the location specified in step 4 (the root of the volume where the Web server resides), the paths for the following settings in the webacc.cfg and webpub.cfg should already be correct. If not, you need to modify the paths to make them correct from the perspective of the Web server.

    File.Upload.path
    Log.path
    Security.Timeout.path
    Provider.GWAP.Config.file
    Provider.LDAP.Config.file (webacc.cfg only)

  8. Copy the index.html file to the Web server's document root directory.

    You can replace your Web server's current default home page with this file, or you can rename the file and link to it from your current default home page.

  9. Copy the commgr.cfg file, located in the WebAccess gateway home directory (domain\wpgate\webac65a), to the \novell\webaccess directory and the \novell\webpublisher directory.


3.6.5 Configuring WebAccess to Use a Java Servlet Engine Other Than the Novell Servlet Gateway or Tomcat Servlet Engine

If you use a Java servlet engine other than the Novell Servlet Gateway or the Tomcat servlet engine, the servlet engine needs to be JSDK 2.0 and JDK 1.1.6 compatible.

After you've installed WebAccess, complete the following tasks to configure WebAccess to work with the Java servlet engine:

  1. Modify the Java servlet engine's servlet properties file to include the settings shown in the sample WebAccess servlets.properties file.

    The sample servlets.properties file is located in the \internet\webacces\other directory of GroupWise 6.5 Support Pack 1.

  2. In the webacc.cfg and webpub.cfg files, modify the Templates.path setting to replace java/servlets with the path to the servlet root directory.

    The files are located in the novell\webaccess and novell\webpublisher directories on the root of the server.

  3. Add the WebAccess jar files (ldapfilt.jar, ldapjdk.jar, njgwap.jar, njweb.jar, spellservlet.jar, xalan.jar, and xerces.jar) to the class path.

    On a NetWare server, the jar files are located in the java\lib directory. On a Windows server, the files are located in the novell\java\lib directory.


3.6.6 Login Page Reappears after Successful Login

If the WebAccess login page appears in one or more of the frames (for example, the Folder list or the Item list) after a WebAccess user has successfully logged in, the user is probably accessing WebAccess through one or more proxy servers.

To prevent this problem:

  1. In ConsoleOne, right-click the WebAccess Application object (GroupWiseWebAccess), then click Properties.

  2. On the Security page (located on the Application tab), deselect the Use Client IP in Securing Sessions option.

    For information about this option, click Help on the Environment page.

  3. Click OK to save the change.


3.6.7 Security Issue with WebAccess and Internet Explorer 5.0

When using Internet Explorer 5.0 to view messages through WebAccess, URLs to messages become part of the History cache and can be read by other users who have access to the same workstation. For solutions to this problem, see TID 10056452 in the Novell Knowledgebase.


3.6.8 Recommendation for Tomcat Memory Allocation (Heap Size)

If you are using the Tomcat servlet engine with GroupWise WebAccess, the maximum memory allocation (heap size) for Tomcat should be at least 128 MB. The maximum memory allocation is set by using the -Xmx parameter when starting Tomcat (for example, -Xmx128m).


4.0 International Issues


4.1 Double-Byte Characters in Directory Names and Filenames

Do not use double-byte characters in directory names and filenames.


4.2 Double-Byte Characters in Passwords

Do not use double-byte character in users' passwords.

The Change GroupWise Password dialog box in ConsoleOne currently allows entry of double-byte characters. However, the GroupWise client login does not allow entry of double-byte characters in passwords, so a user who was assigned a password with double-byte characters in ConsoleOne would not be able to type the double-byte characters when attempting to log in to GroupWise.


4.3 Euro Character in Subject Field

If a WebAccess client user receives a message, task, or appointment with a Euro character in the Subject field, it might display as an upside-down question mark when viewed in the Java version of the Calendar. The issue resides with the user's browser.

Netscape users need to upgrade to Netscape Communicator* 6.

Internet Explorer users need to be using at least version 3309 of the JVM*. The latest JVM can be downloaded from the Microsoft Web site and installed on the user's workstation. This JVM enables Internet Explorer 4.x and later to correctly display the Euro character.


4.4 Print Calendar Language

The GroupWise client Print Calendar feature always prints calendars in the language specified in Regional Options or Regional Settings in the Control Panel, even if the client is installed in a different language. For example, if French (Switzerland) or French (Swiss) is specified in the Control Panel and the client is installed in German, calendars will print in French.


4.5 RichWin and GroupWise 6.5

If you use RichWin in combination with GroupWise 6.5, be sure to run RichWin first, then run GroupWise.


5.0 Defect Fixes


5.1 Address Book Fixes


5.2 Administration Fixes


5.3 Admin API Fixes


5.4 Agent Fixes


5.5 Client Fixes


5.6 Client API Fixes


5.7 Engine Fixes


5.8 GWCheck Fixes


5.9 Internet Agent Fixes


5.10 Monitor Fixes


5.11 WebAccess Fixes


6.0 Documentation


6.1 GroupWise 6.5 Readme Files

For Readme information about specific GroupWise 6.5 components, see the following additional Readme files that shipped with the original release of GroupWise 6.5:

Administration: \admin\readmeus.txt
Agents: \agents\readmeus.txt
Client: \client\win32\readmeus.txt
WebAccess: \internet\webaccess\readmeus.txt
Internet Agent:\internet\gwia\readmeus.txt
Monitor: \admin\monitor\readmeus.txt


6.2 GroupWise 6.5 Installation Guide

For detailed installation and update instructions, see the GroupWise 6.5 Installation Guide (GroupWiseInstallationGuide.pdf) in the \docs\us directory of the Support Pack. It has been updated to correspond with GroupWise 6.5 Support Pack 1.


6.3 GroupWise 6.5 Administration Guide

For additional GroupWise 6.5 documentation, see the GroupWise 6.5 Administration guide at the Novell Documentation Web site. It has been updated to correspond with GroupWise 6.5 Support Pack 1.


6.4 GroupWise 6.5 Help

To support accessibility requirements within GroupWise Help, the Help for all GroupWise components uses Microsoft HTML Help. In order for Microsoft HTML Help to display on a Windows workstation, the workstation must have Internet Explorer 4.x or later installed.


7.0 Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (®, TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.


8.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.

U.S. Patent Nos. 4,555,775; 4,580,218; 5,412,772; 5,701,459; 5,717,912; 5,760,772; 5,870,739; 5,873,079; 5,884,304; 5,903,755; 5,913,209; 5,924,096; 5,946,467; 5,963,938; 6,081,804; 6,138,170; 6,167,393; D393,457; 6,216,123 and Patents Pending.

Copyright © 2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

GroupWise, NetWare, and Novell are registered trademarks of Novell, Inc. in the United States and other countries.

NLM is a trademark of Novell, Inc.

All third-party trademarks are the property of their respective owners.