GroupWise 2012 Support Pack 1

5.1.1 GroupWise Version Compatibility

If you install GroupWise on multiple platforms, or if you run multiple versions (for example, GroupWise 7 or 8 and GroupWise 2012 in the same GroupWise system), refer to GroupWise Version Compatibility in the GroupWise 2012 Installation Guide to make sure that the combinations you are using are supported.

For example, you cannot run a GroupWise 2012 client against a GroupWise 8 or earlier post office. Earlier POAs cannot support later GroupWise clients. However, you can run a GroupWise 8 or earlier client against a GroupWise 2012 POA.

Also, you should not run the GroupWise 8 or earlier snap-ins to ConsoleOne to access GroupWise 2012 databases or eDirectory objects. You can use Admin Lockout Settings under Tools > GroupWise System Operations > System Preferences to specify the required version of the ConsoleOne snap-ins for each domain as needed.

5.2.1 32-bit Runtime Libraries Required on 64-bit Linux

When you install a Linux operating system for use with GroupWise, do not deselect the 32-bit runtime libraries. GroupWise requires the 32-bit runtime libraries.

5.2.2 SLES Base System Installation Required

When you install SUSE Linux Enterprise Server (SLES) for use with GroupWise, select the Base System option. If you select the Minimal System (Appliances) option, the GroupWise Installation program prompts you to install additional packages to meet GroupWise dependencies. Although you can manually install the additional packages after installing SLES, it is simpler to install SLES so that all GroupWise dependencies are automatically met.

5.2.3 System Creation on SLES 11 in a Virtual Machine

When you run the Linux GroupWise Installation program and create a new GroupWise system in a virtual machine on SLES 11, the system creation process might crash with a Java exception. There are two workarounds:

5.2.4 GroupWise Installation to a Xen Guest on SLES 10

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:

5.2.5 eDirectory Reinstallation on Open Enterprise Server

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.

5.3.1 Windows Client Installation in a 64-bit Environment

The GroupWise 2012 Windows client does not install successfully in a 64-bit environment when the following situations exist on the workstation:

To enable the GroupWise 2012 Windows client to function correctly in these situations, use either of the following workarounds:

If you do not repair or reinstall the GroupWise Windows client in these situations, you encounter the following errors:

5.3.2 Windows Security Rights for GroupWise Client Installation

If the GroupWise Windows client is originally installed by the Windows Administrator user, the Administrator user must also perform software updates. When the client is installed by the Administrator, the GroupWise client software cannot be updated by a regular user or a Windows Power User.

5.3.3 Can’t Launch the GroupWise Client from the Client Setup Program

In GroupWise 2012 Support Pack 1, you cannot launch the GroupWise client directly from the client Setup program. You must exit the client Setup program, then launch the GroupWise client.

5.3.4 Norton Internet Security 2010 and SetupIP

Older versions of Norton Internet Security 2010 incorrectly identify GroupWise SetupIP as a virus and automatically remove it while it is trying to install the GroupWise Windows client on a workstation. Symantec indicates that this problem is resolved by running LiveUpdate to obtain the latest version of Norton Internet Security 2010. If you still encounter the problem, you must disable Norton Internet Security 2010 before SetupIP can successfully run on a workstation.

6.1.1 GWCSRGEN Functionality

In earlier versions of GroupWise, the GroupWise Generate CSR Utility (GWCSRGEN) created a certification signing request (CSR) that returned an MD5 certificate. The MD5 algorithm is now considered compromised and should not be used.

Starting in GroupWise 2012 SP1, GWCSRGEN creates a CSR that returns an SHA-1 certificate. The SHA-1 algorithm is more secure than MD5, but also has some potential weaknesses.

For the most stringent security needs, GWCSRGEN should no longer be used for generating CSRs. For suggested alternatives, see Generating a Certificate Signing Request in Security Administration in the GroupWise 2012 Administration Guide.

6.1.2 Server Names

When filling in a UNC Path field in ConsoleOne, you must specify the server name. You cannot use an IP address or DNS hostname.

