GroupWise Mobility Service 2.0.1 Readme

3.1 Obtaining the GroupWise Mobility Service 2.0.x ISO from the Novell Downloads Website

3.2 Installing GroupWise Mobility Service 2.0.x to Create Your New Mobility System

For complete installation instructions, see GroupWise Mobility Service Installation in the GroupWise Mobility Service 2.0 Installation Guide.

5.1 Valid Hostname Required for Installation

In order to install GroupWise Mobility Service 2.0.x, your SLES server must have a valid hostname.

You can check this using the following command:

hostname -f

If your SLES server is properly configured, this command returns the hostname of the server.

5.2 GroupWise Trusted Application Creation

Before you run the GroupWise Mobile Service Installation program, you must create a GroupWise trusted application. This enables the GroupWise Sync Agent to log in to a GroupWise Post Office Agent (POA) in order to access GroupWise mailboxes without needing personal user passwords.

When you set up the GroupWise Sync Agent as a trusted application, you must fill in only these three fields in the New Trusted App Key dialog box in the GroupWise Admin console (or in the Create Trusted Application dialog box in ConsoleOne in older GroupWise systems):

5.3 YaST Untrusted Key Warning

When you install the GroupWise Mobility Service for the first time, you receive the following warning:

Import Untrusted GnuPG Key

The following GnuPG key has been found in repository Unknown: Unknown

This is normal for an initial installation of the Mobility Service. Click Import to continue.

5.4 YaST Proposal Error

When you run the GroupWise Mobility Service Installation program in YaST, you might see the following error:

The proposal contains an error that must be resolved before continuing

This error indicates that you clicked Next without providing the configuration information for your Mobility system. Instead of clicking Next, click Change > GroupWise Mobility Service Configuration, then provide the configuration as prompted. After you provide the configuration information, click Next.

5.5 YaST Error When Configuring LDAP

When you run the GroupWise Mobility Service Installation program in YaST and select LDAP as the user source, the Installation program displays the following error if you click Browse next to the LDAP User Container field or next to the LDAP GroupWise Container field on the Mobility Service Settings page:

Connection to the LDAP server cannot be established

A possible reason for the failed connection may be that your client is
configured for TLS/SSL but the server does not support it

Retry connection without TLS/SSL?

Click Yes to successfully browse for the user and group containers.

This error occurs regardless of whether you specified a secure LDAP port on the LDAP Server Settings page. The same error also appears if you click Browse on the Add Users and Groups page.

To avoid the error, type the information, rather than browsing for the LDAP users and groups.

You can configure a secure LDAP connection after installation, as described in Enabling and Disabling SSL for the Mobility Service LDAP Connection in the GroupWise Mobility Service 2.0 Administration Guide.

5.6 Organization Container Required

In order for you to browse for user and group LDAP containers, the Mobility Service Installation program requires an Organization container. If your tree does not have an Organization container, use the following workaround:

5.7 Feature Preview: GWAVA Integration

The feature preview script (previewfeature.sh) lets you enable functionality that is currently under development but not yet officially released and supported. Such functionality is disabled by default, but you can use the feature preview script to enable it.

The new preview feature in GroupWise Mobility Service 2.0.x is GWAVA Virus Scanning, which enables integration with the GWAVA Security Message Gateway.

6.1 Compatibility with GroupWise 2014

When you are ready to upgrade from GroupWise 2012 or GroupWise 8 to GroupWise 2014, update your Mobility system to Mobility Service 2.0.1 before you upgrade your GroupWise system.

The following GroupWise changes affect how you manage your Mobility system:

For more information about GroupWise 2014, see GroupWise System Upgrade in the GroupWise 2014 Installation Guide.

6.2 Valid Hostname Required for Update

In order to update from Data Synchronizer Mobility Pack 1.2.x to GroupWise Mobility Service 2.0.x, your SLES server must have a valid hostname.

You can check this using the following command:

hostname -f

If your SLES server is properly configured, this command returns the hostname of the server.

