Notify Technology Corporation - Confidential




          Notify Technology Corporation
  Release Notice for NotifyLink E...
Notify Technology Corporation - Confidential



      07/24/09                          Jodie Grazier                    V...
Notify Technology Corporation - Confidential



I. Installer Information ....................................................
Notify Technology Corporation - Confidential



I. Installer Information

Original Release Date (NLES v4.6.0): 02/26/2009
...
Notify Technology Corporation - Confidential



                    POST
                    OPTIONS
               c.   R...
Notify Technology Corporation - Confidential



     13.)This issue applies to both Windows Mobile and webOS devices. A fo...
Notify Technology Corporation - Confidential




B. NotifyLink Server Things to Know and Outstanding Issues

     1.) Andr...
Notify Technology Corporation - Confidential



     11.)When you forward a plain text message from TouchDown, the origina...
Notify Technology Corporation - Confidential



           further changes to the contact, made on the server, will only a...
Notify Technology Corporation - Confidential



     2.) If "Drafts" folder is selected for folder monitoring in the NLES ...
Notify Technology Corporation - Confidential



     16.)When a remote lookup is done on an iPhone/iPod touch device, the ...
Notify Technology Corporation - Confidential



VI. Specifics for webOS devices
A. Features Not Supported

     1.) webOS ...
Notify Technology Corporation - Confidential



               j.   Mac OS Turkish
     4.) webOS devices will not use WiF...
Notify Technology Corporation - Confidential



         selected for synchronization on the device. Folders can be select...
Upcoming SlideShare
Loading in...5
×

NT Manage Server Escalation Procedures