6.1.3 Identity Manager Driver Version Compatibility

Do not run a DirXML or Identity Manager driver earlier than version 3.5.2 against a GroupWise 2012 system. Older drivers are not compatible. You can download the latest version of the GroupWise Identity Manager driver from Novell Downloads.

For more information, see TID 7002222: “How is the GroupWise Driver Configured for Identity Manager?” in the Novell Support Knowledgebase.

6.1.4 Identity Manager Driver in a 64-bit Environment

The GroupWise 2012 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 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 Identity Manager Remote Loader. For most installations, we recommend deploying the 64-bit version of the Identity Manager engine on a 64-bit system, and then deploying the 32-bit Identity Manager Remote Loader along with the Identity Manager driver for GroupWise on a 32-bit system as described here.

In this configuration, the Identity Manager 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.

6.1.5 Server-Based Antivirus Software

If you run server-based antivirus 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.

6.2.1 NFS Not Supported

Because of long-standing file lock issues with NFS, you cannot use an NFS mount to mount a server file system where your GroupWise system is located to a workstation where you are running ConsoleOne. In addition, you cannot use an NFS mount between Linux servers, for example when a POA needs access to a remote restore area or a remote document storage area.

Use a Samba mount if you want to use Windows ConsoleOne to access a domain located on a Linux server. For access between Linux servers, use a Samba mount or an NCP (Novell Core Protocol) mount. For instructions to set up a Samba mount or an NCP mount, see ConsoleOne Administration Tool in System in the GroupWise 2012 Administration Guide.

6.2.2 SNMP Not Supported on 64-bit Linux Operating Systems

All GroupWise agents can be monitored through an SNMP management console. However, 64-bit Linux operating systems do not include the 32-bit components required for communication with the 32-bit GroupWise engine. Therefore, SNMP monitoring of GroupWise agents is not currently available on 64-bit Linux operating systems.

6.2.3 GWTSAFS Discontinued

GroupWise 2012 does not include GWTSAFS. The supported versions of Novell Open Enterprise Server (OES) provide TSAFS, which is the preferred backup approach moving forward. For more information, see GroupWise Backup in the Storage Management Services Administration Guide for your version of OES.

6.2.4 Path Names and File Names in Lowercase

All directory names in paths to GroupWise domains and post offices should consist of lowercase letters. File names should also consist of lowercase letters. There are no length restrictions.

However, on Open Enterprise Server (OES), when you create an NSS volume, the volume name automatically appears in all uppercase in the path name. Because the use of lowercase letters in directory names is recommended for convenience, but is not required by any GroupWise program, this behavior on OES does not present any problems for GroupWise. You simply need to remember to type the uppercase letters when you specify the path name on OES.

6.2.5 Unavailable Administration Features

GroupWise 2012 administration on Linux does not include the following features that are available in GroupWise 2012 on Windows:

6.3.1 eDirectory and Windows Support

Versions of Novell eDirectory earlier than 8.8.4 are not supported on Windows Server 2008.

6.3.2 Domain Services for Windows Issue

If you create a DSfW static group and then convert it to a GroupWise distribution list by assigning it to a post office, email 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 Tools > GroupWise Utilities > Synchronize.

6.3.3 Quotas on NSS Volumes

If you use NSS volumes with quotas turned on, you must turn on quotas on all GroupWise directories. Otherwise, you receive No Disk Space errors.

7.1.1 SOAP Required for the POA

The GroupWise 2012 WebAccess Application communicates directly with the POA through SOAP. Therefore, the POA that the WebAccess Application is configured to communicate with must have SOAP enabled in order for WebAccess to function. For appropriate security, SSL should be enabled on the SOAP connection.

For setup instructions, see the following sections in the GroupWise 2012 Administration Guide:

7.1.2 Incoming Message Size Limit

When the GWIA receives an incoming message from the Internet, it creates a MIME version of the message that includes the message and any attached files. This doubles the size of the message.