If the hostname is not returned, you cannot update to GroupWise Mobility Service 2.0.x.

If you discovered the problem after update to GroupWise Mobility Service 2.0.x failed:

6.3 Novell Customer Center Configuration

When you run Patch CD Update to install GroupWise Mobility Service 2.0.x, you can configure the update channel through which you will receive future updates to the Mobility Service software. On the Novell Customer Center Configuration page, you must select Registration Code under Configure Now. If you do not select Registration Code, you receive an error and cannot complete the update.

After you have completed the channel configuration, you might receive a warning that the configuration is not complete. Click Skip It to continue past the warning.

6.4 Transition from ActiveSync 2.5 to 12.1

When mobile devices connect for the first time to a system that has been updated from the Data Synchronizer Mobility Pack to GroupWise Mobility Service 2.0.x, some devices automatically switch from ActiveSync 2.5 to 12.1. When this occurs, some devices prompt users to accept a new “security policy,” which can sound like a substantial change. In reality, no substantial change is being made, and users should simply accept the “policy” when prompted.

Users whose devices do not automatically switch from ActiveSync 2.5 to 12.1 probably are not aware that this change needs to take place in order to get the full benefit of updating to GroupWise Mobility Service 2.0.x. In the Dashboard in the Mobility Admin console, you can display the version of ActiveSync that is in use on users’ devices.

6.5 New Command and Log File Names

The Data Synchronizer Mobility Pack rcdatasync command has been replaced with the rcgms command for the GroupWise Mobility Service.

The names of some of the log files have also changed:

If you have scripts that reference the rcdatasync command or the connector log file names, you must update these scripts for use with the GroupWise Mobility Service.

6.6 Increased Security through Obfuscation

The LDAP server password and the GroupWise trusted application key are obfuscated in the Mobility Admin console and in the configuration file where the strings reside. You must use the Mobility Admin console in order to change these settings.

6.7 Long Update Process

The process of updating to GroupWise Mobility Service 2.0.x from versions of the Data Synchronizer Mobility Pack earlier than 1.2.5 might take longer than previous Mobility Pack updates. It is not unusual for the Update script to run for over an hour for a large database.

Do not cancel the Update script. Wait for it to run to completion.

6.8 Update through ssh Not Recommended

Updating the GroupWise Mobility Service software through an ssh connection is not recommended. An ssh connection can be interrupted before the update process finishes.

6.9 Update Issue from SLES 11 SP1 to SLES 11 SP2 or SP3

When you update a Mobility server from SLES 11 SP1 to SP2 or SP3, you must select the GroupWise Mobility Service as an add-on product during the SLES update process. This informs the SLES update process that you want to retain the Mobility Service on the updated Mobility server. For more information, see TID 7010339, How to Upgrade a Novell Data Synchronizer Mobility Pack Server to SLES 11 SP2 in the Novell Support Knowledgebase.

7.1 Agent Alerts in the Dashboard

The Agent Alerts panel in the Dashboard lists all alerts that are currently in the Dashboard database. The alerts accumulate over time. The Count column in the list shows how many times each type of alert has been recorded in the database.

Alerts are retained in the database until you delete them. Only then is the count updated. The color of each alert indicates the type of alert, not the current state of your Mobility system.

The various status fields in the Agents panel and in the Details panel provide the best indication of the current state of your Mobility system.

7.2 Unknown Device Information in the Dashboard

For most devices, the Dashboard displays the operating system version for each device. However, for some less common devices and for some newer devices, the Dashboard lists the device operating system as Unknown. Additional device operating systems will be recognized in future updates.

7.3 POA Status in the Dashboard

When a POA goes down, the Dashboard promptly displays Critical status. However, when the POA comes up again, it might take as much as an hour for the Dashboard to again display Normal status for the POA.

7.4 References to “LDAP” in the Dashboard

When you have chosen GroupWise as your user source, the Dashboard user interface still refers to “LDAP”. In this context, the LDAP Connection field in the system Details panel displays the status of the connection to your GroupWise system. The LDAP ID field in the user Details panel displays the user_name.post_office.domain location for the GroupWise user.

