September 12, 2012
GroupWise 8.0.2 HP4 is specifically for Mac client users who are running Mac OS 10.6.8 (Snow Leopard) or later.
A substantial number of bugs have been fixed, as listed in the GroupWise 8.0.2 HP4 Bug Fix List.
GroupWise 8.0.2 HP4 includes all bug fixes that are available in GroupWise 8.0.1 and earlier Hot Patches.
IMPORTANT:For best results, update the post offices where Mac client users are located to GroupWise 8.0.3 or GroupWise 2012.
GroupWise 8.0.2 provides enhancements for both administrators and end users.
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
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.
For a list of the bugs that have been fixed in GroupWise 8.0.2, see the GroupWise 8.0.2 Bug Fix List.
GroupWise 8 system requirements are listed in the GroupWise 8 Installation Guide.
In GroupWise 8.0.2, the following additional GroupWise client operating systems are supported:
Windows 7
Mac OS 10.6 (Snow Leopard)
IMPORTANT:If you are installing the GroupWise software in a cluster, refer to the GroupWise 8 Interoperability Guide for cluster-specific installation instructions before starting to install the GroupWise 8.0.2 software.
Download the NetWare/Windows GroupWise 8.0.2 compressed executable file to a temporary directory on your NetWare or Windows server:
gw802_full_nlmwin_en.zip gw802_full_nlmwin_multi.zip
Extract 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.
In Windows, click , then locate the directory where you extracted the GroupWise 8.0.2 administration files.
Select the setup.exe file, then click to run the GroupWise Installation program.
Click .
Follow the on-screen instructions to install the GroupWise 8.0.2 software.
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 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.
Download the GroupWise 8.0.2 Windows Client compressed executable file to a temporary directory on your workstation:
gw802_client_win_en.exe gw802_client_win_multi.exe
In Windows, click , then locate the directory where you downloaded the GroupWise 8.0.2 Client compressed executable file.
Double-click the downloaded file, then click to extract the GroupWise client software and start the GroupWise client Setup program.
Follow the on-screen instructions to install the GroupWise 8.0.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 tab of the Windows Task Manager to observe CPU usage.
IMPORTANT:If you are installing the GroupWise software in a cluster, refer to the GroupWise 8 Interoperability Guide for cluster-specific installation instructions before starting to install the GroupWise 8.0.2 software.
Download the GroupWise 8.0.2 Administration compressed tar file to a temporary directory on your Linux server:
gw802_full_linux_en.tar.gz gw802_full_linux_multi.tar.gz
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.
Become root by entering su - and the root password.
In the directory where you extracted the GroupWise 8.0.2 files, use the following command to start the GroupWise Installation program:
./install
Click .
Follow the on-screen instructions to install the GroupWise 8.0.2 software.
When you install a Support Pack, you can streamline the update process by using the option to install the updated RPM for each agent. Typically, you do not need to use the 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 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.
At your Linux workstation, download the GroupWise 8.0.2 client compressed tar file to a temporary directory:
gw802_client_linux_en.tar.gz gw802_client_linux_multi.tar.gz
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.
In a terminal window, become root by entering su - and the root password.
In the directory where you extracted the GroupWise 8.0.2 client files, run the GroupWise Setup program to install the GroupWise Linux client software:
./install
To start the Linux client after installation, double-click the GroupWise icon on your Linux desktop.
At your Macintosh workstation, download the GroupWise 8.0.2 HP4 client file to a temporary directory
gw8.0.2HP4-client_mac_en.dmg gw8.0.2HP4-client_mac_multi.dmg
Browse to the GroupWise 8.0.2 HP4 client file that you downloaded.
Double-click the .dmg file to install the GroupWise Mac client in the Applications folder.
Drag the GroupWise package from the Applications folder to the Mac dock to create a GroupWise icon there for convenient access.
To start the Mac client after installation, click the GroupWise icon on the Mac dock.
Installation issues for individual GroupWise components are located under the heading for each component.
GroupWise 8 includes new functionality that requires you to extend the schema of any Novell eDirectory trees where you have GroupWise objects created by an earlier version of GroupWise. The GroupWise 8 Installation program does not currently extend the eDirectory schema for you when you update to GroupWise 8. Before you update your GroupWise system, use ConsoleOne to extend the eDirectory schema for GroupWise 8.
Install the GroupWise 8 snap-ins to ConsoleOne.
In ConsoleOne, select an eDirectory tree that contains GroupWise objects.
Click .
If the schema is current, a message notifies you. If the schema is not current, you can use this utility to update to the current schema.
Repeat this procedure for each eDirectory tree that contains GroupWise objects.
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 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 under to specify the required version of the ConsoleOne snap-ins for each domain as needed.
See also Section 11.1.2, GroupWise 8 WebAccess Compatibility with Earlier Versions of WebAccess.
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.
Platform-specific installation issues are listed in separate sections below. Installation issues for individual GroupWise components are located under the heading for each component.
The GroupWise 8.0.2 Windows client does not install successfully in a 64-bit environment when the following situations exist on the workstation:
A GroupWise 8.0.1 or earlier GroupWise version is installed, then the 64-bit version of Office 2010 is installed, then GroupWise is updated to 8.0.2.
The 32-bit version of Office 2007 or 2010 is installed, then a GroupWise 8.0.1 or earlier GroupWise version is installed, then Office is updated to the 64-bit version of Office 2010, then GroupWise is updated to 8.0.2.
To enable GroupWise 8.0.2 to function correctly in these situations, use either of the following workarounds:
Run the GroupWise Windows client Setup program a second time, selecting .
or
Uninstall the GroupWise Windows client, then reinstall it.
If you do not repair or reinstall the client in these situations, you encounter the following errors:
Either there is no default mail client or the current mail client cannot fulfill the messages request.
The ‘MAPI Session Handle’ of the Novell GroupWise ‘Objet Request Broker’ could not be accessed. The address book cannot run.
GroupWise is not properly installed. The Address Book component could not be initialized.
To successfully distribute the GroupWise Windows client using ZENworks, some .msi files must be distributed in advance of the GroupWise software. These .msi files are part of the standard client installation, but they are not successfully installed when you perform a ZENworks silent installation using the /qb or /qn switches. (The /qn switch is used by default.)
For ZENworks 10, the following .msi files must be distributed before the GroupWise client software:
wse3.msi
msxml.msi
To successfully distribute the GroupWise Windows client software using ZENworks 10:
Create a ZENworks bundle for each .msi file:
In the ZENworks Control Center, click , then click .
Select , then click .
Select , then click .
Specify a name for the bundle such as WSE3, MSXML, or GroupWise Windows Client, then click .
Select the .msi file for the bundle that you are creating:
In the field, browse to and select the .msi file in your GroupWise software distribution directory:
\grpwise\software\client\win32
(Conditional) If you are creating a bundle for the wse3.msi or msxml.msi file, do not select .
or
(Conditional) If you are creating a bundle for the groupwise.msi file, select .
This includes all the contents of the win32 subdirectory, which is the GroupWise client software.
Click .
Click .
Finish creating the bundle as usual.
Repeat Step 1 until you have created all the bundles that you need.
After you create all three bundles, set the executable security level for each bundle:
Click a bundle name, then click the tab.
Click the tab, then click .
Click .
Set to , then click .
Repeat Step 2 for each bundle that you created.
Assign each bundle to the appropriate GroupWise users.
Create a launch schedule for each bundle so that the bundles launch in the following order:
wse3.msi
msxml.msi
groupwise.msi
For ZENworks 7, the following files must be distributed before the GroupWise client software:
dotnetfx.exe (if .NET 2.0 or later is not already installed on workstations)
wse3.msi
msxml.msi
To successfully distribute the GroupWise Windows client software using ZENworks 7:
Copy the GroupWise client installation directory from the GroupWise software distribution directory:
\grpwise\software\client\win32
to a convenient location on the ZENworks server or other network location.
Create a NAL Application object for each file that you need to distribute:
In ConsoleOne, right-click the container where you want to create the NAL Application object, then click .
(Conditional) When you are creating the object for dotnetfx.exe, select , then click .
or
(Conditional) When you are creating the object for a .msi file, select .
Click .
Specify the path to the file, then click .
Specify the name for the NAL Application object, such as DOTNETFX, WSE3, MSXML, or GroupWise Windows Client, then click .
Finish creating each NAL Application object as usual.
Repeat Step 2 for each file that you need to distribute.
(Conditional) When you are installing dotnetfx.exe:
Right-click the DOTNETFX NAL Application object that you created in Step 2.b, then click .
Click the tab, then click .
In the field, specify:
/q:a /c:"install /q"
Click .
Select for each NAL Application object.
Assign each NAL Application object to the appropriate GroupWise users.
Create a schedule for each NAL Application object so that the applications are installed in the following order:
dotnetfx.exe
wse3.msi
msxml.msi
groupwise.msi
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, such as:
\\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.
Perform the installation from a Windows XP machine.
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.
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 |
|
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 |
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.
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.
If the GroupWise Windows client is originally installed by the Windows Administrator user, the Administrator user must also perform software updates. When the client is installed by the Administrator, the GroupWise client software cannot be updated by a regular user or a Windows Power User.
Section 7.3.3, GroupWise Installation to a Xen Guest on SUSE Linux Enterprise Server 10
Section 7.3.4, Problem Copying the Monitor Files to the Software Distribution Directory
Section 7.3.5, Upgrading from an Incomplete Software Distribution Directory
Section 7.3.6, eDirectory Reinstallation on Open Enterprise Server
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 Tomcat is included with the GroupWise 8.0.2 software. The GroupWise 8.0.2 Installation program detects SLES 11, installs Tomcat, and configures it for use with GroupWise.
Starting with GroupWise 8.0.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.
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:
Make sure that SSH is enabled on the Xen guest.
Open an X terminal window on the SLES 10 Xen host, using the following command:
ssh -X root@guest_ip_address
Run the GroupWise Installation program from the Xen host.
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.
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 in the GroupWise Installation program to create a complete software distribution directory.
If you need to uninstall and reinstall eDirectory on Open Enterprise Server for Linux, your GroupWise system is affected, because the GroupWise objects in eDirectory are lost when eDirectory is uninstalled. Therefore, you need to re-create the GroupWise objects in the new eDirectory tree.
(Conditional) If ConsoleOne has been uninstalled and reinstalled along with eDirectory, reinstall the GroupWise snap-ins to ConsoleOne, as described in Installing ConsoleOne and the GroupWise Snap-Ins on Linux
in System
in the GroupWise 8 Administration Guide.
In ConsoleOne, extend the eDirectory schema for GroupWise objects, as described in Check eDirectory Schema
in System
in the GroupWise 8 Administration Guide.
Graft the GroupWise objects into the new eDirectory tree:
Access the primary GroupWise domain directory, as described in Select Domain
in System
in the GroupWise 8 Administration Guide.
Graft your GroupWise domains and post offices into the new eDirectory tree, as described in Graft GroupWise Objects
in System
in the GroupWise 8 Administration Guide.
For additional assistance, see TID 7004121: How to Graft GroupWise Objects.
Graft in GroupWise users and other GroupWise objects that belong to post offices.
Start all the GroupWise agents.
When filling in a field in ConsoleOne, you must specify the server name. You cannot use an IP address or DNS hostname.
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.
For more information, see TID 7002222: “How is the GroupWise 8 Driver Configured for Identity Manager?” in the Novell Support Knowledgebase.
The GroupWise 8 product is comprised of many 32-bit services and applications. These pieces all run successfully on 64-bit hardware and operating systems.
The Identity Manager (IDM) driver for GroupWise is also a 32-bit application. It requires either a 32-bit version of the Identity Manager engine, or a 32-bit version of the IDM Remote Loader. For most installations, we recommend deploying the 64-bit version of the Identity Manager engine on a 64-bit system, and then deploy the 32-bit IDM Remote Loader along with the IDM driver for GroupWise on a 32-bit system as described here.
Set up a 32-bit server for use by the IDM driver for GroupWise.
Install and configure the IDM Remote Loader on the 32-bit server.
Follow the setup instructions for your version of Identity Manager:
Install and configure the IDM driver for GroupWise on the same 32-bit server with the IDM R3mote Loader.
Follow the setup instructions for your version of the IDM driver for GroupWise:
In this configuration, the IDM Remote Loader on the 32-bit server communicates successfully with the Identity Manager engine and with the GroupWise agents that are both running on 64-bit servers.
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 setting and the 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.
In ConsoleOne, browse to and select the Domain object.
Right-click the GroupWiseWebAccess object, then click .
Click .
Deselect .
Deselect the check boxes in the column.
Click .
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 for compatible products.
Versions of Novell eDirectory earlier than 8.8.4 are not supported on Windows Server 2008.
If you create users in a Domain Services for Windows (DSfW) domain, then add those users to a new GroupWise system as you install GroupWise, the users are not successfully added to the post offices specified during GroupWise system setup. You must manually assign the users to post offices after setup of the new GroupWise system is complete.
If you create a DSfW static group and then convert it to a GroupWise distribution list by assigning it to a post office, e-mail messages addressed to the group are not delivered to GroupWise users. To correct the problem, synchronize the post office that owns the distribution list. In ConsoleOne, select the post office, then click .
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:
GroupWise System/[Dom]Provo2: GroupWise System/[Dom]Provo2:
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.
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.
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.
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.
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
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 option under > > 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.
Whenever the POA runs an audit report, it causes the MTA for the domain to restart. In a domain with a large number of post offices, these MTA restarts might become noticeable. This is working as designed, although improved functionality has been requested.
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.
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.
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.
By default, the maximum number of open files on a Linux server is 1024. This default might not be sufficient for a busy POA. Therefore, the POA initializes the maximum number of open files to 200000.
The default number of open files is acceptable for the other GroupWise agents.
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.
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 in YaST ().
The GroupWise Windows client does not recognize RSS feeds that begin with:
feed://
Use the following format instead:
http://
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.
Starting in GroupWise 8.0.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, team members are listed by default. 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.
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.
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 . If GroupWise is listed twice, remove the obsolete instance.
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:
Remove yourself from the Power Users group.
Log out of Windows.
Log back in to Windows.
Uninstall the GroupWise Windows client.
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.
Users of the JAWS screen reader should install the 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.
The Mac/Linux 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.
The required location for a Mac/Linux client user’s archive is on his or her local workstation. Creating an archive on a network drive is not currently supported.
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.
If you want to start the Mac client whenever you click an e-mail address on a Web page, you must configure your Mac with GroupWise as your default mail client.
Open the Mail application from the Applications folder.
Click Mail > Preferences.
In the Default mail reader field, change Mail (5.0) to GroupWise.
Depending on the Linux version on your workstation, you might need to install the following packages to resolve dependencies for the GroupWise Linux client:
Open Motif 2.2 or later
The GIMP Toolkit (GTK) 2 or later
libstdc++33 or later
Typically, these packages are part of your base Linux operating system.
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.
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.
If you run the Linux client in Caching mode as root, 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.
When prompted to rebuild your database, there is no progress indicator displayed during the rebuild process.
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.
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.
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.
The WebAccess client and WebPublisher cannot access documents in libraries where there are spaces in the library name.
On Windows, WebAccess requires ISAPI support. ISAPI support is no longer installed by default when you install Windows Server 2008 and Internet Information Services (IIS). Ideally, you should select ISAPI support during the installation of IIS. However, if you are installing WebAccess on Windows Server 2008 and ISAPI support is not yet installed, you can add it after the fact.
In Windows Server Manager, expand , then right-click .
In the section, click .
Select , select and , then click .
(Conditional) If you installed the GroupWise WebAccess Application before you installed ISAPI support, reinstall the GroupWise WebAccess Application.
The WebAccess Installation program restarts Tomcat and IIS to put the ISAPI changes into effect.
Do not install WebAccess and Novell iManager on the same Windows 2000/2003 server. Because WebAccess installs and configures its own Tomcat and Jakarta connector, it must be installed on a server where Tomcat is not already in use by another program. If they are installed on the same server, either WebAccess or iManager does not work.
When you specify the location of your SSL certificate file in a NetWare cluster, do not include the virtual server name. Use the following format:
cluster_volume:\path_to_certificate
If you include the virtual server name, you receive the following error message:
8209 Path not found
On NetWare, the Viewer Agent requires at least 1 GB of memory for running about 5 worker threads. By default, 5 threads are started. The maximum number of threads has been lowered to 8.
On NetWare, must be set to in order for the Viewer Agent worker processes to recover successfully when a document fails HTML conversion.
On NetWare, should be set greater than 1.
On NetWare, when a document fails HTML conversion and its worker process dies, NetWare creates a small file named core*.dmp in the server’s root directory. You should periodically delete these files.
During installation, the Linux WebAccess Installation program requires access to eDirectory by way of LDAP authentication. The LDAP Group object includes an option named , which is enabled by default. With this option enabled, you must provide the LDAP server’s trusted root certificate, which must be exported from the LDAP server, in order for LDAP authentication to take place (typically on port 636) during installation of WebAccess.
Unless you already have SSL set up, an easier alternative is to disable in ConsoleOne, which allows LDAP authentication to take place using clear text (typically on port 389), during installation of WebAccess. After disabling the option, restart eDirectory, install WebAccess, then re-enable and restart eDirectory again.
If you update an existing WebAccess installation to GroupWise 8, you must use both the and options in the GroupWise Installation program in order for the GroupWise 8 version of the WebAccess Application to be installed and configured correctly. If you do not run the option, you continue to run the old WebAccess Application, not the GroupWise 8 version.
If you install Linux WebAccess in an eDirectory context where the WebAccess objects already exist, a message informs you that you can “use the existing objects.” In actuality, the objects are deleted and re-created, so if you have customized the properties of the existing objects, you must customize the objects again after you install WebAccess on Linux.
On Linux, if you run the Viewer Agent as a user that is not running the X Window system, WebAccess client users cannot view embedded vector-based graphics in attachments. To enable users to view embedded vector-based graphics, make sure that the user that starts WebAccess (and hence, the Viewer Agent) is running the X Window System and has a DISPLAY environment variable set so that the Viewer Agent can write to the local display. One way to accomplish this is to use the sux command to become root before you start the WebAccess Agent.
On Linux, the third-party viewer software used by the Viewer Agent has a dependency on libXm.so.1, which might not be included with your Linux package. To resolve this, create a symbolic link in the agents lib directory to the version of the libXm modules that is available on your Linux server. For example:
ln -s /usr/X11R6/lib/libXm.so.3.0.1 /opt/novell/groupwise/
agents/lib/libXm.so.1
In GroupWise 6 and its Support Packs, there was a problem with the address format used for sending to distribution lists and resources if you set Internet Addressing to one of the following formats (which are not appropriate for distribution lists and resources):
first_name.last_name@Internet_domain
last_name.first_name@Internet_domain
Messages to distribution lists and resources were initially undeliverable and were sent to the Internet Agent. The Internet Agent then successfully resolved the addresses and sent the messages back into the GroupWise system. Users did not notice the problem, but some administrators noticed unnecessary traffic through the Internet Agent.
In GroupWise 6.5, the address format problem for sending to distribution lists and resources was corrected. However, users who originally used GroupWise 6 have the erroneous address format for distribution lists and resources in their Frequent Contacts address books. If you are updating from GroupWise 6 to GroupWise 8 and unnecessary traffic through the Internet Agent is a continuing problem, have users delete distribution lists and resources from their Frequent Contacts address books so that the correct address format is used for name completion in the future.
None.
During installation, the Linux Internet Agent Installation program requires access to eDirectory by way of LDAP authentication. The LDAP Group object includes an option named , which is enabled by default. With this option enabled, you must provide the LDAP server’s trusted root certificate, which must be exported from the LDAP server, in order for LDAP authentication to take place (typically on port 636) during installation of the Internet Agent.
Unless you already have SSL set up, an easier alternative is to disable , which allows LDAP authentication to take place using clear text (typically on port 389), during installation of the Internet Agent. After disabling the option, restart eDirectory, install the Internet Agent, then re-enable and restart eDirectory again.
If you try to start the Linux Internet Agent 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 Internet Agent with the --show switch. If you start the Internet Agent without the --show switch, you can use the Internet Agent Web console to monitor the Internet Agent from your Web browser.
The Calendar Publishing Host Installation program now prompts for the name of the Calendar Publishing Host. If you are updating an existing Calendar Publishing Host installation, the Calendar Publishing Host name must match the name provided in ConsoleOne under . If the names do not match, you receive an error.
If calendar items include attachments, the attachments are not published to the Web, but the calendar items themselves are still successfully published.
None.
None.
The location of the Monitor Application configuration file (gwmonitor.cfg) has changed in GroupWise 8.
|
Platform |
Old Location |
New Location |
|---|---|---|
|
NetWare: |
sys:\novell\gwmonitor |
sys:\novell\groupwise\gwmonitor |
|
Linux: |
/opt/novell/groupwise/gwmonitor |
/var/opt/novell/groupwise/monitor |
|
Windows: |
c:\novell\gwmonitor |
c:\novell\groupwise\gwmonitor |
If you have manually modified settings in your existing gwmonitor.cfg file in the old location, you must make the same manual changes to the new gwmonitor.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.
Monitor settings are stored in the monitor.xml file in the Monitor installation directory. Agent groups are also stored in this file. If you reinstall the Monitor software, the monitor.xml file is backed up as monitor.001. To restore previous Monitor settings and agent groups, remove the newly installed monitor.xml file and rename monitor.001 to monitor.xml.
If you want to enable SSL by using the Monitor Agent /httpssl and /httpcertfile switches, the certificate file must be in PEM format. This differs from the other GroupWise agents, which take a .b64 public certificate file and a .key private key file. The PEM format combines the certificate and key in a single file.
None.
Monitor and WebAccess share a substantial amount of functionality. The following WebAccess issues also pertain to Monitor:
Starting with GroupWise 8, some language codes have changed from their previous values to ISO-standard values.
|
Language |
Old Code |
New Code |
|---|---|---|
|
Danish |
DK |
DA |
|
English |
US |
EN |
|
Finnish |
SU |
FI |
|
Hungarian |
MA |
HU |
|
Japanese |
JP |
JA |
|
Korean |
KR |
KO |
|
Portuguese |
BR |
PT |
After GroupWise 7 Support Pack 1, the GroupWise client started using UTF-8 instead of ISO for MIME encoding. This causes occasional problems in some languages where GroupWise 6.5 clients are being run against GroupWise 7 or 8 post offices. To help with the transition, a Support option has been added to GroupWise Check (GWCheck) to convert user databases back to the ISO encoding for your language.
Start GWCheck as described in GroupWise Check in Databases in the GroupWise 8 Administration Guide on the GroupWise 8 Documentation Web site.
Under , select .
In the field, browse to and select the post office directory.
Under , select .
If you want to perform the conversion on all user and resource databases in the post office, specify ALL in the field.
In the drop-down list, select .
In the field on the tab, type setmimeencoding=number, where number is one of the following character set numbers:
|
Character Set Number |
Language |
|---|---|
|
1 |
Windows default |
|
2 |
ISO default |
|
7 |
Arabic (Windows 1256) |
|
9 |
Baltic (Windows 1257) |
|
12 |
Central European (Windows 1250) |
|
13 |
Chinese Simplified (GB2312) |
|
15 |
Chinese Traditional (Big5) |
|
18 |
Cyrillic (K018-R) |
|
27 |
Hebrew (Windows 1255) |
|
29 |
Japanese (ISO2022-JP) |
|
30 |
Japanese (Shift-JIS) |
|
32 |
Korean (EUC-KR) |
|
33 |
Thai (Windows 874) |
|
35 |
Turkish (Windows 1254) |
|
3 |
UTF-8 |
Click to perform the conversion of user and resource databases from UTF-8 to the selected character set.
Do not use double-byte characters in directory names and filenames.
Do not use double-byte characters in user passwords. The Change GroupWise Password dialog box in ConsoleOne currently allows entry of double-byte characters. However, the GroupWise client login does not allow entry of double-byte characters in passwords, so a user who was assigned a password with double-byte characters in ConsoleOne cannot type the double-byte characters when attempting to log in to GroupWise.
On Windows, Mozilla-based browsers such as Firefox and Netscape do not save extended character filenames correctly, even though the filename displays correctly in the Save As dialog box. This is a browser problem, not a GroupWise problem. There is no workaround.
In Safari on Macintosh, extended character filenames are not interpreted correctly. As a workaround, use Firefox instead of Safari if you receive attachments with extended character filenames. This is a browser problem, not a GroupWise problem.
On Windows, Mozilla-based browsers such as Firefox and Netscape do not handle extended character filenames correctly for published calendars. This is a browser problem, not a GroupWise problem. There is no workaround.
In Safari on Macintosh, extended character filenames are not interpreted correctly. As a workaround, use Firefox instead of Safari to display published calendars. This is a browser problem, not a GroupWise problem.
In the Windows client, you can select Turkish as your interface language, but the online help still displays in English. In the Mac/Linux client, Turkish is not available. Turkish will be fully supported in a future release.
For non-English languages on Internet Explorer 7, some features of the agent Web consoles, such as viewing events in a log file, might not display correctly. Update to the latest version of Internet Explorer.
Hebrew has been dropped from the list of supported languages in GroupWise 8.0.1.
On a Windows server running the Spanish version of Windows, the GWCSRGEN utility does not start successfully. Use the English version of GWCSRGEN instead. GWCSRGEN runs successfully on other language versions of Windows.
If you run the Linux client on SUSE Linux Enterprise Desktop (SLED) 11, Chinese, Japanese, and Korean characters display incorrectly. You must meet the Linux client system requirements and install SLED 11 Support Pack 1 in order for double-byte characters to display correctly.
If you run the Linux GroupWise agents with an agent console interface in languages other than English, the logging information might not display correctly. The problem occurs if your language encoding is set to UTF-8.
To determine your current language encoding, use the following command in a terminal window:
locale
You can change your language encoding in YaST:
Start YaST, click , then double-click .
Select the language you are running the agents in, then click .
Deselect , then click .
Stop and then restart the agents to put the new setting into effect.
When you use a Russian keyboard, the Linux environment variables that provide language and locale information are usually set to ru_RU. Typically, this setting implies the Russian character set ISO-8859-5. However, on some distributions of Linux, the ISO-8859-5 character set must be set explicitly in order for your Russian keyboard to work with the GroupWise Mac/Linux client. Use the following command to specify the character set along with the language and locale information:
export LANG=ru_RU.ISO-8859-5
In most cases, setting the LANG environment variable also sets all LC_* environment variables and resolves all Russian keyboard problems. If you set the LANG environment variable and your Russian keyboard still does not work, use the following command to view the current settings for the LANG and LC_* environment variables:
locale
If any of the LC_* environment variables have not inherited the ISO-8859-5 specification, export them individually.
Keyboard mnemonics for menu items work for characters a-z and A-Z, but not for other characters.
The Linux GroupWise agent user interfaces display correctly if the Linux environment is using the ISO-8859-1 character set, which is the default for the GroupWise administration languages and locales.
|
Language |
Character Set Code |
|---|---|
|
French |
fr_FR |
|
German |
de_DE |
|
Portuguese |
pt_BR |
|
Spanish |
es_ES |
If the Linux environment is using a different character set encoding, such as UTF-8 (for example, fr_FR.UTF-8), the localized agent user interfaces do not display correctly.
None.
None.
When you start the Linux POA, the Linux MTA, and the Linux Internet Agent by using the ‑‑show switch to display a GUI user interface, if the agents are running as a non-root user, clicking does not display the agent help file. Help is displayed in a browser window and the agents currently launch the browser as root. Giving the user access to the browser window as root would be a security risk. This is working as designed.
If you display help from an agent Web console on a server where Novell Access Manager is installed, and if Access Manager is configured to use the option, the image at the top of the help topic does not display.
For a list of the bugs that have been fixed in GroupWise 8.0.2 HP4, see the GroupWise 8.0.2 HP4 Bug Fix List.
For a list of the bugs that have been fixed in GroupWise 8.0.2, see the GroupWise 8.0.2 Bug Fix List.
If you have access to Novell Bugzilla, you can look up the bug numbers for more information about each bug.
All GroupWise 8 documentation is available at the GroupWise 8 Documentation Web site:
Full GroupWise product Readme
Quick Start
Installation Guide
Administration Guide
Multi-System Administration Guide
Interoperability Guide
Troubleshooting Guides
GroupWise Client User Guides
GroupWise Client FAQ
NOTE:As GroupWise 8 Support Packs are released, Support Pack Readmes are placed on the GroupWise 8 Documentation Web site.
In addition to the GroupWise product documentation, the following resources provide additional information about GroupWise 8:
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2010-2012 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.