GroupWise Mobility Service 18 Readme

1.0 What’s New

1.1 GroupWise Mobility Service 18

  • ActiveSync 16: Mobility 18 supports ActiveSync 16 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.

  • 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: If you are using SLES 11, you can follow the steps found in Upgrading from SLES 11 to SLES 12 in the GroupWise Mobility Service 18 Installation Guide to move from SLES 11 to SLES 12.

  • 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 Licensing in the GroupWise 18 Administration Guide.

1.2 GroupWise Mobility Service 18.1

  • Draft Folders: Draft folders now sync both to an 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 > Config > GroupWise > Proxy Calendars. For more information, see Synchronizing Proxy Calendars in the GroupWise Mobility Service 18 Administration Guide.

  • Performance enhancements for login: Mobility caches POA information after the first sync to GroupWise so subsequent logins are faster.

2.0 Known Issues in Mobility 18

2.1 The GroupWise client previous to 18.1 doesn’t display draft attachments from iOS devices properly

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.

2.2 Running the Profile Creation Tool for Outlook on Windows 10 fails

The Profile Creation Tool for Outlook fails on Windows 10. Follow the steps in Creating the GroupWise Account Manually in the GroupWise Mobility Service 18 Administration Guide to manually create the profile.

2.3 Error during Install: "GroupWise Maintenance was not stored. This may cause problems. Please consult the readme."

If you see the error "GroupWise Maintenance was not stored. This may cause problems. Please consult the readme." during the install, go to /opt/novell/datasync and run the update.sh script.

2.4 Calendar Attachments issues on Android

The native calendar app on Android might not display attachments on calendar items even though ActiveSync 16 is supported on Android.

2.5 iOS devices not connecting to Mobility server

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.

6.0 Documentation

For all GroupWise Mobility Service documentation, see the GroupWise Mobility Service18 Documentation website.

In addition to the GroupWise Mobility Service product documentation, the following resources provide information about the Mobility Service: