Novell GROUPEWISE 8 - SUPPORT PACK 2 05-2010, GroupWise 8 Support Pack 2 User Manual

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

novdocx (en) 16 April 2010

Novell®

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)

GroupWise 8 Support Pack 2 1

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.

1 Download 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

2 Extract the

that can handle long pathnames.

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

3 In Windows, click Start > Run > Browse, then locate the directory where you extracted the

GroupWise 8 Support Pack 2 administration files.

4 Select the

5 Click Create or Update a GroupWise System.

.zip

file into a directory at the root of your local drive or to a network server drive

setup.exe

file, then click OK to run the GroupWise Installation program.

novdocx (en) 16 April 2010

6 Follow 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

1 Download 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

2 In Windows, click Start > Run > Browse, then locate the directory where you downloaded the

GroupWise 8 Support Pack 2 Client compressed executable file.

3 Double-click the downloaded file, then click Yes to extract the GroupWise client software and

start the GroupWise client Setup program.

2 GroupWise 8 Support Pack 2

4 Follow 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.

novdocx (en) 16 April 2010

1 Download 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

2 In 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.

3 Become

4 In the directory where you extracted the GroupWise 8 Support Pack 2 files, use the following

command to start the GroupWise Installation program:

./install

5 Click Create or Update GroupWise System.

6 Follow 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).

root

by entering

su -

and the

root

password.

4.2 Linux Client Software Installation Instructions

1 At your Linux workstation, download the GroupWise 8 Support Pack 2 client compressed tar

file to a temporary directory:

GroupWise 8 Support Pack 2 3

gw802_beta1_client_linux_en.tar.gz
gw802_beta1_client_linux_multi.tar.gz

2 In 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.

3 In a terminal window, become

by entering

su -

and the

root

password.

root

4 In 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

5 To start the Linux client after installation, double-click the GroupWise icon on your Linux

desktop.

4.3 Mac Client Software Installation Instructions

1 At 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

2 Browse to the GroupWise 8 Support Pack 2 client file that you downloaded.

3 Double-click the

4 Drag the GroupWise package from the

GroupWise icon there for convenient access.

5 To start the Mac client after installation, click the GroupWise icon on the Mac dock.

.dmg

file to install the GroupWise Mac client in the

Applications

folder to the Mac dock to create a

Applications

folder.

novdocx (en) 16 April 2010

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

4 GroupWise 8 Support Pack 2

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

novdocx (en) 16 April 2010

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

us

view files have had the language code

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

GroupWise 8 Support Pack 2 5

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

novdocx (en) 16 April 2010

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

c:\Program Files\Novell

under

GroupWise
Component

Client

6 GroupWise 8 Support Pack 2

Previous Default Location Current Default Location

c:\novell\groupwise c:\Program Files\Novell\GroupWise

into the following subdirectories:

novdocx (en) 16 April 2010

GroupWise
Component

Agents

Internet
Agent

WebAccess
Agent

Monitor
Agent

Previous Default Location Current Default Location

c:\grpwise c:\Program Files\Novell\GroupWise Server

\Agents

c:\grpwise\gwia c:\Program Files\Novell\GroupWise Server\GWIA

c:\webacc c:\Program Files\Novell\GroupWise Server

\WebAccess

c:\gwmon c:\Program Files\Novell\GroupWise Server

\Monitor

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.

GroupWise 8 Support Pack 2 7

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.

novdocx (en) 16 April 2010

At present, the SLES 10 Xen console window does not report its dimensions properly. To work
around this:

1 Make sure that SSH is enabled on the Xen guest.

2 Open an X terminal window on the SLES 10 Xen host, using the following command:

ssh -X root@guest_ip_address

3 Run 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

8 GroupWise 8 Support Pack 2

 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

novdocx (en) 16 April 2010

 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).

GroupWise 8 Support Pack 2 9

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

novdocx (en) 16 April 2010

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.

1 In ConsoleOne, browse to and select the Domain object.

2 Right-click the GroupWiseWebAccess object, then click Properties.

3 Click Application > Security.

4 Deselect Use client IP in securing sessions.

5 Deselect the check boxes in the Use Cookies column.

6 Click 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:

10 GroupWise 8 Support Pack 2

Support Pack GWTSA

GroupWise System/1[DOM]Provo2:
GroupWise System/2[DOM]Provo2:

novdocx (en) 16 April 2010

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

GroupWise 8 Support Pack 2 11