HCL Notes Traveler 11.0.1 FP1 available

Yesterday HCL released the FP1 for the Notes Traveler 11.0.1 including the following new features:

Support for Microsoft SQL Server 2019

Traveler 11.0.1 Fix Pack 1 has been validated with Microsoft SQL Server 2019 as the Traveler server database when running in high availability mode.

Changes in calendar notice routing

A side effect of the server support for Exchange ActiveSync (EAS) 16.1 is that meeting notices from the Apple calendar application on these devices are sent using the Traveler server’s mail.box. Routing failures can occur if the Traveler server is not configured to route mail to and from the mail servers. Meeting notices from the HCL Verse client on Apple devices are not impacted as these notices are still routed via the mail server mail.box. In configurations where customer wants to avoid routing these notices though the Traveler server then in this fixpack there is a new notes.ini setting NTS_AS_SEND_NOTICES_FROM_MAIL_SERVER that can be used to route the notices via the user’s mail server mail.box. Note that this setting does not apply to notices sent from HCL Verse mobile clients. For more information, see the updated knowledge article Traveler 11 Calendar Notice Routing Considerations for Apple iOS and iPadOS Devices.

Also some fixes are included in this FP1:

Traveler warning Unexpected tag in Options: Class
Details:
Exchange ActiveSync 14.0 moved the Class XML element for GetItemEstimate commands from being a child of Collection to a child of Options which is a child of Collection. Traveler was not looking for Class as a child of Options and was logging a warning indicating an unknown child of Options was detected on the GetItemEstimate request. Traveler now expects Class to be a child of Options and no longer logs an incorrect warning. Traveler does not use the Class value, so there is no functional change – only no longer incorrectly logging the warning.

Display name of groups with / on their names
Details:
Display names for email addresses have been compacted by Traveler to the content before the first forward slash to save user interface space on the devices. However, some customers have asked that the full display name be used, so new notes.ini’s have been added to give customers more display name options.
NTS_ADDRESSCACHE_ENCODING_DISPLAY_NAME_COMPACT controls the display name for addresses that are not internet addresses and need to be encoded as described in “Address encoding for Microsoft Exchange ActiveSync devices” of the Traveler documentation. The default is true which means the display name is the content up to the first forward slash.
NTS_ADDRESSCACHE_DISPLAY_NAME_COMPACT controls the display name for all other (not encoded) addresses. The default is true which means the display name is the content up to the first forward slash.

Provide an option to avoid routing meeting notices via the Traveler server’s mail.box when making changes from the Apple iOS or iPadOS Calendar application
Details:
Invitations and other meeting notices will be routed via the Traveler server’s mail.box when the meeting chair creates or updates the meeting from an Apple iOS or iPadOS Calendar application on a device syncing with Microsoft Exchange ActiveSync 16.0 or 16.1. This is the default behavior for HCL Traveler version 11.0 and later (note that there was no change in meeting notice routing from HCL Verse mobile clients). Failure to have routing and connection documents configured on the HCL Traveler server to/from the mail servers can prevent meeting notices from being received by the chair and/or invitees of the meeting.  To avoid routing these notices through the HCL Traveler server, the notes.ini setting NTS_AS_SEND_NOTICES_FROM_MAIL_SERVER can be set to True to route the notices via the user’s mail server mail.box. Product documentation will be updated with this new setting. For more details on the issue, see the updated knowledge article Traveler 11 Calendar Notice Routing Considerations for Apple iOS and iPadOS Devices.

You can check further informations here: https://bit.ly/2Xr7bGA

Verse app 10.0.13.0 on Android is not syncing calendar entries after upgrade to Traveler 11

