NT Manage Server Escalation Procedures



Globo Mobile Technologies Inc

Release Notice for GO!NotifyLink Enterprise Server -

Exchange

|REVISION HISTORY |

|Date |Author |Description of Changes |

|01/23/2012 |Jodie Grazier |Version 4.8.0 |

|11/03/2010 |Jodie Grazier |Version 4.7.1 |

|09/20/2010 |Jodie Grazier |Version 4.7.0 |

|12/04/2009 |Jodie Grazier |Noted with release of GO!NLES v4.6.x Update 12 |

| | | |

| | |Section IV.A. Added issue for Delete Invitations From Device |

| | |setting. 12208 |

|09/23/2009 |Jodie Grazier |Added Outstanding Issue: |

| | |- contact edited on server loses email address data 11668 |

|02/26/2009 |Jodie Grazier |Version 4.6.0 |

|08/12/2008 |Jodie Grazier |Important Things To Know: |

| | |multi-day events 8887 |

| | |recurring event exceptions 8904 |

|01/29/2008 |Jodie Grazier |Added Outstanding Issue: |

| | |- delete contact from device 5904 |

|01/07/2008 |Jodie Grazier |Important Thing To Know – OL 2000 not supported with Exchange |

| | |2007. 6940 |

|10/15/2007 |Jodie Grazier |Important Thing To Know – Forms-Based Authentication 6717 |

|08/15/2007 |Jodie Grazier |Version 4.5.0 |

I. Installer Information 3

II. Functional Summary 3

A. Installer New/Changed Features 3

B. Server New/Changed Features 3

C. User Interface (Web) New/Changed Features 3

III. Important Things to Know 3

A. Features Not Supported 3

B. GO!NotifyLink Server Things to Know 3

C. Device Things to Know 4

D. Exchange Things to Know 4

IV. Outstanding Issues/Bugs 4

A. GO!NotifyLink Server Outstanding Issues/Bugs 5

B. Exchange Outstanding Issues/Bugs 6

I. Installer Information

Original Release Date (GO!NLES v4.7.1): 11/03/2010

Base Product: GO!NotifyLink Enterprise Server

II. Functional Summary

A. Installer New/Changed Features

B. Server New/Changed Features

1. Attendees are now notified of changes to a meeting when that meeting was created on the device. 5128

C. User Interface (Web) New/Changed Features

III. Important Things to Know

A. Features Not Supported

1. Responses to Meeting Invitations are not sent to the device. If the GO!NotifyLink user organizes a meeting, the Meeting Invitation is sent out, but Attendee’s responses are not sent to the device.

B. GO!NotifyLink Server Things to Know

1. For devices NOT using ActiveSync, the following mail folders will not be displayed in the web and will not be available to track for new email:

I. The “Sent Items” folder as defined for the Mail Server via the Administrative Web.

II. The “Deleted Items” folder as defined for the Mail Server via the Administrative Web.

2. During the Add New User process, the Exchange user list is displayed to allow selecting a user to add to the GO!NotifyLink Enterprise Server. This will automatically fill in some of the user information (for example: First Name, Last Name, Email Address). The user list is populated using LDAP and can only be retrieved if the Exchange Domain Controller information is provided and the LDAP port is open. The Exchange Domain Controller information is entered via the web administration on the Server Administration > Server Settings page. If the LDAP information cannot be retrieved, users must be entered manually.

3. When using Outlook or Outlook Web Access to reply to an email, the email is deleted from the IMAP server and re-created with a new UID. This can cause unexpected results on the device depending on the GO!NotifyLink settings. The suggested workaround it to enable the Control Options for Synchronize All Mail and Synchronize Message Changes. This will cause GO!NotifyLink to detect the delete of the original email and also the creation of the new email and keep the device synchronized. This also results in many messages moved to the Trash folder on the device. Cleanup options on the device can be used to automatically empty the Trash.

4. If Forms-Based Authentication is enabled on the Exchange server AND Forms-Based Authentication is disabled on the GO!NotifyLink Enterprise Server, PIM will fail but the status reported in GO!NotifyLink Web will show success. 6717

5. If an item is changed such that it no longer occurs within the synchronization range, a delete will not be sent to the device immediately. The delete will be sent the next time a manifest is processed (at midnight or if the synchronization range is change in the GO!NotifyLink web).

I. This applies to calendar events if the start date is moved beyond the look ahead date or behind the look back date.

II. This applies to task if the due date is moved beyond the look ahead date.

6. When a contact is created on the device, the 'File As' property of a contact is set using the format 'Firstname Lastname'. If the contact is updated on the device, the 'File As' property is not changed.