575

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
575
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "NT Manage Server Escalation Procedures"

  1. 1. Notify Technology Corporation - Confidential Notify Technology Corporation Release Notice for NotifyLink Enterprise Server - ActiveSync Solution REVISION HISTORY Date Author Description of Changes 04/12/10 Jodie Grazier Edited wording of iPhone/iPod section to include iPad devices. 03/25/10 Jodie Grazier Added note for issue 12774 03/04/10 Jodie Grazier Added notes for issues 11899, 12664, 12665, 12693 and 12699 02/24/10 Jodie Grazier Release of NLES v4.6.x Update 14. Added notes about support for Android OS devices using TouchDown client. 12/04/09 Jodie Grazier Noted with release of 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/09 Jodie Grazier Added issue for iPhone v3.1 with emails that have an email/message attachment. 11761 10/13/09 Jodie Grazier Added note for issue 11555 10/09/09 Jodie Grazier Added items for webOS support. Updated Knowledge Base links 10/05/09 Jodie Grazier Updated issues 10483 and 11380 09/25/09 Jodie Grazier Updated issue 8964 09/23/09 Jodie Grazier Added iPhone specific NotifyLink Issue: - Viewing meeting response message on device 11661 08/19/09 Jodie Grazier Added issue 11380. 08/05/09 Jodie Grazier Additional issues added: 11096, 11209, 11294, 11333. 5/8/10 Page 1 of 14
  2. 2. Notify Technology Corporation - Confidential 07/24/09 Jodie Grazier Version 4.6.1 Added items for WM AS support. Removed issue 9688 5/8/10 Page 2 of 14
  3. 3. Notify Technology Corporation - Confidential I. Installer Information ............................................................................................4 II. Functional Summary...........................................................................................4 A. Installer New/Changed Features....................................................................4 B. Server New/Changed Features......................................................................4 C. User Interface (Web) New/Changed Features...............................................4 III. Applicable to all supported ActiveSync devices................................................4 A. Features Not Supported.................................................................................4 B. NotifyLink Server Things to Know and Outstanding Issues...........................4 C. Other Things to Know and Outstanding Issues..............................................6 IV. Specifics for Android devices using TouchDown..............................................6 A. Features Not Supported.................................................................................6 B. NotifyLink Server Things to Know and Outstanding Issues...........................7 C. Android Things to Know and Outstanding Issues..........................................7 V. Specifics for iPhone devices..............................................................................8 A. Features Not Supported.................................................................................8 B. NotifyLink Server Things to Know and Outstanding Issues...........................8 C. iPhone device Things to Know and Outstanding Issues................................9 VI. Specifics for webOS devices...........................................................................12 A. Features Not Supported...............................................................................12 B. NotifyLink Server Things to Know and Outstanding Issues.........................12 C. webOS Things to Know and Outstanding Issues.........................................12 VII. Specifics for Windows Mobile devices...........................................................13 A. Features Not Supported...............................................................................13 B. NotifyLink Server Things to Know and Outstanding Issues.........................13 C. Windows Mobile Things to Know and Outstanding Issues..........................14 5/8/10 Page 3 of 14
  4. 4. Notify Technology Corporation - Confidential I. Installer Information Original Release Date (NLES v4.6.0): 02/26/2009 Base Product: NotifyLink Enterprise Server II. Functional Summary A. Installer New/Changed Features B. Server New/Changed Features 1.) Added support for Windows Mobile device with ActiveSync interface. 2.) Added rule for “Enforce Policies on Device” that allows the administrator to turn ActiveSync provisioning on or off. 11248 3.) Added support for webOS devices (Palm Pre) with ActiveSync interface. C. User Interface (Web) New/Changed Features 1.) What was previously displayed as the “NLES-<Server> iPhone” is now “NLES-<Server> ActiveSync” and supports both iPhone devices and Windows Mobile devices using ActiveSync. The administrator must select the correct device type when adding a user in order to get the correct set of options/settings for the user. For example, if the user is set as an iPhone device but is actually registered with a Windows Mobile, tasks will not be enabled. 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. 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 NotifyLink Enterprise Server HTTP/Web Component. a. Open the C:WINNTsystem32inetsvrurlscanurlscan.ini file. b. 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 5/8/10 Page 4 of 14
  5. 5. Notify Technology Corporation - Confidential POST OPTIONS c. Restart IIS. 2.) Customers using Apache web server who experience web crashes, please see Knowledge Base article 371. 3.) Direct Push connections on ActiveSync devices may prematurely disconnect when a reverse proxy is used to route traffic to the NotifyLink Http/Web component. For more details, see Knowledge Base article 692. 11209 4.) Calendar Sync Rules on the NotifyLink Administrative Web provide an option to select the conditions under which invitations are deleted from the device. It is recommended that ActiveSync devices be configured to delete all invitations from the Inbox to which the user has responded. This option provides the most consistent expected behavior on ActiveSync devices. Other options may not consistently delete invitations as expected according to the rule. 11899 5.) Some information is not sent by ActiveSync devices and thus does not appear on the Device Management page of the NotifyLink Administrative Web. The following fields display blank for these devices: NotifyLink Version, Phone Number, Battery Status, Free Memory, Network Type, Roaming - will always show 'No', Signal Level. 9310 6.) Two NLAirSyncRedirect filters appear in the IIS admin after upgrading from NLES 4.5.1 to NLES 4.5.2. This happens because the filter is not removed when NLES 4.5.1 is uninstalled and is added again when 4.5.2 is installed. This will not have an adverse affect and can remain this way until a subsequent upgrade, after which a single filter will remain. 9560 7.) The calendar Look-back range is set on the ActiveSync device and the Look-ahead range is set in the NotifyLink Admin or Client Web interface. For more details, see Knowledge Base article 673. 9152 / 11223 a. On an iPhone device – “Settings” > “Mail, Contact, Calendar”, set the “Sync” value under “Calendars”. b. On a Windows Mobile - Start > Programs > ActiveSync > Menu > Options > (select “Calendar”) > Settings. Set the “Synchronize only the past …” value. 8.) If an ActiveSync device user is removed from the NotifyLink Enterprise Server (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 9.) 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 10.)In order to correctly synchronize HTML email, the 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 11.)ActiveSync device users may experience synchronization failures in one of the following situations: a. They delete email on the device (move an item to the Trash folder), but the items are not deleted on the server. b. They move an email from one folder to another on the device, but the change is not reflected on the server. This may happen only when moving items to one or two particular folders. The issue is with the destination folder and is caused by the way the user's mail and PIM folders are identified internally by NotifyLink Enterprise Server. For more details, see Knowledge Base article 691. 11294 12.)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 5/8/10 Page 5 of 14
  6. 6. Notify Technology Corporation - Confidential 13.)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). 14.)This issue applies to ActiveSync device users who have tagged their trash folder for synchronization in the 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 15.)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 16.)This issue applies to customers using an ActiveSync device with an Oracle PIM Server. When a recurring event is created on the device, the server processing turns the series into individual events. The individual events are then sent from the server back to the device, resulting in duplicate instances in the calendar display. The original recurring event is then deleted from the device at midnight such that the server and device are then both correct. This will be resolved in a future release of NotifyLink Enterprise Server. 11751 17.)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 18.)Users operating on a Scalix or 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 19.)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 20.)This issue applies to both Windows Mobile and webOS devices. A meeting invitation sent to the device appears in the device calendar only after the invitation is accepted on the device. In order for invitations accepted on the server to affect the device calendar similarly, a setting on NotifyLink Calendar Sync Rule must be configured properly. If the user accepts the invitation on the server and does not have the NotifyLink Calendar Sync Rules set properly, the item will remain in the device Inbox and will not populate the device calendar unless the user also responds to the invitation on the device. To avoid this, it is recommended that users set their NotifyLink Calendar Sync Rule to delete invitations from the device Inbox when they have been responded to on the server. This will result in the automatic removal of the invitation from the device Inbox and the addition of the event to the device calendar when the user responds from the server. In the NotifyLink Web, it is recommended to set the Delete Invitations From Device option to All Responded. 11597 / 11900 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. Recurring events synchronized to the TouchDown calendar are treated as individual events, not a series. 12487 5/8/10 Page 6 of 14
  7. 7. Notify Technology Corporation - Confidential B. NotifyLink Server Things to Know and Outstanding Issues 1.) Android devices are only supported when using the TouchDown client for the ActiveSync connection. Additionally, the TouchDown client must be downloaded from the NotifyLink portal. http://notifylink.notify.net/AndroidTDAS.asp C. Android Things to Know and Outstanding Issues 1.) Android OS version and device model do not display on the User Statistics page of the 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 1141. 12614 a. An items arrives via direct push b. A scheduled push (polling) session occurs c. A manual sync is initiated 3.) When a 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 reregistring (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. 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 a. 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. b. When a remote wipe occurs, the TouchDown application becomes unusable, but can be removed and reinstalled. 9.) 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 1132 for details on how to reinstall. 12601 10.)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 5/8/10 Page 7 of 14
  8. 8. Notify Technology Corporation - Confidential 11.)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 1139. 12588 12.)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 13.)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 14.)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 15.)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. 12661 16.)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 17.)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 V. Specifics for iPhone devices NOTE: Unless otherwise noted, the term “iPhone” or the phrase “iPhone device” used throughout this document will refer to the iPhone, iPod touch, and iPad devices inclusively. A. Features Not Supported 1.) The iPhone devices do not support Tasks. B. NotifyLink Server Things to Know and Outstanding Issues 1.) If your iPhone device had contact and calendar data on it prior to registration, Contact and Calendar synchronization will default to OFF to prevent existing data from being removed. You can enable Contact and Calendar synchronization by enabling them on the device. For more details, see Knowledge Base article 647. On devices running OS 3.0, you may choose to have existing data kept on the device in a separate area or deleted and replaced with what syncs from the server. With older OS versions, turning synchronization ON will delete existing items. 8861 / 8864 / 10686 2.) For the iPhone 3GS and iPad, a Remote Wipe is completed immediately when the request is received by the device. For all other iPhone devices, the estimated time for completing a Remote Wipe is 1 hour per 8GB of space on the device. 8868 3.) This issue applies to iPhone device users operating on a CommuniGate Pro, GroupWise, Scalix, or Zimbra server. Moving a contact on the server into a different selected address book results in the contact appearing in both address books on the device. Deletion of or 5/8/10 Page 8 of 14
  9. 9. Notify Technology Corporation - Confidential further changes to the contact, made on the server, will only affect the contact in the new address book on the device. 9667 4.) This issue applies to iPhone device users operating on an Exchange or Kerio server. A contact created on the device may contain fields not supported by the NotifyLink Enterprise Server. However, should the contact be moved on the server into a different selected address book, the unsupported fields will be cleared on the device when the change is synchronized. 9678 5.) Received meeting invitations appear as both an item in the iPhone device Calendar and as an email in the Inbox with the meeting invitation attached. Meeting invitation recipients may respond to the meeting from either the calendar or the Inbox. Users may also experience the following scenarios depending on the groupware system they are operating on. 9012 a. Users of Mirapoint, Google, Oracle 10, Oracle Beehive, Oracle CalDAV, Zimbra and Zimbra CalDAV will also receive a second email for each invitation. This email cannot be used to respond to the meeting on the device. b. Users of MeetingMaker, which does not support email, may receive a second email if their email user was also invited to the meeting. This email cannot be used to respond to the meeting on the device. c. Users of FirstClass and MDaemon will receive an email, but not a meeting invitation. 6.) In some situations, recurring meeting invitations synchronize incorrectly to iPhone devices. 9168 a. If a recurring meeting invitation is created on an Oracle or GroupWise server with some of the instances occurring on past dates, invitations for those instances appear in the device's Calendar Inbox and the Mail Inbox. However, if a single instance meeting invitation is created with a past date, it appears only in the device's Mail Inbox. b. A recurring meeting invitation created using Scalix Connect for Outlook will appear as one long multi-day event, until it is accepted. Once accepted, the individual instances of the recurring meeting appear correctly. Example: A recurring meeting created to occur on Mondays for 4 weeks initially appears as a month long event. Once accepted, the 4 individual instances of the recurrence appear correctly. c. For a recurring meeting invitation created using Scalix Web Access, only the first instance of the recurring meeting appears on the device until it is accepted. Once accepted, all instances appear correctly. 7.) This issue involves meeting invitation responses viewed on the iPhone devices. When the sender of a meeting invitation views the response from an attendee that has included text with his/her response, the text is only visible when viewed from the message list. When the message is opened, the added text is not visible and an .ics file is attached but cannot be opened. 11661 8.) This issue applies to iPhone device users operating on an Oracle Beehive server. A recurring series created on the device and synchronized to the server results in duplicates on the device. The server sends a copy of each individual instance back to the device resulting in duplications. This issue is resolved when NLES Update 8 (v4.6.1) is applied. 10407 C. iPhone device Things to Know and Outstanding Issues 1.) After disabling the "Lock Enabled" user IT policy in the NotifyLink Administrative Web, the Passcode prompt still displays after inactivity. This is normal behavior, disabling the feature simply exposes an option that allows the user to turn the passcode off. However, disabling "Lock Enabled" does not consistently enable the "Turn Passcode Off" option on the iPhone device. For more details, see Knowledge Base article 383. 9098 5/8/10 Page 9 of 14
  10. 10. Notify Technology Corporation - Confidential 2.) If "Drafts" folder is selected for folder monitoring in the NLES web, two "Drafts" folders may appear in the iPhone device folder list, each with a different function. One is displayed with a Drafts icon and is used for saving messages originating on the device. The other is displayed as a regular folder and is synchronized with the server's "Drafts" folder. This may or may not occur, depending on the version of firmware the device is running. 9378 3.) The “Sent” and “Trash” folders on the device are always named as such; the names will not necessarily match the name of the folder in the user’s collaboration suite. 4.) iPhone devices with multiple email folders tagged for synchronization, will synchronize only the Inbox folder automatically in Push mode. On devices running OS 3.0, however, other folders (excluding Trash) can be selected to automatically synchronize like the Inbox. See Knowledge Base article 409 for more details. 9155 5.) When a message is moved from one folder to another on the iPhone device, it is not viewable until the message change synchronizes to the server and then back down to the device. This is expected behavior of the iPhone device. 8886 6.) When you forward an email containing some attachment types from the iPhone device, the recipient receives the attachment, plus an extra .htm attachment. These file type attachments have been observed to produce the extra file: doc, xls, ppt, bmp, txt, gif, jpeg, tif, pdf, vcf, png, tiff. 8752 7.) This issue occurs with iPhone devices running the OS v3.1. When the user receives an email that has an email attachment (file type .eml or .msg) the attachment will be displayed on the device but when opened will contain no information. Note that this issue did not occur with OS v3.0 of the devices. 11761 8.) Beehive users viewing messages from the Zimbra web will see that email with attachments sent from an iPhone device are missing the paperclip icon in the message list. However, the attachments are present when the email is opened. 11096 9.) A large .docx file (MS Word 2007), sent to the iPhone device as an attachment, may not be viewable. When the user attempts to open the attachment, the iPhone device may shut down. The minimum file size for which this occurs is not known. 8754 10.)Email with a large recipients list does not synchronize to the iPhone device. The email is sent to the device, but the device either: 8964 a. times out and closes the connection before it receives the email b. recevies the email, but exits to the home screen when attempting to open it 11.)When using an iPhone device with NotifyLink, if you forward an email that has an attachment to another user on NotifyLink, the recipient cannot view the attachment on their device. This is a result of the MIME format sent by the device being incorrect. 12693 12.)This issue applies to iPhone / iPod touch devices running OS 3.0 and using a WiFi connection. If the connection to the NotifyLink ActiveSync Server returns a 500 error, the email (and possilby PIM) data is deleted from the device. This issue no longer occurs with iPhone OS v3.1.1. 11380 13.)iPhone Contacts have fields for Custom and Other phone numbers and for Ringtone. If used, the iPhone does not send these fields to the server. The contact will be missing these fields when viewed on the server. In addition, if any change is made to the contact on the server, it is synchronized back to the device. Since the contact change coming from the server does not contain the custom/other phone number fields, they are deleted on the device. Ringtone, however, is preserved on the device. On devices running OS v3.0, Customer and Other phone number fields are no longer part of the Contacts application for an ActiveSync account, therefore only the Ringtone note applies. 8814 14.)When creating a contact on the iPhone/iPod touch and the country field is left as the default, it is not synchronized to the server. A workaround is to change the default country and then change it back to the default before saving the contact. 8987 15.)Some non-numeric characters (hyphen and period) used in the phone number fields of a contact created on the server, do not synchronize to the iPhone/iPod touch. 8986 5/8/10 Page 10 of 14
  11. 11. Notify Technology Corporation - Confidential 16.)When a remote lookup is done on an iPhone/iPod touch device, the search returns a maximum of only 26 results and does not provide an option to retrieve more search results. A workaround for this is to further refine the search by adding one or more additional characters to the search entry. On devices running OS 3.0, however, the search returns a maximum of 51 results. 8999 17.)The iPhone/iPod touch user's account must be configured to synchronize contacts before remote lookup is available in the Contacts application (this does not apply to devices running OS v3.0). Contact synchronization is not a prerequisite for using remote lookup while composing mail, however. As long as your NotifyLink account is set up to access the LDAP server, when you begin to type an email address in the To/Cc/Bcc fields, the device will automatically perform a remote lookup based on the characters you enter. For more details, see Knowledge Base article 669. 9023 18.)When an instance of a recurring event is modified from the device, a duplicate of the exception appears on the iPhone/iPod touch. The instance appears in its original form along with the modified form. The duplicates also appear on the server. This issue has been fixed in iPhone/iPod touch devices running OS v3.0. 8767 / 8876 19.)Recurring events created on the server to end on a specific date appear on the iPhone device with the end date one day late. The end date is correct, however, on the client's calendar display on the server. This issue has been fixed in iPhone/iPod touch devices running OS v3.0. 8714 20.)Monthly recurring events for the 31st of the month, created on the server or the device appear on the iPhone/iPod touch calendar only in the months with 31 days. On the server or in Outlook, the events appear on the last day of the month regardless of the number of days in the month. Furthermore, the event will appear for the number of occurrences specified, but only in months with 31 days. 8750 21.)A recurring series can be created in Outlook for events that occur on the first weekday, first weekend day, or first day of the month or year. These patterns are not supported on the iPhone. The events will show up on the device calendar, but not in the expected pattern. 8751 22.)When an exception to a recurring event is created on an iPhone/iPod touch device by deleting a field (such as the location), the deletion is not rendered on the server even though the item appears as an exception. 11229 23.)A single calendar event changed to a recurring event on an iPhone/iPod touch may end one day early (specified end date is one day earlier) on the server. This may or may not occur, based on the firmware the device is running. 9532 24.)iPhone calendar allows you to respond to a meeting a second time and change your response if you originally responded with an "Accept" or "Tentative." If you respond a second time, however, using the responses in the calendar item, the MeetingResponse command is not sent and the item is not updated with the response. The device does send an email to the meeting organizer and a change for the calendar event (with no information about the response). 10483 25.)An all day meeting invitation appears on the iPhone/iPod touch Calendar application Invitations list with a date one day prior to the actual event. When the details of the item are viewed, however, the date is correct. 11333 26.)The iPhone/iPod touch allows users to respond to the same meeting invitation multiple times, however, if the device is running an OS less than 3.1 it sends only the first response and does not send subsequent responses should the user wish to change his/her response. This issue has been resolved with the iPhone OS version 3.1. 10483 5/8/10 Page 11 of 14
  12. 12. Notify Technology Corporation - Confidential VI. Specifics for webOS devices A. Features Not Supported 1.) webOS devices do not have capability to send meeting requests. You can receive and respond to meeting invitations on a webOS device, however, you cannot create meeting invitations. 11169 B. NotifyLink Server Things to Know and Outstanding Issues 1.) Clearing data out of a Contact's Notes or Job Title fields does not synchronize correctly. If the data in the Notes or Job Title field of a contact is removed, the deletion does not always synchronize correctly. If the edit (clearing out of the data) is done on the device, the Job Title is correctly removed from the contact on the server. However, in all other situations the data removal is not performed correctly. 11806 2.) This issue applies to Contacts created on a webOS device. The contact will synchronize to the server and will also sometimes send a subsequent “change" shortly after even if no change actually occurred. After this change is processed by the server, the Display Name may be removed from the contact on the server. This is not consistently reproducible. 11185 3.) Only tasks created from a task list associated with the Exchange account on the webOS device will synchronize to the NotifyLink server. Likewise, only task changes or deletions made to tasks that specifically belong to the Exchange account will synchronized. 11182 C. webOS Things to Know and Outstanding Issues 1.) Palm continually provides operating system updates to your webOS device to enhance performance and add functionality. Update notifications are sent to your phone automatically when a system update is available. For a time, you have the option to postpone installation, however, eventually the phone will automatically install the update, as long as the battery has a 30% charge. Notify Technology tests webOS updates as soon as possible, however, please be aware that functionality may change as a result of updates and new versions may not be supported as soon as they are available. 2.) webOS sends incorrect information about the device OS version, which appears on the NotifyLink Administrative Web Device Statistics page. 11274 3.) The webOS devices have a single font, Prelude, which supports the following codepages. In terms of languages, this includes Afrikaans, Albanian, Basque, Belarusian, Bulgarian, Catalan, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Icelandic, Indonesian, Italian, Latvian, Lithuanian, Macedonian, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Turkish, and Ukrainian. Additionally, there is also now support for Chinese, Japanese, and Korean characters as well. There are still some issues with the Chinese fonts in terms of style though. As a result, data synchronized by NotifyLink that contains characters not in the supported sets will show up as empty blocks/squares on the device. 11814 a. Windows 1250 Latin 2 Eastern Europe / Mac OS Central European b. Windows 1251 Cyrillic / Mac OS Cyrillic c. Windows 1252 Latin 1 / Mac OS Roman d. Windows 1253 Greek / Mac OS Greek e. Windows 1254 Turkish / Mac OS Turkish f. Windows 1257 Baltic g. Mac OS Romanian h. Mac OS Croatian i. Mac OS Icelandic 5/8/10 Page 12 of 14
  13. 13. Notify Technology Corporation - Confidential j. Mac OS Turkish 4.) webOS devices will not use WiFi if operating in Direct Push mode (As items arrive). If WiFi is on and the device is set to get mail As items arrive (Direct Push mode), it will attempt to use the carrier network to connect. However, if the device is registered against the internal IP address of the server, attempts to connect through the carrier network will fail as well. 11610 5.) webOS devices do not distinguish between email that is normal and low priority Email delivered to the webOS device will correctly indicate if the item is high priority. Normal and low priority email, however, look the same as one another. 11736 6.) This issue was found on devices with webOS version 1.4.0. Attempting to open an email that has no body, but one or more attachments, will show an error that the message could not be downloaded and so you cannot reply or forward the message. 12699 7.) webOS devices (v1.2.1) will only allow synchronization of one address book, however, you may choose which folder to synchronize via the NotifyLink Client or Administrative Web. The setting default is your main contact folder or address book. If you change this you must reregister the device. 11150 8.) webOS devices support contact fields that ActiveSync protocol does not. When these fields are added to a contact on the device, the extra data is stored in the Contact Notes field on the server. 11555 9.) The webOS devices do not always send tasks adds, edits, and deletes to the server as soon as the modification is performed. As a work around, you can make a change to the Calendar. This will force the device to synchronize task changes as well. 11182 VII. Specifics for Windows Mobile devices A. Features Not Supported 1.) Although the Windows Mobile ActiveSync device allows adding, editing, or deleting folders on the device, this is not supported by NotifyLink. Therefore, if a user adds a folder on the device, it will be deleted immediately. Attempts to edit or delete a native folder will not be successful. 10409 B. NotifyLink Server Things to Know and Outstanding Issues 1.) Windows Mobile ActiveSync devices may not be able to register if Integrated Windows authentication is enabled on the "sync" virtual directory. This is primarily seen on devices that have the 6.5 operating system. 12774 2.) Local PIM data that exists on a Windows Mobile device when a device is registered is sent to the server at registration time. When the device is registered, it retrieves the items from the server, and sends the items that were on the device before registration, to the server. The items are removed from the device. To get the items which were sent to the server back on the device, remove the account and reregister the account. The items, which now reside on the server, will synchronize to the device. Calendar items must fall within the synchronization range, however, in order to synchronize. 8861 3.) To synchronize folders other than the Inbox, the folder must be selected in both NotifyLink and the ActiveSync client on the device. For more details, see Knowledge Base article 727 and 728. 9465 / 9470 4.) Email that has been moved to an alternate folder on the device may appear to "disappear" from the device, however, the change is successful on the server. This occurs when a folder has been selected for synchronization in the NotifyLink web, but not 5/8/10 Page 13 of 14
  14. 14. Notify Technology Corporation - Confidential selected for synchronization on the device. Folders can be selected on the device by going to the device Inbox, tap Menu > Tools > Manage Folders. Check mark the folders you wish to synchronize. For more details, see Knowledge Base article 728. 11225 5.) Under some conditions, an error popup with the message “A problem has occurred with repllog.exe.” is displayed. One cause is a meeting invitation that contains an attendee with email address longer than 26 characters. The error does not cause any loss of funcationality and, as a workaround, it may be disabled. On the device, navigate to Settings > System > Open "Error Reporting"; Select "Disable error reporting" and ok. 11230 6.) A Windows Mobile ActiveSync (WM AS) device does not always display Calendar or Task notes as expected. When blank lines are entered in the notes field of a Calendar Event or Task created on the server, they appear as spaces when viewed from the WM AS device. 12193 7.) If you create a contact on a Meeting Maker server and change the category from a Windows Mobile ActiveSync device, the change will not synchronize to the server correctly. The contact will be listed with a ctegory of "None" in the Meeting Maker client. Other changes to the contact made on the device will synchronize to the server correctly. 12665 C. Windows Mobile Things to Know and Outstanding Issues 1.) When security rules have been enforced for a Windows Mobile ActiveSync devices from the NotifyLink Enterprise Server, the lock password cannot be disabled on the device. If the user account is removed from the device while this policy is still in place, the lock remains enabled and cannot be disabled. For more details, see Knowledge Base article 679. 11292 2.) When a remote lookup is done on a Windows Mobile device, the search returns a maximum of 100. If a full 100 matches are returned, before displaying the results, the device shows a warning to narrow down your search. 8999 3.) With Windows Mobile ActiveSync, the Deleted Items folder synchronizes in only one direction, from the device to the server. Items in the Deleted Items folder on a user's PC will not appear on the device. 9471 4.) When an email is sent as an attachment through the Mirapoint web to a Windows Mobile ActiveSync device, the device displays the subject of attached email incorrectly. This is most likely to occur when the subject of the attached email contains Upper ASCII. 12001 5.) The Windows Mobile device will only allow synchronization of one address book. The NotifyLink web console will only allow selection of a single address book for the user. 11210 6.) If a new contact is created on the device and assigned to a category which does not exist on the server, the contact will be added to the default address book instead of the assigned category. The new category is not created on the server. 11211 7.) A custom response to a meeting is never received by the event organizer. The organizer does, however, get the response, just not the custom text. 11213 5/8/10 Page 14 of 14

×