You can restrict message size at the GWIA, the MTA, and the POA. The message size that you set at the GWIA determines the maximum size of messages that are allowed into your GroupWise system. However, because of the way that the GWIA creates the MIME version of incoming messages, message size limits at the MTA and POA must be two to three times the size set at the GWIA. Otherwise, some messages can successfully enter your GroupWise system at the GWIA, but they cannot be delivered because of the size limits set at the MTA or the POA.

When such a delivery failure occurs, no undeliverable message is sent, so no one is notified of the problem.

7.1.3 New View Files Overwrite Existing View Files

When you update the POA software to GroupWise 2012, 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 2012 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 2012 POA, so that your customized view files are not lost when the post office view files are updated. After you start the GroupWise 2012 POA, restore your custom view files.

Occasionally, the POA is unable to copy the updated view files from the software distribution directory to its post office. When this happens, users receive a message that their view files are out of date. To resolve this, use the Refresh Views option under Tools > GroupWise Utilities > System Maintenance in ConsoleOne to update the post office view files from the software distribution directory. After you refresh the views, you must restore your customized view files to the post office.

7.1.4 Audit Reports

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.

7.2.1 Non-root GroupWise Agents and Low Port Numbers

On Novell Open Enterprise Server and SUSE Linux Enterprise Server, services such as IMAP and IMAP SSL, which require port numbers below 1025, cannot be initiated or restarted after the GroupWise agents are running as a non-root user. To initiate or restart those services, you must manually stop the services and then restart the GroupWise agents.

7.2.2 Maximum Number of Open Files

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 typically acceptable for the other GroupWise agents.

7.2.3 Document Viewer Agent Issues

7.3.1 POA Instability

Support Pack 1 includes a fix for the problem where the Windows POA terminates unexpectedly and repeatedly when GroupWise Windows client users connect from outside of the firewall on the external client/server port. If you continue to see the problem after installing Support Pack 1, add the /udpslap switch to the POA startup file. This switch is designed specifically to alleviate this particular connection issue.

7.3.2 Document Viewer Agent Issue

If you run the Document Viewer Agent (DVA) on Windows Server 2008, and if you have not configured it to run as the Administrator user, you must use the /home switch in the gwdva.dva file to specify a directory where the DVA user can write files. You might want to create a c:\novell\groupwise\gwdva directory for this purpose.

8.1.1 SetupIP Programs Identified as Viruses

The setupip.exe and writeip.exe SetupIP programs are falsely identified as viruses by Norton Internet Security 2010. As a workaround, configure Norton Internet Security 2010 to ignore these files.

8.1.2 New Speller

The GroupWise 2012 Windows client uses a new speller engine technology named Hunspell. You should not notice any difference in the “spell-as-you-type” mode. However, there are a few features available in the old Spell Checker dialog box that are no longer available.

8.1.3 Archiving over the Network

The recommended location for a Windows client user’s archive is on his or her local workstation.

Creating an archive on a network drive is supported in the following two configurations:

Other configurations, including Samba on a SUSE Linux Enterprise Server (SLES) server, are not currently supported.

8.1.4 Initial Cache Priming

The first time you prime a new Caching mailbox, the GroupWise client might terminate at the end of the priming process. However, the Caching mailbox is successfully created. Restart the client to access the new Caching mailbox.

8.1.5 GroupWise/Vibe Compatibility

If you use Novell Vibe with GroupWise, Vibe 3 or later is required for GroupWise 2012 integration.

8.1.6 GroupWise/iFolder Compatibility

Do not use iFolder with your GroupWise mailbox. For more information, see GroupWise Files Become Corrupted in an iFolder in Troubleshooting in the Novell iFolder Cross-Platform User Guide.

The issues involved with trying to use iFolder with GroupWise apply to using GroupWise with other directory synchronization applications such as Microsoft Offline Files. Do not use any of these applications with GroupWise.

8.1.7 Windows XP and Power Users

If you are a member of the Power Users group when you install the GroupWise Windows client, you cannot immediately uninstall the GroupWise Windows client in the Control Panel. You must follow these steps to uninstall:

8.1.8 Address Books Do Not Display in GroupWise When Installing GroupWise after Outlook 2003

