Migrator Notes-Exchange and editing items through EWS

Question

Hello, 
 we have problems when editing calendar items through EWS that have been migrated with MNE. No problems occur with newly created entries from Outlook or OWA, or entries that have been edited through Outlook after migration. 
 Four issues have been identified so far: 
 
 In meetings migrated from Notes mailbox test@contoso.com to Exchange mailbox test2@contoso.com , the organizer address is still set to test@contoso.com , although the organizer should be the owner of the mailbox. 
 When updating a calendar item, appointments created during MNE migration are reversed to meetings, although we correctly send the parameter SendInvitationsOrCancellationsMode.SendToNone. 
 When binding (Appointment.Bind()) to calendar entries that have been created in Notes in timezone W. Europe, have been migrated through MNE and that are correctly displayed in timezone &ldquo;W. Europe&rdquo; in Outlook, EWS returns them as created in tzone://Microsoft/Utc 
 When updating all-day events that have been created in timezone W. Europe, and providing a new time in timezone W. Europe, the time is wrongly updated to Utc. 
 
 Is there anything we can do to mitigate these issues? (Except manually editing every migrated entry through Outlook before editing it through EWS.) 
 Kind regards, 
 Alexander

Trevor Taegder · Answer

Hello Alexander, 
 
Thanks for posting to the Migrator for Notes to Exchange (MNE) community forum. I understand you are experiencing issues when editing migrated calendar items using Exchange Web Services (EWS). 
 
1.) MNE is designed to migrate Notes data to Exchange by mapping the source Notes information to the target Exchange mail system. Although MNE allows you to manually change the target mailbox to which items are migrated, it may be possible that this change could introduce limitations. We would suggest creating a Service Request to investigate this issue further. 
 
2.) Just to clarify, you are stating that MNE migrated an appointment as an appointment, but after you manually edit/update this appointment in the target it is being changed into a meeting, is that correct? We would suggest creating a Service Request to investigate this issue further. 
 
3.) Just to clarify, you are stating that MNE migrated the calendar entries using the correct time zone, as verified in Outlook, but EWS is showing the incorrect time zone, is that correct? Is this before or after modification? Have you compared this behavior to calendar entries that were natively created in Outlook/OWA? We would suggest creating a Service Request to investigate this issue further. 
 
4.) Just to clarify, you are manually updating migrated all-day calendar events that were created in the W. Europe time zone, to include a new time frame and those mail items are being updated to UTC time instead. Have you compared this behavior to calendar entries that were natively created in Outlook/OWA? We would suggest creating a Service Request to investigate this issue further. 
 
The issues you are describing here are advanced topics that will require further investigation. We will need additional information, such as the exact version of MNE used for the migration, the exact version of Domino you migrated from, the exact version of Exchange you migrated to, code you are using to make changes, migration log files, etc. In order to protect the privacy of your information, we would suggest creating a Service Request for each of these issues so that they can be thoroughly investigated.

Trevor Taegder · Answer

Thanks for the update. I understand that the items in question were migrated with MNE version 4.14.1.119. In a later hotfix version of MNE, 4.14.1.155, the following enhancement was added: 
 
TFS 674823 
 
Added support for the additional MAPI time zone properties that were introduced in Office 2007. Support for these additional MAPI time zone properties corrects a scenario where mobile devices that sync their calendar to the migrated mailbox using ActiveSync (such as iOS and Android devices) may display All Day calendar events spanning multiple days instead of one day as expected. The new configuration parameter [TimeZoneNames] has been added. 
 
IMPORTANT This enhancement contains a breaking change to the [TimeZoneInfo] Program Parameter. If your installation currently contains configuration data in the [TimeZoneInfo] section, this configuration data must be updated. See the [TimeZoneInfo] section in the NME Program Parameters Reference for details. 
 
This Enhancement Request included a redesign of the way MNE handles time zone data, which may have resolved the issue you are experiencing, as the product team is unable to reproduce the issue in the current version of MNE.