8.1 Unsuccessful Shutdown

Occasionally, when you shut down the Mobility Service, related Python processes fail to shut down along with it. A message notifies you of the problem. To resolve the problem:

10.1 Synchronization to a Mobile Device Stops

Synchronization from the Mobility system to a mobile device might occasionally stop, perhaps because abnormal cellular network conditions resulted in dropped synchronization data. To resolve the situation, follow the instructions in Resynchronizing a Device in the GroupWise Mobility Service 2.0 Administration Guide. For additional troubleshooting assistance, see Device Troubleshooting in the GroupWise Mobility Service 2.0 Administration Guide.

10.2 Multiple Device IDs for a Single Mobile Device

In the Mobility Admin console, the User/Device Actions page might list two device IDs for one mobile device. Some mobile devices have one device ID for email and contact information, and a second device ID for calendar information. This is working as designed.

10.3 Log File Security Issue

If you set the Mobility Service log level to Debug, Subject lines are included in log files for troubleshooting purposes. This information identifies items that are experiencing synchronization problems.

If you use the Debug log level, ensure that log files are kept secure to protect users’ personal information. The Info log level is strongly recommended for a smoothly functioning Mobility system.

No text about recipients or from message bodies is included in log files.

11.1 Mobile Devices Supported by the AutoDiscover Service

The AutoDiscover Service currently works with Apple devices and with Windows 8 devices.

11.2 Unnecessary Traffic Created by Extraneous Users

When you add a user to your Mobility system, GroupWise data continually synchronizes from GroupWise into your Mobility system. If that data is not being used on a mobile device, that synchronization produces unnecessary overhead in your Mobility system.

11.3 New GroupWise Users

When you add new users to GroupWise, they are not immediately available in the Mobility Admin console for adding to your Mobility system. They automatically become available within 30 minutes of when the Mobility Global Address List (GAL) is updated from the GroupWise Address Book.

For more information, see When New Users Are Added to the GroupWise System in the GroupWise Mobility Service 2.0 Installation Guide.

12.1 Copied Contacts

If you copy a contact from one GroupWise address book to another, the contact is not synchronized to your mobile device in the destination address book. The GroupWise client links the original contact into the destination address book rather than physically copying it. Such links are not currently synchronized to your mobile device. However, on some mobile devices, you can search for contacts, regardless of which address book they are located in.

If the original contact is in an address book that is not synchronized to your mobile device, such as the Frequent Contacts address book, the copied contact does not appear on your mobile device at all, even when you are synchronizing the address book that it was copied into. If you want a copied contact to appear on your mobile device, delete the original contact from the original address book. This creates the contact as a normal contact in the address book that is being synchronized.

12.2 Contacts with Pictures

If you create a contact on your mobile device and add a picture to it, the contact might not synchronize to GroupWise if the picture that you added to the contact on your mobile device exceeds the GroupWise picture size limit. For more information, see Section 12.16, Picture Quality.

12.3 Large Distribution Lists

If a message synchronizes to your mobile device that has a very large number of recipients, your mobile device might seem to hang when opening the message. To prevent this problem, open an item that has a small distribution list, then configure your device to hide distribution lists.

12.4 Organizations

Organizations currently do not synchronize to mobile devices.

12.5 Personal Address Books

When your default personal address book synchronizes to your mobile device, it is named Contacts, rather than the name that you see in GroupWise.

When you create contacts on your mobile device, they are added to your default personal address book in GroupWise. If you want them added to a different personal address book, select that personal address book on the Mobility Settings page in the Mobility Admin console, as described in the GroupWise Mobility User Quick Start.

On some mobile devices, personal address books that have categories on contacts appear to be duplicated. If this is a problem, remove the categories from the contacts in the personal address books.

12.6 Shared Address Books

Shared address books are synchronized to the owner’s mobile device, but not to the mobile devices of those with whom the address book has been shared.

