1

GroupWise 6 Support Pack 2
July 25, 2002

Overview

The information in this Readme file pertains to GroupWise 6 Support Pack 2.

This Support Pack contains updates for all components contained in the GroupWise product only. If the Support Pack file was downloaded, it must be extracted at the root of the drive because it contains directory paths that could exceed the DOS limits.

The purpose of this Support Pack is to provide a bundle of fixes that have all been tested together. These files have undergone component testing, core OS testing, and integration testing with other Novell products.

This Support Pack includes all fixes from the previous Support Pack; therefore, you do not need to install Support Pack 1 before installing this Support Pack. Do not install individual files from the Support Pack.

Install the NetWare Support Pack before installing other Novell product support packs like GroupWise and BorderManager. These Support Packs are included with the Consolidated Support Pack, or they can be downloaded individually from http://support.novell.com/tools/csp/.

For information on the latest Support Pack issues, see TID 10070085 in the Novell Knowledgebase at http://support.novell.com/search/kb_index.htm.

If you experience problems downloading large files, refer to TID 2947202.

To order the Support Pack CD, go to http://support.novell.com/tools/csp/orderinfo.html.

Table of Contents

1.0 Support Pack Installation
    1.1 Version Information
    1.2 Prerequisites
    1.3 Installing the Support Pack

2.0 Installation Issues
    2.1 NDS Schema Extension during Installation
    2.2 Windows Version Requirements for WebAccess and Monitor
    2.3 WebAccess and Monitor on the Same Web Server
    2.4 Wireless Device Support for WebAccess and Monitor
    2.5 Windows 2000 Service Pack 2 or Above Required for Agents
    2.6 WSOCK32.DLL Dated July/August 1995
    2.7 Additional Installation Issues

3.0 Component Issues
    3.1 Administration Issues
    3.2 Agent Issues
    3.3 Client Issues
    3.4 Internet Agent Issues
    3.5 Monitor Issues
    3.6 WebAccess Issues

4.0 International Issues
    4.1 Installation on Windows 98
    4.2 Double-Byte Characters in Directory Names and File Names
    4.3 Double-Byte Characters in Passwords
    4.4 Euro Character in Subject Field
    4.5 Print Calendar Language
    4.6 RichWin and GroupWise 6
    4.7 Windows Messaging System
    4.8 German Spell Checker

5.0 Changes Since the Last Support Pack
    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 Product Testing

7.0 Documentation
    7.1 Support Pack Documentation
    7.2 GroupWise 6 Readme Files
    7.3 GroupWise 6 Installation Guide
    7.4 GroupWise 6 Administration Guide
    7.5 GroupWise 6 Help

8.0 Legal Information
    8.1 Disclaimer, Patents, Copyright, and Export Notice
    8.2 Trademarks

1.0 Support Pack Installation

1.1 Version Information

GroupWise 6 Support Pack 2 can be applied to any of the following GroupWise versions in your software distribution directory:

GroupWise 6 (original version)

GroupWise 6 SP1 (Support Pack 1)

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

1.2 Prerequisites

Before installing GroupWise 6 Support Pack 2:

Ensure that the network login account used to apply the Support Pack has Read, Write, Create, and Erase rights to the GroupWise software distribution directory.

Make sure you have rights to the root of the Directory Services tree. This is necessary in order to extend the schema.

Ensure that users do not access the software distribution directory during the update process.

Verify that the GroupWise software distribution directory and files are not flagged Read-Only.

1.3 Installing the Support Pack

To install GroupWise 6 Support Pack 2:

If you are installing from the Web, extract the contents of the downloaded Support Pack file by copying it to a temporary directory and running it. If you are installing from the CD, no extraction is needed; continue with step 2.

Extract the file on the server's SYS: volume or on another server volume that has read/write access. This compressed file contains directory paths that could exceed the DOS limits. The file must be extracted in a root-level directory on your local drive or on a NetWare volume that accepts longer paths.

Use Windows to run the SETUP.EXE program extracted in the previous step. Click Start > Run > Browse > select the file from the temporary directory > click OK.

See Section 1.2: Windows Version Requirements for Installation in GW6_ISS.TXT if you are installing GroupWise WebAccess or GroupWise Monitor.

Follow the on-screen instructions provided in the Support Pack program to update the software distribution directory and the administration, agent, and client software in production.

