GroupWise 2014 Support Pack 1

5.1.1 GroupWise 2014 Upgrade Process

When you upgrade your GroupWise system to GroupWise 2014, you must use the Upgrade an Existing Domain or Post Office to GroupWise 2014 option in the GroupWise Installation console. For instructions, see Upgrading the Primary Domain Server in the GroupWise 2014 Installation Guide.

If you do not use the Upgrade option, the .dc files are not successfully updated.

5.1.2 Upgrade of a Post Office with Multiple POAs

If you use the Upgrade an Existing Domain or Post Office to GroupWise 2014 option in the GroupWise Installation console for a post office that has two POAs running on the same server, you receive the following error:

Database 'post_office_folder' already in upgrade list

In order to upgrade the post office, you must remove the second POA object from the post office. You can then use the GroupWise Admin console to add a new POA object for the upgraded post office.

5.1.3 GroupWise Version Compatibility

If you install GroupWise on multiple platforms, or if you run multiple versions (for example, GroupWise 2012 and GroupWise 2014 in the same GroupWise system), see Appendix A: GroupWise Version Compatibility in the GroupWise 2014 Installation Guide to ensure that the combinations you are using are supported.

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

Do not run ConsoleOne to access GroupWise domains and post offices that have been upgraded to GroupWise 2014. You can use the GroupWise 2014 Administration console to manage legacy domains and post offices, or you can continue to use ConsoleOne.

5.2.1 Linux Installation across a Remote Connection

If you connect to a Linux server across a remote connection such as ssh, the GroupWise Installation Wizard displays some garbage characters. To resolve the display problem, configure the remote connection to use the UTF-8 character set.

The Installation Wizard does work correctly even with the garbage characters displayed.

5.3.1 Reboot Warning after Installation on Windows

The GroupWise Installation Wizard prompts you to reboot the Windows server when the installation is finished. Rebooting is not necessary for an initial installation GroupWise.

5.3.2 GroupWise Installation Console in Internet Explorer

Some versions of Internet Explorer do not successfully authorize access to the GroupWise Installation console.

5.3.3 Windows Security Rights for GroupWise Client Installation

If the GroupWise 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.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 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 GroupWise 2014 Terminology Changes

6.1.2 GroupWise Admin Console Access from Outside the Firewall

If your network uses natting or port forwarding from a public IP address in order to reach the IP address of the GroupWise Admin Service on a GroupWise domain server, one of the following conditions must be met in order to access the GroupWise Admin console from outside the firewall:

Additionally, if you do need to configure the MTA with a public IP address, or you do not have an internal DNS, then you must open the GroupWise Admin Service port (9710) in order to provide GroupWise Admin console access from outside the firewall.

6.1.3 User Moves for Imported Users

When you import users from an LDAP directory such as NetIQ eDirectory or Microsoft Active Directory and when you move users from one context to another in the LDAP directory, the users cannot immediately log in to GroupWise. The situation automatically resolves itself the next time the MTA performs user synchronization. To provide moved users with immediate GroupWise access, you can manually synchronize the moved users.

For more information, see the following sections in the GroupWise 2014 Administration Guide:

6.1.4 LDAP User Synchronization Issue

In order for LDAP user synchronization to succeed when you are using NetIQ eDirectory, the user that the MTA uses to perform user synchronization must have Read and Compare rights to all attributes on the User objects to synchronize.

In NetIQ iManager:

6.1.5 Password Issue with GWAdminUtil

If you use special characters in a GroupWise administrator password, you cannot use the -p option of the GWAdminUtil command to specify the password, unless you surround the password with quote marks. This is typical of how operating systems interpret commands on the command line.

The preferred usage is to use the -p option without the password and let the operating system prompt you for the password.

6.1.6 Underscore Characters in DNS Hostnames

If the DNS hostname of a domain server includes an underscore character, you cannot access the GroupWise Admin console for that domain in Internet Explorer. Technically, the underscore is not a DNS character. Internet Explorer blocks cookies on hostnames that include underscores.

If your domain server as an underscore in its DNS hostname, use a browser other than Internet Explorer for accessing the GroupWise Admin console.

6.1.7 Issues in the GroupWise Plugin for iManager

The GroupWise plugin for iManager enables an eDirectory administrator to assign new eDirectory users and groups to GroupWise post offices.

6.1.8 Server-Based Antivirus Software

If you run server-based antivirus software, you must configure it so that it does not scan GroupWise folder structures such as domains and post offices. Running antivirus software on GroupWise folder structures creates file locking conflicts with the GroupWise agents, which prevents email and administration messages from being delivered.

If you need virus scanning on GroupWise data, check the GroupWise Partner Products page for compatible products.

6.2.1 GWTSAFS Discontinued

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

6.2.2 Path Names and File Names in Lowercase

