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 GroupWise Mobility Service 18 Administration Guide.
SLES 11 is no longer supported for Mobility
GroupWise Licensing required for Mobility: With GroupWise and Mobility 18, you are required to use a license for all features to work. For more information about the GroupWise license, see GroupWise 18 Administration Guide.
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 > 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 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.
GMS 18.3.2 includes several important bug fixes. See the GroupWise Mobility Service 18.3 Support Pack 2 Bug Fix List.
Deleted Users Still Listed: In some cases GMS continues to display user mailbox accounts that have been deleted in GroupWise.
If you see this discrepancy, restart GMS by entering the gms restart command at a terminal prompt.
GroupWise Mobility Service 18 Administration Guide now includes an overview of how Autodiscovery works as well as more configuration and setup information.
GroupWise Mobility Service 18 Administration Guide now includes additional information and instructions.
For a list of bugs fixed in GroupWise Mobility Service 18.4, See the GroupWise Mobility Service 18.4 Bug Fix List.
The following new features and enhancements are included in GroupWise Mobility Service 18.4:
GMS has added support for ActiveSync’s Resolve Recipients functionality.
When you create a new meeting and include invitees, GMS checks for appointment conflicts. As users are added, a gray icon on the left indicates availability (a check mark means that they’re available, an x indicates a conflict).
When you click, GMS reports which users have conflicts, possible alternative times when everyone can attend, and times when some of the invitees are open.
GMS Script Enhancements: Commands now include gms enable and gms disable. For more information, see GroupWise Mobility Service 18 Administration Guide.
Load Script Support: Load scripts now run on the BTRFS and XFS file systems. However, EXT4 is still the strongly recommended file system for GMS.
MCheck Enhancements: MCheck now includes management options that were formerly only available in Support’s DSAPP tool:
Remote Account Only Wipe: See see GroupWise Mobility Service 18 Administration Guide.
Security Enhancements: Mobility 18.4 supports TLS 1.3 or later and is updated to Django 3.2.
For a list of bugs fixed in GroupWise Mobility Service 18.4.1, see the GroupWise Mobility Service 18.4 Support Pack 1 Bug Fix List.
The following new features and enhancements are included in GroupWise Mobility Service 18.4.1:
Dashboard messaging for python updates: Detection of python updates with an automated message in the GMS Dashboard to prompt a GMS restart if needed due to a python update.
User and Group enhancements: Users and groups with their visibility set toin GroupWise can now be added to the GroupWise Mobility Service.
Checks & Queries: Item, is a new main menu option in MCheck that includes the checks below:
Option 1: General Health Check, in the Checks & Queries menu enables you to run an automated series of tests that display a status for each test run. More details are also generated in the logs.
Option 2: GW pending events by User (consumer events)
Option 3: Mobility pending events by User (sync events)
Database: The Database menu now includes option datasync_user account., which enables you to change the password for the
The issues listed below have been discovered in various 18.x versions of GroupWise Mobility Service and several of them have been resolved. Resolved issues are appended with the version they were fixed in and they remain in the list for those who may still be using an older version of GroupWise Mobility Service 18.
Mobility does not support GroupWise linked items. For more information on GroupWise linked items, see GroupWise 18 Client User Guide.
If you create a draft and add an attachment on an iOS device and then view the draft using a GroupWise client earlier than 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 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.
Micro Focus recommends using a Chrome or Chromium-based Edge browser for administering device settings in the Web Admin console.
If you want to use a different browser, be aware of the following caveats:
Safari: The Safari browser doesn’t work for changing device settings.
If you change any of the device setting options in> > , even though the UI shows activity when you click Save, no configuration settings are actually saved.
Firefox: The issues in> > are as follows:
IP Address field changes are not saved no matter how many times you try.
Other settings can be saved, but some of them require that you make and save the change twice. Therefore, you need to visually confirm that the change is made each time you click Save.
When GMS issues an alert, an entry for it displays in theunder > .
As documented in the help, you can clear alert entries individually by clicking the red icon to the right of the alert, or you can clear all alerts using the icon that displays on the right in the header row.
Unfortunately, in GMS 18.4.0 for all non-English languages, the red icon fails to display.
Nevertheless, both clear actions are still available by clicking where the icons should display:
To clear individual alerts: Hover over the action area until a line displays, then click the line.
To clear all alerts: Hover over the action area in the header until a hand displays, then click the hand.
This issue will be fixed in a future release.
The Autodiscovery feature for mobile device users to automatically connect to the GroupWise Mobility Service using their email address is not working on Android operating systems.
Users can still connect to the Mobility Service manually. For information, see the GroupWise Mobility Quick Start for Mobile Device Users.
NOTE:Micro Focus recommends EXT4 as the file system when installing your Mobility server. Switching to EXT4 is a manual process.
For a complete list of system requirements, see GroupWise Mobility Service 18 Installation Guide.
See GroupWise Mobility Service 18 Installation Guide.
See GroupWise Mobility Service 18 Installation Guide.
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 - 2022 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.