After applying the update on NetWare servers where agents are running, restart the NetWare servers to ensure that all updated NLM programs are loaded. This will resolve any errors you may see during the update process.

2.0 Installation Issues

2.1 NDS Schema Extension during Installation

The installation programs for the following components extend the NDS schema of the tree where you are installing the components:

GroupWise Administration

GroupWise WebAccess

GroupWise Monitor

You must be an admin equivalent to extend an NDS tree's
schema.

2.2 Windows Version Requirements for WebAccess and Monitor

Limitations with Windows 95a (SR1) require that you install GroupWise WebAccess and GroupWise Monitor from a Windows 95b, Windows 98, Windows NT, Windows XP, or Windows 2000 workstation. Do not install from a Windows 95a (SR1) workstation.

2.3 WebAccess and Monitor on the Same Web Server

The WebAccess Application, WebPublisher Application, and Monitor Application share a common library. This library changed significantly from GroupWise 6 to GroupWise 6 SP1 and above. If you will run these applications on the same Web server, you must update all three before any of them will work properly.

2.4 Wireless Device Support for WebAccess and Monitor

The GroupWise Monitor software included on the GroupWise 6 SP2 CD supports the following wireless devices:

WAP-enabled wireless devices that use HDML 3 or WML 1.1 compatible microbrowsers

Palm OS 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:

http://www.novell.com/wireless

We encourage you to check this site frequently for updates and news.

2.5 Windows 2000 Service Pack 2 or Above 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 (or any non-Windows servers), you need to apply the Windows 2000 Service Pack 2 or above on the Windows servers.

You can download Windows 2000 Service Packs from:

http://windowsupdate.microsoft.com

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

2.6 WSOCK32.DLL Dated July/August 1995

WSOCK32.DLL versions dated July 1995 and August 1995 are known to cause the following problems:

The GroupWise 32-bit client installation fails as GWCMA1.DLL is registered with Windows.

WebAccess installation may fail with an "invalid path" error.

An updated version of WSOCK32.DLL is available from Microsoft as WSOCKUPD.EXE.

2.7 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 File Names

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

File names can consist of up to 8 characters, with extensions of up to 3 characters. Do not use long file names. This requirement applies to any non-GroupWise-specific files (such as SSL certificates and key files) that are used by GroupWise components.

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    Current System Address Book for Caching Mode Users

The POA should be configured to generate the system Address Book for Caching mode users daily, as described in “Performing Nightly User Upkeep” in “Post Office Agent” in the “Administration” guide.

If you want to generate the system Address Book for download more often than once a day, you can delete the existing WPROF50.DB file from the \WPCSOUT\OFS subdirectory of each post office. A new downloadable system Address Book will be generated automatically for users on each post office.

3.1.4    GroupWise Target Service Agent and the SBackup Console

If you are using the SBackup Console (SBCON.NLM) in conjunction with the GroupWise Target Service Agent (GWTSA), you may encounter the following limitation: If you navigate down through the directory structure and then back up to the root directory, you are unable to navigate down a different directory. You can exit the SBackup Console and restart it to choose a different directory below the root directory.

3.1.5    Restoring Mailbox Items

If you create a backup copy of a post office, you must define the backup copy as a GroupWise restore area, as described in “Restoring Mailbox Items” in “Databases” in the “Administration” guide. If you don’t define the backup as a restore area, GroupWise users can still access the restore area (if you let them know the location), but they will receive an error when they try to restore items.

3.1.6    ConsoleOne on Windows NT 4

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

3.1.7    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.8    TurboFat Compatibility

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

To turn off TurboFat on NetWare 5.x servers, use TURBODIS.NLM.

To turn off TurboFat on NetWare 6.x servers, use TDIS600.NLM.

These NLM programs disable TurboFat at startup.

3.2 Agent Issues

3.2.1    LDAP Server Failover

Starting in GroupWise 6, users can authenticate through LDAP. You can configure one LDAP server on the Security property page of the Post Office object in ConsoleOne. You can configure multiple LDAP servers by using the /ldapipaddr POA startup switch. For setup instructions, see “Configuring Single Server Mode for Multiple LDAP Servers” in “Post Office Agent” in the “Administration” guide.

3.2.2    New LDAP Pooling Feature

In Support Pack 2, you can configure a pool of as many as five LDAP servers to facilitate load balancing and fault tolerance, so the POA cycles to a different LDAP server each time it needs to authenticate a user. For setup instructions, see “Configuring Pooling Mode” in “Post Office Agent” in the “Administration” guide.