All folder 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 folder 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.3.1 Quotas on NSS Volumes

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

7.1.1 Agent Startup Files

In GroupWise 2014, MTA startup files are stored in the domain folder, POA startup files are stored in the post office folder, and GWIA startup files are stored in the domain/wpgate/gwia folder. If you start the agents from the command line or in a script, you must always specify the full path to the agent startup file. For example, on Linux, you would use one of the following commands to start the POA:

./gwpoa --home /gwsystem/post_office_name
./gwpoa @/gwsystem/post_office_name/post_office_name.poa

When you upgrade existing domains and post offices, existing agent startup files are left in their original locations if the upgrade process can locate them and can verify the locations of domains and post offices. If the upgrade process cannot locate existing startup files, or if the --home switch in the existing startup files specifies an invalid location, the upgrade process creates new startup files in the new GroupWise 2014 locations.

7.1.2 Agent Server Console Limitation

The GroupWise Installation and Admin consoles cannot stop the GroupWise agents when they run with server consoles (with a user interface). In GroupWise 2014, you should run the agents as services, without a user interface.

In order to monitor the agents, rely on the web-based agent consoles, rather than on the server consoles.

7.1.3 Agent Upgrade Process

If you are currently running the GroupWise agents with a user interface, you should run them as services instead, before you start the upgrade process. The upgrade process automatically uses the same agent configuration for GroupWise 2014 as the one being used for the existing version of GroupWise.

The GroupWise Installation console cannot stop the agents when they are running with server consoles. The GroupWise Installation console must be able to stop the agents as part of the upgrade process.

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.1.5 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.6 Spamhaus on the GWIA Real-Time Blacklist

If you use Spamhaus on the GWIA real-time blacklist, you might receive a “cannot be contacted” message after you upgrade to GroupWise 2014. The GWIA now logs many conditions that were not logged in the past.

The condition that is now being reported by the GWIA is a known issue with certain combinations of Spamhaus and specific types of DNS servers. For more information, see the FAQ titled “Your DNSBL Blocks Nothing at All!” on the spamhaus.org website.

7.1.7 Functionality of the GWIA --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.

7.2.1 More Secure GroupWise High Availability Service

The GroupWise High Availability Service (gwha) has been made more secure with the introduction of the gwha.allow file. This file must contain the name of the user that the High Availability Service uses to access the GroupWise agents to obtain their status information. For more information, see Automatically Restarting the Linux GroupWise Agents with the GroupWise High Availability Service in the GroupWise 2014 Installation Guide.

7.2.2 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.3 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.

9.1.1 WebAccess Busy Search Error

If you specify an invalid user in an appointment and do a Busy Search, WebAccess displays an error that does not indicate the cause of the problem. If you receive an error doing a Busy Search in WebAccess, verify the information that you have specified in the appointment to ensure that it is valid.

9.1.2 WebAccess Time Zone

In GroupWise 8 WebAccess, you were required 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. Starting 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.3 Shared Folder Notification Issue

Starting with GroupWise 2012, you can share folder trees. In the GroupWise 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 2014 and GroupWise 2012 occur in GroupWise 8, in both the GroupWise client and in WebAccess.

9.1.4 Proxy Calendar Availability

In the GroupWise 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 GroupWise 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.5 WebAccess Mobile and Tablet Issues

9.1.6 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. Use the web-based WebAccess Application console instead.

9.1.7 Preventing Web Server Folder Browsing

If your web server is configured to allow folder browsing, a user can access the /com folder of your web server and browse downward from there. There is no confidential information located in any of the folders 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 folder options for the htdocs folder. Either remove the Indexes option from the Options directive or place a minus (-) in front of it. Restart Apache to put the change into effect.

9.1.8 WebPublisher Availability

Starting in GroupWise 2012, WebPublisher is not part of GroupWise. To continue using WebPublisher, you must maintain a GroupWise 8 domain with GroupWise 8 WebAccess to support your WebPublisher needs.

9.2.1 WebAccess Installation Issue

When you install WebAccess on Open Enterprise Server (OES) 11, you might see the following warning messages:

[warn] module rewrite_module is already loaded, skipping
[warn] worker ajp://localhost:9009/gw/webacc already used by another worker
[warn] The Alias directive in /etc/opt/novell/httpd/conf.d/gw.conf at line 4 
       will probably never match because it overlaps an earlier Alias.

These warnings are cosmetic. The installation proceeds successfully.

9.2.2 WebAccess Upgrade Issue

If you upgrade an existing WebAccess installation to GroupWise 2014, you must use both the Install option and the Configure option in the GroupWise Installation Wizard in order for the GroupWise 2014 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 and not the GroupWise 2014 version.

9.3.1 Installation on Windows Server 2008 R2 and Later