If you install Outlook, then install GroupWise, then uninstall Outlook, you must reinstall GroupWise in order to restore MAPI, which is uninstalled along with Outlook. To avoid this problem, uninstall Outlook before you install GroupWise.

8.1.9 Word 2010 Not Supported as the GroupWise Text Editor

The GroupWise Windows client allows you to use Microsoft Word or OpenOffice.org as the text editor for composing messages. Microsoft Word 2010 is not currently supported, although earlier versions of Word are fully supported. Microsoft Word 2010 will be supported in a future GroupWise release.

8.1.10 JAWS Script Available

Users of the JAWS screen reader can install the JAWS script available for GroupWise. Follow the instructions in the \client\jaws\gw_jaws_readme.txt file to install the JAWS script and other files on your workstation.

If you encounter Section 508 accessibility issues in the GroupWise 2012 Windows client, continue to use the GroupWise 8 Windows client. Section 508 accessibility issues will be addressed in a future GroupWise release.

8.2.1 GroupWise 8 Mac/Linux Client with GroupWise 2012

Novell is currently formulating a long-term GroupWise Mac/Linux client strategy. In the interim, the GroupWise 8 Mac/Linux client has been included in GroupWise 2012. Although no enhancements have been made to this client, it is completely compatible with a post office that has been updated to GroupWise 2012.

8.2.2 Indexing Limitation of the Mac Client in Caching Mode

The new indexable file types of PDF, OpenOffice.org, and Microsoft Office 2007 are not indexed by the Mac client in Caching mode. The module that provides this functionality is not currently available on Mac. If you change to Online mode, the POA handles this indexing, so you can find these documents in Online mode.

8.2.3 Sound Device Issue

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.

8.2.4 Linux Client Package Dependencies

Depending on the Linux version on your workstation, you might need to install the following packages to resolve dependencies for the GroupWise Linux client:

Typically, these packages are part of your base Linux operating system.

8.2.5 Problem Displaying Flash Content in Web Panels

In the GroupWise Linux client, if you display a Web page that includes Flash content, and if you have Adobe Flash Player 9 installed in your Web browser, the GroupWise Linux client might crash. Install the latest Service Pack for SUSE Linux Enterprise Desktop to resolve the problem. This Service Pack includes an updated version of Flash Player 9, where the problem no longer occurs.

8.2.6 KDE Integration with the Linux Client

By default, KDE applications like Konqueror do not launch the Linux GroupWise client when a mailto link is selected. To configure KDE applications to work with the GroupWise Linux client, see TID 7001213, Configuring KDE Applications to Launch GroupWise in the Novell Support Knowledgebase.

8.2.7 Running as root in Caching Mode

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.

8.2.8 Archiving Over the Network

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.

8.2.9 No Progress Bar Displayed When a Database Is Rebuilt

When you are prompted to rebuild your mailbox, there is no progress indicator displayed during the rebuild process.

9.1.1 WebAccess Time Zone

In GroupWise 8 WebAccess, you needed to manually set the WebAccess time zone if you wanted WebAccess to use a time zone that was different from the time zone of your post office. In GroupWise 2012, the WebAccess time zone automatically matches the time zone of your workstation. To change the WebAccess time zone, change your workstation time zone.

9.1.2 Gray Page instead of WebAccess Login Window

Occasionally, after you update the WebAccess software, the WebAccess URL displays a gray page instead of the WebAccess Login window. The problem occurs when you install multiple GroupWise Web applications in quick succession. It is possible for one Web application installation to be incomplete when the next one starts, which results in an unusable installation.

To prevent the problem, display each Web application in your Web browser before you install the next application:

http://web_server_address/gw/webacc
http://web_server_address/gwcal/admin
http://web_server_address/gwmon/gwmonitor

9.1.3 Shared Folder Notification Issue

Starting with GroupWise 2012, you can share folder trees. In the GroupWise Windows client, the shared folder notification for the folder tree arrives as a single notification. In WebAccess, you receive a shared folder notification for each folder in the shared folder tree. In a large folder tree, this could result in a large number of shared folder notifications.