12.7 Draft Items

If you create a draft item on your mobile device, it does not synchronize to your Work in Progress folder in the GroupWise client. If you create a draft item in the GroupWise client, it does synchronize to your mobile device, but you cannot modify it on your mobile device.

12.8 HTML Formatted Appointments

Appointments with HTML formatting in GroupWise synchronize to mobile devices without the HTML-formatted text. As a result, you see the subject line of these appointments on your mobile device, but not the accompanying text that resides in the message body.

12.9 Shared Calendars

Shared calendars are synchronized to the owner’s mobile device, but not to the mobile devices of those with whom the calendar has been shared.

If shared calendars are important to users, shared calendar owners can post them to the Internet using the GroupWise Calendar Publishing Host, as described in Publishing Personal Calendars on the Internet in the GroupWise 2014 Client User Guide. After the owner publishes the calendar, other users can view the calendar URL in the web browser on their mobile devices.

12.10 Reminder Notes

Reminder notes are synchronized to your device as all day events. If you edit the all day event on your mobile device, it synchronizes back to GroupWise as an all day event.

If you create a note on your mobile device using its native Note app, the note does not synchronize to GroupWise. The mobile device Note app is completely independent from GroupWise.

12.11 Tasks

Tasks that originate as other GroupWise item types (such as emails or calendar items) are synchronized as tasks when they are dragged to the Tasklist, when they are displayed in the Tasklist, or when they are changed to tasks. However, existing tasks of this type are not synchronized during initial synchronization. They synchronize to your device after they are modified in GroupWise.

12.12 Tasklists

The GroupWise Tasklist does not synchronize to mobile devices. You cannot create a tasklist on a mobile device that is associated with a GroupWise account.

12.13 Attachments on Appointments

Attachments on appointments are not supported on mobile devices. When you accept an appointment that has attachments, the attachments are removed as the appointment is added to the calendar on your mobile device.

As a workaround, you can delegate the appointment to yourself, accept the original appointment into your calendar, and retain the delegated appointment as an email item with attachments.

12.14 Large Attachments

Synchronizing large attachments to mobile devices can put a substantial load on the Mobility Service. To decrease the amount of data that is synchronized to mobile devices, you can control the maximum size of synchronized items, as described in Controlling Synchronization Size Limits in the GroupWise Mobility Service 2.0 Administration Guide.

12.15 Non-Synchronizing Folders

The following GroupWise folders do not synchronize to your mobile device:

Any folders that you move under a non-synchronizing folder no longer synchronize.

12.16 Picture Quality

GroupWise personal address books limit contact pictures to 64x64 pixels and less than 2K in size. Mobile devices often handle pictures with more pixels and a larger file size.

When pictures are synchronized from your mobile device to GroupWise, GroupWise makes two attempts to optimize the picture to fit within the GroupWise limits of 64x64 pixels and 2K file size. The resulting picture might not display as well as expected in the GroupWise personal address book. You can use an image editing program to manually adjust the original picture to fit within the GroupWise limits, and then synchronize it from your mobile device to GroupWise.

When pictures are synchronized from GroupWise to your mobile device, they might not display as well as expected on the mobile device because the GroupWise limit is retained on the mobile device.

12.17 Items Archived and Stubbed by a Third-Party Application

If your GroupWise system is backed up using an archive solution that employs GroupWise stubbing, GroupWise items synchronize to your mobile device when they are archived and stubbed in GroupWise. Stubbing replaces an existing item with a copy of the item, without any attachments and without the message body text.

13.1 Language Versions of the Mobility Admin Console and Informational Messages on Mobile Devices

The Mobility Admin console is translated into the standard GroupWise administration languages. Informational messages from the Mobility system to mobile devices are translated into the standard GroupWise user languages. For language lists, see Multilingual GroupWise Systems in the GroupWise 2014 Administration Guide.

When users log in to the Mobility Settings page in the Mobility Admin console, the administration languages, not the user languages, are available.

14.1 PDF Display in Firefox

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.