Globo Mobile Technologies Inc - Confidential
Globo Mobile Technologies Inc
Release Notice for GO!NotifyLink Enterprise Server -
ActiveSync Solution
REVISION HISTORYDate / Author / Description of Changes
04/30/2012 / Anthony Costello / Version 4.8.2 Patch 1
Added Outstanding Issue:
- Blank invitee to a meeting on the device - 7742
01/23/2012 / Jodie Grazier / Version 4.8.0
10/12/2011 / Jodie Grazier / Updated iOS note about task support
04/22/2011 / Jodie Grazier / Updated Knowledge Base links
01/13/2011 / Jodie Grazier / Updates for Patch 3
Max ActiveSync Message Availability – default changed from 1 month to 180 days. Edited the device behavior note. 797 / 1992
11/30/2010 / Jodie Grazier / Added notes about support for Windows Phone 7 devices.
11/03/2010 / Jodie Grazier / Version 4.7.1
09/20/2010 / Jodie Grazier / Version 4.7.0
07/29/2010 / Jodie Grazier / Updated items for TouchDown v6.1.0007:
12487, 12635, 12661
07/22/2010 / Jodie Grazier / Added Outstanding Issue:
-iOS4 All Day events in Day View 12938
07/12/2010 / Jodie Grazier / Added Outstanding Issues:
-iOS4 save/copy image attachment 875
-iOS4 “Download Full Message” option 12917
04/12/2010 / Jodie Grazier / Edited wording of iPhone/iPod section to include iPad devices.
03/25/2010 / Jodie Grazier / Added note for issue 12774
03/04/2010 / Jodie Grazier / Added notes for issues 11899, 12664,12665, 12693 and 12699
02/24/2010 / Jodie Grazier / Release of GO!NLES v4.6.x Update 14.
Added notes about support for Android OS devices using TouchDown client.
12/04/2009 / Jodie Grazier / Noted with release of GO!NLES v4.6.x Update 12
Section III.B. Noted behavior for WM and webOS devices for invitation responses. 11597 / 11900
Section VI.B. Added issue for WM with Calendar and Task notes. 12193
Section VI.C. Added issue for WM with attachment of type email. 12001
10/29/2009 / Jodie Grazier / Added issue for iPhone v3.1 with emails that have an email/message attachment. 11761
10/13/2009 / Jodie Grazier / Added note for issue 11555
10/09/2009 / Jodie Grazier / Added items for webOS support.
Updated Knowledge Base links
10/05/2009 / Jodie Grazier / Updated issues 10483 and 11380
09/25/2009 / Jodie Grazier / Updated issue 8964
09/23/2009 / Jodie Grazier / Added iPhone specific NotifyLink Issue:
- Viewing meeting response message on device 11661
08/19/2009 / Jodie Grazier / Added issue 11380.
08/05/2009 / Jodie Grazier / Additional issues added: 11096, 11209, 11294, 11333.
07/24/2009 / Jodie Grazier / Version 4.6.1
Added items for WMAS support.
Removed issue 9688
I. Installer Information
II. Functional Summary
A. Installer New/Changed Features
B. Server New/Changed Features
C. User Interface (Web) New/Changed Features
III. Applicable to all supported ActiveSync devices
A. Features Not Supported
B. GO!NotifyLink Server Things to Know and Outstanding Issues
C. Other Things to Know and Outstanding Issues
IV. Specifics for Android devices using TouchDown
A. Features Not Supported
B. GO!NotifyLink Server Things to Know and Outstanding Issues
C. Android using TouchDown Things to know and Outstanding Issues
V. Specifics for Android devices using Native ActiveSync
A. Features Not Supported
B. GO!NotifyLink Server Things to Know and Outstanding Issues
C. Android Native ActiveSync Things to Know and Outstanding Issues
VI. Specifics for iPhone (iOS) devices
A. Features Not Supported
B. GO!NotifyLink Server Things to Know and Outstanding Issues
C. iPhone (iOS) device Things to Know and Outstanding Issues
VII. Specifics for Symbian ActiveSync devices
A. Features Not Supported
B. GO!NotifyLink Server Things to Know and Outstanding Issues
C. Symbian Things to Know and Outstanding Issues
VIII. Specifics for webOS devices
A. Features Not Supported
B. GO!NotifyLink Server Things to Know and Outstanding Issues
C. webOS Things to Know and Outstanding Issues
IX. Specifics for Windows Phone 7 devices
A. Features Not Supported
B. GO!NotifyLink Server Things to Know and Outstanding Issues
C. Windows Phone 7 Things to Know and Outstanding Issues
X. Specifics for Windows Mobile devices
A. Features Not Supported
B. GO!NotifyLink Server Things to Know and Outstanding Issues
C. Windows Mobile Things to Know and Outstanding Issues
I. Installer Information
Original Release Date (GO!NLES v4.8.0):01/23/2012
Base Product:GO!NotifyLink Enterprise Server
II. Functional Summary
A. Installer New/Changed Features
B. Server New/Changed Features
1.)Contact Display Name will now sync to and from ActiveSync devices when supported. Only TouchDown and certain HTC Androids such as the EVO support a separate Display Name field. Other devices will send a display name made up of the individual name properties, most of the time formatted as “Lastname, Firstname”. 1424 / 4675
- The following collaboration suites support Contact Display Names:Sun, CGP, Kerio, Oracle 10, Exchange, Mirapoint, Groupwise.
- The following collaboration suites do not support a Contact Display Name: FirstClass, MDaemon, MeetingMaker, Oracle Beehive7596, Scalix. These will send "First Last" to the device and ignore the display name fromthe device.
- Zimbra can send a Display Name, but not receive one.
2.)Email deleted on certain Android devices is now deleted on the server. For example, Samsung Galaxy S models and the Samsung Captivate. 3011
3.)Corrected an issue with Calendar events in the Atlantic time zone sent from TouchDown. 3659
4.)Email attachments can now be limited by a maximum size. Attachments larger than the size specified in the database will be synced as a txt file to ActiveSync devices containing the original file name, original file size, and reason it could not be downloaded.For example, if the name of the attachment is “file.doc”, it will be sent as “file.doc.txt”. Note that if an attachment has a .txt extension, an additional .txt will not be added. 4091
5.)Tasks arenow supported when using an iOS 5 device. 6011
6.)Fixes for Android Sprint Samsung Galaxy S II Epic 4G Touchinclude:
- No longer display email as MIMEs. 6404
- No longer Force Closes when replying or forwarding an HTML message with images as long as the image filename does not contain a curly bracket ‘}’.6406 7613
- Can now open and attach .doc and .xls files.7514
7.)The system can be configured to disallow connections from devices that are using TouchDown but are not registered on a TouchDown for Android license. This must be configured directly in the database; please contact Technical Support for assistance if this feature is desired. 5924
C. User Interface (Web) New/Changed Features
III. Applicable to all supported ActiveSync devices
A. Features Not Supported
1.)Level 1 filters are not supported for ActiveSync devices. The email will be delivered to the device, but no special audible alert will be sounded. 9670
B. GO!NotifyLink Server Things to Know and Outstanding Issues
1.)After applying the changes for ActiveSync support, the following configuration must be made to URLScan on the server running the GO!NotifyLink Enterprise Server HTTP/Web Component.
- Open the C:\WINNT\system32\inetsvr\urlscan\urlscan.ini file.
- Underneath the [AllowVerbs] section, make sure OPTIONS and POST exist. If these are not present, add them:
[AllowVerbs]
;
; The verbs (aka HTTP methods) listed here are those commonly
; processed by a typical IIS server.
;
; Note that these entries are effective if "UseAllowVerbs=1"
; is set in the [Options] section above.
;
GET
HEAD
POST
OPTIONS
- Restart IIS.
2.)When adding an ActiveSync user, the administrator must select the correct device type in order to get the correct set of options/settings for the user.
3.)Customers using Apache web server who experience web crashes, please seeKnowledge Base article.
4.)Direct Push connections on ActiveSync devices may prematurely disconnect when a reverse proxy is used to route traffic to the GO!NotifyLink Http/Web component. For more details, see Knowledge Base article. 11209
5.)Some information is not sent by ActiveSync devices and thus does not appear on the Device Management page of the GO!NotifyLink Administrative Web. The following fields display blank for these devices: GO!NotifyLink Version, Phone Number, Battery Status, Free Memory, Network Type, Roaming - will always show 'No', Signal Level. 9310
6.)The calendar Look-back range is set on the ActiveSync device and the Look-ahead range is set in the GO!NotifyLink Admin or Client Web interface. For more details, see Knowledge Base article. 9152 / 11223
- On an iPhone device – “Settings” > “Mail, Contact, Calendar”, set the “Sync” value under “Calendars”.
- On a Windows Mobile - Start > Programs > ActiveSync > Menu > Options > (select “Calendar”) > Settings. Set the “Synchronize only the past …” value.
7.)If an ActiveSyncdevice user is removed from the GO!NotifyLink Enterprise Server (GO!NLES), the device retains the Email and PIM (calendar and contacts) data. The data can be cleared from the device, however, by removing the account from the device. 8856
8.)If the designated PIM server is switched from MDaemon or FirstClass to another server and then back again to the same MDaemon or FirstClass server, PIM items will not synchronize to the ActiveSync device. 9120
9.)In order to correctly synchronize HTML email, the GO!NotifyLink setting for Attachments is always ON and Smart Retrieval is always OFF. These settings are imposed for the ActiveSync device users regardless of the global settings. When editing User IT Policies, these options are not available for changes. 8871
10.)Message content encryption is not supported for ActiveSync devices. The encryption key field will be disabled in the Security Settings in the Admin and Client web. 8874
11.)This issue applies to both Windows Mobile and webOS devices. A forward of an email that contains attachments, when performed from the device, will not have the correct attachments delivered to the recipient(s).
12.)This issue applies to ActiveSync device users who have tagged their trash folder for synchronization in the GO!NotifyLink Enterprise Server web. For Zimbra users, email with no body which is synchronized to an ActiveSync device and subsequently deleted on the server, does not get synchronized to the trash folder on the device as it should. 9701
13.)This issue involves CGP and calendar events and contacts created on an ActiveSync device. The items synchronize to the CommuniGate Pro server, but do not appear when viewed via the CommuniGate Pro Outlook Connector until the user exits, then reenters Outlook. 9702
14.)Since meeting invitations are sent as emails, mail synchronization must be enabled in order to receive invitations. If disabled, the invitation will not appear in either the Mail or Calendar application on the device.9305
15.)Users operating on a Scalix CalDAV PIM server will see duplicate meeting invitations on their ActiveSync device calendar - one for the Calendar Event and one for the invitation. The issue stems from separate fields being used for appointments and invitations in the groupware product. Note that the duplicate will not appear on the Windows Mobile device until the meeting has been accepted.8779
16.)The organizer of a meeting will receive two responses - one with Comments, one without - from recipients who have responded to the invitation via an ActiveSync device. 8768
17.)The Max ActiveSync Message Availability setting in the Administrative Web Console limits the range of emails synchronized to the ActiveSync devices. This gives the Administrator a way to help control the size of the database. The setting can be configured at the User Class level or at the Server Administration level (for unclassified users). The default setting is 180 days.797 / 1992
- Messages that exceed the range will be removed from the database, but not from the mail server. Messages may remain on the device. This means that changes on the device such as Read/Unread status, deletes, and moving to a different folder will not be synchronized. However, the message on the device can be forwarded or replied to successfully. See the Administrative User Guide for more details.
18.)Meeting invitations sent to the device from the server can include a blank invitee on the device. 7742
C. Other Things to Know and Outstanding Issues
IV. Specifics for Android devices using TouchDown
A. Features Not Supported
1.)The TouchDown client does not support creating recurring events in versions prior to v6.1.0007. Recurring events synchronized to the TouchDown calendar are treated as individual events, not a series. 12487
B. GO!NotifyLink Server Things to Know and Outstanding Issues
1.)Android devices are supported using the TouchDown client for the ActiveSyncconnection. See more information on the GO!NotifyLink portal.
Additionally, some Android 2.2 devices are supported using the native Exchange Active Sync implementation; see section V and the GO!NotifyLink portal.
C. Android using TouchDown Things to know and Outstanding Issues
1.)Android OS version and device model do not display on the User Statistics page of the GO!NotifyLink Administrative Web. In their place is information about the TouchDown device client. 12551
2.)Unless configured to do so, TouchDown will not synchronize items (new, changed or deleted) originating on the device until synchronization is triggered by one of the items outlined below. To change this default behavior to instead synchronize immediately, see Knowledge Base article.12614
- An items arrives via direct push
- A scheduled push (polling) session occurs
- A manual sync is initiated
3.)When a GO!NotifyLink account is reregistered via the TouchDown device client, it may not immediately do an initial synchronization. When a new item comes in via Direct Push or a Scheduled Push (polling) synchronization interval occurs, the initial synchronization will happen. To workaround this, you can issue a manual synchronization after re-registering (from TouchDown Home screen, press Menu key and choose Sync). 12567
4.)Weak password strength requirements (8 to 20 characters of any type) are enforced in TouchDown. Strong password strength requirements (one each of alpha, numeric, symbol characters) are not enforced, however, Touchdown will impose Weak requirements when Strong is selected. 12637 / 12638
5.)An Inactivity Timeout lock will only lock the TouchDown application. Everything else on the Android device will be accessible. If you have TouchDown open when the lock is imposed, press the Back key to return to the device Home screen. 12579
6.)TouchDown does not prompt for the existing password when you manually choose to change the Inactivity Timeout password. (TouchDown behavior has changed with v6.1.0007 and the user is now prompted for the existing password). Of course, if the Inactivity Timeout lock has been imposed, an unauthorized user could not access the 'Change PIN' option. It is only when the device is not locked that this is an issue. It is therefore advisable to set a lower Inactivity Timeout interval. 12635
7.)TouchDown only enforces IT security policies if they are mandated by policies sent to the device from the server. The user has no way to set a policy, such as Inactivity Timeout, Wipe on Fiailed Unlock Attempts, etc. if it is not required. 12640
8.)A Remote Wipe or a Wipe on Failed Unlock Attempts will only wipe data synchronized by TouchDown. 12583
- When the wipe occurs because of failed unlock attempts, you are returned to the TouchDown Home screen where a prompt to accept the license agreement is displayed. The user account must then be recreated.
- When a remote wipe occurs, the TouchDown application becomes unusable, but can be removed and reinstalled.
9.)When a remote wipe is issued to TouchDown, the whole device is not wiped. The TouchDown information is cleared and the app is reset back to the welcome screen. 6444
10.)When a Remote Wipe is done, the TouchDown application becomes unusable. TouchDown needs to be removed from the device and reinstalled. See Knowledge Base article for details on how to reinstall. 12601
11.)If a mail folder containing unread messages is deleted on the server, the unread messages will still appear on the TouchDown Home screen where a list of unread messages is displayed. The message can be opened and viewed once, but when it is closed it will finally disappear from the device. 12597
12.)When you forward a plain text message from TouchDown, the original message and sometimes the signature appear twice when the message is viewed on the server. A work around options is discussed in Knowledge Base article. 12588
13.)You are unable to add an attachment to an email while the device is connected to a PC via a USB port. While the device is connected, you are unable to view files or folders on the device SD card, therefore making it impossible to select and attach a file. 12639
14.)When sending an email to the device with an attachment, the attachment is duplicated. One copy of the attachment downloads automatically and the other results in a 500 error when attempting to download. 6095
15.)When you select a different or additional address books to synchronize to the device you must issue a "Refresh All" from the TouchDown Contacts application menu (from TouchDown Home screen, tap the Contacts icon then press the Menu key and select Refresh All). Otherwise, contacts from the newly selected address book(s) will not populate the Contact list. 12566
16.)If you choose to save a contact from the Global Address List (GAL) search result set to the device, it will be saved to the default TouchDown address book. There is no option to choose a different address book. 12592
17.)Events created on the server sometimes appear a day early in the TouchDown 'Month' view. In other views such as Day, Week, Aganda, the events appear on the correct day. This no longer occurs with TouchDown v6.1.0007. 12661
18.)To allow past events to show in the TouchDown Calendar's Agenda view, you must change a Calendar option. In the TouchDown Calendar application press the Menu key, tap More > Options, remove the selection of "Agenda View shows upcoming only". 12652
19.)If you edit the calendar event via TouchDown for a meeting that you did not create, the event will appear changed in the TouchDown calendar, but will not synchronize to the calendar on the Oracle server. It is expected that attendees would not have permissions to edit meetings they did not create. Be aware that if you attempt this your calendars will not match. 12654
20.)In TouchDown, when making any exceptions to any recurring event that is two years in advance, the exception is not handled correctly. The event will not change if it is outside the sync range. If it is inside the sync range, TouchDown will show the change and then re-add the original event. 6273