3.2.3    Improving POA Performance on NetWare NSS Volumes

If you run the POA on NetWare 5.x or 6.x NSS volumes, you can significantly improve GroupWise performance by using the following parameters and settings on the NSS command in the AUTOEXEC.NCF file:

/NameCacheSize=20000
/OpenFileHashShift=15
/ClosedFileCacheSize=50000
/CacheBalance=60
/FileFlushTimer=75
/BufferFlushTimer=75

The best /ClosedFileCacheSize setting for a server depends on many things, such as the amount of memory on the server, the load on the POA, and the number of other programs running on the server. For example, the 50000 setting can work well for a server that has 650MB of memory. Experiment with various settings in order to optimize performance.

The following TIDs, although originally written for GroupWise 5.x and NetWare 5.x, apply to GroupWise 6 and NetWare 6.x as well:

TID 10021605: Implementing GroupWise 5.x on a
              NetWare 5 NSS Volume
TID 10065215: Resolving GroupWise Performance
              Issues with NSS Volumes

3.2.4    Updating to GroupWise 6 Agents

If you are updating an existing GroupWise 5.x system, and you are running the MTA and a POA on the same machine, you should not choose to launch the agents at the end of the installation process. Start the MTA first, so that it can update the domain to a GroupWise 6 level. When this process is finished, then start the POA to update the post office.

3.2.5    Unread Message Count Feature Requires at Least the SP1 Version of the Post Office Agent (POA)

Starting with GroupWise 6 SP1, client includes the Unread Message Count feature. Next to each folder, GroupWise displays the number of unread messages included in the folder.

For the Unread Message Count feature to work when the GroupWise client is running in Online mode, the POA must be at least the GroupWise 6 SP1 version.

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 client, you may encounter an error if you are installing the client from a NetWare 5.1 server where Support Pack 1 has been installed. The SETUPIP.EXE program used during the AutoUpdate process may not run correctly.

To resolve the problem, you must modify the MAGNUS.CONF file located in the SYS:\NOVONYX\SUITESPOT\HTTP-<web_server_name>\CONFIG directory by adding the following line:

MaximumFilesReturnedInIndex 500

Then run the client installation again.

3.4 Internet Agent Issues

3.4.1 IMAP Access Requires at Least the SP1 Version of the POA

The GroupWise 6 SP1 or SP2 version of the Post Office Agent (POA) must be running against any post offices that the SP2 Internet Agent will access via IMAP.

3.4.2 Viewer Issue with the Internet Agent and Clustering

If you are running the Internet Agent in a clustering environment, you must copy the Inso viewer NLM files (SCC*.NLM) to the SYS:\SYSTEM directory of each server in the Internet Agent’s failover path. Otherwise, the Internet Agent will not be able to locate the Inso viewer files.

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    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 Client. The Novell Client is available for download from the Novell Software Downloads site:

http://www.novell.com/download

3.6.2    Installing NetWare 5 Support Pack 3a or NetWare 5.1

If you install NetWare 5 Support Pack 3a or NetWare 5.1 after you install the WebAccess and WebPublisher Applications to a NetWare 5 server, you will need to reinstall the WebAccess and WebPublisher Applications. The Support Pack and NetWare 5.1 replace the JAVA.CFG file and other files that are modified by the GroupWise WebAccess Installation program.

If you install the WebSphere Application Server that is part of NetWare 5.1, the WebAccess and WebPublisher Applications will no longer function. Reinstalling them will not resolve the problem. You will need to restore them from backup.

3.6.3    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 Services will provide support.

NetWare Enterprise Web Server for NetWare 5 (and higher)

Apache Web Server 1.0.3 (or higher) for NetWare 6 (and higher)

Netscape Enterprise Server 3.6 (or higher) for Windows NT

Microsoft Internet Information Server 4.0 (or higher) for Windows NT, or Microsoft Internet Information Server 5 (or higher) for Windows 2000

Apache Web Server 1.3.3 (or higher) for UNIX Solaris

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 > complete the following steps to install the applications:

Unzip WEBACCESS.ZIP to the root of the network server volume where the Web server resides. WEBACCESS.ZIP and the ZIP files referred to in the next three steps are in the INTERNET\WEBACCES\OTHER directory on the GroupWise 6 SP2 CD.

Unzip WEBACCESSDOCS.ZIP to the Web server's document root directory.

