Novell GROUPEWISE 8 - SUPPORT PACK 2 05-2010 User manual

GroupWise 8 Support Pack 2 1
novdocx (en) 16 April 2010
Novell®
GroupWise 8 Support Pack 2
May 18, 2010
1 Overview
GroupWise 8 Support Pack 2 provides enhancements for both administrators and end users.
For Administrators
Access control for distribution lists for controlling which users can send to a restricted
distribution list
Attachment restrictions for specified file types
Limitation on the number of recipients for items
For End Users
Improved WebAccess functionality
Date range and category filters for the WebAccess Find feature
Improved integration with Novell Teaming 2.1
Drag-and-drop in the GroupWise Windows client for transferring GroupWise items and
files to a Teaming folder that is displayed in the GroupWise Folder List
Find option in the GroupWise Windows client for searching a Teaming site
Integration with Novell Conferencing
Schedule a conference in the GroupWise Windows client
Join a conference from a scheduled appointment in the GroupWise Windows client
For more information, see the Novell Conferencing product Web site (http://
www.novell.com/products/conferencing).
2 GroupWise System Requirements
GroupWise 8 system requirements are listed in the GroupWise 8 Installation Guide (http://
www.novell.com/documentation/gw8).
In GroupWise 8 Support Pack 1, the following additional GroupWise client operating systems are
supported:
Windows 7
Mac OS 10.6 (Snow Leopard)