Multiple shared folder notifications for folder trees shared in GroupWise 2012 occur in GroupWise 8 in both the Windows client and in WebAccess.

9.1.4 Deleted Recipients

In WebAccess, if you delete recipients from the To, CC, or BC fields of an item after the item has been manually saved or auto-saved, and then send the item before the item is saved again, the deleted recipients still display in the properties of the sent item. However, the item is not actually sent to the deleted recipients.

9.1.5 Proxy Calendar Availability

In the GroupWise Windows client, you can right-click a Calendar folder, then click New Proxy Calendar to display the Calendar of a proxy user as a sub-calendar in your own Calendar.

In WebAccess, you cannot create a Proxy Calendar, and Proxy Calendars created in the Windows client do not display in WebAccess. In WebAccess, you must proxy to the other user’s mailbox in order to view that user’s Calendar.

9.1.6 WebAccess Mobile and Tablet Issues

9.1.7 WebPublisher Availability

WebPublisher is not part of GroupWise 2012. To continue using WebPublisher, you must maintain a GroupWise 8 domain with GroupWise 8 WebAccess to support your WebPublisher needs until comparable functionality becomes available in the future.

9.1.8 WebAccess Monitoring

Starting in GroupWise 2012, the WebAccess Application communicates directly with the POA, and the WebAccess Agent is no longer needed. As a result, WebAccess cannot be monitored by GroupWise Monitor, because Monitor communicates with agents, not with Web applications.

9.1.9 Preventing Web Server Directory Browsing

If your Web server is configured to allow directory browsing, a user can access the /com directory of your Web server and browse downward from there. There is no confidential information located in any of the directories that are accessible in this manner.

However, if you want to prevent access, you can change the configuration of your Web server. For example, if you are using Apache, you can modify the httpd.conf file to remove the access that is provided by default. Locate the section that provides directory options for the htdocs directory. Either remove the Indexes option from the Options directive or place a minus (-) in front of it. Restart Apache to put the change into effect.

9.2.1 WebAccess Update Issue

If you update an existing WebAccess installation to GroupWise 2012, you must use both the Install and Configure options in the GroupWise Installation program in order for the GroupWise 2012 version of the WebAccess Application to be installed and configured correctly. If you do not run the Configure option, you continue to run the old WebAccess Application, not the GroupWise 2012 version.

9.3.1 Installation on 64-bit Windows Server 2008

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.

9.3.2 Novell iManager Compatibility on Windows

Do not install WebAccess and Novell iManager on the same Windows 2003/2008 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.

9.3.3 Internet Explorer and Google Chrome Frame

In Internet Explorer 6 and 7, WebAccess relies on Google Chrome Frame in order to provide a variety of advanced features. If a user’s workstation does not have Google Chrome Frame, the user is prompted to download and install it from the Internet. If your WebAccess users do not have access to the Internet, you can make Google Chrome Frame available locally.

10.1.1 Functionality of the --msstu Switch

The --msstu switch replaces spaces with underscores (_) in the email address of the sender, but not in the addresses of recipients. This is working as designed.

10.2.1 Internet Agent Installation Security

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 Require TLS for Simple Binds with Password, 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 Require TLS for Simple Binds with Passwords in ConsoleOne, 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 Require TLS for Simple Binds with Password and restart eDirectory again.

11.1.1 Calendar Publishing Host Name Required During Installation

The Calendar Publishing Host Installation program 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 Tools > GroupWise System Operations > Web Calendar Publishing Hosts. The name must be specified identically in both places, including spacing and capitalization. If the names do not match, the Calendar Publishing Host cannot function.

11.1.2 Attachments Not Published

If calendar items include attachments, the attachments are not published to the Web, but the calendar items themselves are still successfully published.

11.2.1 Linux Calendar Publishing Host Issues Shared with WebAccess

The Calendar Publishing Host and WebAccess share a substantial amount of functionality. The following WebAccess issue also pertains to the Calendar Publishing Host:

• Section 9.2.1, WebAccess Update Issue