On Windows, WebAccess requires ISAPI support. ISAPI support is no longer installed by default when you install Windows Server 2008 R2 or later 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 R2 or later, and ISAPI support is not yet installed, you can add it after the fact.

9.3.2 New Message Notification Sound Not Activated in Internet Explorer 9

If you are using WebAccess in Internet Explorer 9, the notification sound for new messages is not activated. Update Internet Explorer to a later version.

9.3.3 Refresh Issue in the Work in Progress Folder

When WebAccess is installed on a Windows server, changes to an item that is saved in the Work in Progress folder might not take effect immediately. This occurs when WebAccess selects an IPv6 address as the best IP address to register the poll notifications with.

As a workaround, edit the webacc.cfg file and set the SOAP.Poll.host setting to the correct IPv4 address for the POA to use for poll notifications.

9.3.4 NetIQ iManager Compatibility on Windows

Do not install WebAccess and NetIQ iManager on the same Windows 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.5 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 URL for Published Calendars

When you publish a calendar to the Internet, you can send non-GroupWise users a URL to your published calendar. The GroupWise client provides one of the following formats for the URL, depending on whether the CalPub Host is configured for http:

webcal://calpubhost_hostname/gwcal/calendar/
                             a3NvcmVuc2VuQGd3Lm5vdmVsbC5jb20_Y249Q2FsZW5kYXI

10.1.2 Time Discrepancy in Published Calendars

In some time zones and depending on whether Daylight Saving Time is in effect, appointments that are created in WebAccess might display one hour earlier in a published calendar compared to when they are actually scheduled.

10.1.3 Calendar Publishing Host Name Required During Installation

The Calendar Publishing Host Installation Wizard prompts for the name of the Calendar Publishing Host. If you are upgrading an existing Calendar Publishing Host installation, the Calendar Publishing Host name must be specified identically as before, including spacing and capitalization. If the names do not match, the Calendar Publishing Host cannot function.

10.1.4 Attachments Not Published

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

10.2.1 Linux Calendar Publishing Host Issues Shared with WebAccess

The Calendar Publishing Host and WebAccess share a substantial amount of functionality. Section 9.2.1, WebAccess Installation Issue and Section 9.2.2, WebAccess Upgrade Issue also pertain to the Calendar Publishing Host.

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

11.2.1 Linux Monitor Issues Shared with WebAccess

Monitor and WebAccess share a substantial amount of functionality. Section 9.2.1, WebAccess Installation Issue and Section 9.2.2, WebAccess Upgrade Issue also pertain to Monitor.

11.2.2 Restoring Monitor Settings after Reinstallation

Monitor settings are stored in the monitor.xml file in the Monitor installation folder. 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.

11.3.1 Upgrade of the Monitor Agent

When you upgrade the Monitor Agent to GroupWise 2014, a problem occurs if you have installed the earlier version of the Monitor Agent in a folder that is different from the default location:

c:\Program Files\Novell\GroupWise Monitor

The Monitor Agent Installation Wizard places the new monitor.xml file in that default location. On startup, the Monitor Agent looks once in that default location, and then it saves the new monitor.xml file in the new default location

c:\ProgramData\Novell\GroupWise Monitor

When the Monitor Agent starts, it always looks for the monitor.xml file in the ProgramData location.

12.1.1 Pre-existing GroupWise/Exchange Synchronization

If you have been using the legacy GroupWise Gateway for Microsoft Exchange or another method for connecting your GroupWise and Exchange systems, you must consider how to handle information that has already been synchronized before you implement the coexistence solution. For a list of considerations, see Appendix A, Preexisting GroupWise/Exchange Synchronization in the GroupWise/Exchange Coexistence Guide.

12.2.1 Address Book Synchronization Licensing

When you enable address book synchronization in the GroupWise Admin console, you receive the following notification:

Exchange address book synchronization requires its own license. 
If you enable Exchange address book synchronization, 
your GroupWise system might be subject to additional licensing fees. 
 
We invite you to contact your Novell representative, reseller, or partner 
to learn more about this feature or for pricing and licensing information.

Ensure that you understand the licensing fees that might apply before you implement address book synchronization.

12.2.2 Names for the GroupWise External Domain and Post Office Objects

After address book synchronization, Exchange objects are organized under a GroupWise External Domain object. The original Active Directory context of each object is represented by an External Post Office object. The External Post Office object cannot have the same name as the External Domain object.

12.2.3 Shared Internet Domain Names

If you want your GroupWise system and your Exchange system to have the same Internet domain name (for example, novell.com), some specialized configuration is required. For background information, see Configure Exchange 2010 to Route Messages for a Shared Address Space.

12.2.4 Object Names with Spaces

During the synchronization process, GroupWise and Exchange object names become part of email addresses. The space character is not valid in email addresses. As a result, objects with spaces in their names do not synchronize, because their email addresses are invalid.

