GroupWise Mobility Service 2014 R2 Readme

1.0 What’s New

  • GMSsslCheck: A new tool has been created because of the SSL changes to ensure that all POAs are correctly setup for the SSL setting you have set in GMS.

    IMPORTANT:This tool needs to be run before upgrading to GMS 2014 R2.

    For more information, see the GroupWise Mobility Service 2014 R2 Security Enhancements Quick Start

  • SSL changes: GMS 2014 R2 security has been enhanced with SSL enhancements. These include requiring all POAs to have SSL enabled or disabled and certificate verification. For more information, see the GroupWise Mobility Service 2014 R2 Security Enhancements Quick Start.

  • Outlook support: Outlook 2013 and 2016 for Windows are now supported with GroupWise Mobility Service 2014 R2. For more information about using Outlook with GMS, see GroupWise Mobility for Microsoft Outlook in the GroupWise Mobility Service 2014 R2 Administration Guide.

  • GroupWise Profile Setup Utility: This tool allows users to automatically create the GMS profile for Outlook on their Windows machine. It is found in /opt/novell/datasync/tools/GMSOutlookSetup.zip. For more information, see Using the GroupWise Profile Setup Utility in the GroupWise Mobility Service 2014 R2 Administration Guide.

  • UI changes: There have been a few UI changes in GMS 2014 R2. They are listed below:

    • POA SOAP Address:Port: These two options are now on the same line and the https:// has been removed. This setting can be found in the Mobility Admin console > Config > GroupWise.

    • Allow Connections: This used to be Block Connections and has also been enhanced to let you specify the Outlook Client and Mobile App settings. This setting is found in the Mobility Admin console > Config > Device.

    • Minimum Special Characters: This option has been added to the Device Security Policy section in the Mobility Admin console > Config > Device tab. You can specify the minimum number of special characters that need to be used in the device password.

  • New MCheck option: The SSLCheck option has been added to MCheck. It has been enhanced beyond the SSLCheck tool and also checks the Mobility Certificate Store for certificate verification. The new option is found under the System options in MCheck. For information about running MCheck, see Using MCheck in the GroupWise Mobility Service 2014 R2 Administration Guide.

  • Feedback changes: The feedback script now sends feedback information once a week instead of daily. It also will track Outlook clients connecting to GMS.

  • Free/Busy search in Outlook: Using the GroupWise CalPub server, the Outlook client can do a Free/Busy search against GroupWise. The Free/Busy URL that needs to be entered as below with the server name being replaced with your CalPub server:

    https://gwcalpub.example.com/gwcal/freebusy/%NAME%@%SERVER%

  • GroupWise LDAP Provisioning: You can provision users in Mobility using GroupWise 2014 R2 LDAP. If you provision using GroupWise LDAP, you must use GroupWise authentication in Mobility as you cannot authenticate to the GroupWise LDAP. For more information, see Configuring GroupWise LDAP Provisioning in the GroupWise Mobility Service 2014 R2 Administration Guide.

2.0 Known Issues in Version 2014 R2

2.1 GroupWise Limiting People who can Send to a Group Breaks Mobility’s Ability to Read Group Members

In GroupWise, in Groups > Select a Group > Access Control, if a user is defined in People who can send to this group or People who can modify this group, it might break Mobility’s ability to get a list of the group members. If the group is being used by Mobility for user provisioning, you may be unable to add or delete users in Mobility.

2.2 Maximum Sync Limit Setting not applying in Outlook when Changed

If a user’s Mail to keep online setting is set to the to All and the admin changes the Maximum Sync Limit for either Email or Calendar, the user will not get the change. You need to re-initialized the user to get the new admin defined setting. Outlook does not provide a way for the end user to change the number of days to sync.

2.3 Sending Email to Incorrect Addresses Using Outlook Leaves the Message in the Outbox

If you send an email to an email address that is incorrect, Outlook delivers the email to GroupWise and all valid email addresses receive the email. Outlook does not remove the message from the Outbox because it detects the bad email address. Outlook does not tell you about the bad email address.

2.4 Running the GroupWise Profile Setup Utility Multiple Times on a Windows Machine Creates a New Device in Mobility

This issue is only seen in a very specific case. You must have created an Outlook profile on your Windows machine using the GroupWise Profile Setup Utility. Using that profile, you then login to Outlook and connect to Mobility. After closing out Outlook, you run the GroupWise Profile Setup Utility with identical user information as the first profile that was created. When you open Outlook again, it uses the second profile that was created and creates a new device in Mobility for the user. The first profile is not used again and is removed from the Mobility system during nightly maintenance after 30 days.

2.5 GroupWise LDAP Provisioning Not Available During Installation

GroupWise LDAP provisioning is not currently available during the installation of Mobility. You can currently only configure GroupWise LDAP provisioning after the install. Please contact support to receive a patch if you want to configure GroupWise LDAP provisioning during the install.

2.6 Attachment Streaming Fails With Multiple Consecutive Spaces in File Name

If you have an attachment to an email that has two or more spaces next to each other in the attachment name, Mobility is unable to handle the email and the processer utilization on the server is maxed. If this occurs, you can block the user with the problem in GMS. To receive a patch for this issue, contact Micro Focus support.

2.7 Dsapp Compatibility with Mobility 2014 R2

Because of the version number change with Mobility 2014 R2, version so dsapp previous to v226 use identify GMS 2014 R2 as datasync 1.x. To prevent this problem, make sure you update dsapp to v226 or newer.

2.8 Contacts Lost when Upgrading from DS 1.x to GMS 2.x

In DS 1.x, contacts on the device side were stored in the GroupWise frequent contacts address book. In GMS 2.x and later, contacts on the device are now stores in the GroupWise personal address book. Because of this, when you upgrade from DS 1.x to GMS 2.x or higher, all device created contacts are removed from the device. To prevent this from happening, before upgrading to GMS 2.x or higher, copy all device created GroupWise frequent contacts entries to your personal address book and then delete the frequent contacts entries. Once the upgrade has been completed, the contacts sync properly.

4.0 Installation Instructions

IMPORTANT:Make sure to run the SSL Check option in MCheck after installing GMS 2014 R2.

See GroupWise Mobility Service Installation in the GroupWise Mobility Service 2014 R2 Installation Guide.

5.0 Update Instructions

IMPORTANT:Make sure to run the GMSsslCheck utility before upgrading to GMS 2014 R2.

See GroupWise Mobility Service Update in the GroupWise Mobility Service 2014 R2 Installation Guide.