A question was asked on the HCL support forum ( https://bit.ly/3a2hiWt ) because after upgrading Traveler to V11 just calendar entries have not been synced to Android devices.

The cause has been located and will be fixed like mentioned as answer:

We have determined the cause of this issue and have a fix for it in the HCL Verse Android Google Play Store beta slot. We are beginning the production deployment of the fix via the Google PlayStore at this time which should complete by Wed Jan 15th. This issue can affect Verse Android client apps with versions from 10.0.11->10.0.13 and is fixed in the 11.0.0 version (202001092238) of the app.

If a single user is experiencing this issue, the simplest solution is to have them open the Verse App on their device and click the overflow menu in the upper right hand corner of the UI and select Tools->Replace Data and select “Mail and Calendar”. Once the Replace Data is complete, the issue will be resolved. For larger sets of users the suggestion above using “traveler reset” can be used.

If you want to reset all Android devices you can download an agent here:

https://www.dropbox.com/s/cmwy4uk57b0fjm2/Traveler_ResetAllDevices.txt?dl=0

Request is empty and command SendMail is expected to have a body.

Today I had the issue on a customer site that no iOS device was able to send mail after upgrading Traveler to 10.0.1.2 on Domino 9.0.1 FP10IF3, implementing a new wildcard certificate and reconfiguring the HTTP server to redirect HTTP calls to HTTPs.

After some investigation I checked the console log and discovered multiple error messages:

[12DC:000C-0FEC] 10.12.2019 08:39:06 Traveler: WARNING username´s Request is empty and command SendMail is expected to have a body.

After rechecking the server document of the Notes Traveler server I checked the entry for the external URL >> http://servername.company.com. So the company did not use SSL certificates for the communication of mobile devices with their Traveler !!! Therefore no NOTES.INI entry called “NTS_EXTERNAL_URL=https://….” was set.

A small correction of the entry in the server document, setting the NOTES.INI entry via “set configuration NTS_EXTERNAL_URL=https://servername.company.com UPDATE” and a restart of the Traveler service was only half the way.

If you have this configuration of configured profiles on iOS devices WITHOUT SSL ( hopefully no one is using this anymore ) you have to remove and recreate the profile because you can´t modify the account to use SSL !

Traveler V11 – What´s new

In the current Beta 2 there are also new features included:

  • View attachments in calendar events
    When you receive an invitation from a Notes® or Verse web user that includes an attachment in the event description,
    you can now open or download the attachment from your mobile device, if your device supports the capability. Note
    that opening or downloading inline attachments or creating or editing attachments isn’t supported.
  • Support for ActiveSync 16.x
    Traveler now supports Microsoft™ Exchange ActiveSync versions 16.0 and 16.1 on iOS devices. This change allows
    for the development of future features that require this version, such as the ability to sync calendar attachments.
    Traveler automatically switches to ActiveSync 16.x when it detects devices that run on it; no user interaction is
    required.
  • Support for APNS HTTP/2
    Traveler now supports HTTP/2 for communication with Apple’s Apple Push Notification Service (APNS) servers. No
    configuration is required and there is no change in behavior.
  • Support for draft message synchronization
    Traveler now supports the syncing of draft messages on iOS. As part of Exchange ActiveSync 16.X, which Traveler
    now supports, the draft messages will sync from the server to the device and from the device to the server.
  • Support for 24+ hour meetings or events
    You can now create and modify non-repeating meetings and appointments that are longer than 24 hours.

HCL Traveler 10.0.1.2 available with important content – especially for iOS

The most important “feature” is that new APNS p12 certificates – which will expire in Juni 2020 – are included in 10.0.1.2. There are also updates in the database structure so if you are using an Enterprise Database you have to go through some configuration steps listed here: http://help.hcltechsw.com/traveler/10.0.1/UpdatingTheEnterpriseDatabase.html

The version 10.0.1.2 does not require HCL Domino 10.0.1 but at least Domino 9.0.1 FP8.

A complete listing about the fixes can be found here.

Especially for iOS users the administrators must be aware of the following issues

( https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0069584 ):

Starting with HCL Verse 10.0.7 for iOS (when it is available), the application is now transferred to an HCL Technologies Apple account and is signed by an HCL-owned certificate.

Expect the following changes:

  • The Verse application is being rebranded to HCL Verse. Not all references to IBM have been removed in this release.
  • The Verse application will no longer be able to access any data that the previous IBM signed versions had stored on the keychain. Therefore, you will be prompted for your password after you upgrade to 10.0.7 and launch the application for the first time. If you choose to remove an existing version and then install 10.0.7, then the user will be required to reconfigure the client. This is not a change in behavior. However, for reasons stated below, we recommend you upgrade over your previous version of the Verse application. Note that the same applies when upgrading from the IBM ToDos application to the HCL ToDos application (when available).
  • The device ID generated by iOS will change (clients managed by IBM Maas360 and MobileIron are not affected). Moving to the HCL account caused a change in the development team ID for the IBM Verse application. This team ID is input to the Apple API that the application uses to generate a unique device ID. The result is a different device ID which will be used when communicating with the Traveler server (in the form HCL_IOS_xxxxxxxxxx). After installing 10.0.7, the client application will look like a new device to the Traveler server. You can see your new device ID on the About screen under Verse settings, the user’s Traveler home screen or in the Traveler Administration view. A new device ID will have the following effects:
  • After you install 10.0.7 (either new or as an upgrade), the device will re-sync because Traveler treats the device as a new device because of the device ID change. You will see all mail in the all folders disappear and then start to re-populate. There is no way to avoid this re-sync, so plan accordingly.
  • A new profile document will be created for the new device ID (HCL_IOS_xxxxxxxxxx) by the Traveler server. This means all your preferences (things like days to sync, signature, etc) will be set to the defaults. However, if you take the recommended approach of upgrading (installing 10.0.7 over the top of a previous version), the Verse application will recognize the previous install and push all of your local preferences up to the server so that the new profile document is populated with your device preferences rather than the defaults.
  • If device approval is enabled on the Traveler server, the IBM Verse client may need to be re-approved depending upon the automatic approval settings.
  • The old device id (IBM_IOS_xxxxxxxxxx) will appear in the user’s device list until it is either reaped by the Traveler Server due to inactivity or deleted by the Administrator
  • The user may see duplicate notifications on the device for a period of time, typically 24 hours from the upgrade, because both the old and new device IDs are active on the server. There is no way for the new application to tell the server to stop sending notifications for the old device ID. After that period, the Traveler server will mark the old device as offline and stop sending notifications to the old device ID.

IBM Verse for Android is not affected by this change.