Exchange prevents the creation of invalid email addresses. For GroupWise, you must set up a preferred email ID for each object that would, by default, have an invalid email address. For more information, see Object Naming Consideration in the GroupWise/Exchange Coexistence Guide.

12.2.5 Checking Free/Busy information on GroupWise Users in an Exchange Distribution Group

The current version of the GroupWise Free/Busy service does not provide free/busy information for groups.

If you use the Scheduling Assistant in Outlook, you see free/busy information from GroupWise users in a group only if you expand the group.

In Outlook WebAccess, you cannot expand the group. Therefore, you cannot see free/busy information for GroupWise users in the group, and you might get an error.

12.2.6 Unsupported GroupWise Send Options

The following GroupWise send options were supported by the legacy GroupWise Exchange Gateway, but are not supported in the GroupWise/Exchange coexistence solution:

If users select these send options in GroupWise, the options have no effect on messages sent to Exchange users.

12.3.1 Passwords for the Free/Busy Service User Accounts

If the passwords for the Free/Busy service user accounts that access the GroupWise and Exchange systems change for any reason, the Free/Busy service can no longer obtain free/busy information. Ideally, set up these user accounts to be exempt from password expiration rules. If these account passwords need to change for any reason, run the Free/Busy Configurator to provide the current passwords to the Free/Busy service.

12.3.2 GroupWise User Display in the Outlook Suggested Times Box

In the Outlook Scheduling Assistant, GroupWise users’ schedules are correctly listed as you add attendees to the appointment. However, the Suggested Times box cannot determine the availability of GroupWise users.

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

Do not use double-byte characters in the following places in your GroupWise system:

13.1.3 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.4 Double-Byte Characters in WebAccess Mobile

13.1.5 Hebrew and Arabic Not Available

Starting in GroupWise 8 SP1, Hebrew was dropped from the list of supported languages. Starting in GroupWise 2014, Arabic has been dropped.

13.2.1 Display Problem with Agent Server Console Interfaces

If you run the Linux GroupWise agents with an agent server 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.2 Mnemonics for Double-Byte Languages

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

13.2.3 Localized Agent User Interface Display

The Linux GroupWise agent server consoles 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 Client Auto-Update Issue in a Silent Installation

When you set up the configuration for the Client Auto-Update feature to install multiple languages, you must allow the display of the prompt to select the languages to install in order for the languages to install successfully. You currently cannot set ShowLanguageDialog to No in the setup.cfg file.

13.3.2 Installation Error about the component.msi File

When you upgrade WebAccess, the Calendar Publishing Host, or Monitor, if you install over the English-only version of an earlier GroupWise release, 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 Wizard correctly handles the situation without your assistance.

13.3.3 Unwanted Language Selection Dialog Box during Auto-Update of the GroupWise 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 client. The interface language dialog box is displayed by InstallShield to ask what language the GroupWise Client Setup Wizard should run in. It does not affect which client languages are installed by the Client Setup Wizard.

For instructions to suppress the interface language dialog box, see Step 6 in Customizing the Setup Configuration File in the GroupWise 2014 Administration Guide.

13.3.4 Incorrect Chinese Version in the Browse List of Published Calendars

When you display a browse list of published calendars at the following URL, the incorrect version of Chinese might be displayed:

http://web_server_address/gwcal/calendar

If you are using Internet Explorer 10 on Windows 8, Traditional Chinese displays instead of Simplified Chinese. As a workaround, use Mozilla Firefox.

13.3.5 Novell Vibe Folders in the GroupWise 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.

14.1.1 Help Display in the GroupWise Admin Console and Agent Web Consoles

The behavior of the online help window in the GroupWise Admin console and the agent consoles varies depending on the capabilities of your browser.

When your browser is correctly handling the help window, you can position the help window in a convenient location, and the help windows reappears in that location as long as you do not close it.

Under other circumstances, the help window can become obscured by other windows and does not reappear the next time you click Help. Under these circumstances, you must locate the hidden browser window and manually bring it to the foreground the next time you display help.

More recent browsers on more recent operating systems behave better than older browsers on older operating systems. A workaround in a misbehaving browser is to always close the help window when you are finished viewing a help topic.

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 GWIA with a server console by using the ‑‑show switch, if the agents start 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, even if they start as a non-root user. Giving the user access to the browser window as root would be a security risk. This is working as designed.

14.3.1 PDF Display in Firefox

Starting in Firefox 19, Firefox includes a built-in PDF viewer by default. In earlier versions, Adobe Acrobat has been used with Firefox.

The built-in Firefox PDF viewer does not include the ability to expand and collapse the table of contents bookmarks in the left panel of PDF guides. In a large GroupWise guide, this expand/collapse functionality can be very useful.