Unzip WEBACCESSSERVLETS.ZIP to the servlet root directory.

Unzip WEBACCESSJARS.ZIP to a library or jar file directory on the network server (for example, you may 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.

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 on the GroupWise 6 SP2 CD.

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.

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)

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.

Copy the COMMGR.CFG file, located in the WebAccess gateway home directory (<DOMAIN>\WPGATE\<WEBAC60A>), to the NOVELL\WEBACCESS directory and the NOVELL\WEBPUBLISHER directory.

3.6.4    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:

Modify the Java servlet engine’s servlet properties file to include the settings shown in the sample WebAccess SERVLETS.PROPERTIES file. The SERVLETS.PROPERTIES file is located in the INTERNET\WEBACCES\OTHER directory on the GroupWise 6 SP1 CD.

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.

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 NT server, the files are located in the NOVELL\JAVA\LIB directory.

3.6.5    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:

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

On the Environment page (located on the Application tab), deselect the Use Client IP in Securing Sessions option. For information about this option, click the Help button on the Environment page.

Click OK to save the change.

3.6.6    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 at:

   http://support.novell.com/search/kb_index.htm

3.6.7    Running Busy Search on a UNIX Post Office

GroupWise WebAccess will not return valid Busy Search results for users whose mailboxes are on UNIX post offices.

4.0 International Issues

4.1 Installation on Windows 98

During installation of international versions of the Support Pack, select Copy to GWTEMP in order to avoid the possibility of long file names being truncated.

4.2 Double-Byte Characters in Directory Names and File Names

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

4.3 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.4 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 may display as an upside-down question mark when viewed in the Java 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 above to correctly display the Euro character.

4.5 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 and the client is installed in German, calendars will print in French.

4.6 RichWin and GroupWise 6

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

4.7 Windows Messaging System

When installing the GroupWise client to a non-English or non-Japanese Windows NT/2000 operating system, users will receive a prompt asking them to replace a Windows Messaging System DLL with the English version of the DLL. Users must click YES and replace this Windows Messaging System DLL. Otherwise, GroupWise will not function properly.

4.8 German Spell Checker

The German spell checker technology is no longer owned by Novell. The company that purchased it has changed its plans about updating that technology. If you use WordPerfect, GroupWise can use the updated German spell checker that comes with the latest version of WordPerfect.

5.0 Changes Since the Last Support Pack

5.1 Address Book Fixes

From the Address Book, you can create a personal group and immediately send a message to it.
Personal address book entries now have a Creation Date field.
Any text provided in the Description field of a Distribution List object is now displayed for the distribution list in the Comment field in the Address Book. This is now parallel to how description information has always been handled for users.
Including Internet users that are not in the Address Book no longer causes a search to fail.
Lookups on custom fields work correctly.
The maximum number of characters in the LDAP context has been increased.
The Add to Frequent Contacts option can be canceled.

5.2 Administration Fixes

The GroupWise Support Pack installation program installs the .DC files correctly.
ConsoleOne can be installed on a NetWare 6 server and run from that location.
When you move a user, the client options records also move to the new post office.
The GroupWise snap-in to ConsoleOne no longer interferes with changing User object properties that are not associated with GroupWise.
ConsoleOne checks object rights before allowing an administrator to modify Client Options settings.
When an administrator deletes a user, the correct user ID of the administrator is logged.
Data is saved correctly when you set the Archive Directory or Custom Views file paths in Client Options.
Librarian rights assigned in ConsoleOne display and work correctly in the client.
ConsoleOne prevents you from creating duplicate users that have Internet addressing and their visibility set to None.
ConsoleOne allows you to reset the database version setting for External Domains and Non-GroupWise Domains, which allows support of updated gateways.
You can change which MTAs are assigned to perform NDS user synchronization in ConsoleOne.
System-level rights are checked for domain connections and scheduled events.
Deleting a template no longer affects the user that the template was based on.
Area access records, such as those required when setting up users of a Restore Area, are replicated from the primary domain to secondary domains.
The membership of an organization role that is not a GroupWise distribution list can be successfully modified.
An error message displays if a post office cannot be created.
An error message is logged if a post office rebuild causes a duplicate entry error.
The GroupWise Target Service Agent (GWTSA) for backing up live GroupWise systems now autoloads all supporting NLM programs.

5.3 Admin API Fixes

Fixed a memory leak.

5.4 Agent Fixes