12.1.1 Monitor Agent SSL Configuration

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.

12.3.1 Linux Monitor Issues Shared with WebAccess

Monitor and WebAccess share a substantial amount of functionality. The following WebAccess issue also pertains to Monitor:

• Section 9.2.1, WebAccess Update Issue

12.3.2 Restoring Monitor Settings after Reinstallation

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.

13.1.1 SMS Texting and European Phone Numbers

GroupWise cannot correctly identify a country code in a phone number when there is no delimiter between the country code and the rest of the phone number. For example, if +49 is the country code, and if you enter a contact phone number as +491234567890, an SMS text message to that contact is undeliverable. If you put a space or a dash between the country code and the phone number, such as +49 1234567890, the SMS text message is successfully delivered.

Sending SMS text messages from GroupWise is free of charge for senders. However, in some European countries, recipients must pay a small charge when they receive SMS text messages.

13.1.2 Double-Byte Character Restrictions

13.1.3 Linux Agent Server Consoles

If you start an individual GroupWise agent in a language other than English with a command like the following:

./gwmta --show @provo.mta

you must turn off UTF-8 in order for the agent server console to display properly.

If you do not want to turn off UTF-8 for the server, you can use the grpwise script to start the agents, because it turns off UTF-8 automatically when it starts the agents with the user interface provided by the --show switch. However, by default, the grpwise script starts the agents as daemons, without the user interface. To configure the grpwise script to start the agents with the user interface, see Starting the Linux Agents as Daemons in Installing GroupWise Agents in the GroupWise 2012 Installation Guide.

13.1.4 Published Calendars with Extended Characters in File Names

On Windows, Mozilla-based browsers such as Firefox do not handle extended character file names correctly for published calendars. This is a browser problem, not a GroupWise problem. There is no workaround.

In Safari on Macintosh, extended character file names 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.

13.1.5 Double-Byte Characters in WebAccess Mobile

13.1.6 Arabic Display of Help in Internet Explorer 9

In WebAccess, the online help does not display correctly in Arabic. To correct the problem, enable Compatibility View by clicking Tools > Compatibility View.

13.1.7 Hebrew Not Available

Hebrew was dropped from the list of supported languages in GroupWise 8 Support Pack 1.

13.2.1 Double-Byte Character Display in the Linux Client on SLED 11

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 Service Pack 1 in order for double-byte characters to display correctly.

13.2.2 Display Problem with Agent Server Console Interfaces

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:

13.2.3 Russian Keyboard

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.

13.2.4 Mnemonics for Arabic, Hebrew, and Double-Byte Languages

Keyboard mnemonics for menu items work for characters a-z and A-Z, but not for other characters.

13.2.5 Localized Agent User Interface Display

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.

13.3.1 Installation Error about the component.msi File

When you update WebAccess, the Calendar Publishing Host, or Monitor, if you install the multilanguage version over the English-only version or vice versa, you receive the following message:

The feature you are trying to use is on a network resource that is unavailable.

Click OK to try again, or enter an alternate path to a folder containing the installation package ‘component.msi’ in the box below.

Simply click Cancel. This is an automatic InstallShield message. The GroupWise Installation program correctly handles the situation without your assistance.

13.3.2 Unwanted Language Selection Dialog Box during AutoUpdate of the GroupWise Windows Client Software

Setting ShowDialogs=No in the setup.cfg file does not suppress the interface language dialog box that appears when you install the GroupWise Windows client from the multilanguage GroupWise software image. The interface language dialog box is displayed by InstallShield to ask what language the GroupWise Client Setup program should run in. It does not affect which client languages are installed by the Client Setup program.

13.3.3 Novell Vibe Folders in the GroupWise Windows Client

Files with certain extended and double-byte characters in their file names cannot be dragged into Novell Vibe folders. The problem is resolved in Novell Vibe 3.3.

13.3.4 GWCSRGEN Utility Does Not Start in Spanish

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.

14.2.1 Agent Help Does Not Display When the Agent Runs as a Non-root User

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 Help 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.