March 16, 2010
The information in this Readme file pertains to Novell® GroupWise® 7 Support Pack 4. This Support Pack contains updates for all components contained in the GroupWise 7 product. It includes the NetWare®, Linux*, and Windows* GroupWise 7 software. The NetWare and Windows software is provided in one set of downloads; the Linux software, including the Cross-Platform client for Linux and Macintosh*, is provided in a separate set of downloads.
The system requirements for GroupWise 7 Support Pack 4 are the same as those currently documented for GroupWise 7. Complete GroupWise system requirements are listed in the GroupWise 7 Installation Guide.
IMPORTANT:If you are installing the GroupWise software in a cluster, refer to the GroupWise 7 Interoperability Guide for cluster-specific installation instructions before starting to install the Support Pack.
Download the NetWare/Windows GroupWise 7 SP4 compressed executable file to a temporary directory on your NetWare or Windows server:
Unzip the 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 SP4 administration files.
Select the setup.exe file, then click to run the GroupWise Installation program.
Click .
During installation of a Support Pack, the GroupWise Installation program requests access to existing GroupWise software. You can provide the path to a software distribution directory or you can use your original GroupWise 7 media.
Follow the on-screen instructions to create the GroupWise 7 SP4 software distribution directory and install the administration and agent software.
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 7 Installation Guide on the GroupWise 7 Documentation Web site.
Download the GroupWise 7 SP4 Windows Client compressed executable file to a temporary directory on your workstation:
Unzip the file into a directory at the root of your local drive.
The compressed file contains directory paths that could exceed DOS limits.
In Windows, click , then locate the directory where you extracted the SP4 client files.
Select the setup.exe file, then click to run the GroupWise client Setup program.
Follow the on-screen instructions to install the SP4 client software on your workstation.
IMPORTANT:If you are installing the GroupWise software in a cluster, refer to the GroupWise 7 Interoperability Guide for cluster-specific installation instructions before starting to install the Support Pack.
Download the GroupWise 7 SP4 Administration compressed tar file to a temporary directory on your Linux server:
In a terminal window at your Linux server, change to the temporary directory, then use the following commands 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 sux and the root password.
Use the following command to start the GroupWise Installation program:
./install
Click .
Follow the on-screen instructions to create the GroupWise 7 SP4 software distribution directory and install the administration and agent software.
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.
When you use the Linux GroupWise Installation program to install a Support Pack, use 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. (For an exception to this procedure, see Section 7.3.1, Run Configure When Updating the Linux Agents). If you encounter a problem starting the updated agent, use the option to update the configuration information.
For additional instructions, refer to the GroupWise 7 Installation Guide on the GroupWise 7 Documentation Web site.
Download the GroupWise 7 SP4 Client compressed tar file to a temporary directory on your Linux workstation:
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.
Run the GroupWise Setup program to install the GroupWise Cross-Platform client software:
./install
To start the Cross-Platform client after installation, click the GroupWise icon on your Linux desktop.
Download the GroupWise 7 SP4 Client file to a temporary directory on your Macintosh workstation:
At your Macintosh workstation, browse to the file you downloaded.
Double-click the file to install the GroupWise Macintosh client.
To start the Cross-Platform client after installation, click the GroupWise icon on your Macintosh desktop.
Installation issues for individual GroupWise components are located under the heading for each component.
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 section in the GroupWise 7 Installation Guide 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.
Also, you cannot run the GroupWise 6.5 or earlier snap-ins to ConsoleOne® to access GroupWise 7 databases or eDirectory™ objects. You can use under to specify the required version of the ConsoleOne snap-ins for each domain as needed.
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.
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.
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.
Platform-specific installation issues are listed in separate sections below. Installation issues for individual GroupWise components are located under the heading for each component.
When you create a new system and you 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.
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.
When you install GroupWise on 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 by using the following command:
ssh -X root@guest_ip_address
Run the GroupWise Installation program from the Xen host.
The text-based GroupWise Installation program does not run on all Windows versions of ssh. An open source product named PuTTY that can be downloaded from the Internet free of charge is compatible with the text-based GroupWise Installation program. There are several Web sites where PuTTY is available for download.
All GroupWise components on a server must be updated at the same time. Therefore, 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 for Linux CD to update the server, then use Configure Administration to create a complete software distribution directory.
Issues related to uppercase letters and lowercase letters in directory names for libraries have been resolved, as described in TID 3697382: Document Management Case Change for GW7 SP3 in the Novell Support Knowledgebase.
The “Migrate” 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.
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.
If ConsoleOne has been uninstalled and reinstalled along with eDirectory, reinstall the GroupWise snap-ins to each instance of ConsoleOne, as described in Installing ConsoleOne on Linux
in System
in the GroupWise 7 Administration Guide.
This process includes extending the schema of the new eDirectory tree for GroupWise objects.
or
Reinstall the GroupWise snap-ins to one instance of ConsoleOne so that the GroupWise Installation program extends the schema of the new eDirectory tree for GroupWise objects.
In ConsoleOne, 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 7 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 7 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.
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 now works differently, you must use the GroupWise 7 version of the ConsoleOne snap-ins when administering a GroupWise 7 domain to prevent the possibility of duplication.
In the original release of GroupWise 7, the text version of a global signature was generated automatically from the HTML version; you did not have any control over it. In GroupWise 7 Support Packs, you can display and edit the text version as well as the HTML version. If you created global signatures in the original version of GroupWise 7, you should verify that the text version is what you want and modify it as needed.
In ConsoleOne, click .
Select a global signature, then click .
Modify the text version as needed.
For example, if the HTML version included an image, such as your company logo, you might want to add text to take the place of the image, such as the name of your company.
Click to save your changes.
Repeat this procedure for each global signature.
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.
Global signatures are not added to empty messages. Users can create empty messages by filling in the field but not providing a message body. They can also create empty messages by forwarding messages as attachments.
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.
With the GroupWise 7.0.2 default POA settings, the POA starts 6 TCP handler threads, 20% of which are available for priming (only 1 thread). If a user tries to prime his or her Caching mailbox when that one thread is already busy, the user receives the message Server Busy. If the GroupWise administrator uses ConsoleOne to increase the number of TCP handler threads and the percentage allowed for priming, so that 2 or more threads are available, the POA goes through a polling cycle before the changes go into effect. Use the POA Web console to make sure that the changes are in effect before starting to prime a second Caching mailbox, or use the POA Web console to change settings. The settings are put into effect immediately when they are made from the POA Web console.
For new POAs configured with GroupWise 7 SP3 and SP4, the POA starts 10 handler threads, 30% of which are available for priming (3 threads) to prevent this problem.
If the field on the General page of a User object needs to be changed as a result of the information in the gateway alias, and if the User object cannot be found, a -601 SPI Exception displays and is written to the Alias Migration utility log file. This situation can arise when the association between the eDirectory object and the GroupWise object is broken for some reason. The association can be reestablished using .
When filling in a UNC Path 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 driver earlier than version 2.1.3 against a GroupWise 7 system. Version 2.2.1 or later is recommended. Older drivers are not compatible. You can download the latest version of the GroupWise driver from the Novell Identity Manager Patches Web site.
Section 3.3.3: GroupWise WebAccess Templates
in 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
In addition to these changes in the webacc.cfg file, you need to make the following change in ConsoleOne:
Browse to and select the Domain object.
Right-click the GroupWiseWebAccess object, then click .
Click .
Deselect , then click .
The setting defaults to selected (true). If you do not deselect it, the “true” setting is written to the webacc.cfg file, overwriting your manual change to that file. If this happens, the WebAccess client prompts for login multiple times.
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.
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).
When you run ConsoleOne, Novell Client file caching should be turned off to protect database integrity.
Right-click the red N in the notification area, then click .
Click , select , then select .
Click to save your change.
If you are running ConsoleOne 1.3.6f with JRE* 1.5 or if you are running ConsoleOne 1.3.6h, ConsoleOne might prompt you to log in when it tries to attach to the domain, even if you are already logged in to the server where the domain is located. Click to close the two unnecessary dialog boxes.
If you try to log in using these unnecessary prompts, you receive the following error:
NMAS: bad request syntax error - 1632 (0xffff9a0)
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, then you must turn on quotas on all GroupWise directories. Otherwise, you will receive No Disk Space errors.
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.x servers, use turbodis.nlm.
To turn off TurboFat on NetWare 6.x servers, use tdis600.nlm.
These NLM™ programs disable TurboFat at startup.
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.
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.
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.
When you create a new eDirectory tree on Linux, 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.
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
On the Links page of the MTA Web console in Firefox*, previous versions had a problem with the functionality of the and buttons. Support Pack 2 or later resolves the problem. However, some browser settings need to be cleared in order for the fix to take effect.
In Firefox:
Click .
Click , then click .
Select , then click twice.
Exit Firefox, then start Firefox again.
When you update the POA software, 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. When you use the option under > > in ConsoleOne, the post office view files are updated from the software distribution directory. If you have created custom view files with the same names as standard view files, you must create backup copies so that your customized view files are not lost in the refresh process. After you refresh the views, you must restore your customized view files to the post office.
The POA’s QuickFinder™ indexing feature does not currently index PDF files or OpenOffice files.
If you enabled SOAP in the original GroupWise 7 release, and if you changed the SOAP port number from its default of 7191, this information was not correctly replicated from the domain database to which ConsoleOne was attached to the post office database used by the POA for its configuration information. As a result, SOAP e-mail clients that relied on POA redirection (ngwnameserver) were not able to connect to the proper POA unless the correct IP address and port number were provided when starting the client.
In later GroupWise 7 Support Packs, successful POA redirection is critical to proper functioning of GroupWise Mobile Server. If you enabled SOAP in GroupWise 7 and changed the port number, you need to force the port number to replicate from the domain database to the post office database.
Install the GroupWise Administrator snap-in to ConsoleOne from the Support Pack.
In ConsoleOne, browse to and right-click the POA object.
Click .
Deselect , then click .
Select , then click .
Repeat this procedure for each POA in your GroupWise system.
By manually modifying the SOAP information, the SOAP information, including the port number, is written to the domain database and then properly replicated to the post office database so that redirection works properly for SOAP clients.
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 that 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.
Earlier versions of GroupWise and the default MTA startup file included the /tcptrunkwidth switch. This switch has not been functional for several releases and has not been included in the product documentation. If you have been using the /tcptrunkwidth switch in the MTA startup file, you should remove it. It is no longer performing the function that it did in earlier versions because the MTA now handles the trunk width tuning automatically.
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 by using the /capport switch in the POA startup file.
Normally, when you update your agent software with a Support Pack, you can use the option in the GroupWise Installation program to install the updated agent software, but you do not need to use the option because your agents are already configured. However, in GroupWise 7 Support Packs, you should use after updating the agent software in order to obtain the updated grpwise script.
Under certain circumstances, the Linux agents to do not start automatically at system startup, even though you selected during installation. Use the following commands as root to correct the problem:
chkconfig grpwise off chkconfig grpwise on
On Novell Open Enterprise Server SP2, 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.
This also applies to SUSE® Linux Enterprise Server 9 SP3, the version of SLES that is bundled with Open Enterprise Server SP2.
When the POA, the MTA, or the Internet Agent starts, it creates a file named process_id.pid in the same directory where log files for the agent are created. The process_id.pid file includes the build date of the agent that created the core file. When a GroupWise agent creates a core file, it is always named core.process_id. If you need to submit a core file to Novell Support, please include the corresponding process_id.pid file so that Novell Support can determine the specific agent build that created the core file. Old process_id.pid files can be manually deleted along with their corresponding core files.
On OES Linux SP1, the Linux POA does not currently support the SOAP protocol when running as a non-root user. However, it does support the SOAP protocol when running as root.
On OES Linux SP2, the Linux POA does support the SOAP protocol when running as a non-root user, as well as when running as root.
If you try to start the Linux 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.
A security vulnerability exists in the GroupWise Windows Client API that can allow programmatic access to non-authorized e-mail under certain conditions. The attacker must first authenticate to GroupWise and be a recipient of a shared folder from another user. The attacker could then exploit the vulnerability to gain unauthorized access to non-shared e-mail in the mailbox of the sharer.
Users who have shared folders with other users can protect their e-mail by removing shared access until remedial steps have been completed. It is not necessary to delete the contents of the shared folders, and folders can be re-shared after the administrator has locked out older client versions. To remove shared access to a folder, select the shared folder, click , select , then click .
Administrators should lock out earlier versions of the GroupWise client in ConsoleOne in post offices where shared folders are in use.
Right-click each Post Office object, then click .
Click .
Select , specify 7.0.4, then click .
Repeat this procedure for each post office in your GroupWise system where shared folders are in use.
If you are running a mixed environment of GroupWise 6.5 and 7 clients, base the lockout on the client release date rather than the client version. The recommended release date should be 9 Mar 2008 in order to ensure that your system is not vulnerable.
If you install the GroupWise Windows client with Outlook* XP already installed, an error message appears:
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 GroupWise installation directory, then restart the client.
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.
If GroupWise 7 has already been installed on a workstation by an administrator user, and if a GroupWise 7 Support Pack 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 send a message with a subject only (no message body), a global signature is not appended. This is working as designed. The presence of a global signature on a message with an empty message body would prevent the Internet Agent /flatfwd switch from functioning correctly.
GroupWise might not handle iCal attachments correctly if they are received from a non-GroupWise external system.
In particular, iCal appointments sent from non-GroupWise external systems (except Microsoft* Exchange) display as all-day appointments instead of All Day Events. Because of this, such appointments display in the Appointment pane instead of the All-Day-Events pane.
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.
In Online mode, if you have been granted rights to modify a distribution list, you can edit that distribution list in the GroupWise Address Book. In Caching mode, you cannot edit the distribution list in the GroupWise Address Book. However, if you go into the Address Selector in a new message, you can administer the distribution list from there.
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.
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.
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.
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 GroupWise client help.
Users of the JAWS* screen reader should install the new JAWS script available in GroupWise 7. 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.
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.
If you run the GroupWise Windows client in a VMware* virtual machine, you might receive an 8503 error when you try to proxy to another user’s mailbox or display a Multi-User Calendar. To eliminate this problem, you need to disable the VMware adapters on your Windows workstation.
Right-click , then click .
In the list of LAN connections, you see one or more VMware adapters.
Right-click each adapter, then click
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.
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.
The Cross-Platform client does not recognize the mailbox size limits set in ConsoleOne ().
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.
Archiving with the Cross-Platform client can only be done to your local computer hard drive.
When prompted to rebuild your database, there is no progress indicator displayed during the rebuild process.
When you click 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.
The improved rendering of HTML in the WebAccess client is not available on Mac OS X on Intel because the WebRenderer* product that has been incorporated into GroupWise is not yet available for Mac OS X on Intel.
The GroupWise 7 Connector for Microsoft Outlook cannot be installed with Outlook 2007. If you run the Outlook Connector Setup program in this environment, you receive the following message:
A version of Outlook compatible with the GroupWise Connector cannot be found. Install Outlook and run this install again.
The Outlook Connector is not supported with Outlook 2007.
Before GroupWise 7.0.3, 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 7.0.3, 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 recommended. You must update both the WebAccess Agent and the WebAccess Application to the same version in order to ensure proper functioning of the GroupWise 7.0.3 WebAccess client.
Running a new WebAccess Application with an older WebAccess Agent is no longer supported.
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 Support Knowledgebase.
Before GroupWise 7, WebAccess stored its default user interface files in the following directory on the Web server:
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 exteNd™ 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 to determine which exteNd template files you should copy to the css directory.
IMPORTANT:Do not copy the entire contents of the frames directory into the css directory; this damages 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
After the WebAccess software has been updated, users’ browsers might pull old WebAccess files from the local cache rather than using the updated files that have just been installed. The results are unpredictable, including not being able to compose an item, reply, and so on. To resolve such problems, users need to clear the browser cache and then log in to the WebAccess client again.
If the WebAccess login page appears in one or more of the frames (for example, the Folder list or the Item list) after a WebAccess user has successfully logged in, the user is probably accessing WebAccess through one or more proxy servers.
To prevent this problem:
In ConsoleOne, right-click the WebAccess Application object (GroupWiseWebAccess), then click .
Click , then deselect .
For information about this option, click on the Environment page.
Click to save the change.
If you are already logged in to the WebAccess client and you try to log in again without logging out first, you receive the “Login In Not Current” error. This is working as designed for security reasons.
Very occasionally, a pop-up blocker can prevent you from opening messages in the WebAccess client. If this happens, you can turn off the pop-up blocker or use a different one. Many pop-up blockers are available.
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).
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.
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
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).
In GroupWise 7, the GroupWise 6.5 frame template files were still included in the GroupWise 7 software image. Some users for whom the GroupWise 7 WebAccess client performance was unacceptably slow returned to using the GroupWise 6.5 frame template files in their GroupWise 7 WebAccess installations.
Because the performance issues in the WebAccess client have been resolved in GroupWise 7 Support Packs, the Installation program does the following when you install the WebAccess 7 software from a Support Pack over the original GroupWise 7 software:
Deletes the frames entry from the user interfaces list (ConsoleOne > WebAccess Application object > ).
Resets the default user interface to by using the css templates.
Moves the GroupWise 6.5 template files into a backup directory.
Installs the new css template files to the templates directory of your Web server.
If you were using the GroupWise 6.5 frame templates with your GroupWise 7 installation, please do not continue to do so.
On older versions of Internet Explorer*, users might receive this message after the WebAccess software has been updated. See TID 10081268 in the Novell Support Knowledgebase for instructions to correct the problem. Update to the latest version of Internet Explorer to avoid the problem.
On Internet Explorer, when you exit from Address Book Options in the WebAccess Address book, the Address Book page might be blank. Press F5 (Refresh) to redisplay the Address Book.
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.
The Document Viewer Agent startup file (gwdva.dva) lists a /template startup switch that is not yet implemented.
If you receive an error during installation indicating that the nvweb.dll file cannot be found, update the workstation to the latest Novell Client. The Novell Client is available for download from the Novell Downloads Web site.
If you install the WebAccess Agent as a Windows service, reboot the server, and then do a workstation login as an Administrator, the WebAccess Agent service might fail to start. If this occurs, update to the latest Novell Client. The Novell Client is available for download from the Novell Downloads Web site.
If WebAccess and Novell iManager are installed on the same Windows 2000/2003 server, iManager might stop working. Because WebAccess installs and configures its own Tomcat and Jakarta connector, it is preferable to install it on a server where Tomcat is not already in use by another program.
WebAccess might stop responding for a period of time on NetWare. It might or might not resume operation. To resolve this problem, update to the latest Winsock patch available on the Novell Downloads site.
If the GroupWise 6.5 WebAccess Application is running on the server where you plan to install GroupWise 7 WebAccess, you should manually stop WebAccess, the Web server, and Tomcat before starting the GroupWise 7 installation. Under certain circumstances, the WebAccess Installation program cannot stop them for you.
Existing users of WebAccess are accustomed to accessing the following URLs on NetWare and Windows Web servers:
|
Web Services page: |
Default index.html file of the Web server |
|
WebAccess: |
http://web_server_address/servlet/webacc
|
|
WebPublisher: |
http://web_server_address/servlet/webpub
|
The WebAccess URLs on NetWare and Windows Web servers are now the same as the URLs used on Linux:
|
GroupWise-specific Web Services page: |
http://web_server_address/gw/index.html
|
|
WebAccess: |
http://web_server_address/gw/webacc
|
|
WebPublisher: |
http://web_server_address/gw/webpub
|
To keep users’ browser bookmarks from being broken, you should redirect the old URLs to the new URLs. Follow the instructions below for your Web server.
Change to the conf subdirectory of the Apache root directory (for example, \apache2\conf.
Edit the Apache configuration file for GroupWise.
On NetWare 6, the Apache configuration file is gwapache.conf. On NetWare 6.5, the Apache configuration file is gwapache2.conf.
Add the following line:
redirect permanent /servlet/webacc http://web_server_address/
gw/webacc
If you use WebPublisher, add the following additional line:
redirect permanent /servlet/webpub http://web_server_address/
gw/webpub
Save the file, then exit the editor.
Restart Apache to put the redirections into effect.
Change to the inetpub\wwwroot subdirectory of the IIS root directory (for example, c:\inetpub\wwwroot)
Create a subdirectory named servlet.
Under the servlet subdirectory, create a subdirectory named webacc.
If you use WebPublisher, create a second subdirectory named webpub.
In IIS Manager, expand the tree in the left pane to display under .
Under , you should see the servlet subdirectory you created in Step 2.
Expand the servlet subdirectory to display the webacc subdirectory (and optionally, the webpub subdirectory) that you created in Step 3.
Right-click the webacc subdirectory, then click .
Click , select , then type /gw/webacc in the associated field.
Select , then click to save your changes.
If you use WebPublisher, repeat Step 7 through Step 9, using webpub in place of webacc.
Restart the IIS Web server to put the redirections into effect.
For redirection instructions, search the Novell Support Web site.
As part of the change from /servlet/webacc to /gw/webacc, the WebAccess Installation program installs the WebAccess Application files into the servlet container (gw) but it does not remove old servlet and htdoc files located under the ROOT container of the servlet and the Web server. Therefore, you might want to manually delete the following directories and files:
sys:\apache2\htdocs\com sys:\apache2\htdocs\index.html (if customized for GroupWise) sys:\apache2\htdocs\novell.html (if index.html was not customized) sys:\tomcat\4\webapps\ROOT\WEB-INF\classes\com sys:\tomcat\4\webapps\ROOT\WEB-INF\lib\ldapfilt.jar sys:\tomcat\4\webapps\ROOT\WEB-INF\lib\ldapjdk.jar sys:\tomcat\4\webapps\ROOT\WEB-INF\lib\njgwap.jar sys:\tomcat\4\webapps\ROOT\WEB-INF\lib\njweb.jar sys:\tomcat\4\webapps\ROOT\WEB-INF\lib\SpellServlet.jar sys:\tomcat\4\webapps\ROOT\WEB-INF\web.xml
You should definitely delete web.xml, because it might cause the WebAccess, WebPublisher, and Monitor Applications to run in both the old and new locations. Also, if you have customized the GroupWise template files, you should copy the contents of the template subdirectories under:
sys:\tomcat\4\webapps\ROOT\WEB-INF\classes\com\novell
to the corresponding templates subdirectories under:
sys:\tomcat\4\webapps\gw\WEB-INF\classes\com\novell
On NetWare 6.5 Support Pack 5, you might need to install a Winsock patch that enables users to download large attachments when they are using SSL connections to WebAccess. For a workaround, see TID 10100680 in the Novell Support Knowledgebase.
On NetWare 6.5 Support Pack 5, you might receive one of the following error messages on the server where the WebAccess Agent is running:
Server logical address space is running low ... Short term memory allocator is out of memory ... Cache memory allocator out of available memory ...
A patch for this problem is available in TID 2973639 in the Novell Support Knowledgebase.
When using Internet Explorer 5.0 to view messages through WebAccess, URLs to messages become part of the History cache and can be read by other users who have access to the same workstation. For solutions to this problem, see TID 10056452 in the Novell Support Knowledgebase.
On NetWare, the Viewer Agent requires at least 1 GB of memory for running about 5 worker processes. By default, 5 processes are started.
On NetWare, you must install the latest Support Pack for your version of NetWare in order to have the correct version of clib.nlm.
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, 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.
SUSE Linux Enterprise Server 10 uses Tomcat 5 rather than Tomcat 4. It also uses the MOD_PROXY module rather than the MOD_JK connector. Installation instructions that compensate for these differences are available in TID 3248145 in the Novell Support Knowledgebase.
GroupWise 7 on Linux includes a Novell distribution of Apache and Tomcat that you can install along with the WebAccess Application if you do not already have Apache and Tomcat running on that server. The Novell distribution relies on OpenSSL libraries. If OpenSSL is not already installed on the server where you plan to install the Novell distribution of Apache and Tomcat, you can obtain it from the OpenSSL Project. Download and build OpenSSL for your version of Linux before installing the Novell distribution of Apache and Tomcat.
The Novell distribution is installed in the following directories:
|
Apache: |
/var/opt/novell/http and /etc/opt/novell/http |
|
Tomcat: |
/var/opt/novell/tomcat4 and /etc/opt/novell/tomcat4 |
It is started by using the following customized commands:
The WebAccess Installation program lets you choose whether you want to install the Novell distribution. During installation, select if you want to install the Novell distribution. Select if you do not want to install the Novell distribution of Apache and Tomcat because you have an existing Apache and Tomcat installation that you want to use with WebAccess.
NOTE:If you are installing on Novell Open Enterprise Server (OES), the option to install with Apache and Tomcat is not available.
If you install the Novell distribution on a server where a standard distribution of Apache and Tomcat is already installed and running, you will encounter a port conflict on port 80. You can resolve the port conflict by choosing to run one distribution or the other, or you can reconfigure one distribution or the other.
To reconfigure the Novell distribution to use a different port number, edit the httpd.conf file in the /etc/opt/novell/httpd/conf directory. Locate the following line:
Listen 80
Change the port number to a something that is not already being used on the server, then save and exit the file.
On slower Linux machines, if you select , your machine might appear to hang on the “Please Wait” message. Apache and Tomcat are being installed while the “Please Wait” message is displayed, before the WebAccess Application installation begins.
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 the 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 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 installing WebAccess on Linux.
The -httpport switch has been added to the Linux WebAccess Agent to specify the port number for HTTP communication. However, it is currently not listed in the webac70a.waa file on Linux.
On Linux, if you run the Viewer Agent as a user that is not running The X Window system, then 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
The WebAccess Installation program does not configure WebPublisher for you. Some manual configuration is required. For instructions, see the GroupWise 7 Installation Guide (/docs/us/GroupWiseInstallationGuide.pdf).
If you have commented out any lines in the Linux WebAccess configuration file (webacc.cfg) or the WebPublisher configuration file (webpub.cfg), you should back up those files before installing GroupWise 7. If you use the option in the Installation program, those commented lines become uncommented and the settings return to their defaults. However, any other changes you have made to the configuration files are retained. You must comment out the lines again and edit the settings as needed, using the backup copies for reference.
In Firefox on Linux, the horizontal scroll bar in the left panel of the WebAccess client help displays in the middle of the column instead of at the bottom. It does not interfere with help functionality.
If you use the /copyonly startup switch on the Internet Agent Installation program to install GroupWise 7 Internet Agent software from a Support Pack to update original GroupWise 7 software, the database version on the GWIA object is not updated. As a result, the Support Pack 1 enhancement described in Consolidated Configuration Information
in What’s New in GroupWise 7
in the GroupWise 7 Installation Guide does not occur. Therefore, you should not use the /copyonly startup switch when updating an existing Internet Agent installation to a GroupWise 7 Support Pack.
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 7 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.
GroupWise 6.5 included the /etc/init.d/grpwise-ia script for starting and stopping the Linux Internet Agent. In GroupWise 7, the Internet Agent is started along with the POA and the MTA, using the grpwise script. Therefore, you should delete the obsolete grpwise-ia script from /etc/init.d so that it is not used inadvertently.
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 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.
If the location of the Monitor template files is inadvertently changed, then you cannot start GroupWise Monitor. To resolve the problem:
Locate the gwmonitor.cfg file.
The location of the Monitor configuration file varies by platform:
Locate the Templates.Path line and correct the path as needed.
The location of the template files varies by Web server platform:
In ConsoleOne, browse to and right-click the GroupWiseMonitor object, then click .
Click .
In the field, correct the path as needed, then click
When the correct template path has been supplied in the gwmonitor.cfg file and on the GroupWiseMonitor object in ConsoleOne, you should be able to start GroupWise Monitor.
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 use a .b64 public certificate file and a .key private key file. The PEM format combines the certificate and key in a single file.
If you’ve used Monitor on a NetWare or Windows Web server, you are accustomed to accessing the following URLs:
|
Web Services page: |
Default index.html file of Web server |
|
Monitor Web Console: |
http://web_server_address/servlet/gwmonitor
|
Starting in GroupWise 7, use the following URLs on NetWare and Windows Web servers:
|
GroupWise-specific Web Services page: |
http://web_server_address/gw/index.html
|
|
Monitor Web Console: |
http://web_server_address/gw/gwmonitor
|
To keep users’ browser bookmarks from being broken, you should redirect the old URLs to the new URLs. Follow the instructions in Section 9.2.6, New NetWare and Windows WebAccess URLs, substituting /gw/gwmonitor for /gw/webacc as needed in the instructions.
If you have installed interim releases of Monitor between Support Pack 1 and Support Pack 2, and if you are installing Monitor on a server where other GroupWise agents are also running, you might receive the following error message:
Install failed for an unknown reason (8)
To work around this error message:
In a terminal window, uninstall the Monitor Application by using the following command:
rpm -ev --justdb novell-groupwise-monitor
This command removes the Monitor Application from the RPM database so that it does not interfere with the installation of the other GroupWise components on the server.
In the GroupWise Installation program, update the other GroupWise components on the server.
Reinstall the Monitor Application individually, and do not select the option in the GroupWise Installation program.
Monitor and WebAccess share a substantial amount of functionality. The following WebAccess issues also pertain to Monitor:
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 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 7 Administration Guide.
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:
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.
Auto-detection of character encoding for the WebAccess/WebPublisher index.html page does not work for some Web browsers. If you do not see the localized languages in the drop-down menu on the Web services page (index.html), set your Web browser’s character encoding to UTF-8. In some browsers, you can click to set the Web browser’s encoding.
You might also encounter character encoding problems when reading HTML-formatted messages. In this case, set your Web browser’s character encoding for the new message window to UTF-8. You can do this by right-clicking in the new message window and then setting the encoding, or by clicking .
When Russian characters are used, they are displayed in the Spell Checker as corrupt characters.
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.
The GroupWise client Print Calendar feature always prints calendars in the language specified in Regional Options or Regional Settings in the Control Panel, even if the client is installed in a different language. For example, if French (Switzerland) or French (Swiss) is specified in the Control Panel and the client is installed in German, calendars print in French.
In the WebAccess client running on Japanese Windows XP, some characters might not display correctly.
If you run the Linux GroupWise agents with an agent console interface in languages other than English, 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 typically 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 Cross-Platform 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.
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.
To support accessibility requirements within GroupWise Help, the Help for the GroupWise Windows client uses Microsoft HTML Help. In order for Microsoft HTML Help to display on a Windows workstation, the workstation must have Internet Explorer 4.x or later installed.
If you install the WebAccess Application and the WebPublisher Application on a UNIX* Web server, as described in Completing the Installation on a UNIX Apache Web Server in Installing GroupWise WebAccess
in the GroupWise 7 Installation Guide, you now need to install the WebAccess and WebPublisher help files manually.
After installing the WebAccess Application and the WebPublisher Application:
Change to the gw/com/novell/webaccess directory of the Web server.
Unzip the __help__.zip file.
Change to the gw/com/novell/webpublisher directory of the Web server.
Unzip the __help__.zip file.
Online help is now available for WebAccess and WebPublisher users.
When you start the Linux POA, the Linux MTA, and the Linux Internet Agent 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 iChain® is installed, and if iChain 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 7 Support Pack 4, see the GroupWise 7 Support Pack 4 Bug List. You can look up the bug numbers in Bugzilla for more information about each bug
For installation instructions, known issues, and bug fixes relating to the GroupWise Connector for Microsoft Outlook, see the Support Pack 1 Readme for the GroupWise Connector for Microsoft Outlook.
For installation instructions, known issues, and bug fixes relating to GroupWise Mobile Server, Powered by Intellisync*, see the Readme for GroupWise Mobile Server.
For a list of the bugs that have been fixed in GroupWise 7 Support Pack 4, see the GroupWise 7 Support Pack 4 Bug Fix List.
All GroupWise 7 documentation is available on the GroupWise 7 Documentation Web site.
In addition to the GroupWise product documentation, the following resources provide additional information about GroupWise 7:
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
A trademark symbol (®, ™, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark
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 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.