Novell GROUPWISE 7 - SECURITY POLICIES User manual

GroupWise 7
novdocx (en) 6 April 2007
1
GroupWise 7
August 15, 2005
Updated October 5, 2007, with upgrade instructions for Open Enterprise Server 2 and SUSE®Linux
Enterprise Server 10.
1 Product Overview
Novell®GroupWise®7 provides substantial improvements over GroupWise 6.xin six areas:
Windows Client Enhancements: The Windows* client has a new look and feel that includes
the Navigation Bar, Panels, Home Folder, color schemes, and new icons. In addition to the new
look and feel, you can now create and view multiple calendars, create all day events, spell
check as you type, perform Quick Filters, see the Messenger presence information for users,
create HTML signatures, and control inline quotations.
Cross-Platform Client Enhancements: The Cross-Platform client has added many features
including spell checking, rules, junk mail handling, cleanup tools for your mailbox, backup and
restore, and the ability to set your default views, create all day events, and control inline
quotations.
WebAccess Client Enhancements: The WebAccess client has a new look and feel that brings
it closer to the look and feel of the Windows client. Some of the new features include the ability
to drag and drop items, right-click items to display menus, easier tabbed navigation, and name
completion from your Frequent Contacts address book.
Administration Enhancements: GroupWise administrators have additional control over
users' working environments, including granting rights to users to edit distribution lists,
appending global signatures to users' messages, and controlling the appearance of the
GroupWise Windows client interface.
Agent Enhancements: The POA now supports SOAP, so that SOAP clients such as
EvolutionTM can connect to GroupWise. The Internet Agent can fail over to an alternate Internet
Agent to provide redundancy for outbound Internet mail. The GroupWise Linux* agents can
now run as a non-root user and the new High Availability service automatically restarts the
Linux agents if they go down unexpectedly. The Linux and Windows agents support IPV6.
GroupWise Connector for Outlook: The GroupWise Connector for Outlook* allows you to
use Microsoft* Outlook to connect to your GroupWise System. The GroupWise Connector for
Outlook includes support for e-mail, meeting requests and appointments, recurring
appointments, scheduling, tasks, contacts, shared folders, delegates, and proxy.
For a complete list of new features in GroupWise 7, see What's New in Update in the GroupWise 7
Installation Guide (http://www.novell.com/documentation/gw7).
2 NetWare/Windows: GroupWise System
Installation Instructions
To install GroupWise 7 on NetWare®or Windows:
1Run setup.exe at the root of the GroupWise 7 Administrator (NetWare/Windows) CD.

2GroupWise 7
novdocx (en) 6 April 2007
The GroupWise Installation program lets you view the Readme, the Quick Start, and the
Installation Guide before you start installing GroupWise.
2Click Create or Update a GroupWise System.
3Follow the on-screen instructions.
For detailed system requirements, installation and update instructions, and a complete list of new
features, see the GroupWise 7 Installation Guide (GroupWiseInstallationGuide.pdf) in the \docs\us
directory on the GroupWise 7 Administrator (NetWare/Windows) CD or on the GroupWise 7
Documentation Web site (http://www.novell.com/documentation/gw7).
3 Linux: GroupWise System Installation
Instructions
1For ease of installation, make sure that ConsoleOne®is installed on the Linux server where you
want to create your GroupWise system.
ConsoleOne is located in /usr/ConsoleOne/bin.
If necessary, you can download ConsoleOne from the Novell Downloads Web site (http://
download.novell.com).
2At the server where you want to create your GroupWise system, open a new terminal window,
then become root by entering sux and the root password.
When creating your GroupWise system, you must run the GroupWise Installation program in
an environment where The X Window System* is running.
3Change to the root of the GroupWise 7 Administrator (Linux) CD.
4Start the GroupWise Installation program:
./install
5Click Create or Update a GroupWise System.
6Follow the on-screen instructions.
For detailed system requirements, installation and update instructions, and a complete list of new
features, see the GroupWise 7 Installation Guide (GroupWiseInstallationGuide.pdf) in the \docs\us
directory on the GroupWise 7 Administrator (NetWare/Windows) CD of the GroupWise 7
Documentation Web site GroupWise 7 Documentation Web site (http://www.novell.com/
documentation/gw7).
3.1 Linux: Operating System Update
If you are updating your version of Linux as well as updating GroupWise, perform the Linux
operating system upgrade first. In addition, when you upgrade on a server where GroupWise
WebAccess or Monitor is installed, you need to run a script that reconfigures the WebAccess
Application or the Monitor Application for the new Apache and Tomcat configuration and directory
structure.
“Open Enterprise Server 1 to Open Enterprise Server 2” on page 3
“SUSE Linux Enterprise Server 9 to SUSE Linux Enterprise Server 10” on page 5
“Updating the WebAccess Application and the Monitor Application after the Operating System
Upgrade” on page 6

GroupWise 7 3
novdocx (en) 6 April 2007
3.1.1 Open Enterprise Server 1 to Open Enterprise Server 2
When you upgrade from Open Enterprise Server (OES) 1 to OES 2 with GroupWise installed on
your OES server, you encounter package conflicts that must be resolved. A pop-up message appears
immediately before the Installation Settings screen that informs you that the Delete Unmaintained
Packages option is selected under Update Options. OES 2 considers GroupWise an “unmaintained
package.” This means that, by default, your GroupWise software will be deleted as part of the
upgrade process, unless you follow the instructions below.
1Read the pop-up warning carefully, then click OK to close the pop-up.
The pop-up describes three possible actions you can take to resolve the GroupWise status as an
unmaintained package. This procedure steps you through the second of the three possible
actions. This alternative works most efficiently for preserving your GroupWise installation.
2When ConsoleOne®is installed on the server:
The following message displays below the Packages link on the Installation Settings screen:
Cannot solve all conflicts. Manual intervention is required.
2a Click the Packages link.
The upgrade process checks for package conflicts, then displays the following message:
NOVLc1-1.3.6-1.i386 is locked and cannot be uninstalled.
2b Select Keep NOVLc1, then click OK - Try Again.
The upgrade process checks again for conflicts for NOVLc1 and displays one or more
package-related warnings, providing you with alternatives for how to handle each conflict.
The specific warnings you receive depend on the packages installed on the server you are
upgrading. Therefore, warnings vary. Here are some examples:
NOVLc1-1.3.6-1.i386 cannot be installed due to missing
dependencies.
novell-eguide-2.1.32.noarch cannot be installed due to
missing dependencies.
The messages fall into two categories of problems:
Missing dependencies for ConsoleOne (the NOVLc1 package)
Missing dependencies for some other product package besides ConsoleOne (for
example, eGuide)
The following steps help you decide which action to take for each type of message.
2c If the message indicates missing dependencies for ConsoleOne (NOVLc1), select Ignore
This Requirement Just Here.
2d If the message indicates missing dependencies for some other product package besides
ConsoleOne, and you are sure that you do not want that product package, select Delete
package_name.
WARNING: ConsoleOne is dependent on a variety of packages. Delete packages only
when you are certain that they are not required by ConsoleOne. If in doubt, select Keep
package_name.
2e When you have selected an action for each conflict message, click OK - Try Again.

4GroupWise 7
novdocx (en) 6 April 2007
The upgrade process checks again for conflicts for NOVLc1. Additional messages might
be displayed for you to select actions to resolve the conflicts. This cycle repeats until all
conflicts have been resolved, then you successfully reach the Packages page.
3On the Packages page, select Search in the Filter field.
4Search for the GroupWise packages that are installed on the server by typing the following in
the Search field:
novell-groupwise
5Click Search.
Depending on what GroupWise components are installed on the server, the search results
include some of the following packages:
novell-groupwise-admin
novell-groupwise-agents
novell-groupwise-dbcopy
novell-groupwise-gwcheck
novell-groupwise-gwha
novell-groupwise-gwia
novell-groupwise-gwinter
novell-groupwise-gwmon
novell-groupwise-monitor
novell-groupwise-webaccess
6Right-click the first GroupWise package in the list, then click All in This List > Keep.
This changes the status of each GroupWise package from Delete to Keep.
7Search for the NOVLc1 package.
The NOVLc1 and NOVLc1Linuxjre packages should be listed and marked as locked. This
means that they will not be deleted.
8If these packages are marked with a Delete status, change their status to Keep.
9Click Accept on the Packages page.
10 If you are presented with a font License Agreement, click Accept.
11 Click Continue to return to the Install Settings page.
12 Verify that the package conflict message is now gone from under the Packages link, then
continue with the upgrade process.
13 After you have finished the upgrade, reinstall the NDSbase RPM that was originally installed
with ConsoleOne.
The upgrade process removed it, but it is still needed by ConsoleOne.
13a In a Linux terminal window, log in as root, then change to the directory where you
originally extracted the ConsoleOne files.
13b Change to the Linux subdirectory.
13c Use the following command to reinstall the NDSbase RPM:
rpm -ivh NDSbase-8.7.3.7-38.i386.rpm
If you encounter problems with GroupWise after you have upgraded from OES 1 to OES 2, see TID
3570778 in the Novell Knowledgebase (http://www.novell.com/support/supportcentral) for
assistance.

GroupWise 7 5
novdocx (en) 6 April 2007
3.1.2 SUSE Linux Enterprise Server 9 to SUSE Linux Enterprise Server 10
When you upgrade from SLES 9 to SLES 10 with GroupWise installed on your SLES server, you
encounter package conflicts that must be resolved.
1When ConsoleOne is installed on the server:
The following message displays below the Packages link on the Installation Settings screen:
Cannot solve all conflicts. Manual intervention is required.
1a Click the Packages link.
The upgrade process checks for package conflicts, then displays the following message:
NOVLc1-1.3.6-1.i386 is locked and cannot be uninstalled.
1b Select Keep NOVLc1, then click OK - Try Again.
The upgrade process checks again for conflicts for NOVLc1 and displays one or more
package-related warnings, providing you with alternatives for how to handle each conflict.
The specific warnings you receive depend on the packages installed on the server you are
upgrading. Therefore, warnings vary. Here are some examples:
NOVLpkia-2.7.0-6.i386 is locked and cannot be
uninstalled.
NOVLc1-1.3.6-1.i386 cannot be installed due to missing
dependencies.
The messages fall into two categories of problems:
A locked package
Missing dependencies for ConsoleOne (the NOVLc1 package)
The following steps help you decide which action to take for each type of message.
1c If the message indicates a locked package, select Keep package_name.
1d If the message indicates missing dependencies for ConsoleOne (NOVLc1), select Ignore
This Requirement Just Here.
1e When you have selected an action for each conflict message, click OK - Try Again.
The upgrade process checks again for conflicts for NOVLc1. Additional messages are
displayed for you to select actions to resolve the conflicts. This cycle repeats until all
conflicts have been resolved (approximately nine times), then you successfully reach the
Packages page.
2On the Packages page, select Search in the Filter field.
3Search for the GroupWise packages that are installed on the server by typing the following in
the Search field:
novell-groupwise
4Click Search.
Depending on what GroupWise components are installed on the server, the search results
include some of the following packages:
novell-groupwise-admin
novell-groupwise-agents
novell-groupwise-dbcopy
novell-groupwise-gwcheck
novell-groupwise-gwha
novell-groupwise-gwia

6GroupWise 7
novdocx (en) 6 April 2007
novell-groupwise-gwinter
novell-groupwise-gwmon
novell-groupwise-monitor
novell-groupwise-webaccess
5Right-click the first GroupWise package in the list, then click All in This List > Keep.
This changes the status of each GroupWise package from Delete to Keep.
6Search for the NOVLc1 package.
The NOVLc1 and NOVLc1Linuxjre packages should be listed and marked as locked. This
means that they will not be deleted.
7If these packages are marked with a Delete status, change their status to Keep.
8Click Accept on the Packages page.
9If you are presented with a font License Agreement, click Accept.
10 Click Continue to return to the Install Settings page.
11 Verify that the package conflict message is now gone from under the Packages link, then
continue with the upgrade process.
12 After you have finished the upgrade, reinstall the NICI RPM and the NDSbase RPM that were
originally installed with ConsoleOne.
The upgrade process removed them, but they are still needed by ConsoleOne.
12a In a Linux terminal window, log in as root, then change to the directory where you
originally extracted the ConsoleOne files.
12b Change to the Linux subdirectory.
12c Use the following commands to reinstall the RPMs:
rpm -ivh nici-version-i386
rpm -ivh NDSbase-version.i386.rpm
If you encounter problems with GroupWise after you have upgraded from SLES 9 to SLES 10, see
TID 3570778 in the Novell Knowledgebase (http://www.novell.com/support/supportcentral) for
assistance.
3.1.3 Updating the WebAccess Application and the Monitor Application after the
Operating System Upgrade
When you upgrade your Linux operating system, OES 2 installs new versions of Apache and
Tomcat by default. SLES does not; you must install them manually by following the procedure in
this section. In addition, the GroupWise 7 installations of the WebAccess Application and the
Monitor Application must be modified to accommodate changes made in Apache and Tomcat. The
WebAccess/Monitor Update script takes care of this process for you. This script is available with
TID 3624780 in the Support Knowledgebase (http://www.novell.com/support/supportcentral).
1If you have upgraded to SLES 10, use YaST to install Apache and Tomcat if they were not
already installed on SLES 9:
1a Start YaST, then provide the root password.
1b Click Software Management.
1c In the Search field, type Apache, click Search, then select apache2 from the list.
1d In the Search field, type Tomcat, click Search, then select tomcat5 from the list.

GroupWise 7 7
novdocx (en) 6 April 2007
Apache 2 was part of your SLES 9 installation, so it should have been automatically
upgraded. Tomcat changed from Tomcat 4 to Tomcat 5, so unless Tomcat 5 was installed
on SLES 9, Tomcat 5 needs to be installed.
1e Click Accept.
1f Follow the prompts to install the needed packages to your SLES 10 server.
1g Exit YaST.
2Download the WebAccess/Monitor Update script from TID 3624780 in the Novell Support
Knowledgebase (http://www.novell.com/support/supportcentral) to a convenient location on
your Linux server.
3Change to the directory where you downloaded the script file.
4Give the script file execute permissions:
chmod +x fixgwweb.sh
5Run the script.
The script makes some slight reconfigurations of GroupWise files and directories that were
originally set up when the WebAccess Application and the Monitor Application were installed
on your previous version of Linux.
Apache 2: On OES 1 and SLES 9, Apache 2 used the mod_jk connector to facilitate
communication between Apache and Tomcat. On OES 2 and SLES 10, Apache 2 uses the
mod_proxy module instead. The WebAccess/Monitor Update script modifies the
gw.conf file with this change. On SLES 10, the script also creates a symbolic link from
/etc/opt/novell/gw/gw.conf to the new Apache 2 location of /etc/
apache2/conf.d/gw.conf.
Tomcat 5: On OES 1 and SLES 9, the WebAccess /var/opt/novell/gw directory
was linked to /var/opt/novell/tomcat4/webapps/gw. The script changes this
link to /var/opt/novell/tomcat5/webapps/gw. For Monitor, the /var/opt/
novell/gwmon directory now links to/var/opt/novell/tomcat5/webapps/
gwmon.
6Start or restart Tomcat.
7Start or restart Apache.
8If you are upgrading to OES 2:
You might receive the following message when starting Apache 2:
Module "Jk" is not installed, ignoring.
You can safely ignore this message, but if you want to eliminate it:
8a Start YaST, then provide the root password.
8b Click NetWork Services > HTTP Server.
OES 2: /etc/init.d/novell-tomcat5 restart
SLES 10: /etc/init.d/tomcat5 start
OES 2: /etc/init.d/apache2 restart
SLES 10: /etc/init.d/apache2 restart

8GroupWise 7
novdocx (en) 6 April 2007
8c On the Server Modules tab, select the jk module in the list of services, then toggle the
status to Off.
8d Click Finish to save your change.
8e Exit YaST.
You should now be able to run WebAccess and Monitor successfully on your upgraded Linux
operating system.
4 GroupWise Client Installation
Section 4.1, “Windows: Installation Instructions,” on page 8
Section 4.2, “Linux: Installation Instructions,” on page 8
Section 4.3, “Macintosh: Installation Instructions,” on page 8
Section 4.4, “GroupWise Connector for Outlook,” on page 8
For detailed installation instructions, see the GroupWise 7 Installation guide
(GroupWiseInstallationGuide.pdf) in the \docs\us directory on the GroupWise 7 Administrator CD.
4.1 Windows: Installation Instructions
1Run setup.exe at the root of the GroupWise 7 Client (Windows) CD.
or
Run setup.exe from the client\win32 subdirectory on the GroupWise 7 Client (Windows) CD.
2Follow the on-screen instructions.
4.2 Linux: Installation Instructions
1From a terminal window, change to the \linux directory of the GroupWise 7 Client (Linux/
Macintosh) CD.
2Run the GroupWise Setup Advisor to install the GroupWise Cross-Platform client software:
./install
3To start the Cross-Platform client after installation, click the GroupWise icon on your Linux
desktop.
4.3 Macintosh: Installation Instructions
1Browse to the \mac directory of the GroupWise 7 Client (Linux/Macintosh) CD.
2Double-click the GroupWise.dmg file to install the GroupWise Macintosh* client.
3To start the Cross-Platform client after installation, click the GroupWise icon on your
Macintosh desktop.
4.4 GroupWise Connector for Outlook
For instructions on how to install and for additional information about the GroupWise Connector for
Outlook, see the GroupWise Connector for Outlook Readme. The GroupWise Connector for

GroupWise 7 9
novdocx (en) 6 April 2007
Outlook Readme is available in the \client\doc\us\ directory of the GroupWise 7 Client (Windows)
CD.
5 Installation Issues
Section 5.1, “General Installation Issues,” on page 9
Section 5.2, “NetWare/Windows Installation Issues,” on page 10
Section 5.3, “Linux Installation Issues,” on page 10
5.1 General Installation Issues
“Version Compatibility” on page 9
“GroupWise 7 Reinstallation” on page 9
“WebAccess and Monitor on the Same Web Server” on page 9
“Web Clipping Application (PQA) Support with WebAccess and Monitor” on page 9
“Additional Installation Issues” on page 10
5.1.1 Version Compatibility
If you install GroupWise on multiple platforms, or if you run multiple versions (for example,
GroupWise 6.5 and GroupWise 7 in the same GroupWise system), refer to the GroupWise Version
Compatibility appendix in the GroupWise 7 Installation Guide (http://www.novell.com/
documentation/gw7) to make sure that the combinations you are using are supported. For example,
you cannot run a GroupWise 7 client against a GroupWise 6.5 or earlier post office. Earlier POAs
cannot support later GroupWise clients. However, you can run a GroupWise 6.5 or earlier client
against a GroupWise 7 POA.
5.1.2 GroupWise 7 Reinstallation
If you install GroupWise 7 components from a software distribution directory located on your local
drive or a network drive and then try to update those components by installing from a CD, the
installation fails by erroneously prompting for a disk:
Please insert the disk: 1
Uninstall the existing software, then install from the CD.
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 Web Clipping Application (PQA) Support with WebAccess and Monitor
Palm OS* devices are no longer supported in GroupWise 7. However, the Installation program still
offers the opportunity to configure this feature. If you have been using a PQA in an earlier version of
GroupWise, you can continue to do so, but it is no longer a supported feature.

10 GroupWise 7
novdocx (en) 6 April 2007
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
“Software Distribution Directory Dependency” on page 10
“Problem Installing from a Windows XP Service Pack 2 Machine” on page 10
“GroupWise Version Compatibility” on page 10
5.2.1 Software Distribution Directory Dependency
When you create a new system and are prompted for software to copy to the software distribution
directory, select at least the agent and client software. The GroupWise Installation program launches
the Agent Installation program and the Client Installation program. It currently must run those
programs from the software distribution directory.
5.2.2 Problem Installing from a Windows XP Service Pack 2 Machine
When installing 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 ClientTM 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.3 GroupWise Version Compatibility
If you still have GroupWise 4.1 domains or post offices in your GroupWise system, you must update
them to at least GroupWise 5.2 before updating your primary domain to GroupWise 7. If you try to
update a 4.1 domain or post office to 7 after the primary domain has already been updated to 7, you
need to rebuild each 4.1 secondary domain database using the GroupWise 7 or later snap-ins to
ConsoleOne, and you also need to have each rebuilt secondary domain database manually edited by
Novell Support before it can function correctly with the 7 primary domain.
5.3 Linux Installation Issues
“Configuring a GroupWise 6.5 Upgrade Installation” on page 10
“Upgrading from an Incomplete Software Distribution Directory” on page 11
“Moving a GroupWise 4.1 System from NetWare or Windows to Linux” on page 11
5.3.1 Configuring a GroupWise 6.5 Upgrade Installation
When you upgrade any GroupWise component to GroupWise 7, all GroupWise components on a
server must be updated at the same time. A message prompts you to update all components.
However, you must still run the Configure option for each component so that the software that was
automatically installed is also configured. If you do not run Configure, the new GroupWise High
Availability service is not properly configured for the agents.

GroupWise 7 11
novdocx (en) 6 April 2007
5.3.2 Upgrading from an Incomplete Software Distribution Directory
Because all GroupWise components on a server must be updated at the same time, if you are
installing GroupWise 7 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 7 component cannot be updated because its RPM is not present in the software
distribution directory. You can use the GroupWise 7 Administrator (Linux) CD to update the server,
then use Configure Administration to create a complete software distribution directory.
5.3.3 Moving a GroupWise 4.1 System from NetWare or Windows to Linux
The Update section of the GroupWise 7 Installation Guide provides instructions for moving from
NetWare or Windows to Linux. If you are moving post offices and domains belonging to a
GroupWise 4.1 system, you might need to manually rename the domain database (wpdomain.db)
from uppercase to lowercase, along with all .dc files. In addition, subdirectories in post office and
domain directories might need to be renamed to lowercase.
6 Administration Issues
Section 6.1, “General Administration Issues,” on page 11
Section 6.2, “NetWare/Windows Administration Issues,” on page 12
Section 6.3, “Linux Administration Issues,” on page 13
6.1 General Administration Issues
“Images in Global Signatures” on page 11
“Global Signatures and Flat Forwarding through the Internet Agent” on page 11
“ConsoleOne Snap-In Version Compatibility” on page 12
“Server Names” on page 12
“Identity Manager Version Compatibility” on page 12
“Server-Based Anti-Virus Software” on page 12
6.1.1 Images in Global Signatures
You might encounter a problem including an image file in a global signature if the path to the image
is too long. This is a Java* problem. The easiest workaround is to move the image to a location with
a shorter path. Another solution on Windows is to set the TMP environment variable to c:\temp
before starting ConsoleOne.
6.1.2 Global Signatures and Flat Forwarding through the Internet Agent
If you enable global signatures, it disables flat forwarding through the Internet Agent because the
signature is appended to each message. As an administrator, you must choose which is more
important in your GroupWise system, global signatures or flat forwarding.

12 GroupWise 7
novdocx (en) 6 April 2007
6.1.3 ConsoleOne Snap-In Version Compatibility
After a domain has been updated to GroupWise 7, do not administer that domain with earlier
versions of the GroupWise snap-ins to ConsoleOne. Doing so could result in the unintentional
creation of duplicate e-mail IDs.
The e-mail ID indexing scheme has been changed to allow the same e-mail ID to be used in different
Internet domains within the same GroupWise system. This was prevented by the previous indexing
scheme. Because the check for uniqueness works differently now, you must use the GroupWise 7
version of the ConsoleOne snap-ins when administering a GroupWise 7 domain to prevent the
possibility of duplication.
6.1.4 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.5 Identity Manager Version Compatibility
Do not run an existing DirXML®or Identity Manager driver dated earlier than July, 2005, against a
GroupWise 7 system.
GroupWise 7 requires the latest version of the GroupWise Identity Manager driver. Older drivers are
not compatible. You can download the required version of the GroupWise driver from the Novell
Identity Manager Patches Web site (http://support.novell.com/filefinder/20560/index.html).
6.1.6 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/p100031.html) for
compatible products.
6.2 NetWare/Windows Administration Issues
“Directory Names and Filenames” on page 12
“ConsoleOne on Windows NT” on page 13
“GWTSA and Duplicate Source Directories” on page 13
“Utility Startup Switches” on page 13
“Quotas on NSS Volumes” on page 13
“TurboFat Compatibility” on page 13
6.2.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).

GroupWise 7 13
novdocx (en) 6 April 2007
6.2.2 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.
6.2.3 GWTSA and Duplicate Source Directories
The GroupWise Target Service Agent (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
GroupWise 6.5 Support Pack 1 or later, you must re-create your backup jobs because the path has
changed.
6.2.4 Utility Startup Switches
The NetWare version of the GroupWise Time Stamp Utility (GWTMSTMP) currently requires
startup switches to use a dash (for example, -u), rather than the standard NetWare switch format (for
example, /u).
6.2.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.
6.2.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.
To turn off TurboFat on NetWare 5.xservers, use turbodis.nlm.
To turn off TurboFat on NetWare 6.xservers, use tdis600.nlm.
These NLMTM programs disable TurboFat at startup.
6.3 Linux Administration Issues
“NFS Not Supported” on page 14
“Pathnames and Filenames in Lowercase” on page 14
“Display Problem with ConsoleOne Property Page Tabs” on page 14
“Unavailable Administration Features” on page 14

14 GroupWise 7
novdocx (en) 6 April 2007
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.
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.
However, if you update a GroupWise 4.1 system and move it to Linux, you might see uppercase
letters in database names. This is not a problem. The Database Copy (DBCopy) utility that you use
to move domains and post office to Linux handles any uppercase/lowercase issues that might arise,
so you should not manually rename any databases that have been copied to Linux using DBCopy.
6.3.3 Display Problem with ConsoleOne Property Page Tabs
If you run ConsoleOne on SUSE®LINUX 9 with Ximian®Desktop 2 installed, the label text on the
property tabs does not display. As a workaround, click the tab to select it, then use the Up-arrow and
Down-arrow keys to display each property page until you reach the one you want.
6.3.4 Unavailable Administration Features
GroupWise 7 administration on Linux does not include the following features that are available in
GroupWise 7 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 14
Section 7.2, “NetWare/Windows Agent Issues,” on page 14
Section 7.3, “Linux Agent Issues,” on page 15
7.1 General Agent Issues
None.
7.2 NetWare/Windows Agent Issues
“Potential CAP Port Conflict” on page 14
7.2.1 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 by the Windows Task Scheduler or other Windows service.
If this occurs, configure the POA to use a different CAP port using the /capport switch in the POA
startup file.

GroupWise 7 15
novdocx (en) 6 April 2007
7.3 Linux Agent Issues
“libXm.so.3 Error” on page 15
7.3.1 libXm.so.3 Error
If you try to start the POA or MTA 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.
8 Client Issues
Section 8.1, “Windows Client Issues,” on page 15
Section 8.2, “Cross-Platform Client Issues,” on page 16
8.1 Windows Client Issues
“Can't Set a Primary Archive Computer” on page 15
“Error Messages When You Install GroupWise Windows Client” on page 15
“Windows XP Service Pack 2” on page 16
“Updated JAWS Script Available” on page 16
“Screen Flickers When Scrolling a Message” on page 16
“Can't Switch Modes Using Microsoft Anti-Spyware” on page 16
“Address Books Do Not Display in GroupWise When Installing GroupWise After Outlook
2003” on page 16
“Notify Alarms Disappear for Appointments” on page 16
“Spyware Detection Software Causes Installation to Not Work” on page 16
8.1.1 Can't Set a Primary Archive Computer
Currently there is no way to set one computer as a primary archive. This can result in multiple
archives if you use GroupWise on different computers.
8.1.2 Error Messages When You Install GroupWise Windows Client
If you install the GroupWise Windows client with Outlook XP already installed, an error message
appears reading, “Either there is no default mail client or the current mail client cannot fulfil the
messaging request. Please run Microsoft Outlook and set it as the default mail client”. In addition, if
you open the Address Book, the GroupWise client crashes.
To fix the problem run win32\wms\nt\us\wms.exe from the install directory, then restart the client.

16 GroupWise 7
novdocx (en) 6 April 2007
8.1.3 Windows XP Service Pack 2
Installing Windows XP Service Pack 2 enables the Windows Firewall by default. The default
Windows Firewall configuration blocks UDP (User Datagram Protocol). GroupWise is dependent
on UDP for several key features such as listing new messages in your Mailbox, displaying
notifications, and performing Busy Searches. To reconfigure the Windows Firewall so that it does
not interfere with GroupWise functionality, follow the instructions in TID 10094089 in the Novell
Support Knowledgebase (http://support.novell.com/search/kb_index.jsp).
8.1.4 Updated JAWS Script Available
Users of the JAWS* screen reader should install the new JAWS script available in GroupWise 7.
Copy the groupwise.jsb file from the \client\jaws directory of the GroupWise 7 Client (Windows) CD
to the \jaws510\settings\enu directory on your workstation. This JAWS script includes Section 508
accessibility defect fixes that have occurred since the script was updated for GroupWise 6.5 Support
Pack 3.
8.1.5 Screen Flickers When Scrolling a Message
If you use ClearType to smooth the edges of screen fonts and have an LCD display, your screen
might flicker when scrolling in a text message.
8.1.6 Can't Switch Modes Using Microsoft Anti-Spyware
If you are using Microsoft's Anti-Spyware software, and you try to switch modes, GroupWise does
not close. You must manually close GroupWise to switch modes.
8.1.7 Address Books Do Not Display in GroupWise When Installing GroupWise After
Outlook 2003
The address books do not display in GroupWise if you install GroupWise for the first time after you
have installed Outlook 2003. To resolve the problem, uninstall Outlook 2003 before you install
GroupWise for the first time.
8.1.8 Notify Alarms Disappear for Appointments
After your account has been moved from one post office to another, your Notify alarms disappear
for appointments. To get your Notify alarms back, you need to re-create all the alarms manually. For
information on setting alarms for appointments, see the help.
8.1.9 Spyware Detection Software Causes Installation to Not Work
If you have spyware detection software installed on your Windows computer, the GroupWise client
for Windows might not install properly. Disable the spyware detection software before you install
the GroupWise client for Windows.
8.2 Cross-Platform Client Issues
“Items Forwarded from the GroupWise Connector for Outlook Do Not Open” on page 17
“Running as root in Caching Mode” on page 17
“Mailbox Size Limits Not Recognized” on page 17

GroupWise 7 17
novdocx (en) 6 April 2007
“Bold Not Displaying on Macintosh” on page 17
“Archiving Over the Network” on page 17
“No Progress Bar Displayed When a Database Is Rebuilt” on page 17
“Focus Is in the Wrong Place When Creating a Reply on Macintosh” on page 17
“GWCheck Must Be Run from a Terminal Window on Macintosh” on page 17
“Corrupt Characters in Asian Languages” on page 18
8.2.1 Items Forwarded from the GroupWise Connector for Outlook Do Not Open
If you receive an item that was forwarded from the GroupWise Connector for Outlook, the item does
not open in the Macintosh version of the Cross-Platform client.
8.2.2 Running as root in Caching Mode
If you run the Cross-Platform 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 get
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.3 Mailbox Size Limits Not Recognized
The Cross-Platform client does not recognize the mailbox size limits set in ConsoleOne (Tools >
GroupWise Utilities > Client Options > Send > Disk Space Management).
8.2.4 Bold Not Displaying on Macintosh
If you have installed Microsoft Office or Internet Explorer on your Macintosh, new messages might
not display as bold in your mailbox. To resolve the problem, disable your user fonts, which are
typically duplicates of your system fonts, or update to JVM* 1.4.2 Update 1 or later.
8.2.5 Archiving Over the Network
Archiving with the Cross-Platform client can only be done to your local computer hard drive.
8.2.6 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.
8.2.7 Focus Is in the Wrong Place When Creating a Reply on Macintosh
When you click Reply on Macintosh, you cannot just type the message. You must move the mouse
cursor to the message body window of the reply message before you can start typing.
8.2.8 GWCheck Must Be Run from a Terminal Window on Macintosh
If you try to browse to the GWCheck program and run it by double-clicking the icon, you receive an
error stating that there is no associated program. You must run GWCheck from a terminal window
on Macintosh.

18 GroupWise 7
novdocx (en) 6 April 2007
8.2.9 Corrupt Characters in Asian Languages
If you're using an Asian language for the client and external recipients are seeing corrupt characters
in their received messages, then compose your message in HTML instead of text.
9 WebAccess Issues
Section 9.1, “General WebAccess Issues,” on page 18
Section 9.2, “NetWare/Windows WebAccess Issues,” on page 21
Section 9.3, “Linux WebAccess Issues,” on page 24
9.1 General WebAccess Issues
“WebAccess 7 Compatibility with Older Versions of WebAccess” on page 18
“WebAccess 7 Compatibility with Virtual Office 1.5 and Earlier” on page 18
“WebAccess Compatibility with Novell exteNd” on page 18
“WebAccess 7 Client on Macintosh” on page 19
“Login Page Reappears after Successful Login” on page 19
“Recommendation for Tomcat Memory Allocation (Heap Size)” on page 19
““Browser Doesn't Support Java” Error in the WebAccess Java Calendar” on page 19
“Preventing Web Server Directory Browsing” on page 20
“Preventing Unauthenticated Template Access” on page 20
“Updates to WebAccess Templates” on page 20
“Document Viewer Agent Cache Compatibility” on page 20
“Document Viewer Agent /template Switch” on page 20
9.1.1 WebAccess 7 Compatibility with Older Versions of WebAccess
If you have more than one WebAccess Agent in your GroupWise system, you do not need to update
all of them to GroupWise 7 at the same time. The GroupWise 7 WebAccess Application is
compatible with older versions of the WebAccess Agent. However, users in post offices with a older
default WebAccess Agent do not have all of the features available to users in post offices with a
default GroupWise 7 WebAccess Agent. For more information, see Taking Advantage of Some of
the New GroupWise 7 WebAccess Features While Still Running GroupWise 6.5 (http://
www.novell.com/coolsolutions/feature/15667.html).
9.1.2 WebAccess 7 Compatibility with Virtual Office 1.5 and Earlier
If you access the WebAccess client through Virtual Office 1.5 or earlier, you might see the old
WebAccess client interface rather than the new one. To resolve this problem, see TID 10098412 in
the Novell Knowledgebase (http://support.novell.com/search/kb_index.htm).
9.1.3 WebAccess Compatibility with Novell exteNd
Before GroupWise 7, WebAccess stored its default user interface files in the following directory on
the Web server:

GroupWise 7 19
novdocx (en) 6 April 2007
tomcat_root/webapps/gw/WEB-INF/classes/com/novell/webaccess/templates/frames
In GroupWise 7, the user interface files are stored in the css subdirectory of templates rather than the
frames subdirectory.
If you have exteNdTM portlets configured to use WebAccess, you must copy some of the exteNd
template files from the frames directory into the css directory. Refer to the Novell exteNd
documentation (http://www.novell.com/documentation/extend5/index.html) to determine which
exteNd template files you should copy to the css directory. Do not copy the entire contents of the
frames directory into the css directory; this would damage the new GroupWise 7 WebAccess user
interface.
In addition, modify the WebAccess URL in the exteNd Portal Preferences from:
http://Web_server_address/servlet/webacc
to:
http://Web_server_address/gw/webacc
9.1.4 WebAccess 7 Client on Macintosh
If you use the WebAccess client in the Safari* Web browser on Macintosh, name completion is
disabled because of lack of support for certain browser capabilities in Safari. Name completion is
supported in the Mozilla* Firefox* Web browser on Macintosh.
9.1.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:
1In ConsoleOne, right-click the WebAccess Application object (GroupWiseWebAccess), then
click Properties.
2Click Application > Security, then deselect the Use Client IP in Securing Sessions option.
For information about this option, click Help on the Environment page.
3Click OK to save the change.
9.1.6 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).
9.1.7 “Browser Doesn't Support Java” Error in the WebAccess Java Calendar
This error indicates a browser setup issue. You would encounter the same problem on any Web site
that uses Java in frames. Depending on your browser, check mozilla.org, sun.com, or other browser
supplier for more information.

20 GroupWise 7
novdocx (en) 6 April 2007
9.1.8 Preventing Web Server Directory Browsing
If your Web server is configured to allow directory browsing, it is possible for a user to access the /
com directory of your Web server and browse downward from there. There is no confidential
information located in any of the directories that are accessible in this manner.
However, if you want to prevent access, you can change the configuration of your Web server. For
example, if you are using Apache, you can modify the httpd.conf file to remove the access that is
provided by default. Locate the section that provides directory options for the htdocs directory.
Either remove the Indexes option from the Options directive or place a minus (-) in front of it.
Restart Apache to put the change into effect.
9.1.9 Preventing Unauthenticated Template Access
Under certain very specific circumstances, it is possible for a user to view WebAccess template files
from a Web browser without logging in to WebAccess. There is no confidential information located
in any of the template files that are accessible in this manner.
Starting with GroupWise 6.5 Support Pack 4, a line was added to the webacc.cfg file to prevent such
access:
Templates.requireAuthentication=true
With this setting, unauthenticated users have no access to any WebAccess template files except for
the Login page. If you have customized WebAccess templates for your own specialized use, this
setting causes your templates to be inaccessible, even if GroupWise authentication was not
previously required. You can turn off the authentication requirement by changing the line in the
webacc.cfg file to:
Templates.requireAuthentication=false
9.1.10 Updates to WebAccess Templates
If you have created your own customized versions of the WebAccess send.inc and msgitem.htt
templates, you need to make the following changes to these files in order for them to be compatible
with GroupWise 7:
Do not use the Url.Item.Reply.to and Url.Item.Reply.cc variables to pass and post names in a
reply message's To and CC fields. Instead, use Item.toFullID and Item.ccFullID (or
Item.toName or Item.ccName).
When issuing an Item.Read action for a reply, set the Item.Reply parameter to either “sender”
(to reply only to the sender) or “all” (to reply to all).
9.1.11 Document Viewer Agent Cache Compatibility
The cache created by the Document Viewer Agent is not compatible with the cache previously used
with WebPublisher. Old WebPublisher cache directories should be removed from servers where the
Viewer Agent is installed.
9.1.12 Document Viewer Agent /template Switch
The Document Viewer Agent startup file (gwdva.dva) lists a /template startup switch that is not yet
implemented.