Install and configuration issues
Table 1. Install and configuration issues
A mobile device user cannot complete registration if the user home mail server is down.
During the registration of a mobile device with IBM Notes Traveler, the IBM Notes Traveler server reads the user home mail server and mail path name from the Domino® directory. It then attempts to contact this mail server to determine if there are any replica mail databases configured for the user. If this home mail server is down during the registration attempt, registration may fail until this server is brought back online or the home mail server entry for this user is changed to a different mail server in the Domino directory.
Once registration is complete and the IBM Notes Traveler server learns the locations of the mail replicas, then IBM Notes Traveler can redirect push and sync operations to other replicas if the home server is down.
Problems with migrating security data from an enterprise database.
When you configure a stand alone server to use an Enterprise database, the server will migrate existing user and security information to the Enterprise Database. However, if you are moving from an enterprise database to another database, enterprise or standalone, no user or security data is migrated.
General server issues
Table 2. General server issues
Items marked as Private or with $Reader fields that do not contain the IBM Notes Traveler server cannot be synced to the device. This includes mail, calendar, to do, journal and contacts items.
Any document marked Private can only be viewed by the user. IBM Notes Traveler is a server and runs as the server ID. As a result, it is not the user and by definition does not have access to the document.
IBM Notes Traveler authentication does not work correctly when the Domino server is configured to use Security Assertion Markup Language (SAML).
The means by which the SAML identity provider passes the authentication assertion to Domino is currently unsupported in the IBM Notes Traveler environment.
Syncing large items from device to server may be rejected by HTTP's size or timeout limits.
If the device tries to sync a large (many MB) item in a single HTTP request to the server, the server's HTTP limits may reject the request because it took too long to be made or was over the allowed request size limit. For example, trying to send a large mail with attachments from an Apple iOS, Windows Phone, Windows Tablet or BlackBerry device may fail as the Exchange ActiveSync protocol does not break up the request into multiple requests; sending of attachment data is normally encoded per internet specification which will increase the size by about a third, so the encoded data size is the one that applies. The HTTP limits are in the server document:
Server Document > Internet Protocols > HTTP > Timeouts
Server Document > Internet Protocols > HTTP > Protocol Limits
Maximum size of request content
Server Document > Internet Protocols > Domino Web Engine > POST Data
Maximum POST data (in kilobytes)
Table 3. Mail issues
Mail messages deleted on a mobile device do not display in the Deleted Items (Trash) folder on the device.
Mail messages deleted on a mobile device do not display in the Deleted Items (Trash) folder on the device.
The trash, follow-up, and/or junk folder is not synced.
These folders in IBM Domino are views and not real folders. Therefore when monitoring folder activity, IBM Notes Traveler does not receive notifications related to these folders.
Execution Security Alert popup when opening a mail folder using a Notes client.
If you create a mail folder on a mobile device that supports mail folder operations using the IBM Notes Traveler client, the folder will be created in your mail database using the IBM Traveler server. Since folders are design elements and must be digitally signed, the folder will have the signature of the IBM Notes Traveler server that created it. By default, your Notes client will warn you when it detects a signature it has not seen before and will ask permission to allow the action requested by the folder. If you see this warning, select Start trusting the signer to execute this action so that you will not see this prompt again for this action.
Mail attachments are not always included on reply and forward.
If you are replying to or forwarding a mail message on the mobile device that has had its attachments removed because of IBM Notes Traveler truncation options, then you must first retrieve the complete email message and reply to or forward it from the device. This same restriction applies to a large amount of email body text that may have been truncated. In order to resend the entire message from the device, it must first be retrieved using the Download Message option.
Mail documents only appear in one folder.
The IBM Notes Client allows a single mail document to be in multiple folders or views, but the mail application on the device only allows a single mail document in a single folder. Therefore, the device will only show the mail document in the most recent folder. Sent and Drafts are special in that they are always the "most recent" if the document appears in either one of them.
Folders created on the mobile device do not appear on the Domino server
If you create a folder on the mobile device, it does not appear on the Domino server until after the mail database is closed and reopened.
The "Continue Search on Server..." feature does not work.
This makes an Exchange ActiveSync search request to the server for mail with the criteria the user defines. IBM Notes Traveler currently treats all searches as name look-ups and, as a result, does not return anything the device expects.
Sending encrypted mails from a device to Group recipients is not supported.
The sender will receive a notification mail that the message was not sent. The mail will be saved to the Drafts folder.
Table 4. Calendar issues
Calendar filtering does not apply to individual instances of recurring meetings and appointments.
If a recurring meeting includes some instances that match the criteria of the calendar filter and some that do not, all of the meeting instances are synced to the device.
You cannot change repeat settings for a calendar entry after the repeating entry is created.
Notes does not allow you to change the repeat setting for a calendar entry after it has been created. For example, you cannot change a weekly repeating entry to a daily repeating entry or change a non-repeating entry to a repeating entry.
Not all instances of a repeating meeting display.
If the user creates an infinite event from the device, the Traveler server truncates the event to either 10 instances if there is a yearly repeat rule, or 250 instances otherwise.
Calendar entries past the year 2067, on both the device and server, are not synchronized.
Multiple instances of a repeating calendar event in Notes that occur within the same day are not supported.
If a repeating calendar event contains multiple instances for the same day and in the same time zone that the event occurs, only one of the instances for that day is sent to the mobile device. IBM Notes Traveler does not support multiple instances of a repeating calendar event on the same day, with respect to the time zone of the device.
Limitations with attachments and calendar events.
You cannot add attachments to calendar events, or view attachments in calendar events.
Limitations when using Room and Resource information in calendar events.
The ROOM field is appended to the Location field when the event syncs to the device. The IBM Notes calendar ROOM field cannot be updated from the device. The RESOURCE field is not supported.
Delegate and Propose new time are not supported.
None of the device contacts applications support synchronization of groups, so the server will not send group information to the devices and Propose new time actions are not supported.
Meeting notices deleted from a mobile device by a meeting participant still appear in the participant's All Meetings view.
When a calendar event is deleted from the device, the Domino server removes the meeting notice from the calendar view; however, the meeting notice still appears in the All Meetings view.
Changes made to Domino federated calendar entries are not synced to the server.
If you configure your IBM Notes Calendar to display multiple calendar sources and for viewing even when the Notes client is offline, the calendar will sync to a IBM Notes Traveler device calendar. However, you should not modify these calendar events on the device. If you modify or delete one of these events on the device, the original event will sync back from the server and overwrite the changed event on the device.
Start date is missing from To-do entry
Both “Start” and “Due Date” are required fields for tasks. If you have a start date but no Due Date, the start date will be lost.
Online Meeting type 'Other' not supported
Traveler does not currently synchronize Online Meetings created with type 'Other' to devices.
Attendee status is not synced to Mobile devices.
At this time, attendee status is not maintained between server and device. The server copy of the event should have the correct attendee status. Some mobile devices generate their own attendee status but this may or may not match the status shown on the server.
To do issues
Table 5. To do issues
Start date is the due date
The due date is a required field for tasks. If you have a start date but no due date, the start date is set as the due date. If you do not specify both “Start” and “Due” date, the due date is set as Today.
Unable to change the repeat rule for a To-do item after it is created
IBM Notes does not allow you to change the repeat rule for a task after it has been created. For example, you cannot change from a weekly to a daily repeat, or between non-repeating and repeating.
Out of office isues
Table 6. Out of office issues
Dates appear with **** or 9999 as the year in IBM Notes/iNotes.
Domino 9.0 Interim Fix 2 or greater is required for out of office usage in IBM Notes Traveler. Without this interim fix, certain actions when setting out of office will cause the leaving and returning dates to appear incorrect in IBM Notes and iNotes. To return from this state, disable and re-enable out of office from Notes/iNotes.
Some out of office values appear different between IBM Notes/iNotes and IBM Notes Traveler.
IBM Notes/iNotes can display old information if cached values are used. Restart the IBM Notes client or browser to refresh the information. Alternatively, ensure the device being used is connected to the IBM Notes Traveler server, and is not having trouble sending/receiving data to/from it.
Out of office appears to be off in IBM Notes/iNotes, but on in IBM Notes Traveler.
The out of office away period can be accidentally extended if the return date is modified before the disabling of out of office has fully taken effect. In order to guarantee that out of office is fully disabled, wait for the out of office summary mail to arrive in the user's inbox before making changes to the out of office leaving or returning date/times. Additionally, out of office may remain temporarily enabled if it was disabled from Notes/iNotes on a computer with a system clock that is ahead of the mail server's system clock. Out of office will be disabled once the time on the mail server has reached the time that it was disabled from Notes/iNotes.
Out of office appears to be on in IBM Notes/iNotes, but off in IBM Notes Traveler. Sending mail to the user does not yield an out of office reply.
When the end date is in the past, the out of office service will automatically disable, which is shown by IBM Notes Traveler as out of office being off. No out of office replies will be sent at that time. Once the current date and time are within the out of office window, IBM Notes Traveler will show out of office as on again.
The returning date in IBM Notes/iNotes is in the year 2050.
IBM Notes Traveler uses 12/30/2050 as the theoretical end date for an indefinite out of office period. To turn off indefinite out of office, disable out of office or turn off Indefinite from an Android or iOS device. Out of office enabled on BlackBerry 10 or Windows Phone devices will always be indefinite.
The out of office returning time was set on the device, but the out of office reply message does not include the time component.
Using Notes/iNotes, check the Specify Times check box to allow times to be included in any future out of office reply messages.
The leaving and/or returning dates on the device appear to be today and/or tomorrow instead of the set date.
Out of office leaving and returning date/times cannot sync to devices if all of the following conditions are true:
- Out of office is running as an agent
- Out of office is disabled
- iNotes was last used to modify out of office.
Using IBM Notes or enabling out of office will allow the dates to sync to the device again.
Table 7. Contacts issues
Personal groups do not synchronize to the device contacts application.
The contacts application does not support synchronization of groups.
|Repeated contact update sync may reduce battery life.||Contact updates may repeatedly sync if syncing a Mobile device against a Notes Traveler 9.x or later server and also syncing a Mobile device against a Notes Traveler 8.x server. To avoid this scenario ensure all mobile devices are either pointed to 9.x or later servers or all are pointed to 8.x servers.|
Table 8. Administration issues
When using the web based administration feature and the Microsoft™ Internet Explorer browser, data is not displayed in views.
Make sure you are using a fully qualified internet address to access the IBM Notes Traveler server. For example, https://traveler1.company.com/LotusTraveler.nsf. If you are using only a hostname without any domain qualifiers, Internet Explorer will disable cookie support for the site. Cookies are required for the web based administration feature to work properly.
When using the web administration Approved Applications view import feature in Microsoft Internet Explorer, a message appears after file is selected stating access is denied.
You must adjust the security settings for Internet Explorer based on your environment:
1. Add the server to the Local Intranet or Internet site zone. For example, http://*.my.acme.com.
2. Modify the custom level for your zone (local intranet or internet) to allow access to data across domains.
Currently there is no security setting to govern the behavior of the Apple 5s Fingerprint scanner.
Apple device users can enable or disable the Fingerprint scanner as desired. If enabled, the fingerprint scanner will allow a user to bypass entering a device pass code when unlocking the device. The device will still prompt for passcode when it is powered on and at least once every 48 hours. This is by Apple design. No management of the Fingerprint scanner will be possible until Apple exposes the function to external management via the Apple Configuration Utility and/or ActiveSync protocol.