ActiveSync 16.0: Mobility 18 supports ActiveSync 16.0 which provides enhanced calendar reliability, calendar attachments, and syncing of the drafts folder. Syncing of drafts is not fully supported in this release. Items from the Work in Progress folder in GroupWise syncs to the Drafts folder on devices, but things placed in the Drafts folder does not sync in this release to the Work in Progress folder.
NOTE:Outlook clients still use ActiveSync 14.0 when syncing to GMS.
ActiveSync 16.1 is not currently supported.
GWAVA 7 support for scanning emails: Mobility now integrates with Secure Gateway (GWAVA 7). Device emails are scanned and accepted or rejected. If accepted, the message is delivered to GroupWise. If rejected, the sender receives an email explaining that the email was rejected by the Secure Gateway scan. For more information, see Secure Message Gateway (GWAVA 7) Integration in the GroupWise Mobility Service 18 Administration Guide.
SLES 11 is no longer supported for Mobility
Draft Folders: Draft folders now sync both to and from your mobile devices. You can modify draft emails on your mobile device and have the changes sync to GroupWise. This functionality requires GroupWise 18.1 or later. If you are not using GroupWise 18.1 or later, then Drafts only sync down to the device and not back from the device to GroupWise. Drafts do not sync to Outlook as because it uses ActiveSync 14 instead of 16.
Proxy Calendars: Proxy calendars can now be synced to mobile devices. They show up on devices as a separate selectable calendar. In the user and Admin console, you can see the rights assigned to the user for the proxy calendar. Any changes in the proxy calendar are immediately synced to users’ devices. Appointments, Reminder Notes, Alarms, and Private appointments sync to mobile devices based on proxy rights. Proxy Calendars are disabled by default, but can be enabled in the Mobility Admin console > Synchronizing Proxy Calendars in the GroupWise Mobility Service 18 Administration Guide.> > . For more information, see
Performance enhancements for login: Mobility caches POA information after the first sync to GroupWise so subsequent logins are faster.
For a list of bugs fixed in GroupWise Mobility Service 18.1.1, see the GroupWise Mobility Service 18.1 Support Pack 1 Bug Fix List.
SLES 15 SP1 support: SLES 15 SP1 is now supported in Mobility 18.2. If you want to install a new Mobility server on SLE 15 SP1, follow the regular install steps in Installing GroupWise Mobility Service.
Updated Certificate Requirements for iOS devices: If you are using iOS 13 devices in your GroupWise system, your certificates also need to meet the increased security requirements released by Apple. The requirements can be found here: https://support.apple.com/en-in/HT210176.
Security Enhancement: Mobility 18.2 supports TLS 1.2 or later.
Android Enhancement: Draft emails have been enhanced on Android devices.
For a list of bugs fixed in GroupWise Mobility Service 18.2.1, see the GroupWise Mobility Service 18.2 Support Pack 1 Bug Fix List.
Advanced Authentication: GroupWise 18.3 supports Multi-Factor Authentication (MFA) through NetIQ Advanced Authentication. MFA adds an additional layer of security to your GroupWise login. For more information on MFA, see Using Multi-Factor Authentication in the GroupWise Mobility Service 18 Administration Guide.
For a list of bugs fixed in GroupWise Mobility Service 18.3.1, see the GroupWise Mobility Service 18.3 Support Pack 1 Bug Fix List.
Python 3: GMS 18.3.1 code has been upgraded to Python version 3. This requires a fresh installation.
SLES 12 Not Supported: You cannot run GMS 18.3.1 on SLES 12.
SLES 15 SP2 or later Required: You must install GMS 18.3.1 on SLES 15 SP2 or later.
LDAP User Provisioning and Authentication Not Supported: GMS 18.3.1 supports only GroupWise users and groups.
IMPORTANT:Because LDAP Provisioning is no longer supported, only GroupWise visibility rules apply when provisioning users.
rcgms Commands Not Supported: To start, stop, and restart GMS, use the gms command.
If you create a draft and add an attachment on an iOS device and then view the draft using a GroupWise client previous to 18.1, the attachment does not appear properly in the email. If you save the draft after viewing it using the same client, the attachments are deleted from the draft. These issues are fixed in the GroupWise 18.1 client.
The Profile Creation Tool for Outlook fails on Windows 10. Follow the steps in Adding a GroupWise Account to the Microsoft Outlook Client in the GroupWise Mobility Service 18 Administration Guide to manually create the profile.
Since iOS 10.x, mobile devices might have issues connecting to the Mobility server. This likely is because of changes Apple made to their App Transport Security guidelines which cause issues with self-signed certificates. For more information on this issue, including possible fixes, see TID 7018670.
Users with theirset to (i.e. Hidden users) cannot automatically connect their devices to the Mobility server.
Instead, they must manually enter the Mobility server’s IP address or DNS hostname to configure email accounts on their devices.
If you activate thesetting for a GroupWise user, delivery of new items is immediately suspended.
However, the user can still send email from a mobile device for up to 60 minutes.
To prevent this, do one of the following:
Restart GMS (See GroupWise Mobility Service 18 Administration Guide)
Block the user using the GMS Web Admin Console.
IMPORTANT:You must select EXT4 as the file system when installing your Mobility server.
GMS does not support SLES 15’s default BTRFS file system; installation is prevented.
For all GroupWise Mobility Service documentation, see the GroupWise 18 Documentation website.
In addition to the GroupWise Mobility Service product documentation, the following resources provide information about the Mobility Service:
© Copyright 2009 - 2021 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.