The POA and MTA are now fully supported on NetWare 4.2.
The POA correctly handles SSL with LDAP user names and passwords.
The POA starts the number of maintenance handler threads specified in ConsoleOne.
The QuickFinder startup switches detailed in TID 10063970 are now supported for GroupWise 6.
The MTA replicates nicknames on user moves so that the auto-creation of nicknames can succeed.
The MTA checks send size limits on messages on indirect, gateway, and IDomain links, so that send size limits are enforced on messages to Internet users.
Fixed an 890F error that can occur when the Installation program starts the agents for the first time on NetWare 6.
The Swedish and Finnish POAs can successfully send undeliverable status messages.
Fixed a POA memory leak.
Fixed several POA abends.
Fixed several MTA abends.
Fixed an agent engine abend.

5.5 Client Fixes

The client Installation program lists Presentations 9 along with the other components of the Corel 2000 suite.
You can download the client files using SETUPIP.EXE from a NetWare 6 server where Apache is running.
There is no longer a delay when opening the first mail message in the client.
You can drag forwarded messages to the desktop on Windows XP.
You can drag users from the To field to the CC and BC fields.
Messages can be moved back and forth between the mailbox and the cabinet in the QuickViewer.
You can drag and drop user names from the To field into the Subject field of a message.
When trying to attach files on a workstation where C: is a hidden drive, the client defaults to the location from which files were previously attached, rather than to the next available disk drive.
Hidden drives are no longer visible when attaching files.
Auto-archive is more consistent.
Auto-archive continues past an error on a particular message.
After receiving an 8567 error, the client now tries to reconnect on the POA proxy address.
The Check Spelling before Send option now works for phone messages, posted personal appointments, and discussion threads.
With the Check Spelling before Send option enabled, the automatic spell checking occurs in the foreground even if the cursor is up in a field rather than in the body of the message.
With Return Notification set to When Declined, the decline comment appears in the message body of the return notification.
In Caching mode, you can successfully proxy to a user that has unopened appointments in the Mailbox.
In Caching mode, retraction works when you delete and empty an item.
In Caching mode, requests are properly deleted, so that accumulated requests no longer cause delays and D11B errors.
In Caching mode, the archive directory is successfully synchronized with the Online mailbox.
In Caching and Remote modes, items that were moved while in Online mode synchronize correctly.
Some archiving problems have been fixed.
The Save Draft feature refreshes and saves modified text correctly.
The Place field no longer appears when you view or print a message that includes resources (not places) in the To field.
The time zone information in the month calendar view displays correctly.
Resetting client options no longer interferes with the multiuser calendar.
Proper notification is sent when appointments are canceled.
Unarchived messages and their attachments are properly cleaned up.
You can now print an archived calendar.
The client consistently sends HTML-formatted messages to the printer.
The client correctly handles HTML-formatted TNEF messages.
When you resend an HTML-formatted message, images in the message are no longer lost.
By default, only the message is selected for printing. Attachments are no longer selected by default.
Received items that are deleted along with sent items are not given Retracted status in the sender’s Mailbox.
The multi-user calendar works correctly in Caching mode.
The client can handle very long URLs in messages.
The client handles Internet messages requiring MIME processing more reliably.
Internet addressing works for external users in distribution lists.
With Internet addressing turned off, addresses with the format <gateway>:<domain>.<po>.<userID>@<IDomain> are delivered successfully.
The Window menu items no longer duplicate if you have multiple message windows open.
The Close Others item on the Window menu no longer closes the main GroupWise client window if used from a message window.
Proxy rights on Notes and Reminder Notes are set correctly.
Checking in a document from the Remote client works faster.
You can look up a document by typing its name.
You can set user rights to libraries.
In Caching mode, custom library fields are available when doing a Find by Example.
Circular links between folders have been prevented.
If you add an item to a shared folder that has been deleted by its owner but still appears in your mailbox, the item is not replicated and you receive a task to deleted the obsolete shared folder.
The posting time is correct when you post a new discussion to a newsgroup.
The client can delete messages downloaded from a POP3 account that are in a folder that is linked to the POP3 account.
A search base has been added to the LDAP search to accommodate certain Certificate Authorities.
Handling of LDAP passwords has been improved.
Non-alphanumeric characters can be used in IMAP passwords.
Notify alarms sent to a pager or cell phone include the subject text.
Notify alarms sent to a pager or cell phone are sent only once.
The Inso viewers have been updated to solve a date display problem in Excel spreadsheets.
You can send GroupWise messages from Microsoft Word.
Appointment times sync correctly on a Palm Pilot even if the time zone has changed on the workstation.
Eliminated a C006 error on shared folders that use custom document properties as column headers.
An HTML-formatted message with extended characters that is composed with MIME encoding set to UTF-8 can be saved and retrieved without damage to the extended characters.
When you save, forward, or resend an HTML-formatted message, extended characters in the message are no longer changed to the wrong character set.
International characters in the last name of a user are translated correctly so that they can be read successfully by other programs that access the MAPI message store such as Intellisync for the Palm Pilot and Microsoft Outlook.
The Japanese client handles long messages on Windows 2000 without character display problems.