2GroupWise 8 Support Pack 2
novdocx (en) 16 April 2010
3 NetWare/Windows Installation
Section 3.1, “NetWare/Windows Administration Software Installation Instructions,” on page 2
Section 3.2, “Windows Client Software Installation Instructions,” on page 2
3.1 NetWare/Windows Administration Software Installation
Instructions
IMPORTANT: If you are installing the GroupWise software in a cluster, refer to the GroupWise 8
Interoperability Guide (http://www.novell.com/documentation/gw8) for cluster-specific installation
instructions before starting to install the GroupWise 8 Support Pack 2 software.
1Download the NetWare/Windows GroupWise 8 Support Pack 2 compressed executable file to a
temporary directory on your NetWare or Windows server:
gw802_beta1_full_nlmwin_en.zip
gw802_beta1_full_nlmwin_multi.zip
2Extract the .zip 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.
3In Windows, click Start > Run > Browse, then locate the directory where you extracted the
GroupWise 8 Support Pack 2 administration files.
4Select the
setup.exe file, then click OK to run the GroupWise Installation program.
5Click Create or Update a GroupWise System.
6Follow the on-screen instructions to install the GroupWise 8 Support Pack 2 software on your
test system.
When you install a Support Pack, you can streamline the update process by copying the
updated agent software files but not configuring the agents again. In the Installation program,
select Install the Software Files, But Do Not Configure the Agents on the Installation Path page
when you install the POA, the MTA, and the Internet Agent.
Update the primary domain first. Start the MTA in the primary domain. Then update secondary
domains, followed by the post offices in each domain. Start each MTA and POA for each
domain and post office. Then update the other GroupWise agents.
For additional instructions, refer to the GroupWise 8 Installation Guide on the GroupWise 8
Documentation Web site (http://www.novell.com/documentation/gw8).
3.2 Windows Client Software Installation Instructions
1Download the GroupWise 8 Support Pack 2 Windows Client compressed executable file to a
temporary directory on your workstation:
gw802_beta1_client_win_en.exe
gw802_beta1_client_win_multi.exe
2In Windows, click Start > Run > Browse, then locate the directory where you downloaded the
GroupWise 8 Support Pack 2 Client compressed executable file.
3Double-click the downloaded file, then click Yes to extract the GroupWise client software and
start the GroupWise client Setup program.

GroupWise 8 Support Pack 2 3
novdocx (en) 16 April 2010
4Follow the on-screen instructions to install the GroupWise 8 Support Pack 2 client software on
your workstation.
The GroupWise Setup Progress dialog box displays a green bar during the installation process.
Occasionally, long pauses might occur. You can also check the activity of the GroupWise client
Setup program by viewing the Performance tab of the Windows Task Manager to observe CPU
usage.
4 Linux Installation
Section 4.1, “Linux Administration Software Installation Instructions,” on page 3
Section 4.2, “Linux Client Software Installation Instructions,” on page 3
Section 4.3, “Mac Client Software Installation Instructions,” on page 4
4.1 Linux Administration Software Installation Instructions
IMPORTANT: If you are installing the GroupWise software in a cluster, refer to the GroupWise 8
Interoperability Guide (http://www.novell.com/documentation/gw8) for cluster-specific installation
instructions before starting to install the GroupWise 8 Support Pack 2 software.
1Download the GroupWise 8 Support Pack 2 Administration compressed tar file to a temporary
directory on your Linux server:
gw802_beta1_full_linux_en.tar.gz
gw802_beta1_full_linux_multi.tar.gz
2In a terminal window at your Linux server, change to the temporary directory, then use the
following command to uncompress and untar the downloaded file:
tar -xvzf filename.tar.gz
The files are extracted to the root of the directory.
3Become
root by entering su - and the root password.
4In the directory where you extracted the GroupWise 8 Support Pack 2 files, use the following
command to start the GroupWise Installation program:
./install
5Click Create or Update GroupWise System.
6Follow the on-screen instructions to install the GroupWise 8 Support Pack 2 software.
When you install a Support Pack, you can streamline the update process by using the Install
option to install the updated RPM for each agent. Typically, you do not need to use the
Configure option after installing updated agent software, if the agent configuration has not
changed since the previous installation. If you encounter a problem starting the updated agent,
use the Configure option to update the configuration information for the agent.
For additional instructions, refer to the GroupWise 8 Installation Guide on the GroupWise 8
Documentation Web site (http://www.novell.com/documentation/gw8).
4.2 Linux Client Software Installation Instructions
1At your Linux workstation, download the GroupWise 8 Support Pack 2 client compressed tar
file to a temporary directory:

4GroupWise 8 Support Pack 2
novdocx (en) 16 April 2010
gw802_beta1_client_linux_en.tar.gz
gw802_beta1_client_linux_multi.tar.gz
2In a terminal window at your Linux workstation, change to the temporary directory, then use
the following command to uncompress and untar the downloaded file:
tar -xvzf filename.tar.gz
The files are extracted to the root of the directory.
3In a terminal window, become
root by entering su - and the root password.
4In the directory where you extracted the GroupWise 8 Support Pack 2 client files, run the
GroupWise Setup program to install the GroupWise Linux client software:
./install
5To start the Linux client after installation, double-click the GroupWise icon on your Linux
desktop.
4.3 Mac Client Software Installation Instructions
1At your Macintosh workstation, download the GroupWise 8 Support Pack 2 client file to a
temporary directory
gw802_beta1_client_mac_en.dmg
gw802_beta1_client_mac_multi.dmg
2Browse to the GroupWise 8 Support Pack 2 client file that you downloaded.
3Double-click the
.dmg file to install the GroupWise Mac client in the Applications folder.
4Drag the GroupWise package from the
Applications folder to the Mac dock to create a
GroupWise icon there for convenient access.
5To start the Mac client after installation, click the GroupWise icon on the Mac dock.
5 Installation Issues
Section 5.1, “General Installation Issues,” on page 4
Section 5.2, “NetWare/Windows Installation Issues,” on page 6
Section 5.3, “Linux Installation Issues,” on page 7
Installation issues for individual GroupWise components are located under the heading for each
component.
5.1 General Installation Issues
“GroupWise Version Compatibility” on page 5
“GroupWise Views Compatibility” on page 5
“WebAccess and Monitor on the Same Web Server” on page 5
“SOAP Client Connection Issue during Post Office Updates” on page 5
“Additional Installation Issues” on page 6

GroupWise 8 Support Pack 2 5
novdocx (en) 16 April 2010
5.1.1 GroupWise Version Compatibility
If you install GroupWise on multiple platforms, or if you run multiple versions (for example,
GroupWise 6.5 or 7 and GroupWise 8 in the same GroupWise system), refer to the GroupWise
Version Compatibility section in the GroupWise 8 Installation Guide (http://www.novell.com/
documentation/gw8) to make sure that the combinations you are using are supported.
For example, you cannot run a GroupWise 8 client against a GroupWise 7 or earlier post office.
Earlier POAs cannot support later GroupWise clients. However, you can run a GroupWise 7 or
earlier client against a GroupWise 8 POA.
Also, you cannot run the GroupWise 7 or earlier snap-ins to ConsoleOne to access GroupWise 8
databases or eDirectory objects. You can use Admin Lockout Settings under Tools > GroupWise
System Operations > System Preferences to specify the required version of the ConsoleOne snap-ins
for each domain as needed.
See also Section 9.1.2, “GroupWise 8 WebAccess Compatibility with Earlier Versions of
WebAccess,” on page 20.
5.1.2 GroupWise Views Compatibility
When you create a GroupWise 8 post office, the GroupWise 8 client view files are installed. If an
earlier GroupWise client tries to access the GroupWise 8 post office, some of the view files required
by earlier GroupWise clients are not present. If possible, update all users in the post office to the
GroupWise 8 client.
If you need to run earlier GroupWise clients on a new GroupWise 8 post office, you must copy the
missing client view files from a post office where they are available. Client view files are stored in
the following directory for all platforms:
post_office\ofviews\win
Be sure to copy only the missing files. Some GroupWise 8 view files are new. Some GroupWise
view files have had the language code
us changed to en in GroupWise 8. Some GroupWise 8 view
files have the same names as earlier versions. Do not overwrite GroupWise 8 view files with earlier
versions that have the same names.
5.1.3 WebAccess and Monitor on the Same Web Server
The WebAccess Application, WebPublisher Application, and Monitor Application share a common
library. If you are updating from an earlier GroupWise version and if you run these applications on
the same Web server, you must update all three before any of them can work properly.
5.1.4 SOAP Client Connection Issue during Post Office Updates
For a large post office, a period of time can pass between when the POA starts updating the post
office and when it finishes the update. During this period, programs that connect to POAs by using
SOAP (such as SOAP e-mail clients, GroupWise Mobile Server, and BlackBerry Enterprise Server)
might receive the following error:
53336 - Incompatible Post Office version detected during login

6GroupWise 8 Support Pack 2
novdocx (en) 16 April 2010
This error should disappear when the post office update is complete. You can tell that the update is
complete in ConsoleOne by checking the Database Version field on the Identification page of the
Post Office object. If the update seems complete but the Database Version field has not updated to
8.0, restart the POA.
5.1.5 Additional Installation Issues
Platform-specific installation issues are listed in separate sections below. Installation issues for
individual GroupWise components are located under the heading for each component.
5.2 NetWare/Windows Installation Issues
“NetWare Agent Installation from Windows Vista or Windows 7” on page 6
“Windows Agent Installation Issue” on page 6
“New Default Installation Paths on Windows” on page 6
“Problem Installing from a Windows XP Service Pack 2 Machine” on page 7
“Windows Security Rights for GroupWise Client Installation” on page 7
5.2.1 NetWare Agent Installation from Windows Vista or Windows 7
During Support Pack installation on a Windows Vista or Windows 7 machine, when you specify the
path to your existing software distribution directory on a NetWare server, you might receive the
following error message:
Path: drive:\grpwise\software - Please specify a valid network path.
This message can occur even when you see that the drive is correctly mapped and correctly
specified. Use a UNC path instead, for example:
\\NetWare_server\volume\grpwise\software
If the UNC path also fails, use one of the following workarounds:
Install the latest Novell Client for Vista from Novell Downloads (http://download.novell.com).
Perform the installation from a Windows XP machine.
5.2.2 Windows Agent Installation Issue
Before you update existing GroupWise agent software, make sure that the GroupWise agents have
been stopped on the Windows server. If the GroupWise agents are running during the installation
process, the agent software is not updated, but the GroupWise Installation program does not notify
you that it was unable to update the agent software.
5.2.3 New Default Installation Paths on Windows
On Windows workstations and servers, the default GroupWise 8 software locations are consolidated
under
c:\Program Files\Novell into the following subdirectories:
GroupWise
Component Previous Default Location Current Default Location
Client
c:\novell\groupwise c:\Program Files\Novell\GroupWise

GroupWise 8 Support Pack 2 7
novdocx (en) 16 April 2010
If you update existing software with GroupWise 8 software, the default location is the existing
location. If you install GroupWise 8 software on a new machine, the default location is as listed
above. In either case, you can override the default and specify a different location.
5.2.4 Problem Installing from a Windows XP Service Pack 2 Machine
When you install any GroupWise agent (Post Office Agent, Message Transfer Agent, Internet
Agent, WebAccess Agent, Monitor Agent) to a NetWare server from a Windows XP machine where
Service Pack 2 has been installed, you must have the Novell Client 4.90 SP2 or later installed on the
Windows machine. If you have an earlier Novell Client, the GroupWise Installation program claims
that it cannot find some of the directories to which you want to install software.
5.2.5 Windows Security Rights for GroupWise Client Installation
If the GroupWise Windows client is originally installed by the Windows Administrator user, the
Administrator user must also perform software updates. When it is installed by the Administrator,
the GroupWise client software cannot be updated by a regular user or a Windows Power User.
5.3 Linux Installation Issues
“SUSE Linux Enterprise Server 11 Issues” on page 7
“Domain Services for Windows Issues” on page 8
“GroupWise Installation to a Xen Guest on SUSE Linux Enterprise Server 10” on page 8
“Problem Copying the Monitor Files to the Software Distribution Directory” on page 8
“Upgrading from an Incomplete Software Distribution Directory” on page 8
5.3.1 SUSE Linux Enterprise Server 11 Issues
eDirectory 8.8.5 is supported on SUSE Linux Enterprise Server (SLES) 11. Earlier versions are
not supported.
SLES 11 does not include Tomcat, so it is included with the GroupWise 8 Support Pack 2
software. The GroupWise 8 Support Pack 2 Installation program detects SLES 11, installs
Tomcat, and configures it for use with GroupWise.
Agents
c:\grpwise c:\Program Files\Novell\GroupWise Server
\Agents
Internet
Agent
c:\grpwise\gwia c:\Program Files\Novell\GroupWise Server\GWIA
WebAccess
Agent
c:\webacc c:\Program Files\Novell\GroupWise Server
\WebAccess
Monitor
Agent
c:\gwmon c:\Program Files\Novell\GroupWise Server
\Monitor
GroupWise
Component Previous Default Location Current Default Location

8GroupWise 8 Support Pack 2
novdocx (en) 16 April 2010
5.3.2 Domain Services for Windows Issues
Starting with GroupWise 8 Support Pack 1, GroupWise is supported in a Domain Services for
Windows (DSfW) environment. However, workarounds are required for two specific situations:
The GroupWise Installation program cannot add GroupWise accounts to User objects if the
User objects are located in a DSfW partition. Use ConsoleOne to create GroupWise accounts
for such users after you install the GroupWise software.
The GroupWise Installation program can create all GroupWise objects in a DSfW partition
except for the WebAccess Application object (named GroupWiseWebAccess). Use
ConsoleOne to create the WebAccess Application object, then run the Installation program to
install and configure the WebAccess Application software.
5.3.3 GroupWise Installation to a Xen Guest on SUSE Linux Enterprise Server 10
When you install GroupWise on SUSE Linux Enterprise Server (SLES) 10 to a Xen guest, you
might receive the following error message:
The current window is not large enough to run install. Please resize the window
and run install again.
At present, the SLES 10 Xen console window does not report its dimensions properly. To work
around this:
1Make sure that SSH is enabled on the Xen guest.
2Open an X terminal window on the SLES 10 Xen host, using the following command:
ssh -X root@guest_ip_address
3Run the GroupWise Installation program from the Xen host.
5.3.4 Problem Copying the Monitor Files to the Software Distribution Directory
On SLES 10 SP2, the Installation program occasionally cannot copy the Monitor software files to
the software distribution directory. This appears to be a timing issue. Try again using the Installation
program, or manually copy the Monitor files to the software distribution directory.
5.3.5 Upgrading from an Incomplete Software Distribution Directory
All GroupWise components on a server must be updated at the same time. Therefore, if you are
installing GroupWise 8 from a software distribution directory that does not contain RPMs for all the
components installed on the server, you receive the following error:
Install failed for an unknown reason (7)
The GroupWise 8 component cannot be updated because its RPM is not present in the software
distribution directory. You can use the GroupWise 8 for Linux downloaded image to update the
server, then use Install Products > GroupWise Administration > Configure Administration in the
GroupWise Installation program to create a complete software distribution directory.
6 Administration Issues
Section 6.1, “General Administration Issues,” on page 9

GroupWise 8 Support Pack 2 9
novdocx (en) 16 April 2010
Section 6.2, “NetWare/Windows Administration Issues,” on page 10
Section 6.3, “Linux Administration Issues,” on page 11
6.1 General Administration Issues
“Obsolete Admin-Defined Fields” on page 9
“Server Names” on page 9
“Identity Manager Version Compatibility” on page 9
“Identity Manager Configuration Issue” on page 10
“Server-Based Anti-Virus Software” on page 10
6.1.1 Obsolete Admin-Defined Fields
In GroupWise 8, the following eDirectory fields have been added to the list of default fields that are
available in the GroupWise Address Book:
Street Address
PO Box
City
State or Province
Zip Code
Locality/Mailstop
Mobile Phone
Pager Number
Home Phone
Other Phone
When a domain is converted to GroupWise 8, if you have created any admin-defined fields that
correspond to these new default fields, the values are transferred from the admin-defined fields to
the new fields. In ConsoleOne, you can use Cleanup under Tools > System Operations > Admin-
Defined Fields to delete any admin-defined fields you have created that correspond to the new
default fields.
6.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 hostname.
6.1.3 Identity Manager Version Compatibility
Do not run a DirXML or Identity Manager (IDM) driver earlier than version 3.5.2 against a
GroupWise 8 system. Older drivers are not compatible. You can download the latest version of the
GroupWise IDM driver from Novell Downloads (http://download.novell.com).
For more information, see TID 7002222: “How is the GroupWise 8 Driver Configured for Identity
Manager?” in the Novell Support Knowledgebase (http://www.novell.com/support).

10 GroupWise 8 Support Pack 2
novdocx (en) 16 April 2010
6.1.4 Identity Manager Configuration Issue
The Identity Manager Accessory Portlet Reference Guide provides information for configuring
GroupWise portlets. In particular, it instructs you to edit lines in the
webacc.cfg file to appear as
follows:
Security.UseClientIP.enable=false
Security.UseClientCookie.enable=false
It is preferable to make these changes in ConsoleOne, rather than in the webacc.cfg file. The Use
client IP in security sessions setting and the Use Cookies settings default to selected (true) in
ConsoleOne. If you do not deselect them in ConsoleOne, the “true” settings are written to the
webacc.cfg file, overwriting your manual changes to that file. If this happens, the WebAccess
client prompts for login multiple times.
1In ConsoleOne, browse to and select the Domain object.
2Right-click the GroupWiseWebAccess object, then click Properties.
3Click Application > Security.
4Deselect Use client IP in securing sessions.
5Deselect the check boxes in the Use Cookies column.
6Click OK.
6.1.5 Server-Based Anti-Virus Software
If you run server-based anti-virus software, you should configure it so that it does not scan
GroupWise directory structures such as domains and post offices, where file locking conflicts can
create problems for the GroupWise agents. If you need virus scanning on GroupWise data, check the
GroupWise Partner Products page (http://www.novell.com/partnerguide/section/468.html) for
compatible products.
6.2 NetWare/Windows Administration Issues
“eDirectory and Windows Support” on page 10
“GWTSA and Duplicate Source Directories” on page 10
“Quotas on NSS Volumes” on page 11
“eDirectory Admin User Surname on Windows” on page 11
6.2.1 eDirectory and Windows Support
Versions of Novell eDirectory earlier than 8.8.4 are not supported on Windows Server 2008.
6.2.2 GWTSA and Duplicate Source Directories
The GroupWise Target Service Agent (GWTSA) handles situations where the same directory names
are used for backups on different volumes by numbering the instances. For example:
Original GWTSA
GroupWise System/[Dom]Provo2:
GroupWise System/[Dom]Provo2:

GroupWise 8 Support Pack 2 11
novdocx (en) 16 April 2010
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 the GWTSA with
GroupWise 6.5 Support Pack 1 or later, you must re-create your backup jobs because the path has
changed.
6.2.3 Quotas on NSS Volumes
If you use NSS volumes with quotas turned on, you must turn on quotas on all GroupWise
directories. Otherwise, you receive
No Disk Space errors.
6.2.4 eDirectory Admin User Surname on Windows
When you create a new eDirectory tree on Windows, the surname of the Admin user is
automatically set to a single space. This can cause problem in some GroupWise situations. For best
results, manually set the surname of the Admin user to something meaningful.
6.3 Linux Administration Issues
“NFS Not Supported” on page 11
“Pathnames and Filenames in Lowercase” on page 11
“Unavailable Administration Features” on page 11
6.3.1 NFS Not Supported
Because of long-standing file lock issues with NFS, you cannot use an NFS mount to mount a server
file system where your GroupWise system is located to a workstation where you are running
ConsoleOne. We recommend using an SMB mount instead if you must use Windows ConsoleOne to
access a domain located on a Linux server.
6.3.2 Pathnames and Filenames in Lowercase
All directory names in paths to GroupWise domains and post offices should consist of lowercase
letters. Filenames should also consist of lowercase letters. There are no length restrictions.
6.3.3 Unavailable Administration Features
GroupWise 8 administration on Linux does not include the following features that are available in
GroupWise 8 on NetWare and Windows:
Import/Export utility in ConsoleOne
Document Properties Management feature in ConsoleOne
7 Agent Issues
Section 7.1, “General Agent Issues,” on page 12
Section 7.2, “NetWare/Windows Agent Issues,” on page 12
Section 7.3, “Linux Agent Issues,” on page 13

12 GroupWise 8 Support Pack 2
novdocx (en) 16 April 2010
7.1 General Agent Issues
“New View Files Now Overwrite Existing View Files” on page 12
“Evolution Compatibility with the POA and SOAP” on page 12
7.1.1 New View Files Now Overwrite Existing View Files
When you update the POA software to GroupWise 8, updated view files are copied to the software
distribution directory, but not to post offices. This maintains any customizations you might have
made in the view files in post offices.
However, when each GroupWise 8 POA starts for the first time, it copies the new view files from the
software distribution directory to its post office. Therefore, if you have created custom view files
with the same names as standard view files, you must create backup copies before starting the
GroupWise 8 POA, so that your customized view files are not lost when the post office view files
are updated. After you start the GroupWise 8 POA, restore your custom view files.
Occasionally, the POA is unable to copy the updated view files from the software distribution
directory to its post office. When this happens, users receive a message that their view files are out
of date. To resolve this, use the Refresh Views option under Tools > GroupWise Utilities > System
Maintenance in ConsoleOne to update the post office view files from the software distribution
directory. After you refresh the views, you must restore your customized view files to the post
office.
7.1.2 Evolution Compatibility with the POA and SOAP
Users might experience problems using Evolution to connect to their GroupWise mailboxes if they
are using Evolution 2.6.0 or earlier. In addition, earlier versions of Evolution can cause high
utilization on GroupWise servers. To encourage users to update to the latest version of Evolution,
you can use the /evocontrol switch in the POA startup file to configure the POA to allow only
specified versions of Evolution. The /evocontrol switch takes either of the following parameters:
/evocontrol-"Evolution-1.10-yyyy-mm-dd"
/evocontrol-"Evolution-Data-Server-1.10-yyyy-mm-dd"
You can put up to 10 switch entries in the startup file, so you can list as many as 10 versions of
Evolution. Entries beyond 10 are ignored. You can view the current entries at the POA Web console
with the other SOAP settings. The POA log file lists the settings in the Soap Session section.
7.2 NetWare/Windows Agent Issues
“NetWare POA Cannot Index PDF Files” on page 12
“Windows POA LDAP Authentication to Active Directory” on page 13
7.2.1 NetWare POA Cannot Index PDF Files
The third-party viewer application that converts PDF files to HTML for indexing is not working
properly on NetWare. Use the following startup switch with the NetWare POA to prevent it from
trying to index PDF files:
/dcafilter-pdf
On Linux and Windows, the POA successfully indexes PDF files.

GroupWise 8 Support Pack 2 13
novdocx (en) 16 April 2010
7.2.2 Windows POA LDAP Authentication to Active Directory
If you try to use Active Directory instead of eDirectory for LDAP authentication, LDAP
authentication fails with the following error:
error 32 object not found
As a workaround, point to the Active Directory catalog server on port 3268.
7.3 Linux Agent Issues
“Non-root Agents on Open Enterprise Server for Linux Support Pack 2” on page 13
“Handling GroupWise Agent Core Files on Linux Servers” on page 13
“libXm.so.3 Error” on page 14
“Limitation of the /language Startup Switch” on page 14
7.3.1 Non-root Agents on Open Enterprise Server for Linux Support Pack 2
On Novell Open Enterprise Server 2 and SUSE Linux Enterprise Server 10, services such as IMAP
and IMAP SSL, which require port numbers below 1025, cannot be initiated or restarted after the
GroupWise agents are running as a non-
root user. To initiate or restart those services, you must
manually stop the services and then restart the GroupWise agents.
7.3.2 Handling GroupWise Agent Core Files on Linux Servers
In GroupWise 8 or later, when the POA, the MTA, or the Internet Agent starts, it creates a file named
process_id.pid in the same directory where log files for the agent are created. The
process_id.pid file includes the build date of the agent that created the core file. When a
GroupWise agent creates a core file, it is always named
core.process_id . If you need to submit a
core file to Novell Support, please include the corresponding
process_id.pid file so that Novell
Support can determine the specific agent build that created the core file. Old
process_id.pid files
can be manually deleted along with their corresponding core files.
To cause a GroupWise agent process to create a core file:
1Edit the
/etc/init.d/grpwise script in a text editor.
2Uncomment the following line:
ulimit -c unlimited
3Save the grpwise script, then exit the text editor.
4Restart the agent.
The next time the agent crashes, the core file is created in the root directory of the server (/).
5If the agent does not crash in a timely manner, use the following command as
root to force a
core file from the agent process:
kill -6 pid_number
where pid_number is the process ID number of the agent that is experiencing problems. Use
the following command to obtain the PID number:
ps -eaf | grep agent_executable

14 GroupWise 8 Support Pack 2
novdocx (en) 16 April 2010
where agent_executable is the name of a GroupWise agent (for example, gwpoa ).
6When you no longer need to collect core files, return to the
grpwise script and comment out
the
ulimit line again, so that core files are no longer created.
7.3.3 libXm.so.3 Error
If you try to start the Linux POA or MTA by using the --show switch on a server where the X
Window System and Open Motif are not running, you receive the following error:
libXm.so.3: cannot open shared object file
: no such file or directory
To resolve the error, start the X Window System and Open Motif before starting the POA or MTA
with the --show switch. If you start the POA or MTA without the --show switch, you can use the
agent’s Web console to monitor the agent from your Web browser.
7.3.4 Limitation of the /language Startup Switch
If you use the /language startup switch to start the agents in a language that is different from the
operating system, the list of agent settings does not display correctly. As a workaround, deselect Use
UTF-8 Encoding in YaST (System > Language > Primary Language > Details).
8 Client Issues
Section 8.1, “Windows Client Issues,” on page 14
Section 8.2, “Linux/Mac Client Issues,” on page 17
8.1 Windows Client Issues
“GroupWise Version Compatibility for Panels” on page 15
“GroupWise Version Compatibility for Modified Recurring Calendar Items” on page 15
“Default Contacts Folder” on page 15
“RSS Feed Format Limitation” on page 15
“Archiving over the Network” on page 16
“GroupWise/Teaming Compatibility” on page 16
“Novell Access Manager SSL VPN Compatibility Issue” on page 16
“Windows XP and Administrator Users” on page 16
“Windows XP and Power Users” on page 16
“Address Books Do Not Display in GroupWise When Installing GroupWise after Outlook
2003” on page 17
“Updated JAWS Script Available” on page 17
“VMware and Proxy” on page 17

GroupWise 8 Support Pack 2 15
novdocx (en) 16 April 2010
8.1.1 GroupWise Version Compatibility for Panels
GroupWise 7 allows a maximum of two columns of panels. GroupWise 8 allows you to define
additional columns of panels. If you define three or more columns of panels in GroupWise 8, then
run an earlier GroupWise client, panels do not display correctly in the earlier GroupWise client and
might need to be readjusted when you return to the GroupWise 8 client.
Displaying panels with varying monitor configurations, such as standard vs. wide-screen monitors
and single vs. dual-monitor setups, can also result in altered panel display.
8.1.2 GroupWise Version Compatibility for Modified Recurring Calendar Items
In GroupWise 8, you can right-click a sent calendar item, then click Modify Recipients to add and
remove GroupWise recipients without resending the calendar item. If the recipients include users on
GroupWise 6.5 or GroupWise 7, those recipients see different functionality than GroupWise 8
recipients.
GroupWise 6.5 post offices: The GroupWise 6.5 client still goes through the retract and
resend process. Removed recipients see the retraction. Added recipients receive the new
calendar item. Existing recipients in the post office must re-accept the calendar item.
GroupWise 7 post offices: Install the latest GroupWise 7 Support Pack POA. If you do not
apply the latest Support Pack, GroupWise 7 users might see incorrect retractions and incorrect
Reply to All lists. In addition, orphaned messages can accumulate in the GroupWise 7 post
office. GroupWise 8 users might see incorrect totals for the number of delivered users.
8.1.3 Default Contacts Folder
In GroupWise 8, the default Contacts folder is named Frequent Contacts and corresponds to your
Frequent Contacts address book. Other personal address books display as subfolders under the
Frequent Contacts folder.
In GroupWise 7, there was only one Contacts folder. It was assigned to your Frequent Contacts
address book by default, but you could assign it to different personal address books. If you changed
the address book assigned to the Contacts folder in GroupWise 7, this address book carries over as
the main Contacts folder in GroupWise 8.
If you want to change your main Contacts folder back to the Frequent Contacts address book:
1Right-click your main Contacts folder, then click Properties.
2In the Address Book field, select Frequent Contacts, then click OK.
8.1.4 RSS Feed Format Limitation
The GroupWise Windows client does not recognize RSS feeds that begin with:
feed://
Use the following format instead:
http://

16 GroupWise 8 Support Pack 2
novdocx (en) 16 April 2010
8.1.5 Archiving over the Network
The recommended location for a Windows client user’s archive is on his or her local workstation.
Creating an archive on a network drive is supported only if the Novell Map Network Drive feature
of the Novell Client is used to map a network drive from the user’s workstation to a NetWare server
where the archive is located. Other configurations for archiving to network locations are not
supported.
8.1.6 GroupWise/Teaming Compatibility
Starting in GroupWise 8 Support Pack 1, the GroupWise Windows client is designed to integrate
with a Teaming 2.0 system. It cannot integrate with a Teaming 1.0 system. If you want access to a
Teaming 1.0 system from GroupWise, you must continue to use the GroupWise 8 Windows client.
Update your Teaming 1.0 system to Teaming 2.0 for full compatibility.
When you view a Teaming 2.0 site from the GroupWise Windows client, some functionality is
different from what it would be if you accessed the Teaming site directly:
When the Teaming site is viewed from the GroupWise client, the Teaming Workspace tree is
not displayed. Teaming site navigation is performed through the GroupWise Folder List.
When you select a team in the GroupWise Folder List, by default, team members are listed.
You can click a team member to display that user’s profile, but folders in the user’s personal
workspace are not displayed when viewed from the GroupWise client.
When you display a folder with subfolders, the Teaming Folder tree does not display the
contents of subfolders. However, the subfolders can be accessed from the GroupWise Folder
List.
If you create a new subfolder, it does not immediately display in the Teaming Folder tree or in
the GroupWise Folder List. However, it does display in the GroupWise Folder List the next
time you access the Teaming site from GroupWise.
8.1.7 Novell Access Manager SSL VPN Compatibility Issue
If you want to run Novell Access Manager SSL VPN on the same Windows workstation with
GroupWise 8, install SSL VPN, then install GroupWise 8. If any version of GroupWise is already
installed on the workstation, uninstall GroupWise, install SSL VPN, then install GroupWise 8.
8.1.8 Windows XP and Administrator Users
If GroupWise 7 has already been installed on a workstation by an administrator user, and if
GroupWise 8 is installed by a different administrator user, a second instance of GroupWise is
installed and the first instance is not updated. To fix this problem, go to the Control Panel, then
double-click Add/Remove programs. If GroupWise is listed twice, remove the obsolete instance.
8.1.9 Windows XP and Power Users
If you are a member of the Power Users group when you install the GroupWise Windows client, you
cannot immediately uninstall the GroupWise Windows client in the Control Panel. You must follow
these steps to uninstall:
1Remove yourself from the Power Users group.
2Log out of Windows.

GroupWise 8 Support Pack 2 17
novdocx (en) 16 April 2010
3Log back in to Windows.
4Uninstall the GroupWise Windows client.
8.1.10 Address Books Do Not Display in GroupWise When Installing GroupWise
after Outlook 2003
If you install Outlook, then install GroupWise, then uninstall Outlook, you must reinstall GroupWise
in order to restore MAPI, which is uninstalled along with Outlook. To avoid this problem, uninstall
Outlook before you install GroupWise.
8.1.11 Updated JAWS Script Available
Users of the JAWS screen reader should install the new JAWS script available in GroupWise 7 and
8. Follow the instructions in the
\client\jaws\gw_jaws_readme.txt file to install the JAWS
script and other files on your workstation. This JAWS script includes Section 508 accessibility bug
fixes that have occurred since the script was updated for GroupWise 6.5 Support Pack 3.
8.1.12 VMware and Proxy
If you run the GroupWise Windows client in a VMware virtual machine, you might receive an 8503
error when you try to proxy to another user’s mailbox or display a Multi-User Calendar. To
eliminate this problem, you need to disable the VMware adapters on your Windows workstation.
1Right-click My Network Places, then click Properties.
In the list of LAN connections, you see one or more VMware adapters.
2Right-click each adapter, then click Disable.
8.2 Linux/Mac Client Issues
“Linux Client Package Dependencies” on page 17
“Problem Displaying Flash Content in Web Panels” on page 18
“KDE Integration with the Linux Client” on page 18
“Sound Device Issue” on page 18
“Indexing Limitation of Mac Client in Caching Mode” on page 18
“Default Contacts Folder” on page 18
“Running as root in Caching Mode” on page 19
“Archiving Over the Network” on page 19
“No Progress Bar Displayed When a Database Is Rebuilt” on page 19
8.2.1 Linux Client Package Dependencies
Depending on the Linux version on your workstation, you might need to install the following
packages to resolve dependencies for the GroupWise Linux client:
OpenMotif 2.2 or later
The GIMP Toolkit (GTK) 2 or later
 libstdc++33 or later

18 GroupWise 8 Support Pack 2
novdocx (en) 16 April 2010
Typically, these packages are part of your base Linux operating system.
8.2.2 Problem Displaying Flash Content in Web Panels
In the GroupWise Linux client, if you display a Web page that includes Flash content, and if you
have Adobe Flash Player 9 installed in your Web browser, the GroupWise Linux client might crash.
Install the latest Support Pack for SUSE Linux Enterprise Desktop to resolve the problem. This
Support Pack includes an updated version of Flash Player 9, where the problem no longer occurs.
8.2.3 KDE Integration with the Linux Client
By default, KDE applications like Konqueror or other KDE-based applications do not launch the
Linux GroupWise client when a
mailto link is selected. To configure KDE-based applications to
work with the GroupWise Linux client, see TID 7001213 in the Novell Support Knowledgebase
(http://www.novell.com/support).
8.2.4 Sound Device Issue
The Linux/Mac client currently requires exclusive access to the sound device in your workstation.
As a result, if Notify is turned on and configured to play a sound for notifications or alarms, other
programs cannot use the sound device as long as Notify is running. Novell is awaiting a Sun Java fix
in order to resolve this problem.
8.2.5 Indexing Limitation of Mac Client in Caching Mode
The new indexable file types of PDF, OpenOffice.org, and Microsoft Office 2007 are not indexed by
the Mac client in Caching Mode. The module that provides this functionality is not currently
available on the Mac. If you change to Online mode, the POA handles this indexing, so you can find
these document types in Online mode.
8.2.6 Default Contacts Folder
In GroupWise 8, the default Contacts folder is named Frequent Contacts and corresponds to your
Frequent Contacts address book. Other personal address books display as subfolders under the
Frequent Contacts folder.
In GroupWise 7, there was only one Contacts folder. It was assigned to your Frequent Contacts
address book by default, but you could assign it to different personal address books. If you changed
the address book assigned to the Contacts folder in GroupWise 7, this address book carries over as
the main Contacts folder in GroupWise 8.
If you want to change your main Contacts folder back to the Frequent Contacts address book:
1Linux: Right-click your main Contacts folder.
Mac: Control-click your main Contacts folder.
2Click Properties.
3In the Address Book field, select Frequent Contacts, then click OK.

GroupWise 8 Support Pack 2 19
novdocx (en) 16 April 2010
8.2.7 Running as root in Caching Mode
If you run the Linux/Mac client in Caching mode as root on Linux, you might encounter
synchronization problems with your master mailbox when you next run as a regular user. If pending
requests from the
root session remain when you log in as a regular user, regular user requests are
backed up behind the
root requests, which cannot be processed while you are logged in as a regular
user. To resolve any problems, run the client as
root again so that all messages are synchronized,
then run as a regular user thereafter to prevent further problems.
8.2.8 Archiving Over the Network
The required location for a Linux/Mac client user’s archive is on his or her local workstation.
Creating an archive on a network drive is not currently supported.
8.2.9 No Progress Bar Displayed When a Database Is Rebuilt
When prompted to rebuild your database, there is no progress indicator displayed during the rebuild
process.
9 WebAccess Issues
Section 9.1, “General WebAccess Issues,” on page 19
Section 9.2, “NetWare/Windows WebAccess Issues,” on page 22
Section 9.3, “Linux WebAccess Issues,” on page 23
9.1 General WebAccess Issues
“Apache Optimizations for WebAccess” on page 19
“GroupWise 8 WebAccess Compatibility with Earlier Versions of WebAccess” on page 20
“New Location for the WebAccess Application Configuration File” on page 20
“Blank Login Page” on page 20
“Login Page Reappears after a Successful Login” on page 20
“Login Is Not Current Error” on page 21
“Recommendation for Tomcat Memory Allocation (Heap Size)” on page 21
“Preventing Web Server Directory Browsing” on page 21
“Updates to WebAccess Templates” on page 21
“Library Names with Spaces” on page 22
9.1.1 Apache Optimizations for WebAccess
Starting in Support Pack 1, WebAccess includes Apache optimizations on NetWare and Linux
servers. The optimizations improve management of static content such as images, JavaScript, and so
on. On NetWare and Linux, the
Http EXPIRES header is now set to one year. On NetWare, the Http
DEFLATE
output filter now compresses the static content that is sent from the Web server to the
browser. (The
Http DEFLATE output filter is not currently set on Linux servers.) If you have enabled
these options manually for your Web server, you see warning messages after you install Support
Pack 1. The warning messages are benign and can be ignored.

20 GroupWise 8 Support Pack 2
novdocx (en) 16 April 2010
9.1.2 GroupWise 8 WebAccess Compatibility with Earlier Versions of WebAccess
Before GroupWise 8, you could successfully run different versions of the WebAccess Agent and the
WebAccess Application together. For example, you could install a new version of the WebAccess
Application on your Web server while still running the previous version of the WebAccess Agent for
the domain.
Starting in GroupWise 8, the recommended update procedure is to update all the WebAccess Agents
in your GroupWise system first, then update all the WebAccess Applications. Long-term use of the
mixed-version configuration is not supported and can result in time zone problems. You must update
both the WebAccess Agent and the WebAccess Application to the same version in order to ensure
proper functioning of the GroupWise 8 WebAccess client.
IMPORTANT: Running a new WebAccess Application with an older WebAccess Agent is no
longer supported.
9.1.3 New Location for the WebAccess Application Configuration File
The location of the WebAccess Application configuration file (
webacc.cfg ) has changed in
GroupWise 8.
If you have manually modified settings in your existing webacc.cfg file in the old location, you
must make the same manual changes to the new
webacc.cfg file in the new location. Differences
between the old file and the new file are not merged into the new file by the GroupWise Installation
program.
The WebPublisher Application configuration file (
webpub.cfg ) has also been moved to a parallel
new location and customizations to the file must be transferred manually.
9.1.4 Blank Login Page
The GroupWise 8 WebAccess client Login page might flash and then go blank in Internet Explorer
7. If this happens, clear the browser cache. In Internet Explorer, click Tools > Delete Browsing
History > Delete All.
9.1.5 Login Page Reappears after a 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:
1In ConsoleOne, right-click the WebAccess Application object (GroupWiseWebAccess), then
click Properties.
Platform Old Location New Location
NetWare: sys:\novell\webaccess sys:\novell\groupwise\webaccess
Linux: /opt/novell/groupwise/webaccess /var/opt/novell/groupwise/webaccess
Windows: c:\novell\webaccess c:\novell\groupwise\webaccess