7. A contact created in Outlook Web Access (OWA) without a first name and last name will synchronize to the device, but will not use the 'Display Name' field in place of the missing first name/last name.  Users may expect 'Display Name' to be used as it is in Outlook when the contact is created without a first or last name. They should be advised that OWA will not operate the same in this scenario. 4953

8. This issue involves contacts created on the server with an email address that contains a username, but not a domain name (i.e. without @). When synchronized to the device, the contact's email address field is blank. This does not occur when such a contact is created in Outlook Web Access (OWA). Whatever has been entered in the email address field is synchronized to the device, whether or not it contains a domain name. 5175

9. An exception made to an instance of a recurring event that occurs outside the synchronization range will not synchronize to the device. Once the instance comes into calendar synchronization range, however, the exception is found and sent to the device. 8904

10. Modified exceptions to recurring events outside of the sync range do not sync to the device. 6458

11. A multi-day event, created on the Exchange server, that starts within the calendar synchronization range and ends outside the range, does not synchronize to the device. Once the event comes into calendar synchronization range, however, it is found and sent to the device. 8887

12. When a meeting response is sent using the GO!NotifyLink client on the device, the corresponding meeting request is found in the user's Inbox and removed. This is similar to the behavior of Exchange when Outlook is used to respond to a meeting request.

13. Replying to a meeting request from a device with the 'Tentative' response results in the meeting invitation being resent in a subsequent synchronization cycle. The invitation will continue to resend each time the 'Tentative' response is used. 5165

14. If Administrator Authentication is configured for the PIM server, meeting requests initiated from the device are sent to the attendee from the Administrator on behalf of the sender. 6268

C. Device Things to Know

D. Exchange Things to Know

1. Outlook 2000 is not supported against Exchange 2007. Attempting to use Outlook 2000 may result in incorrect or unexpected behavior. 6940

2. This issue involves contacts opened in Outlook Web Access (OWA). When opened in OWA, a contact's email address is displayed in the 'Display Name' field as well as the email field. 5173

IV. Outstanding Issues/Bugs

A. GO!NotifyLink Server Outstanding Issues/Bugs

1. With Synchronize Message Changes enabled, messages that are read via Outlook may cause a delete on the device. The Unread item on the device will be moved to the Trash. This is an issue when there are many aliases for the account.

2. An email account created with a username containing special characters experiences successful mail processing cycles, however, PIM processing cycles fail and display errors. On the User Statistics page, the check mail cycle is successful, but PIM stats show error 551 (the pim log will show error 401). This issue involves usernames that contain one or more of the following the characters: ampersand (&), plus sign (+), percent sign (%), number sign (#), dollar sign ($), exclamation point (!). 6296

3. The following issues with Meeting Reponses apply to customers using Exchange 2003 SP2. 5441

a. When a meeting is accepted from the device, the server will send down an add/delete for the corresponding calendar event.

b. When a Meeting Response (Accept or Tentative) is sent from the device, the response is processed by GO!NLES and then results in a change event being sent back to the device. If the response is ‘Tentative’, the Meeting Invitation itself will also be resent.

4. Users may configure the GO!NotifyLink Calendar Sync Rules so that meeting invitations are deleted from the device Inbox when they are accepted, declined, or tentatively accepted. For GO!NotifyLink accounts using an Exchange calendar server, when this Delete Invitations From Device option is set to remove Only Accepted invitations, it does not function as expected. The meeting invitation is not removed from the Inbox and the User Statistics do not show a deleted invitation. All other options, such as, Only Declined, Accepted/Declined, All Responded, etc. function properly, resulting in the invitation being removed from the Inbox and the statistics showing a deleted invitation. 12208 / 8448

5. The look ahead date for Tasks specified on the web does not function in Exchange 2000. As such, tasks with a due date greater than the look ahead will still be sent to the device. 4068

6. Monthly and Yearly recurring events that have their first instance prior to the Calendar look back date may not synchronize to the device until a new manifest is retrieved by the server. A new manifest is retrieved every day at midnight, when the user performs a Load Calendar, or whenever the Calendar range is changed on the web. 4110

7. This issue applies to a recurring event that spans beyond the calendar synchronization range (starts before the look-back date and ends after the look-ahead date). If such an event is deleted on the server, it is not deleted from the device. 6273

8. For Appointments and Contacts created or edited on the device, if a newline (carriage return) is added to the end of a field the item will not be processed correctly on the server. 3822

9. This issue involves contact categories that contain one or more of the following the characters: asterisk (*), pipe (|), double quote("), colon (:), forward slash (/), back slash (\), period (.), right angle bracket (>), left angle bracket ( ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download