5.6 Client API Fixes

Buttons on the toolbars of the browser and the QuickView window can be created independently.
You can add a button to the toolbar of the Mail To dialog box when using the HTML view.
Custom field values are refreshed properly so that C3PO programs can obtain the correct values.
The name completion control background can now be set by the client API.
The client API no longer duplicates routed messages.
The client API can update the Message.Private property.
The client API checks for an existing organization name before adding a new organization.
The client API no longer truncates the sender’s name in a draft message.
The client API can now access the body text of a routed message.
All tokens are visible to C3PO programs.
C3PO programs can retrieve HTML files into new mail messages.
C3PO programs can change the properties menu that appears when you right-click a message.

5.7 Engine Fixes

The contents of the Document Subject field are now included in the document BLOB file.
Fixed a problem with moving resources.
Fixed an 8101 error related to memory problems.
Fixed a C00D error that occurred when a user was proxied to a user or resource on a different post office and then tried to send a message by changing the sender to the original user, rather than sending the message as the proxied user or resource.
Fixed an 8209 error that occurred when a user tried to restore items from a Restore Area that was located on a different server from where the POA was located.
Fixed a problem with routed message IDs.
Fixed a QuickFinder abend.
Fixed several abends.

5.8 GWCheck Fixes

GWCheck can process Caching or Remote databases located on a path where a directory name includes a space.
GWCheck now validates the client option information for a user and cleans up duplicate records that could prevent a user from being moved to a different post office. This prevents a D70E error from the destination MTA.
GWCheck reports the correct amount of disk space when disk space management is enabled.
The Validate All Document Security option no longer forces the re-indexing of all documents.
GWCheck correctly logs information for items that exceed a specified size.
In GroupWise 6, the <Minimum User Access> tag was renamed to <All User Access>. GWCheck can handle either tag.
GWCheck no longer reports a Problem 34 when it encounters records originally added to enhance Internet Agent functionality.
GWCheck can access a database when a directory name in the path contains a space.
GWCheck cleans up unnamed, duplicate folders.
Fixed memory leak and pointer problem.

5.9 Internet Agent Fixes

The Internet Agent is now fully supported on NetWare 4.2.
When running as a Windows service configured to interact with the desktop, the Internet Agent can successfully locate the GWIA.CFG file.
The Internet Agent can be configured to offer a pool of LDAP servers, rather than just one, to the POA to use when attempting to authenticate users by way of LDAP.
Users must have a password to authenticate in order to send ESMTP messages.
When IMAP client users search their GroupWise mailboxes, the Internet Agent issues a search for the proper message ID.
Size restrictions on messages are checked before messages are sent.
Sent Items properties include delivery status when notification has been requested.
Reply to All handles multiple Internet recipients whose user names include a period (for example, <first_name>.<last_name>).
Wildcard characters in the prevent list are handled more accurately.
Unknown characters are replaced with question marks (?) rather than generating a C10B error message.
The Internet Agent reads MIME multipart messages correctly.
The Internet Agent ensures that the required ending boundary is present on all messages downloaded from a POP3 account.
The Internet Agent no longer truncates messages that include extended characters.
The Internet Agent includes the recipient information in all undeliverable messages.
Messages sent from Entourage are no longer truncated.
The Internet Agent no longer inserts header info into the body of the message when the message text contains extended characters.
If it receives an error, the Internet Agent sends a quit message before closing the transmission.
The Internet Agent can successfully process MS-TNEF messages with BASE64 encoding.
The Internet Agent returns status information on the specified folder.
Access Control blocks only specified IP addresses and users.
Access Control enforces message size limits.
The /NotFamiliar switch has been added to the Internet Agent so you can prevent users’ familiar (friendly) names from being added to the From line on outgoing messages.
Dates in the MIME header are no longer translated.
Fixed memory leaks and passthrough addressing.
Fixed several Internet Agent abends.

