Simplified Installation and Upgrade: GroupWise software files are quickly laid down by the GroupWise Installation Wizard. You then perform installation and upgrade tasks in the new web-based Installation console. You use the Installation console to create a new GroupWise system, to create domains and post offices on new GroupWise servers, and to upgrade an existing GroupWise system to GroupWise 2014.
New Web-Based Administration Tool: The GroupWise Administration console enables you to perform all required GroupWise administration tasks for which ConsoleOne was used in the past. Many new and enhanced administrative features are also available. Now you can perform GroupWise administration anywhere you have a web browser and an Internet connection.
Directory-Agnostic Administration: In addition to NetIQ eDirectory, Microsoft Active Directory can serve as the source of user information for GroupWise accounts. As an additional alternative, GroupWise users can be created without any directory association. The eDirectory schema is no longer modified with GroupWise-specific user information and objects. Standard LDAP access is used with both eDirectory and Active Directory. You can use different directories for different users in the same post office. You can use different directories for user provisioning and authentication.
Delegated Administration: When you upgrade your GroupWise system to GroupWise 2014, a GroupWise Super Admin user is created. The Super Admin user can then delegate administration responsibilities to other GroupWise users to act as administrators on the system, domain, or post office level.
GroupWise Administration Service: GroupWise administration is now based on the GroupWise Administration Service that runs on each GroupWise server, along with any GroupWise agents that have been installed there. The Admin Service provides the communication between GroupWise servers and the Admin console so that drive mappings and mounted filesystems are no longer required.
Scriptable Administration: The GroupWise Administration Service is based on the GroupWise Administration REST API, which allows you to create customized administrative actions through scripting.
For more information, see the GroupWise for Software Developers website.
Native GroupWise Certificate Authority: You no longer need to purchase commercially signed certificates in order to secure your GroupWise system with SSL connections between agents.
For more information, see Using a Self-Signed Certificate from the GroupWise Certificate Authority in the GroupWise 2014 R2 Administration Guide.
Streamlined Client Software Updates: The new Client Auto-Update feature replaces the software distribution directory for automatically updating GroupWise client software on users’ workstations. The client software is automatically installed to each post office whenever the POA is updated. The software can be automatically distributed by the POA or by a web server.
For usage instruction, seeUsing Client Auto-Update to Distribute the GroupWise Client Software in the GroupWise 2014 R2 Administration Guide.
New Administrative Command Line Utility: The GroupWise Administration Utility (GWAdminUtil) performs the few administrative tasks that cannot be performed in the Admin console, because they require direct file system access.
Such tasks include:
Database maintenance where two databases must be opened simultaneously
Agent service management
Server certificate management
Improved Online Help: The online help in the GroupWise Administration console and the agent consoles now link seamlessly into the GroupWise 2014 R2 Administration Guide, where details beyond the information in the online help is readily available.
GroupWise Client: New, clean look and feel throughout; convenient slide-out in open messages for frequently used options; integrated signature in Compose view; easier file attachment; more flexible name completion;tab for new users.
GroupWise WebAccess: New, clean look and feel throughout; mailbox auto-refresh for quick display of new items; audible notification for new items.
GroupWise WebAccess Mobile: Mailbox auto-refresh for quick display of new items; attachment upload on tablets with hard drives; additional device support (Apple iPad 3, Android 4.1x or later devices, Kindle Fire HD7).
Windows Server 2012 R2 is now supported.
The GroupWise/Exchange coexistence solution integrates GroupWise and Exchange to provide users of both email systems with unified address book lookups and free/busy calendar searching. For setup instructions, see the GroupWise/Exchange Coexistence Guide.
Windows 8.1 is now supported for the GroupWise client.
Internet Explorer 11 and Safari 6 & 7 are now supported for WebAccess.
iOS 5.x, 6.x, and 7.x (with Chrome browser) and Android 4.1 (with Chrome browser) are now supported for WebAccess Mobile templates.
For a list of the bugs that have been fixed in GroupWise 2014 SP1, see the GroupWise 2014 SP1 Bug Fix List.
Browser Support: The following browsers are now supported:
File System Support: The following file systems are now supported for Agents:
SLES 12: BtrFS, EXT3, EXT4, Reiser, and XFS.
Platform Support: The following operating systems are now supported:
Server Protocols: The following server protocols are now supported:
LDAP: Outlook 2013 client
CalDAV/CardDAV: Mac Mavericks and Yosemite
The preferred email address for users is now stored and indexed for searching.
You can now control the number of items to index and the number of indexing threads for QuickFinder. This is found in Admin Console > Select a POA >tab.
Improved the status reporting of move user progress and added the ability to re-do the last step.
You can now configure up to 3 DVAs per POA.
Distribution Lists have been renamed to Groups.
Expired Date Set for Users Not Found in MTA Sync: If a user directory object is not found during an MTA directory sync, GroupWise will set a timestamp on the user which indicates the time at which the sync failed on that user. GroupWise will then set an expiration time for that user for one week in the future. A notification will be displayed in the Admin Console. The MTA will continue to attempt to find the directory object for the user for seven days. If, at that point, the directory object is still not found, the MTA will no longer attempt to sync the user and the user will be unable to send or receive any new items. The user is expired at that point. You can view these expired users in the> > . From there, you can decide whether to , , or .
Granular Scheduling for MTA Scheduled Events: For events with time-based triggers, the (select an MTA) > .option has been added, which allows you to schedule events more frequently than was previously available. This was added to enable the MTA to be able to sync to a directory more often than once per day. This option is found in the >
GroupWise Calendar Server for CalDAV/CardDAV: The GroupWise Calendar Server allows you to use CalDAV and CardDAV to sync your GroupWise Calendar and your GroupWise Contacts book to your Mac.
For Mac user information, see the GroupWise Mac User Quick Start.
GroupWise/Exchange Coexistence Support for Exchange 2013: Microsoft Exchange 2013 is now supported for coexistence with GroupWise 2014 R2. For more information on how to use this feature, please see the GroupWise/Exchange Coexistence Guide.
HTTP Console Login Support for GroupWise Configured Administrators: In GroupWise 2014 R2, administrator configuration rights to the HTTP consoles for each GroupWise administrator are now based on the role that is assigned to the administrator. (All administrators still maintain view access to the consoles).
LDAP Server Capabilities: This provides a read-only LDAP server interface into the GroupWise System Address Book information. This allows lookups and queries via LDAP for the Outlook client. To enable the LDAP server capabilities, go to the (select an MTA) > . To use SSL, you must use a commercially signed server certificate. After the LDAP server is enabled, you must restart the gwadminservice on the MTA server to use it.>
Once enabled in the admin console, it can be added as an address book to the Outlook client. You will need the system name for the search base and for the user name context. The system name is found in the Admin Console > System > Information. It is listed at the top.
To setup the Outlook client to connect to the GroupWise System Address Book through the LDAP server, see Configuring GroupWise Address Lookup in the Microsoft Outlook Client in the GroupWise Mobility Quick Start for Microsoft Outlook Users.
New GWIA Settings: Some new settings have been added to the GWIA. One is brand new and others were previously only available in the gwia.cfg file. To locate these settings, go to the > (Select a GWIA) > , then select .
The following option is new:
Require SSL for Authentication: When enabled, this option requires an SMTP sender to negotiate a secure connection before GWIA would advertise that AUTH is supported. The default setting is disabled.
The following options are now available in the interface:
Force Inbound Authentication
Force Outbound Authentication
Disable ESMTP Extension
No Delete/No Archive Folders: If (select a Domain, PO, or User) > > > , the user can protect folders and individual items from auto-cleanup.is enabled in the >
Photos in the System Address Book: The System Address Book can now include photos. Using the following menu options, you can include a single photo, include a photo already included in eDirectory or Active Directory, or include the photo included in eDirectory or Active Directory as you import the user.
Slow Document Scan for Find: When the option (select Domain, PO, or User) > > > > , then a client will only do a search through all attachments (including those which require DVA conversion) if the POA has at least 20% of the C/S threads available.in the >
Support for Active Directory SSO: GroupWise supports Active Directory single sign-on capabilities, allowing users to bypass the GroupWise login process by virtue of logging in once with Active Directory. Both the POA server and the user workstation must be joined to the same Active Directory Domain in order for single sign-on to work.
Support for KeyShield SSO: GroupWise supports KeyShield’s single-sign-on capabilities, allowing users to bypass logins by virtue of logging in once with KeyShield.
Delayed delivery items are held on the source post office so that retract works for internet messages.
User status now propagates through a Invite or Delegate and delete back to the organizer of the appointment.
Agent web console default to password protected.
Agent web consoles now support authentication using the super admin user and users designated as admins through the Admin console.
Read-only mode has been added to the HTTP web consoles.
Rules merge text with HTML as well as plain text including adding Global signatures to the HTML if appropriate.
Agent web consoles now have a session time out of 30 minutes for users with write access to the web console. Users with read access do not have a session time out.
Web console logins, logouts, and changes are now logged to facilitate change audits.
LDAP authentication is now logged.
DVA reporting in the HTTP console and log files has been improved.
You can now be notified via email when QuickFinder fails to start because the configured DVA isn’t running. You must have a Notify User set for the Domain to receive the notification.
MTA directory synchronization can now be started through the agent web console.
GWCHK now displays the real user’s name for Prime databases. It also has an option disablerules to disable all rules on an account.
Added wild card matching in the route.cfg file.
Deferred Delivery now checks to see if a user is disabled or expired before processing their queued up message.
The POA no longer uses the DCA for document conversion. It now uses the DVA for document conversion. If no DVA is assigned to the POA or none is found on the local server, the POA creates a local DVA to perform the document conversion.
The show switch is now allowed in the grpwise script permanently. During a server reboot, the switch is ignored.
Additional Options on POA Performance Snapshots: The new functionality can be found in (add information) > . The new options allow the GroupWise Administrator to send data through email. In addition, they can schedule when the data will be sent out and can specify multiple recipients to receive the data. The report can be sent , , or . You must input the recipients’ email addresses. The options and are optional. This feature was added in order to improve the ability to troubleshoot a busy POA.> > > >
DCA Removed: The DCA has been removed from GroupWise 2014 R2. All functions previously handled by the DCA are now handled by the DVA. The DCA startup switches are still available and now affect the DVA.
DVA Time Out Changes: The Default time out has been changed to 60 seconds.
DVA Worker Process Threads: On thefor the DVA, the main master DVA process will now display the list of worker processes and the process IDs. If the log level is set to or higher, each worker process will have its own log file which displays more logging information for each document it processes. The logs are stored in the same location specified for the DVA logging ( > > > ). The logs can be viewed from the DVA HTTP console in the tab. The main DVA thread will be designated by an asterisk.
IMAP Enhancements: IMAP now properly maps the Draft, Junk, Sent, and Trash folders for IMAP clients that support RFC6154. This enhancement updates the capabilities specifically for the Mac Mail app. Also, items flagged in GroupWise now appear flagged in IMAP and vice versa.
QuickFinder Time Out Value: The QuickFinder time out can now be lowered to 20 seconds. If a document takes longer than 20 seconds to index, the conversion of the document will stop and the document will not be indexed.
Remote Internet Domain SSL Settings: In GroupWise 2014 R2, an SSL column has been added to the \domain\wpgate\gwia\gwauth.cfg file. Using this column you can disable or enable SSL for a specific internet domain. To enable or disable SSL, enter required or disabled. The text is case-insensitive. If you want to enable SSL for a domain without using the SMTP feature of the file, the SSL setting can be entered following the internet domain.
The file has also been enhanced so a leading period before the domain acts as a wild card so that all emails sent through that domain use the settings specified. Below is a table with examples of how the file can be configured:
Support for SMTP Submission Port: If SMTP is enabled for the GWIA and SSL is enabled for SMTP, the GWIA launches threads for both port 25 (the default port) and port 587(the submission port). If an SMTP client is configured to send via port 587, the GWIA requires the client to secure the connection via TLS and also requires SMTP AUTH before it accepts the message from the client. The threads for both ports are shared according to the number of inbound SMTP threads configured for the GWIA.
SSL Startup Switches: The agents support new SSL startup switches:
IMPORTANT:Unless you are required to modify the default SSL options for your environment, consider carefully before you make any changes as this can decrease the security of your GroupWise system.
MP3 files can now play in the viewer.
Text from legacy custom view templates is preserved when they are opened in GroupWise 2014 R2.
Unicode or Chinese full width digits are now supported in a phone number.
Words that have been added to the speller can now be used as suggestions by the speller.
International character are properly handled when opening mailto: links in GroupWise.
and have been separated in > > > . This allows you to enable warnings for scripts and images separately.
You can now duplicate draft items enabling you to use a drafted item as a template.
Opening views that were saved in previous versions of GroupWise converts the view to the new html view.
Notify alerts now look similar to Novell Messenger pop-ups.
You can define rules to CC and BC users. You do not have to specify a To users when using CC or BC.
Default Directory for Opened Attachments: You can change the default directory where opened attachments are stored. For more information see Changing the Default Location of Opened Attachments in the 2014 R2GroupWise Client User Guide.
Email Windows Remembers “Aero Snap” Location: In previous versions of GroupWise, cycling through email items by opening an item and using the Previous and Next arrows would not preserve the aero snap location of the item. The location is now maintained as you cycle through email.
New Options when Dragging Email and Attachments to the Desktop: When you drag an item or attachment to the desktop (or any other folder) and an item or attachment of the same name exists in that location, you will be presented with the standard Windows copy/move dialog, which will allow you to replace the item or attachment, keep both the old and new items or attachment with a number to the new version being appended, or cancel the operation.
Photos in Client: In previous versions of GroupWise, photos were shown when hovering over a name in the, , , and other similar fields in the read view. The photo options have now been added next to the sender name in the read view and next to names that appear during name completion when you are addressing an item. Also, if enabled by the Admin, you can change the picture used in the GroupWise Address Book via the client with > . If there are different photos for the same user in the GroupWise Address Book and in a Personal Address Book, the photo in the Personal Address Book will be shown.
Quick Response: Quick Response lets you share your input on an item without sending a reply email. In the lower right corner or in the read view for an item, select the response from the list of standard responses or choose. The sender of the item will see the response in the header and the item summary.
Remember Client State on Crash: The Windows client can now save the state of the client every 5 minutes in case of an unexpected termination or crash. This way, when the client is reopened, it will go back to the state it was in the last time it was saved before the crash.
Sent Items Properties Enhancements: Thetab for a sent item will now only show the information. The are now available in the item header through the summary line and a pull-down menu. In the menu, you can use the icon on the right to toggle between view (by item status) or view (by user). You can choose whether you want sent items opened in the tab or the Message Body view by going to > > > and selecting or .
Shortcut Keys: The following shortcut keys have been added to the client:
Ctrl+H: This toggles the HTML highlight option. If you select in the middle of a word, toggles the word to be highlighted.
Ctrl+K: Opens the menu to insert a hyperlink while composing an item.
Ctrl+T: Flagging Toggle (, , ).
Ctrl+Shift+W; Forward item as attachment.
Ctrl+Shift+V: Paste Special Unformatted. This removes any formatting and pastes only text that is on the clipboard.
Ctrl+Alt+Y: Accept. This was previously Ctrl+y, but has been changed to accommodate.
Ctrl+5: Toggles the signature on and off during compose.
Alt+5: Opens the signature drop down menu.
Vacation Rule Widget: A vacation rule widget icon has been added to the bottom right corner of the client, which allows you configure and quickly turn on your vacation rule. It appears as a luggage icon. The color of the icon will change depending on whether your vacation rule is on or off.
Right-clicking in the month calendar now display the same options as week and day calendars.
You can now print subscribed calendars.
The current month is now displayed at the top of the stacked small month controls.
Invite vs Delegate and Delete: In previous versions of GroupWise,allowed you to invite more people to an appointment while still keeping the appointment yourself. This functionality has changed. There are now two options: and .
For more information, see Inviting Others or Delegating and Deleting Calendar Items in the 2014 R2GroupWise Client User Guide.
Propose New Time for an Appointment: This feature allows the recipient of an appointment to perform a busy search of attendees and propose a new time. The new time is then sent back to the original sender, who can then decide whether to accept the new time.
Proxy Calendar Multi-User Check Boxes: You can now use the check boxes next to users in the multi-user calendars while in proxy mode. This allows you to select the users you want displayed in the proxy user’s multi-user calendar.
Recurrence Enhancements: The following enhancements have been made to recurrence items:
If you edit a personal recurring appointment, the appointment you modify no longer is removed from the recurrence set.
If you mark a collapsed recurring item completed or not completed, you are prompted to mark all instances completed or not completed.
If you move a collapsed recurring item out of the checklist, you are prompted to move all instances.
Remember View Mode of Multi-User Calendar: When moving between multi-user calendar and regular calendars, the last view settings for both the multi-user calendar and the regular calendar are “sticky”, meaning they are retained so you don’t have to change back to the view you were using previously.
The contact pop up is now animated in the name completion control.
Contact tool tips have been added to the sharing pages.
Added theproperty to the advanced tab of a personal contact. This allows the user to put a contact back into the name completion control if it was automatically removed because it generated undeliverable emails.
Address Book Changes: Functionality is moving from the Address Book executable to the address books listed in the folder list of the client. The changes made are:
Display of shared address books in the client folder list
Inclusion of the> tab for the book in the folder list
> tab for all personal address books in the folder list
You can now drag and drop text in the plain text message body.
HTML Font menu now shows the font name in their own font.
The From, CC, and BC widget in the compose view displays for all fields that are not made sticky.
More granular control is now available in the Options slide out when choosing whether you want to have, , or displayed for items you compose.
Editing an item now uses your original send options for that item. Duplicating an item you sent also uses your original send options. Duplicating an item sent by another user uses your default send options.
For HTML messages, rules such as reply, delegate, and forward in previous versions of GroupWise only sent merged plain text when executed. Now, they do a merge on the original HTML message.
You can now validate URLs in the message body of items. Hovering your mouse over the URL makes the link appear in the bottom header of the compose view.
Paste Special: We have added three new paste options to the right click menu. The options are dynamic and will change with what you have copied in your clipboard. The three options are as follows:
Formatted Text: This pastes whatever you have in your clipboard exactly as it was copied.
Merge Formatting: Keeps the HTML structure of what is in the clipboard, but removes fonts and headers and uses the font that is currently selected in the GroupWise compose view.
Unformatted Text: This removes any formatting from what is in the clipboard and pastes only the text. This option is also available using the keyboard shortcut Ctrl+Shift+v.
Signature Enhancements: The following enhancements have been made to signatures:
Background color and image: You can now set a background color and background image for your signature.
Disabling the signature: You can disable the signature by going to> > > and unchecking .
In line signature using Microsoft Word: If you have Microsoft Word selected as the editor for plain text or HTML in Tools > Options > Environment > Editors/Viewers, you can now insert your signature.
Plain text signatures now preserve text that is bolded, underlined, and italicized.
Shortcut keys: The shortcut keys Ctrl+5 and Alt+5 have been added. Both are used in the compose view. Ctrl+5 toggles the signature on and off. Alt+5 opens the signature drop down menu.
Single use editing of signatures: You can modify a signature in the message body while in compose view for a one time use signature.
Sticky Notes: In previous versions of GroupWise, this was calledor in the Windows client. Changing the name facilitates synchronization via GroupWise Mobility Service 2.1 and ActiveSync 14.x to notes applications on mobile devices such as Notes on iOS devices. When notes sync is enabled on the mobile device, a new folder called is created in GroupWise. created in or moved to the folder will be synced to and from mobile devices. If you are using a version of the GroupWise client previous to GroupWise 2014 R2, the folder will instead be named . In either case, the folder will be created just below the folder in the client interface.
Voting: Voting allows a user to send a topic with a list of responses to other users, who can then select a response.
You can now copy into or out of shared folder references.
Actions Column: Thecolumn is added to a folder view by clicking in the column headers, selecting , and adding the column. This can also be added through a folder’s properties page. This column adds hover icons next to the items for the most commonly used tasks, which include , , and . When selecting , possible destinations are presented in the following order:
Recently Used: If nothing is displayed from either of the destinations above, these destinations are displayed.
More: Displays the complete folder list.
Category Enhancements: Items can now show multiple category colors assigned to them by adding the Categories column to the folder view or by displaying the folder in summary view.
Protected Folders and Items: You can protect items in folders so that they are not removed when automatic cleanup or automatic archiving occurs. The option must first be enabled in the Admin console before you can protect items.
Quick Tasks/Follow-up Flag: In the GroupWise client, a quick task/follow-up flag option has been added to the left of an item icon. This allows you to click the flag icon and “flag” an item and signify that you want to follow-up on that item. This option is not available for discussion threads, proposed appointment lists, or the summary calendar. When the item is flagged, it also appears in the Tasklist folder.
QuickFinder Improvements: The QuickFinder box, which is found at the top right of all folder views, now searches the message body and any attachments of items instead of just the header fields. This gives you greater access to any item that contains the string for which you are searching. If a user name is typed the QuickFinder box, the user name will be looked up in the Address Book and QuickFinder will also search for items addressed to the email address associated with that name.
Undo and Redo: The ability to undo or redo multiple actions has been added to the client.negates any change that you made, and will make the change again if you have previously undone an action. The options are available in the Actions menu or by using the keyboard shortcuts Ctrl+z for Undo and Ctrl+y for Redo. You can undo or redo the following actions:
Show/Hide Folder List
Show/Hide Quick Viewer
Show/Hide Main Menu
Access and Proxy Record Clean up: Proxy and access records are verified again existing GroupWise users during startup idle time. If records need to be removed, you are notified that the record is being deleted. If you are using caching mode and an online connection cannot be made, the records are not verified.
AES/SHA Enhancements: The option to select Microsoft Enhances RSA and ASE Provider is now available in> > > > . If you then select , you can select form the different versions of AES for encrypting and the new SHA-256 and greater algorithms for signing. Previously, AES was not available in GroupWise and signing was hard coded to SHA-1. This new set of algorithms is more secure and, in some locales, mandated for government use.
Multi-User Calendar Rights More Consistent with Originally Granted Rights: This resolves issues where a user might use multi-user calendars to view calendars for which they have not been given specific rights. For example, User A has rights to view User B’s calendar, but User C does not. If User C has rights to view User A’s calendars, User C should not be able to view User B’s calendars by using User A’s multi-user calendar. This fix enforces that setting by disallowing unintended viewing of calendars by one user piggybacking on another’s multi-user calendars. Rights are set in> > > . The proxy access dialog has also been cleaned up to remove user names for which proxy access has no longer been granted.
Proxy Options Enhancements: When granting proxy access to your mailbox, you can now specifically restrict access to the options in> > > . Previously, these options were included when you granted access to the in general. The options are:
Security Options: This is only available ifis selected.
Thefolder can now be renamed.
WebAccessuser interface has been updated.
Appointments now use the next hour as the start time instead of being fixed at noon.
WebAccess now prefers using SSL connections to DVA when SSL is not specified in the configuration.
have been renamed to .
Auto-refresh Enhancements: Auto-refresh has been enhanced to support multiple WebAccess sessions. There have also been performance and reliability enhancements.
Controlling Items Displayed in CalPub: You can control whether appointments, notes, and tasks are displayed for users in CalPub. By default, all are displayed.
Find Interface Improved: The WebAccess basic find has an improved interface to limit your results to, , or .
For more information, seeSearching for a Word or Phrase Using Basic Find in the GroupWise 2014 R2 WebAccess User GuideGroupWise 2014 R2 WebAccess Help.
Photos in WebAccess: User photos are now displayed in multiple areas in Web Access:
Read Item view.
Name Completion tooltip
System Address Book
Simplified URLs: The URLs for webaccess have been updated for easier access:
Web Access (full): /gw/webacc
Web Access Mobile: /gw/webacc/mobile
Web Access Simple: /gw/webacc/simple
Web Access Admin: /gw/webacc/admin
General performance, security, and stability improvements to WebAccess.
Reduced shutdown time for MTA, POA, and GWIA for improved cluster migration. For example, the MTA shutdown time was improved from an average of 40 seconds to 9 seconds.
Huge improvement when downloading large attachments from a POA on Linux. For example, a 25 MB attachment download was reduced from 40 seconds to 3 seconds.
CalPub can now utilize any POA configured in the startup file. If the first POA is not running, CalPub uses the next active POA for bootstrapping.
Improved iCal import from iOS.
Improved drag and dropping GW link files.
When deleting or modifying users, a prompt is now displayed if one of the users owns shared folders allowing you decide what to do with the user.
If syncronization is enabled on a directory, you can expire users after a specified number of days if they are not found while syncing.
Kerberos single sign-on can now be enabled on Linux POAs.
Calendar Server configuration files have been moved to /etc/opt/novell/groupwise/calsvr. They were previously available in /opt/novell/groupwise/calsvr/.
The DVA maxsize switch has been removed and document conversion size is now set at either the POA or WebAccess.
Two new switches have been added to the DVA:
Abutton has been added to CalPub that allows navigation directly to the last page of the published calendars list.
Tasks can now be set with a due time.
Emails can be saved as PDF files.
You can transfer ownership of shared folders.
Scan search has been disabled when filtering in a folder. Only indexed items are returned.
When upgrading to 14.2.1, the proxy access setting forin the old client now correctly gives access to all of these options in the new client. is still disabled by default.
Recurrence now automatically sets the day of the week for weekly recurrence based on the start date.
The actions column has been added by default to the list view in all folders.
Groups can now be expanded in the Address Selector.
Appointments from subscribed calendars can now be personalized.
Nicknames can be used in Send, Forward, and Reply rule actions.
The WebAccess Vacation Rule has been enhanced to include the same options as the Vacation Rule in the Client.
Calendars can now be added by right-clicking in the calendar list.
You can transfer ownership of shared folders.
When sending performance snapshots CSV files, server information and peak data are now collected as well.
Significant improvement in large attachment download speed in online mode.
Micro Focus Filr Integration: GroupWise 14.2.2 allows you to integrate with Micro Focus Filr. You can enable Filr in the Admin console > select a Domain, PO, or user >> > . You will need to enter the URL of your Filr installation. With Filr enabled, you can force all attachments to be placed in Filr or set a size limit for the attachments and anything over that size is placed in Filr.
In the client, when creating an email, you can add a Filr reference as an attachment or upload an attachment to Filr when you send the email. You can search Filr when using Find. You can save received attachments to Filr using the File > Save menu.
De-Mail Integration: You can enable De-Mail in the Admin console > select a Domain, PO, or user >> > . Users will then see De-Mail options in the client when sending an email to a De-Mail address.
Vacation Rule enhancements: Vacation rules have been updated so that you can have a separate message body for replying to external users and you can limit your replies to external Address Book members.
For a list of bugs fixed in GroupWise 2014 R2 SP3, see the GroupWise 2014 R2 SP3 Bug Fix List.
Installation issues for individual GroupWise components are located under the heading for each component.
Platform-specific installation issues are listed in separate sections below.
When you upgrade your GroupWise system to GroupWise 2014, you must use the
Upgrading the Primary Domain Server in the .
If you do not use the .dc files are not successfully updated.option, the
If you use theoption 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.
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.
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.
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.
Some versions of Internet Explorer do not successfully authorize access to the GroupWise Installation console.
To resolve the problem, add the GroupWise server to the list of trusted sites:
In Internet Explorer, click.
Click, then click .
Add the hostname of the GroupWise hostname to the list of trusted sites.
Click, then click .
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.
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.
Group: In the GroupWise Admin console, GroupWise “distribution lists” are now called “groups.” The groups that are available in the GroupWise client are called “personal groups.” The groups that are available in NetIQ eDirectory or Microsoft Active Directory are called “LDAP groups.” The term “distribution list” is now used only to mean the entire recipient list of a message, regardless of whether the recipients are listed individually or as part of groups.
Replicate: In the GroupWise Admin console, the term “replicate” refers to updating GroupWise databases with the latest information about an object such as a domain, post office, or user. In ConsoleOne, this action was called “synchronize.” In the GroupWise Admin console, the term “synchronize” refers to updating the GroupWise Address Book with user information from an LDAP directory.
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:
The MTA for the domain should not be configured with an exclusive bind to a any IP address or DNS hostname.
If an exclusive bind is required for the MTA, the MTA should be configured with the internal IP address of the domain server, and not the DNS hostname
If the MTA must be configured with the DNS hostname of the domain server, your network must have an internal DNS to resolve the hostname to the IP address.
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.
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 R2 Administration Guide:
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:
Browse to and select the container object where users are located, then click.
Browse to and select the user that the MTA can use to perform user synchronization, then click.
For, select and , then click .
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.
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.
The GroupWise plugin for iManager enables an eDirectory administrator to assign new eDirectory users and groups to GroupWise post offices.
Users: When you want to add an eDirectory user to GroupWise, if the user’sfield is empty, the user is not created in GroupWise. No error message is displayed.
Groups: In the Roles and Tasks view in iManager, thetab on Group objects does not always display properly. Use the View Objects view to add eDirectory groups to GroupWise.
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.
In GroupWise 2014, the Open Document Management API (ODMA) integration is no longer supported when using GroupWise Document Management.
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.
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.
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.
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.
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.
On Linux, this means that you run them without the --show switch.
On Windows, this means that you configure them as Windows services, rather than as Windows applications.
In order to monitor the agents, rely on the web-based agent consoles, rather than on the server consoles.
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.
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.
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.
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.
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.
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 GroupWise 2014 R2 Installation Guide.
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.
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.
Shared personal address books are not included in Name Completion processing when you are addressing messages. To access a shared personal address book when addressing a message, open the Address Selector in the Compose view and manually select the recipients.
This issue is for the most part mitigated because when you send a message from a personal address book, it is added to your Frequent Contacts address book. As a result, it will be available for Name Completion in the future. However, if you turn off Name Completion from the Frequent Contacts address book, you must always manually select recipients from shared personal address books.
Starting in GroupWise 2012, the GroupWise client uses the 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 previous Spell Checker dialog box that are no longer available.
When the Spell Checker dialog box opens, it immediately begins spell checking.
You can no longer check spelling in a paragraph or sentence, or by word.
You can no longer add or manage multiple personal word lists from the Spell Checker dialog box. There is only one personal word list.
The recommended location for a GroupWise 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:
The Novell Map Network Drive feature of the Novell Client is used to map a network drive from the user’s workstation to a Novell Open Enterprise (OES) Linux server where the archive is located.
The OES Linux server must use NSS volumes, and you must use NCP access with cross-protocol locks enabled in order to ensure safe client access to the archive.
The Windows Map Network Drive feature is used to map a network drive from the user’s workstation to an OES Linux server using Novell CIFS access.
Other configurations, including Samba on a SUSE Linux Enterprise Server (SLES) server, are not currently supported.
If you use ZENworks Configuration Management to distribute the GroupWise client, a problem occurs when you update to ZENworks Configuration Management 11.2, if you have enabled Collaboration Single Sign-on (CASA). The Windows registry entry that enables CASA to provide single sign-on convenience for GroupWise users must be reset.
In the Windows registry, browse to the following key:
Add the following string of type REG_SZ:
Set the value to true.
If you use Novell Vibe with GroupWise, Vibe 3 or later is required for GroupWise 2014 integration.
Do not use iFolder with your GroupWise mailbox. For more information, see
GroupWise Files Become Corrupted in an iFolder in the
Troubleshooting section in the Novell iFolder Cross-Platform User Guide.
The issues involved with trying to use iFolder with GroupWise apply to using GroupWise with other folder synchronization applications as well, such as Novell Filr and Microsoft Offline Files. Do not use any of these applications with GroupWise.
If you are a member of the Power Users group when you install the GroupWise client, you cannot immediately uninstall the GroupWise client in the Control Panel. You must follow these steps to uninstall:
Remove yourself from the Power Users group.
Log out of Windows.
Log back in to Windows.
Uninstall the GroupWise client.
If you install the GroupWise 2014 client on a workstation where Outlook 2013 is installed, you must reboot the workstation before you use Outlook. If you do not reboot the workstation, you receive the following error when you start Outlook:
Unexpected Error in gwmsp1.dll
If you install Outlook, then install the GroupWise client, and then uninstall Outlook, you must reinstall the GroupWise client in order to restore MAPI, which is uninstalled along with Outlook. To avoid this problem, uninstall Outlook before you install the GroupWise client.
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 2014 client, continue to use the GroupWise 2012 client. Section 508 accessibility issues will be addressed in a future GroupWise 2014 release.
When you log in to WebAccess (for example, on your desktop computer), Auto-Refresh keeps the mailbox content current in your desktop web browser. If you log in to a second environment (for example, on your tablet), Auto-Refresh starts refreshing the second environment, but might stop refreshing the first environment.
If you return to the first environment, you might need to manually refresh your browser to display current content. If you resume working steadily in the first environment, you might need to log out of WebAccess, and then log back in again, in order to re-establish Auto-Refresh in the first environment.
Auto-Refresh sometimes refreshes only one environment at a time. Logging in always activates Auto-Refresh for the current environment.
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.
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.
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.
In the GroupWise client, you can right-click a Calendar folder, then clickto 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.
On a Samsung Galaxy tablet, the Quickoffice HD location for attaching documents and text files might not be available, depending on the specific model of the Galaxy tablet. You can attach files in WebAccess Mobile only from locations that are available on your particular tablet.
PDF files cannot be displayed on ASUS Transformer TF101 and TF102 tablets. These tablets do not currently have a plug-in for displaying PDF files. As a result, the PDF file is downloaded to the tablet rather than being immediately displayed. To display a PDF file after it has been downloaded, use a native application such as MyLibrary or Polaris Office to view it.
ASUS tablets have browser display issues in WebAccess Mobile, including:
Pages occasionally do not load.
Pages might be very slow to load.
The browser quits. When it is relaunched, the browser does not display the pages and tabs that were originally displayed when it quit.
Typing text in the browser is very slow.
As a workaround:
Enter the following text in the address bar:
In the browser menu, click.
Repeat this procedure each time you restart the tablet.
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.
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.
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.
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.
If you upgrade an existing WebAccess installation to GroupWise 2014, you must use both theoption and the 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 option, you continue to run the old WebAccess Application and not the GroupWise 2014 version.
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.
In Windows Server Manager, expand, then right-click .
In thesection, click .
Select, select and , then click .
(Conditional) If you installed the GroupWise WebAccess Application before you installed ISAPI support, reinstall the GroupWise WebAccess Application.
The WebAccess Installation Wizard restarts Tomcat and IIS to put the ISAPI changes into effect.
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.
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 the POA 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.
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.
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.
Download the Google Chrome Frame installer from the following web site:
The Google Chrome Frame installer is named GoogleChromeframeStandaloneEnterprise.msi.
Place the .msi file under the document root folder on your web server.
Test the location by viewing the URL for the file in your web browser.
Specify the URL for the Google Chrome Frame installer in the WebAccess configuration file:
Edit the webacc.cfg file in an ASCII text editor.
Add the following line at the bottom of the file:
Replace installer_location with the URL that you tested in Step 3.
Save the file and exit the text editor.
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 or https:
webcal://calpubhost_hostname/gwcal/calendar/ a3NvcmVuc2VuQGd3Lm5vdmVsbC5jb20_Y249Q2FsZW5kYXI webcals://calpubhost_hostname/gwcal/calendar/ a3NvcmVuc2VuQGd3Lm5vdmVsbC5jb20_Y249Q2FsZW5kYXI
Outlook accepts webcals, but GMail Calendar and iCal on a Mac accept webcal rather than webcals in the URL.
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.
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.
If calendar items include attachments, the attachments are not published to the Internet, but the calendar items themselves are still successfully published.
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.
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.
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
When you install the GroupWise 2014 Monitor Agent to a location other than the default under the c:\Program Files folder structure,
If you reinstall the Monitor Agent to a location that is different from its previous location, the monitor.xml file is not handled correctly. Under typical circumstances, the Monitor Agent Installation Wizard looks one time for the monitor.xml file in the following folder:
The Monitor Agent Installation Wizard then saves the monitor.xml file in the following folder:
When the Monitor Agent starts, it always looks for the monitor.xml file in the ProgramData location.
If you reinstall the Monitor Agent in a different folder that is not in the P
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.
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.
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.
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.
Edit the Accepted Domain for the Organization Hub Transport Accepted domain.
Change it to an Internal Relay Domain.
Create a new Send Connector.
Configure it to relay by setting its SMTP Address Space to the GWIA IP address or DNS hostname.
Configure the MX record for the shared Internet domain name to point to the Exchange system, which then forwards non-local addresses to the GWIA in the GroupWise system.
Configure any outbound GWIAs to forward undeliverable messages to an Exchange Hub Server.
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.
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.
The following GroupWise send options were supported by the legacy GroupWise Exchange Gateway, but are not supported in the GroupWise/Exchange coexistence solution:
Classification (Normal, Proprietary, Confidential, Secret, Top Secret, For Your Eyes Only)
Reply Requested (When Convenient, WithDays)
If users select these send options in GroupWise, the options have no effect on messages sent to Exchange users.
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.
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.
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.
Do not use double-byte characters in the following places in your GroupWise system:
The GroupWise client login does not allow entry of double-byte characters in a password, even if such a password can be created in the LDAP directory from which GroupWise users are imported.
Calendar Publishing Host names
If you start an individual GroupWise agent in a language other than English with a command such as the following:
./gwmta --show @provo.mta
you must turn off UTF-8 in order for the agent server console to display properly.
To turn off UTF-8 for the Linux server:
In YaST, click.
Deselect, then click .
Clickto save the new setting, then reboot the Linux server.
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 services, without the user interface.
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.
On some tablets, garbage characters display in the WebAccess Mobile Login window instead of readable text. This problem tends to occur on older devices, even when they are running a supported tablet operating system.
On some tablets, when you select a file with double-byte characters in the file name, the characters display as garbage characters. This is a problem with the device.
Starting in GroupWise 8 SP1, Hebrew was dropped from the list of supported languages. Starting in GroupWise 2014, Arabic has been dropped.
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:
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.
Keyboard mnemonics for menu items work for characters a-z and A-Z, but not for other characters.
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.
Character Set Code
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.
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.
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. This is an automatic InstallShield message. The GroupWise Installation Wizard correctly handles the situation without your assistance.
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.
When you display a browse list of published calendars at the following URL, the incorrect version of Chinese might be displayed:
If you are using Internet Explorer 10 on Windows 8, Traditional Chinese displays instead of Simplified Chinese. As a workaround, use Mozilla Firefox.
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.
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. 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.
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 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.
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.
To configure Firefox to use Adobe Acrobat as it did in previous versions:
Infield, select , then click .
© Copyright 1993 - 2018 Micro Focus or one of its affiliates.
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.