5.10 Monitor Fixes

The Monitor Application is now fully supported on NetWare 4.2.
The Monitor Installation program supports Apache.
The Installation program successfully launches the Web server.
Changed the Sender field to From to be consistent with other uses of a From field.

5.11 WebAccess Fixes

WebAccess is now fully supported on NetWare 4.2.
The WebAccess Installation program supports Apache.
The Installation program successfully launches the Web server.
Performance has been substantially improved.
URLs in the message body link correctly.
The WebAccess Address Book now works with Netscape 6.2.
The WebAccess Address Book displays addresses in the selected format, not forcing the <user>.<po>.<domain> format.
Uses of mobile devices with Vodafone accounts can now access their mailboxes through WebAccess.
The WebAccess client properly warns of disk space restrictions.
If the user gives the wrong password when using LDAP authentication to the post office, the WebAccess client tries to log in only once, rather than three times.
In the WebAccess client using simple HTML viewers, the Address Book button works correctly.
The Post button in a new folder displays correctly.
WAV files are not converted, but are passed to the browser to handle.
The WebAccess client no longer displays information from the CC: field in the To: field when doing a Reply to All.
When you proxy to a resource, its name becomes a selectable link.
A message that contains “HRt” followed by “>” can be viewed across a wireless connection to a phone.
Extended characters in the user name of the owner of a shared folder are displayed correctly.
The multilingual WebAccess client displays the correct appointment time for the recipient for all languages.
WebPublisher documents can now be accessed in libraries whose names include extended characters.
WebPublisher searches correctly for multiple word search strings surrounded by quote marks.
An extraneous error message that appeared when changing a password no longer appears.
Fixed several WebAccess Agent abends.

6.0 Product Testing

The Support Pack has undergone component testing, core OS testing, and integration testing with other Novell products. The Support Pack was also tested with the following:

NetWare 6 Support Pack 2

NetWare 5.1 Support Pack 5

NFS 30 Support Pack 4

NFAP 1 Support Pack 2

Novell Cluster Services 1 Support Pack 4

GroupWise 6 Support Pack 2

GroupWise 5.5 Enhancement Pack Support Pack 5

Novell Client 4.83 for Windows NT/2000/XP Support Pack 1

Novell Client 3.32 for Windows 95/98 Support Pack 1

For more information about updates for the Novell Client, see TID 10062546 in the Novell Knowledgebase at:

http://support.novell.com/search/kb_index.htm

7.0 Documentation

7.1 Support Pack Documentation

For installation instructions, see GW6SP2.TXT located at the root of the Support Pack.

For more information on the latest Support Pack issues, see TID 10070085 in the Novell Knowledgebase at:

http://support.novell.com/search/kb_index.htm

7.2 GroupWise 6 Readme Files

For Readme information about specific GroupWise 6 components, see the following additional Readme files:

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

7.3 GroupWise 6 Installation Guide

For detailed installation and update instructions, see the GroupWise 6 Installation guide (GroupWiseInstallationGuide.pdf) in the \GW6SP2\US\DOCS\US directory of the Support Pack.

7.4 GroupWise 6 Administration Guide

For additional GroupWise 6 documentation, see the GroupWise 6 Administration guide at the Novell Documentation Web site:

http://www.novell.com/documentation

7.5 GroupWise 6 Help

Starting with GroupWise 6 Support Pack 1, to better support accessibility requirements within GroupWise Help, the Help for the following GroupWise components has been changed from Microsoft Windows Help to Microsoft HTML Help:

GroupWise client

GroupWise Agents (MTA and POA) for Windows NT/2000

GroupWise Internet Agent for Windows NT/2000

GroupWise Monitor for Windows NT/2000

GroupWise Check utility

GroupWise Certificate Signing Request utility

In order for Microsoft HTML Help to display on a Windows workstation, the workstation must have Internet Explorer 4.x or higher installed.

8.0 Legal Information

8.1 Disclaimer, Patents, Copyright, and Export Notice

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.

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 and Patents Pending.

Copyright (C) 2002 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.

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.

8.2 Trademarks

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

C3PO, NLM, Novell Client, and QuickFinder are trademarks of Novell, Inc.

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