Chat now with support
Chat with Support

On Demand Migration for Email Current - Release Notes

About Quest On Demand Migration for Email

About Quest On Demand Migration for Email

This document contains On Demand Migration for Email 1.15.0.20308 (11/14/2019) release notes.

Quest® On Demand Migration for Email securely migrates data to Office 365 and on-premises Exchange or hosted Exchange email platforms leveraging a hosted infrastructure to minimize the footprint within each organization. From a single console, you can migrate multiple mailboxes simultaneously, including data such as email, calendar, contacts, and tasks.

New Features

New features and enhancements

Release 1.14.0.20157 (10/31/2019)

ODME-6312

ODME is now able to migrate Teams Chat history from the “Conversation history/Team Chat” folder.

Scope:
Migration from Exchange 2016, 2019, and Office 365

Release 1.14.0.20107 (10/28/2019)

ODME-5913

ODME remigrates mail items that were modified in the source mailbox.

Scope:
Migration from Exchange 2010, 2013, 2016, 2019, and Office 365

Release 1.14.0.19531 (08/28/2019)

ODME-6188

The maximum extraction limit for each source mailbox is increased up to 500 GB.

Scope:
All supported migration scenarios.

Release 1.13.0.18846 (07/04/2019)

ODME-5606

Support for migrating room and equipment mailbox content.

Scope:
Migration from Exchange 2010, 2013, 2016, 2019, and Office 365

Release 1.13.0.18805 (07/01/2019)

ODME-2193

The maximum size limit of a migrated mailbox is increased from 50 GB to 100 GB.

Scope:
All supported migration scenarios.

Release 1.13.0.18761 (06/24/2019)

ODME-5168

Support for Microsoft Exchange 2019 as a migration source or target.

Release 1.12.0.17546 (03/13/2019)

ODME-5143

Added support for migrating Hangouts links in the G Suite Calendar events.

The Hangouts link (including dial-in number when available) now is shown in the appointment body after migration to the target.

Scope:
Migration from G Suite

Release 1.12.0.17327 (02/25/2019)

ODME-5211

ODME remigrates Calendar items that were modified in the source mailbox and deletes target items which were removed on the source.

Scope:

Migration from Exchange 2010, 2013, 2016, and Office 365

ODME-5062 ODME now no longer migrates organization contacts from GroupWise.

Release 1.12.0.16437 (12/24/2018)

ODME-5028

For on-premises migrations only.

There are additional IP addresses that On Demand Migration for Email connects from. Please read this KB article for more details.

Release 1.12.0.16404 (12/19/2018)

ODME-4981

You can now specify up to 2047 MB (previously 112 MB) for the Maximum message size on the Options | Advanced tab within a migration plan.

Release 1.12.0.16042 (11/15/2018)

ODME-4898

Support for Zimbra 7 as a migration source.

Release 1.12.0.15978 (11/06/2018)

ODME-4472

Support for Novell GroupWise 18 as a migration source.

Release 1.12.0.15788 (10/17/2018)

ODME-4454

Folder filter options were improved for email migration. The Email section in the Options tab now includes these options:

  • Migrate All - Migrates all folders in the mailbox.
  • Exclude - Excludes the folders you select or specify (and subfolders if any) from migration.
  • Migrate Only - Available when you migrate from Exchange or Office 365, to Exchange or Office 365. This option only migrates the folders you select or specify (and subfolders if any).

For more details, see Filtering Mailbox Folders.

Release 1.12.0.15347 (09/03/2018)

ODME-3408

Added support for migration of shared mailbox data. Supported types of items include:

  • Mail items
  • Calendar items
  • Contacts
  • Tasks
  • Notes
  • Delegate access permissions
  • Folder permissions
  • OWA Inbox rules

Scope:
Migrations from Exchange 2016, 2013, 2010, 2007 and Office 365

Release 1.12.0.15319 (08/31/2018)

ODME-4277

Added the ability to migrate custom attributes for Zimbra contacts. To map such attributes to specific fields of Exchange/Office 365 contact, you should create a support request.

Scope:
Migration from Zimbra

Release 1.12.0.15174 (08/23/2018)

ODME-2349,
PT151121849

The report that you download by clicking Download Additional Details on the Audit Log page now includes a new column Start Time (UTC).

Scope:
Only for new migrations

Release 1.12.0.14764 (08/07/2018)

ODME-4046

Migration of Outlook Web App Inbox rules is now supported.

Scope:
Migrations from Office 365, Exchange 2016, 2013, and 2010.

For more details, see Migrating OWA Inbox Rules in On Demand Migration for Email User Guide.

ODME-4371 Migration of mailbox rules is now supported by Client Profile Updating Utility for the scenarios when Outlook is used to create and manage rules (together with Outlook Web App or not). For details, see Updating Outlook Client Profiles.

Release 1.11.0.14512 (07/26/2018)

ODME-3429

Migration of folder permissions is now supported.

Scope:
Migrations from Exchange or Office 365

Release 1.11.0.14440 (07/20/2018)

ODME-2998

Manage Migrations permission is now ready to deprecation and we introduce 4 new permissions: Manage Migration Plans, Execute Migration Plans, Manage Migration Plans From Templates, and Execute Migration Plans From Templates to replace Manage Migrations permission. These permissions are automatically granted to the default roles Full Administrator and Migration for Email Admin.

TIP: Now you can optimize the permission set for more granularity. For details see Roles and Permissions.

Release 1.11.0.14087 (07/04/2018)

ODME-4155

Added support for migration of mailboxes that are hidden from the Exchange Global Address List.

Scope:
Migrations from Exchange or Office 365

Release 1.11.0.14023 (07/02/2018)

ODME-4179

IBM Notes and Domino is no longer supported as a migration source.

Release 1.11.0.13533 (06/01/2018)

ODME-3919

If the full paths to the Conversation History folder are not the same between the source and target (for example, you moved the Conversation History folder to another location in the source), the folder will be migrated as a normal folder, unless you move it back to its default location in the source before migration.

Scope:
Migrations from Exchange or Office 365

Release 1.11.0.13142 (05/21/2018)

ODME-3831 Azure AD Single Sign-On is now supported to access On Demand Migration for Email.

Release 1.11.0.13028 (05/06/2018)

ODME-4016

For on-premises migrations only.

There are additional IP addresses that On Demand Migration for Email connects from. Please read this KB article for more details.

Release 1.11.0.12938 (05/01/2018)

ODME-2614,
PT135922041

Introduced a new user role "Read" providing the following abilities:

  • View the existing migration plans (including those created from a template) and templates.
  • Download and view audit logs for a migration template.
  • Download and view all types of reports for migration.

For more details, see Roles and Permissions in On Demand Migration for Email User Guide.

Release 1.11.0.12757 (04/20/2018)

ODME-3428 Migration of delegate permissions is now supported. Some limitations are applicable, for details see here for Microsoft Exchange and here for Microsoft Office 365.

Release 1.11.0.12327 (04/03/2018)

ODME-2098,
PT142668835

ODME now migrates from Lotus Notes using the MIME method by default (the latest version of Quest Domino Web Service is required).

NOTE: If you do NOT want to migrate using the MIME method, add the following to the <appSettings> section in the file web.config for the Domino Web Service, and restart Internet Information Services:

<add key="UseMimeMigration" value="false" />

Release 1.11.0.11899 (03/16/2018)

ODME-3828

Support for Microsoft Office 365 F1.

Release 1.11.0.11089 (02/05/2018)

ODME-3556

This specific instance of ODME is designed for United States Public Sector customers only and addresses their requirements of:

  • Content is stored within the United States.
  • Content is restricted to Quest personnel that are US Citizens and these personnel undergo background investigations in accordance with relevant government standards.

Release 1.11.0.10960 (01/29/2018)

ODME-3501

Maximum size limit for a message can be changed on the Options | Advanced tab.

Release 1.11.0.10866 (01/23/2018)

ODME-2169,
PT146605173

Improved the method to calculate the migration time: If a migration is completed by several parts (e.g., paused and resumed), the migration time will calculate a total for every part of the migration (the duration that the migration stays in the Rescheduled state will NOT be counted).

Release 1.11.0.10376 (12/19/2017)

ODME-2132,
PT144343763

ODME now migrates color categories from the source mailbox to the target mailbox with incremental merge.

  • Only the color categories and shortcut keys that do not exist in the target mailbox will be migrated or merged.
  • The name and color of categories that already exist in the target mailbox will not be changed.

Scope:
Migration from Exchange 2007, 2010, 2013, 2016 or Office 365 to Exchange 2010, 2013, 2016 or Office 365

Release 1.11.0.10302 (12/13/2017)

ODME-3048 Active Directory Federation Services (AD FS) is now supported to access ODME. For more details, see here.
ODME-2162 Provided online help for setting up mail forwarding for GroupWise as the source on the Options tab > Forwarding (Optional), and removed information about the forwarding actions from the documentation.

Release 1.11.0.10216 (12/08/2017)

ODME-2166

The user notification settings have been moved to the new tab Notification where you can now specify different 'From display names' and 'From email addresses' for the source and target mailboxes.

NOTE: For existing migration plans with the option Send notification to target mailbox selected previously, the 'From display name' and 'From email address' need to be specified again after this release.

ODME-3052

ODME now supports an IMAP migration using user names only.

Scope:
Migration from IMAP

ODME-2967

Enhancements to migration plans that were copied from a plan that was previously created using a template:

  • The new plan has a subtitle "Created from [template_name]" on the Dashboard.
  • The new plan will keep the connection properties and optional parameters specified by the template, and the same read only fields as the source plan.

Release 1.11.0.10155 (12/06/2017)

ODME-3136

Moving large attachments to OneDrive for Business is no longer supported.

Release 1.11.0.10037 (12/01/2017)

ODME-2151

Microsoft Exchange Server 2003 is no longer supported as a migration source.

Release 1.11.0.10002 (11/29/2017)

ODME-2977

The message filters processing is optimized to reduce number of Gmail API queries. It helps diminish the risk of exceeding the Gmail API daily usage quota.

Scope:
Migration from G Suite

 

Release 1.11.0.9986 (11/28/2017)

ODME-2959

The number of queries to Gmail API per each migrated message is reduced. It helps diminish the risk of exceeding the Gmail API daily usage quota.

Scope:
Migration from G Suite

Release 1.11.0.9577 (10/30/2017)

PT151426166,
PT152020281

For each successfully completed mailbox migration in a plan, ODME can send an email notification to the source and / or target recipient.

Scope:
Microsoft Exchange, Microsoft Office 365, G Suite

Release 1.10.0.9486 (10/19/2017)

PT150665771

New migration source and target types are supported by migration template. With the migration template, now you can migrate to Exchange and Office 365 from these platforms:

  • G Suite
  • GroupWise
  • Exchange
  • Office 365

Release 1.10.0.9384 (10/13/2017)

PT142052219

Now it is not required to enable IMAP for migrations from G Suite on the organization level unless you need 'Important' and 'Starred' target folders to have the same non-English localized names as the corresponding Gmail labels on the source.

Release 1.10.0.9298 (10/09/2017)

PT143961547

A number of mailboxes that can be migrated concurrently is not limited now.
Total number of running plans with the same administrator account is not limited now.

Also, a number of mailboxes that can be migrated concurrently per single plan is configurable: it can be adjusted to any desired value or set to unlimited. The default value is 500.

Release 1.10.0.8785 (08/24/2017)

PT146596791

ODME is now able to migrate Recoverable Items from Exchange 2010 and higher.

Scope:
Migration from Exchange 2010, 2013, 2016 and Office 365.

Release 1.10.0.8478 (08/04/2017)

PT143788655

Now you can create a migration plan from a template.
The migration template was introduced to facilitate the creation of migration plan by specifying the connection properties and optional parameters for the migration.

Release 1.10.0.8365 (07/28/2017)

PT146466199

Microsoft Exchange Server 2000 is no longer supported as a migration source.

Release 1.10.0.8150 (07/19/2017)

PT148920927

Added possibility to configure various actions with forwarding on the source for migrations from Novell GroupWise:

  • DELETE - When arrived, emails are deleted and meeting requests are declined
  • KEEP - Emails remain in the Inbox folder
  • MARK AS READ - Emails are marked as read in the Inbox folder

Release 1.10.0.7825 (06/22/2017)

PT147421857

ODME prompts users to install CPUU 5.7.2 for profile updates when migrating from Office 365 tenant to tenant with domain name transfer.

Release 1.10.0.7630 (06/12/2017)

PT141830797

Added support for migration of Sticky Notes.

Scope: Migration from Microsoft Exchange 2007, 2010, 2013, 2016 or Microsoft Office 365 to Microsoft Exchange 2010, 2013, 2016 or Microsoft Office 365.

Release 1.10.0.7594 (06/09/2017)

PT146159941

Message size limit:

  • A message (including attachments if any) that exceeds the maximum message size (35 MB by default) will be skipped during the migration.
  • If a message is smaller than the maximum message size, but it has attachments that break the size limit, the message will be migrated without the attachments.

Previously, the maximum message size was applied to a message body only.

Release 1.10.0.7496 (06/02/2017)

PT145480345

Migration of archive mailboxes from Exchange 2010 is now supported.

PT146514987

Scope: Migration from Microsoft Exchange 2010 to Microsoft Exchange 2010, 2013, 2016 or Microsoft Office 365

In case of the Move large attachments to OneDrive for Business option is not selected, both the migration throughput and content migration fidelity have been improved by using the Exchange Fast Transfer stream.

As a result, several product issues have been resolved. For details, see here.

PT146514645 Migration of mailboxes from Zimbra 6 and 7 is not supported anymore.

Release 1.10.0.7382 (05/24/2017)

PT144681547

The consumption of ODME resources was reduced for better scalability.

This enhancement was implemented to optimize the content of processing flow. As a result, the consumption of ODME resources per migrated mailbox has been decreased for the benefits of scalability.

Release 1.10.0.7334 (05/22/2017)

PT145267857

The volume of Azure storage that is used to facilitate gathering of migration statistics has been minimized. This lets you avoid excessive utilization of ODME resources in case of migration of extra-large mailboxes.

Scope:
All supported migration scenarios.

Root-cause:
ODME has the mechanism that facilitates gathering of migration statistics. This mechanism has the deficiency: excessive volume of Azure storage is consumed in case of migration of extra-large mailboxes. This deficiency leads to scalability issues that cause the migration slowdown.

PT133190503

For all supported migration scenarios, ODME internal application settings were aligned with Microsoft Azure best practices to ensure the best migration performance and scalability:

  • ODME application settings are set to process concurrent user requests
  • The Nagle’s algorithm that has a negative performance impact is turned off
PT141798857

Scope: Migration from G Suite to Exchange 2010, 2013 or 2016 and from Office 365 to Office 365

The migration performance has been increased up to 30 per cent by introducing multi-threaded upload operations.

Release 1.10.0.7241 (05/16/2017)

PT145269949 In order to allow connectivity to the source and target email service, it is required to ensure that your firewall is opened for the IP addresses used by ODME. The list of IP addresses in the About box from the ODME home page now includes only the product deployments for the current Azure region. So, the region cannot be changed once the customer account is registered.
PT142847477 Overall responsiveness of the ODME portal has been improved.

Release 1.10.0.7013 (04/28/2017)

PT142052299 Migration rescheduling strategy is improved for migrations from G Suite:
Once the size of migrated content has achieved the value of Gmail daily throttling limit, ODME pauses. The duration of this pause is calculated to ensure that the migrated content size for the last 24 hours will not exceed Gmail daily throttling limit. This is especially beneficial for migration of extra-large mailboxes.

Release 1.10.0.6949 (04/25/2017)

PT141209477 ODME deployments now include Azure cloud data center in Australia.

Release 1.10.0.6919 (04/21/2017)

PT140074101

As for migration from G Suite, the overall migration rate has been improved due to change of the message extracting protocol from IMAP to GMAIL API. Therefore daily limit for the amount of data you can extract from your G Suite source during a migration has been safely increased from 2.2GB to 10GB.

The new value will be applied to all newly created plans by default. In order to safely apply the new value to an existing plan, you need to stop the plan and update this value manually.

For details refer to Managing Google Throttling.

PT139373207 ODME deployments now include Azure cloud data center in Canada.

Release 1.10.0.6852 (04/17/2017)

PT140073637,
PT143225785

Migration performance improvement (up to 20%) through better resource utilization on Azure instance and significant enhancement of messages processing flow.

PT142138209 Migration to / from Office 365 China tenants (operated by 21Vianet) and Office 365 Germany tenants (operated by T-Systems) is fully supported now.

 

Release 1.10.0.6545 (03/31/2017)

Microsoft Azure components used in ODME have been upgraded to Azure SDK version 2.9.6 to comply with Microsoft Azure SDK retirement policies.

Release 1.10.0.6450 (03/28/2017)

PT130294827
  • The Trusted API key generation tool for Novell GroupWise 7 has been rebranded to Quest.
  • Introduced the digital signature for the Trusted API key generation tool for GroupWise 7 and Domino Web Service.

Release 1.10.0.6134 (03/16/2017)

PT130294827 Support for Microsoft Exchange 2016 as a source.

Release 1.10.0.5883 (03/02/2017)

Rebranding

  • On Demand Migration for Email has been rebranded as a Quest® product and is now called Quest® On Demand Migration for Email.
  • ODME Domino Web Service has been rebranded as Quest® Domino Web Service. Upgrade from previous versions is supported as before.
PT128642995

Scope: Migration from Microsoft Exchange 2013 and Office 365 to Microsoft Exchange 2010, 2013, 2016 or Microsoft Office 365

In case of the Move large attachments to OneDrive for Business option is not selected, both the migration throughput and content migration fidelity have been improved by using the Exchange Fast Transfer stream.

As a result, several product issues have been resolved. For details, see here.

Release 1.9.0.5790 (02/28/2017)

PT136683327

New design of the Per Mailbox Statistics report:

  • Introduced the new columns that indicate the number of the corresponding failed items: Messages Failed / Contacts Failed / Groups Failed / Appt. Failed / Tasks Failed
  • Now the report shows the latest details about the same issues repeated in multiple migration executions.
  • Items that are migrated successfully by the retry or restart operation are not considered as errors any more.

Release 1.9.0.5500 (02/10/2017)

PT138934967

Scope: Migration from G Suite, Sun ONE/iPlanet, IMAP, IBM Notes/Domino, Zimbra

The current product behavior to overcome short-term connectivity issues to the migration source has been improved. The former tactics "the second reconnection during 1 minute leads to 1 hour reschedule" did not fit well for short-term disconnections. Therefore, it was changed to "the second reconnection during 10 seconds leads to 1 hour reschedule".

Release 1.9.0.5347 (01/31/2017)

You can get the following migration reports in the CSV format directly from the Dashboard:

  • A Per Plan Migration report which shows the same data as the Migrate tab.
  • A Per Company Migration report aggregates the information from all the plans for the current company.

For more details, see Viewing Migration Reports.

Release 1.9.0.5299 (01/25/2017)

  • For the source IMAP servers that support Simple Authentication and Security Layer (SASL), like the Dovecot IMAP server, the Administrator credentials of the IMAP server can be used to migrate user mailboxes. To add the source user mailbox manually to the ODME migration plan, use the following format: <user account name>*<administrator account name> ; <administrator account password>.
  • Migration to Exchange or Office 365:
    Now ODME treats the inability to upload messages to the target due to the mailbox size quota as a fatal error and stops migration (marks the impacted mailbox as "Interrupted").

Release 1.9.0.5001 (01/12/2017)

  • Support for Novel GroupWise 2014 R2 as a source.
  • You can selectively remigrate one or several mailboxes. Now, there is no need to restart the whole migration plan if some mailboxes were not migrated.

Release 1.9.0.3342 (11/16/2016)

  • The corrupted or deleted license information of any of the customers does not affect other migrations.

Release 1.9.0.3074 (10/31/2016)

  • The default number of EWS concurrent connections per administrative account is increased from 10 to 27 for Exchange 2013, Exchange 2016 and Office 365 according to the current EWSMaxConcurrency limit. The value for Exchange 2010 remains 10.
    This change increases effectiveness of usage of administrative accounts and allows more parallel connections per the administrative account.

Release 1.9.0.2363 (09/09/2016)

  • Changed default values of the following parameters:

    • Max Reschedule Attempts: from 10 to 100
    • Max Errors Per Migration: from 500 to 10000

Release 1.9.0.2250 (08/30/2016)

  • Support for Google API upgrade from the version 1.08 to 1.15.

Release 1.9.0.1866 (07/25/2016)

  • For migrations from Exchange Server (any versions) or Office 365 to Exchange Server (any versions) or Office 365:
    we introduce an option that lets you process Outlook user profiles automatically with the help of Client Profile Update Utility 5.5.13 or later.

  • Support for Outlook 2016 profiles in addition to Outlook 2007, 2010 and 2013 profiles.
  • ODME user interface:
    now ODME shows the warning message that requires to use CPUU version 5.5.13 or later if the migration plan is configured to migrate from Exchange Server (any versions) or Office 365 to Exchange Server (any versions) or Office 365.

  • ODME can successfully exclude malformed recurring meetings with exceptions from the migration scope when migrating Calendar items from Gmail to Exchange Server or Office 365. The meetings may not be migrated correctly with the following errors in the logs: "String was not recognized as a valid DateTime..."

Release 1.9.0.917 (04/28/2016)

  • Support for IBM Notes and Domino 9 as a source.

Release 1.9.0.547 (3/24/2016)

  • The Dashboard page works faster. The page shows a list of migration plans while loading migration statuses in the background.

Resolved Issues

Resolved issues

The following is a list of issues addressed in this release.

Table 1: List of resolved issues

Defect ID Issue Description
Release 1.14.0.20128 (10/29/2019)
ODME-6334

In some cases, if mailbox processing is interrupted, the mailboxes may not be displayed in Audit log report.

Scope:
All migration scenarios

Release 1.14.0.20107 (10/28/2019)
ODME-5191

The "Start Time" and "Completion Time" columns in the "Migration Details" report are missing AM/PM values.

Scope:
All migration scenarios

Release 1.14.0.20046 (10/24/2019)
ODME-6379

ODME may fail to migrate a message with the error "Value cannot be null. Parameter name: name".

Scope:
Migration from IMAP sources

Release 1.14.0.19737 (09/21/2019)
ODME-6302

A list of migration plans on the ODME Dashboard may fail to load for some users.

Scope:
Accounts that use Azure AD Single Sign-On to access ODME

Release 1.13.0.19124 (07/24/2019)
ODME-5915

The coupon usage counter showing in the upper-right corner of the Dashboard and the migration plan page is missing when the coupon code is added to a Pay-As-You-Go subscription using the credit card payment method.

Scope:
All migration scenarios

Release 1.13.0.18700 (06/20/2019)
ODME-5759

Failed to migrate a message with the exception "There is an error in XML document (0, 0). Input string was not in a correct format".

Scope:
Migration from GroupWise 18

Release 1.13.0.18610 (06/14/2019)
ODME-5725

ODME cannot get source messages from a folder and does not migrate them due to the critical error "Exchange Web Services are not currently available for this request because none of the Client Access Servers in the destination site could process the request". In this case, migration is marked as completed and counter of migrated items shows that 0 items were migrated.

Scope:
Migration from all versions of Exchange Server or Office 365

Root cause:
ODME receives the critical error "Exchange Web Services are not currently available for this request because none of the Client Access Servers in the destination site could process the request" from Exchange server and neither stops migration session nor re-schedules it.

Fix:
Now if this error arises, the migration session will be restarted in 5 minutes.

Release 1.13.0.18394 (05/30/2019)
ODME-5529

ODME may throw the exception "Could not save: Item save operation did not succeed" while migrating a meeting cancellation message.

Scope:
Migration from Zimbra

Root cause:
The meeting’s time zone information in the source message is not complete.

Fix:
ODME now can fix the incomplete time zone information, and migrates such messages successfully.

Release 1.13.0.18137 (05/07/2019)
ODME-5530

Message attachments containing special characters (such as \ / : * ? ” < > |) in their file names or embedded message subjects cannot be successfully migrated.

Scope:
Migration from GroupWise

Fix:
Now ODME can handle special characters in attachment file names and embedded message subjects, and migrate such attachments successfully.

Release 1.12.0.18007 (04/19/2019)
ODME-5400

Appointments are not migrated from the Calendar folder.

Scope:
Migration from Exchange 2010

Root cause:

When migrating calendar appointments, the error "The property has an invalid value. ICalUid" was considered as a folder-level error and, as a result, all appointments from this folder were not migrated.

Fix:

Now messages that generate the error are skipped, and the rest of the folder migrates in "one-by-one" migration mode.

Release 1.12.0.17624 (03/21/2019)
ODME-5372

ODME stops migrating calendar items and throws the error "The operation has timed out".

Scope:
Migration from Zimbra

Root cause:

In case ODME cannot retrieve appointment details by item ID, it gets the timeout error and stops the migration process.

Fix:

Now ODME skips such appointments and continues the migration process.

Release 1.12.0.17327 (02/25/2019)
ODME-5242

The error "Failed to examine folder <foldername>" occurred during migration.

Scope:
Migration from Zimbra

Release 1.12.0.17092 (02/07/2019)
ODME-5255

ODME displays a blank page when a user attempts to download the Per Mailbox Statistics reports for a deleted plan.

Scope:
All migration scenarios

Release 1.12.0.16977 (02/01/2019)
ODME-5167

ODME throws the exception "hexadecimal value 0x00, is an invalid character" while migrating a mailbox with personal tasks that have been re-posted before.

Scope:

Migration from GroupWise

Release 1.12.0.16936 (01/30/2019)
ODME-5104

Corrupted characters are found after migration when a MIME-encoded appointment or task contains special characters (such as ä, ö, ü and ß) in the source mailbox.

Scope:

Migration from GroupWise to Office 365

Release 1.12.0.16896 (01/28/2019)
ODME-5162

The error "Invalid MIME content" occurred while migrating a message with multiple recipients with non-ASCII symbols.

Scope:

Migration from GroupWise to Office 365

Release 1.12.0.16806 (01/21/2019)
ODME-5145

Migration fails with an error "The Read method cannot be called when another read operation is pending." when more than one item exists in the Inbox folder on the source.

Scope:

Migration from POP servers

Release 1.12.0.16761 (01/18/2019)
ODME-5051

If an occurrence in a recurring event is proposed to the day of another occurrence and the proposal is accepted, a duplicate recurring event starting on the new proposed date will be found on the target after migration.

Scope:
Migration from GroupWise to Office 365

Fix:
This fix removes the duplicate recurring event on the target.

Release 1.12.0.16641 (01/14/2019)
ODME-5154

ODME keeps throwing the error "Could not save: 'An internal server error occurred. The operation failed.' " in the log due to the target mailbox size exceeds the allowable quota.

Scope:

Migration to Office 365

Fix:

In this case, ODME now stops the migration and throws only one error "Migration stopped because the target mailbox size exceeds the allowable limit" in the log.

Release 1.12.0.16449 (12/26/2018)
ODME-5039

When migrating one user’s mailbox, ODME migrates the Contacts folders shared by other users.

Scope:

Migration from GroupWise

Fix:

Contacts folders shared by other users will not be migrated after this fix.

Release 1.12.0.16396 (12/18/2018)
ODME-5021

Migration of email messages may result in creation of duplicates in the target mailbox when the timeout exception happens on uploading these messages into the target mail system. The error "Could not save..." is shown.

Root-cause:

This can happen when the target side cannot handle requests in a timely manner: it is either overloaded or a very large message (100 MB or larger) is being uploaded.

Scope:

All migration scenarios

Fix:

The retry action is not initiated when the timeout exception happens on uploading messages into the target.

Release 1.12.0.16274 (12/07/2018)
ODME-4892

ODME counts the number of messages ("estimated items" count in Migration Status) in the folders excluded from migration by the Exclude or Migrate Only option, as indicated by Log.

Scope:
All migration scenarios

Fix:
The excluded folders are skipped now and the messages in such folders are not estimated.

Release 1.12.0.16074 (11/22/2018)
ODME-4897

In certain scenarios, ODME cannot migrate folder permissions or delegates with the error "…<user> cannot be mapped to a target user or group. Ensure that it is present in permissions' mapping".
The error text is misleading - the actual root-cause is a failure when resolving a target user.

Scope:
Migrations from Exchange or Office 365

Release 1.12.0.16030 (11/13/2018)

ODME-4705

Selecting items on the Options tab might make the OWA Inbox rules checkbox (originally greyed out) available.
Scope:
All migration scenarios except migrations from Office 365, Exchange 2016, 2013, or 2010.

Fix:
ODME now hides the OWA Inbox rules checkbox when the migration source is not Office 365, Exchange 2016, 2013 or 2010.

Release 1.12.0.15926 (10/30/2018)

ODME-4844

When the option Migrate Only is selected for email migration on the Options tab, other non-email items (for example, Contacts, Calendar) that are selected on the page will not be migrated.
Scope:
Migration from Exchange or Office 365, to Exchange or Office 365

Release 1.12.0.15788 (10/17/2018)

ODME-2222,
PT141473739

Declined meetings are shown as 'Accepted' after migration.
Scope:
Migration from G Suite

Fix:
The meetings now are shown as 'Declined' after migration and can be found in the Deleted Items folder.

Release 1.12.0.15370 (09/07/2018)
ODME-4492

Self-sent emails are not migrated from G Suite in the following plan configuration: "If Inbox label is present, ignore all other labels" option is enabled together with the option "If Sent Mail label is present, ignore all other labels"

Scope:
Migration from G Suite

Release 1.12.0.15354 (09/06/2018)
ODME-4468

A user logged in to ODME via Azure Active Directory Single Sign-On cannot switch between companies registered in different data centers.

Release 1.12.0.15287 (08/29/2018)
ODME-2428,
PT147320189

A contact in a distribution list is migrated as a one-off contact even if a contact with the same SMTP address already exists in the Global Address List and/or personal contacts on the target.

Scope:
All migration scenarios except migrations from Office 365 or Exchange

Fix:
ODME now migrates the contact as a group member as long as a unique contact with the same SMTP address can be found in the GAL and/or personal contacts on the target. Also, ODME updates the contact information with the one in the GAL, if available. When more than one contact is found in the GAL or personal contacts, the contact will be migrated as a one-of contact.

Release 1.12.0.15245 (08/27/2018)
ODME-4455

HTML messages that contain non-ASCII characters can be migrated with invalid character set and displayed incorrectly after migration.

Scope:
Migration from GroupWise

Root cause:
The character set was not defined for the message body on the target.

Fix:
Now the character set provided by GroupWise is defined for every target message.

Release 1.12.0.15050 (08/16/2018)

ODME-2225,
PT131421833

Reports dashboard: filtering of the audit logs list by migration plan name does not work.

Scope:
All migration scenarios

ODME-2923,
PT101682492

When viewing the Connections/Mailboxes/Options/Migrate tabs within a plan, a long plan name at the top of the screen is truncated at a length of 38 characters with a trailing "...".

Scope:
All migration scenarios

Fix:
Now the long plan name is truncated at a length of 100 characters with a trailing "...", and the full plan name is shown in the tooltip.

Release 1.11.0.14440 (07/20/2018)
ODME-2998

Manage Templates permission scope is now limited and does not include creation of migration plan from a template.

TIP: To create migration plan from a template use the Manage Migration Plans From Templates permission. For details see Roles and Permissions.

Release 1.11.0.14087 (07/04/2018)
ODME-4221

Archived Hangout Chats are migrated with the date of migration to the target Inbox folder.

Scope:
Migration from G Suite

Fix:
Now Hangout Chats are excluded from mail migration.

ODME-4135

Estimation for folders containing messages with Hashtags fails with the error "The property Hashtags is valid only for Exchange Exchange2015 or later versions".

Scope:
Migration from Exchange 2016 and Office 365

Release 1.11.0.13932 (06/27/2018)
ODME-4077

ODME throws the error "Cannot covert MIME message to Notes Rich Text message" in the log.

Scope:
Migrations from IBM Notes and Domino

Root cause:
ODME did not retrieve a message from Notes using the MIME method as expected.

Fix:
The latest version of Quest Domino Web Service is required to fix this issue.

After this fix, ODME will try the MIME method if the message cannot be retrieved in the native way.

Release 1.11.0.13898 (06/26/2018)
ODME-3864

Added support for switching between companies when managing migration templates.

Release 1.11.0.13826 (06/22/2018)
ODME-3637

When a migration stops responding and then times out, ODME may incorrectly calculate the migration time and create the record "Mailbox was automatically paused and will resume shortly" in the log.

Scope:
All migration scenarios

Fix:
In this scenario, ODME will reschedule the migration and show the correct migration time.

Release 1.11.0.13712 (06/15/2018)
ODME-4116

If the recurring meeting occurrence was modified on the source, the meeting may not be migrated with the "Start time zone could not be resolved" error.

Scope:
Migration from GroupWise

Root cause:
On Demand Migration for Email cannot resolve a time zone for the recurring meeting that was created in the non-English locale. Modify exceptions for such meetings are not migrated.

Release 1.11.0.13520 (05/31/2018)
ODME-4036

ODME may frequently reschedule migrations when migrating messages with multiple or large attachments.

Scope:
Migrations from GroupWise

Root cause:
The connections that ODME set up to migrate attachments reached the maximum number of connections allowed by Azure Load Balancer, which triggered the reschedule during migration.

Fix:
ODME now migrates attachments with less connections.

Release 1.11.0.13429 (05/25/2018)
ODME-4061

ODME may skip a folder and throw an unexpected error during migration if the folder contains an invalid message.

Scope:
Migrations from IBM Notes and Domino

Fix:
Now only the invalid item is skipped instead of the whole folder.

Release 1.11.0.12757 (04/20/2018)
ODME-3876

The description of a calendar event in the HTML format is displayed as HTML code after migration.

Scope:
Migrations from G Suite

Release 1.11.0.12580 (04/12/2018)
ODME-3863 It prompts “Install requires IIS 6 or higher” when running the Domino Web Service installer on a Windows Server 2016 with IIS 10.
Release 1.11.0.12364 (04/05/2018)
ODME-3792 Cannot migrate unlabeled messages in the All Mail folder when a date range is specified for the migration plan.

Scope:
Migrations from G Suite

Release 1.11.0.11899 (03/16/2018)
ODME-2674 After unsuccessful migration, a mailbox license may be stuck in the "in-use" state.
Release 1.11.0.11258 (02/13/2018)
ODME-3676

ODME fails to migrate calendar items with the error "At least one property failed validation...".

Scope:
Migrations from Exchange 2013, Exchange 2016 and Office 365 to Office 365

Root cause:
Recent update in Office 365 enabled additional property constraint on calendar items.

Release 1.11.0.11089 (02/05/2018)
ODME-3450

The modified occurrences in a recurring event may be shown as individual non-recurring events in Office 365 after migration.

Scope:
All migration scenarios

Root cause:
For a recurring event with modified occurrences, ODME first migrates all the original occurrences (the ones with the old time) , then moves the modified occurrences one by one to their new time slot. If time overlap between two occurrences occurs during the move, the modified occurrence will be saved as a new non-recurring event in the Calendar, according to the EWS protocol.

Fix:
The order to move the modified occurrences has been improved to avoid the time overlap to a certain extent. This fix only covers the scenarios with simple modifications to occurrences in the series, for example, all occurrences moved forward or backwards, or simple cross move (some forward while others backwards). Complex cross move probably still result in overlap after migration.

ODME-3611 On the ODME pages, the validation of email and server name fields has been weakened to accept longer top-level domain names, such as .education, .associates, .university etc.
Release 1.11.0.10930 (01/26/2018)
ODME-3301

Messages are counted as successfully migrated when migration of some of its attachments failed.

Scope:
Migration from G Suite, Zimbra, IMAP and Exchange 2007.

ODME-2080,
PT126385313

Duplicate calendar entries are shown in Office 365 but are not visible in G Suite.

Scope:
Migration from G Suite

Root cause:
A recurring event overlapped (partly) the adjacent ones in the series after the "move" or "modify" operation, and the new event was saved as a new non-recurring event in the Calendar, but the old one was not deleted.

Fix: In the case of overlap after the fix, ODME will delete the original occurrence (the one with the old time) from the series, and create a new non-recurring event with the new time.

Release 1.11.0.10808 (01/17/2018)

ODME-2198,
PT149970606

Exception occurred during migration when mail forwarding was enabled.

Scope:
Migration from Zimbra

Release 1.11.0.10712 (01/11/2018)

ODME-2224,
PT142494325

Messages from the system Inbox folder were not migrated to the corresponding target folder (Bandeja de entrada) in Office 365 with the Spanish language setting.

Scope:
Migration from Zimbra

Root cause:
Incorrect folder mapping between the source and target mailboxes.

Release 1.11.0.10544 (12/29/2017)
ODME-3098

ODME does not reschedule a mailbox migration for transient issues like "Mailbox database offline", "Server busy", "Active Directory is unavailable", etc.

Scope:
Migration from Exchange 2010, 2013, 2016 and Office 365 to Exchange 2010, 2013, 2016 and Office 365.

Fix:
Now ODME reschedules a mailbox migration in such conditions.

Release 1.11.0.10489 (12/26/2017)
ODME-3242

Recurring meetings originated from an external Microsoft Exchange user are not migrated.

Scope:
Migration from GroupWise

Root cause:
When a GroupWise user receives a recurring meeting from Microsoft Exchange mail system, the 'Until' field of the meeting has the 'DateTime' format instead of 'Date'.

Release 1.11.0.10426 (12/22/2017)

ODME-2142,
PT143301367

Сalendar items from the archive mailbox are not migrated; the one from the primary mailbox is mistakenly migrated instead.

Scope:
Migration from Exchange 2016, 2013, 2010 and Office 365

Root-cause:
No default Calendar folder was available in the archive mailbox.

Release 1.11.0.10419 (12/22/2017)
ODME-3245

The email ‘Receive’ time is incorrect in Outlook Web Access after migration from some IMAP sources.

Scope:
Migration from IMAP sources

Release 1.11.0.10390 (12/20/2017)
ODME-3138

If the concurrency limit is enabled, ODME may falsely report mailbox status as ‘Running’, showing a greater number of currently processing mailboxes than it actually is.

Scope:
All migration scenarios
Root cause:
In certain scenarios, ODME may stop processing one mailbox and start processing another mailbox in the ‘Queued’ or ‘Rescheduled’ state, without resetting the status of the previously processed mailbox.

Release 1.11.0.10163 (12/06/2017)
ODME-3117

Client Profile Updating Utility 5.7.3 cannot update client profiles using the switch message created by ODME.

Scope:
Migration to Office 365 Germany tenants.

Root-cause:
Incorrect value for the 'Target' field in the switch message.

Release 1.11.0.9986 (11/28/2017)
ODME-2165,
PT152541460

All Gmail migrations are stopped if the Gmail API daily usage quota is exceeded.

Scope:
Migration from G Suite
Fix:
Now ODME introduces the pool of Google projects with separate quotas that reduces the risk of stopping migrations.

Release 1.11.0.9857 (11/16/2017)

ODME-2123,
PT152303759

ODME does not interrupt a mailbox migration when the target mailbox exceeds the mailbox size limit.

Scope:
Migration from Exchange 2010, 2013, 2016 and Office 365 to Exchange 2010, 2013, 2016 and Office 365.
Fix:
Now ODME interrupts mailbox migration in such conditions.

Release 1.11.0.9772 (11/13/2017)
ODME-2339,
PT152098948

Better handling of Gmail throttling.

Scope:
Migration from G Suite

Release 1.11.0.9725 (11/09/2017)
ODME-2122,
PT151516084

The feature "Move large attachments to OneDrive for Business" does not work.

Scope:
Migration to Office 365

Release 1.11.0.9596 (10/31/2017)
PT152021809

CPUU 5.7.3 cannot update client profiles with the switch message created by ODME.

Scope:
All migration scenarios
Root cause:
CPUU has been updated because RPC over HTTP reaches end of support in Office 365 on October 31, 2017, and the fields in the switch message should be updated accordingly .

Release 1.10.0.9494 (10/20/2017)
PT151995778

Cannot perform autodiscover of the mailboxes with the error “Value cannot be null. Parameter name: autodiscoverUri”.

Scope:
Migration from or to on-premises Exchange 2007, Exchange 2010, Exchange 2013 or Exchange 2016.

Root cause:
Defect was introduced with PT143961547.

PT151910571

All-day events are migrated with the UTC time zone, as a result, the events are displayed incorrectly in Outlook after migration.

Scope:
Migration from Exchange 2007, Zimbra, GroupWise, IBM Domino and G Suite.

Release 1.10.0.9384 (10/13/2017)
PT150594533 Now migration of large folders from G Suite is faster in case of rescheduling and re-migrations.
PT150877256

Non-ASCII characters in calendar items are not displayed correctly after mailbox migration.

Scope:
Migration from GroupWise

Release 1.10.0.9193 (09/26/2017)
PT113275105

ODME supports migration of a GroupWise mailbox by using the UserName (FirstnameLastname) format or the Internet address format (FirstnameLastname@domain). The Internet address format is not supported for Forwarding Settings.

Scope:
Migration from GroupWise
Fix:
Now ODME supports the Internet address format (FirstnameLastname@domain) for Forwarding Settings.

PT150081814

Duplicated content was found in the source mailbox for all migrated items.

Scope:
Migration from Exchange 2016, 2013, 2010, 2007 and Office 365

Root cause:
The migration source and target are the same mailbox.

Fix:
When auto-discovery is enabled for the migration source and target, you will get a warning message that you have specified the same mailbox for both sides. While migrating, ODME will check the unique mailbox ID for the source and target, and interrupt the migration if their IDs are the same.

PT150542851

The exception "(503) Server Unavailable" occurred continuously while migrating messages, and the number of the estimated messages was found inconsistent with the number of the migrated ones in the report.

Scope:
Migration from IBM Domino

Root-cause:
The exception was thrown by the Quest Domino Web Service while retrieving messages from a folder in the source, but ODME moved on to the next folder without handling the exception, and so on.

Workaround:
Migrate the mailbox again.
Fix:
In the case of the exception after the fix, ODME will create a record in the log, and reschedule the migration in 5 -10 minutes.

Release 1.10.0.8940 (09/06/2017)
PT150778408

ODME cannot migrate audit enabled mailboxes due to presence of the subfolder Audits in the Recoverable Items folder in the source.

Scope:
Migration from Microsoft Exchange 2010, 2013, 2016 or Microsoft Office 365

Root-cause:

Impersonated user does not have permission to access this subfolder.

Fix:
Now ODME will skip this subfolder during migration, the migration of its contents is not supported.

Release 1.10.0.8890 (09/01/2017)
PT150080895

Non-Delivery Receipts (NDR) were migrated with empty body.

Scope:
Migration from IBM Domino

Root-cause:
The Body property of NDR message composed from the IBM Notes Non-delivery receipts template was not supported.

Fix:
The Body property migration is now fully supported, and all the properties in the default Non-delivery receipts template can be found in the target after migration.

Release 1.10.0.8870 (08/31/2017)
PT150633269

ODME cannot migrate attachments with some special symbols in their names.

Scope:
Migration from non-Exchange sources

Fix:
Now these special symbols in attachment names are skipped during migration.

PT150589535

Contacts and contact groups are incorrectly displayed in Outlook Web Access.

Scope:
Migration from Exchange 2010 to Exchange 2013, 2016 and Office 365

Root cause:

OWA relies on properties that did not exist in previous versions of Exchange.

Release 1.10.0.8674 (08/18/2017)
PT150308387

Migration fails with the error "Object reference not set" if forwarding is enabled on the Google source.

Scope:
Migration from G Suite

Root cause:
Defect was introduced with PT148556353.

Release 1.10.0.8651 (08/17/2017)
PT150037853

ODME keeps trying to migrate when the Per User Rate Limit of the Gmail API is exceeded.

Scope:
Migration from G Suite

Fix:
The Gmail API now returns an error with the time of next migration attempt when the limit is exceeded. ODME now can reschedule the migration to that time.

PT149999385,
PT149998523

Migration rescheduling stops working with the issue "The mailbox database is temporarily unavailable…", and this issue is not considered as an error.

Scope:
All migration scenarios

PT149948724

Accept notifications were migrated with empty body

Scope:
Migration from IBM Domino

Root cause:
ODME cannot migrate Accept notifications as notification messages.

PT118382035

Non-Delivery Receipts (NDR) were migrated with empty body.

Scope:
Migration from IBM Domino

Root cause:
ODME cannot migrate Domino NDRs to Exchange or Office 365.

Fix:
ODME will migrate NDR as a normal message by supporting these NDR message properties:

  • To
  • Subject
  • Attachments
  • Body (partially supported): ODME now can only migrate the original message body, but the other parts of the body composed from the IBM Notes Non-delivery receipts template is not supported yet.
Release 1.10.0.8549 (08/09/2017)
PT149626635

Cannot migrate an attachment if its Record Relocation Vector (RRV) was corrupted.
Scope:
Migration from IBM Notes and Domino

Fix:
After three unsuccessful attempts to retrieve an attachment using RRV, try to renew RRV immediately.

Release 1.10.0.8537 (08/08/2017)
PT149207717

Contact photos cannot be migrated with the "refresh_token is null" exception.

Scope:
Migration from G Suite to all supported targets

Root cause:
ODME does not update the expired G Suite access token before migrating the contacts.

Fix:
Now ODME verifies the G Suite access token before migrating the contacts.

PT147576393

In the target mailbox, the Conversation History system folder hierarchy is not the same as in the source mailbox after migration.

Scope:
Migration from all Microsoft Exchange sources or Microsoft Office 365

Root cause:
In previous versions, if the Conversation History system folder was moved into any other folder (e.g. Inbox) on the source, and Conversation History system folder was enabled at the root in the target mailbox, the data from the source mailbox was migrated to the Conversation History system folder at the root level.

Fix:
In the target mailbox, the folder hierarchy will be the same as in the source mailbox after migration. If the Conversation History system folder is enabled in the target mailbox, and its full path is not the same as the one in the source mailbox, the corresponding source folder will be migrated as a normal folder.

Release 1.10.0.8422 (08/02/2017)
PT149231375

Appointments are not migrated from the Calendar folder.

Scope:
Migration from Exchange 2010

Root cause:
When migrating calendar appointments, the error "The property has an invalid value. ICalUid" was considered as a folder-level error and, as a result, all appointments from this folder were not migrated.

PT148556353

Localized source folders are incorrectly mapped to the default folders on the target Exchange server, such as Inbox, Sent Items etc.

Scope:
Migration from IMAP sources

Root cause:
Previously, ODME mapped folders based on their display name for IMAP sources.

Fix:
Now ODME identifies the folder type by its standard attributes for RFC6154-compliant IMAP servers (such as Dovecot).

PT149882223

Administrator credentials are not displayed in the ODME web interface.

Scope: Migration from Exchange 2010, 2013 or 2016.

Release 1.10.0.8266 (07/21/2017)
PT134337881

You may get the following error when migrating a subfolder of the Task type: "Failed to find or create folder Tasks/[subfolderName] (You cannot specify the FolderClass when creating a non-generic folder.)".

Scope:
Migration of tasks to Microsoft Office 365

Release 1.10.0.8150 (07/19/2017)
PT148909421

Daily quota limits handling in ODME have been aligned with the recent changes in G Suite.

Scope:
Migration from G Suite

PT149088015

Fixed rescheduling for throttling during message estimation.

Scope:
Migration from G Suite, all Microsoft Exchange sources or Microsoft Office 365.

Root cause:
Mailboxes with large amount of folders may be throttled during the estimation phase of migration. ODME did not correctly handled such situations.

Release 1.10.0.8123 (07/17/2017)
PT148736037

Migration of a non-existent mailbox from G Suite hangs when it should fail immediately.

Scope:
Migration from G Suite

Root-cause:
ODME tried to access a non-existent mailbox multiple times with large delays between attempts.

Release 1.10.0.7933 (07/04/2017)
PT147088615

A mailbox may be stuck during migration of a certain system folder in case the folder’s full path in the source mailbox differs from its path in the target mailbox.

Scope:
Migration from Microsoft Exchange 2007, 2010, 2013, 2016 or Microsoft Office 365 to Microsoft Exchange 2010, 2013, 2016 or Microsoft Office 365.

Root-cause:
ODME constructs folder mapping incorrectly.

PT146455431

Incorrect count of 'Estimated', 'Processed' or 'Skipped' items for IMAP source.

Scope:
All IMAP sources

Root-cause:
IMAP message identifiers used by ODME during migration can coincide for different messages, which results in incorrect migration and statistics gathering.

Fix:
The probability of the issue has been decreased significantly.

Release 1.10.0.7914 (07/03/2017)
PT147487029

Cannot add additional administrator credentials for the source Exchange server.

Scope:
Migration from Exchange 2010, 2013 or 2016

Root-cause:
Cannot create another pair of user name and password by clicking on the add additional admin credentials link on the Connections page when the Microsoft Exchange Server 2010, 2013 or 2016 was selected as the source platform.

PT142578617

All day events are synchronized as two day events in case of timezone mismatch on the source and target.

Scope:
Migration from Zimbra, GroupWise, IBM Domino and G Suite

Release 1.10.0.7731 (06/16/2017)
PT146679595

Mailbox migration may get stuck in the Running state with no progress.

Scope:
Migration from G Suite

Root-cause:
Re-scheduling events that are logged when the daily data extraction limit is reached cannot be handled correctly.

Release 1.10.0.7571 (06/07/2017)
PT146680911

There are excessive actions in case of re-scheduling the migration. This might lead to exceeding the daily budget limit to retrieve the data from the source mail platform.

Scope:
All supported migration scenarios.

Root-cause:
An issue with saving of intermediate migration statistics.

Release 1.10.0.7439 (05/29/2017)
PT144079365

There is a lack of some error traces in the ODME audit log but these errors are shown in the Migration Summary report.

Scope:
All supported migration scenarios.

Root-cause:
Some fields in the events were missing due to the internal issues caused by the multithreaded processing implementation of ODME.

PT145588033

In case of remigrations of the content which have been previously migrated by ODME in another migration project, the duplicates are created.

Scope:
All migration scenarios from Microsoft Exchange 2010, 2013 or Office 365 to Microsoft Exchange 2010, 2013, 2016 or Office 365 if the Move large attachments to OneDrive for Business option is not selected.

Release 1.10.0.7382 (05/24/2017)

PT143093697,
PT144014671

Migration was interrupted without any log information when a mailbox had reached the maximum extraction size limit (50 GB) or the limit of the number of migrations (10 migrations).

Scope:
All supported migration scenarios.

Fix:
The relevant information now can be found in the log when the migrations are interrupted due to the limits.

Release 1.10.0.7334 (05/22/2017)
PT145364987

If a mailbox migration plan is started for the first time, license information may not be applied for some mailboxes.

Scope:
All supported migration scenarios.

Root-cause:
ODME may fail to reserve a coupon because of the following error when several mailboxes were started at the same time: "Error reserving pre-paid license. Continuing with migration…".

Fix:
ODME avoids the situation that leads to the original exceptions.

Release 1.10.0.7125 (05/10/2017)
PT142284933

An email address contains the legacy domain name after migration when viewing in Outlook Web Access via Google Chrome or Microsoft Internet Explorer 11.

Scope:
All supported migration scenarios.

Root-cause:
An email address will be resolved as X500 address rather than SMTP address if the target Global Address List (GAL) already contains the same email address.

Fix:
After a contact is created and saved in the target, ODME will set the extended properties of the contact via SetExtendedProperty(PidLidEmail1DisplayName, "FirstName LastName"), SetExtendedProperty(PidLidEmail1AddressType, "SMTP"), SetExtendedProperty(PidLidEmail1Address, "<email_address>") and SetExtendedProperty(PidLidEmail1OriginalDisplayName, "<email_address>"). Thus, the email address will be displayed correctly in Outlook Web Access after migration according to Microsoft Office 365 support recommendations.

PT143387869

The "Display as" field for an email was populated with the email address after migration, rather than the contact name from the source.

Scope:
Migration from Novell GroupWise.

Impact:
Customer cannot find a contact by name.

Root cause:
The original contact name in GroupWise was not migrated, and the corresponding email address was used by default for creating the contact in the target.

Fix:
Now the "Display as" field for an email in the target can display the "FirstName LastName" information migrated from the source.
PT138224889

Migration might be stuck in the "Running" state with the "Caught unexpected exception while updating visibility for message" error in the log.

Scope:
All supported migration scenarios.

Root-cause:
ODME cannot update the migration status because the migration thread was aborted or not responding.

Fix:
The ODME mechanism to take the migration jobs for processing have been improved so that mailboxes in the "Running" state will not be stuck in case of ODME internal issues.

ODS-1229

Significant delay when you log on a user account that has 30 or more companies.

Scope:
ODME user interface slowness

Impact:
For example, some users with 280 or more companies experience 5 min or longer delays or timeout errors when trying to log on or to change a company.

Root cause:
Code deficiency in the ODME internal module.

Fix:
Several optimizations were made, so that a logon time for this use-case was decreased.

Release 1.10.0.6919 (04/21/2017)
PT143591211

Under the high load conditions, the message attachments might be corrupted during migration.

Scope:
All supported migration scenarios, except from Microsoft Exchange 2010, 2013 and 365 to Microsoft Exchange 2010, 2013, 2016 or Microsoft Office 365, in case of the Move large attachments to OneDrive for Business option is not selected

Root-cause:
Messages might be malformed due to exception thrown during message processing.

Fix:
Message processing algorithm has been improved to avoid the exception.

PT143307853

ODME can’t migrate more than 25 contact distribution lists from G Suite.

Scope:
Migration of Contacts from G Suite.

Root-cause:
Migration method limitation for maximum number of contact distribution lists to migrate from G Suite was set to 25.

Fix:
Limitation for migration of contact distribution lists G Suite has been removed.

Release 1.10.0.6852 (04/17/2017)
PT139925217

ODME creates duplicate messages on the target Exchange server if the already migrated mailbox content is moved from ‘primary” to “archive” mailbox on the target side.

Scope:
All supported migration scenarios.

Root-cause:
ODME does not check whether the target archive folder contains already migrated items, and migrate them, creating the duplicates.

Fix:
Now ODME skips already migrated messages, including those, that were archived.

Release 1.10.0.6450 (03/28/2017)
PT142034463

Mailbox names containing non-ASCII characters were corrupted after migration.

Scope:
Migration from IBM Notes and Domino

Root-cause:
ODME could not correctly handle the non-ASCII characters in the mailbox name.

Fix:
Now the mailbox names with non-ASCII characters display properly in the target platform.

PT141831817

ODME cannot migrate the folders of the ProxyFolder type (default user-visible name is "Multi-User Column") from GroupWise.

Scope:
Migration from Novell GroupWise

Root-cause:
In GroupWise 2012 and later versions, a user can use Proxy to manage another user's calendar, but ODME cannot migrate a proxy user's calendar (ProxyFolder folders) because the calendar technically does not belong to the current user.

Fix:
Now ODME skips the folders of the ProxyFolder type while migrating from GroupWise.

Release 1.9.0.5790 (02/28/2017)
PT137587261

ODME corrupts inline attachments for messages in the HTML format, so a user cannot download or view these attachments after migration.

Scope:
Migration from IBM Notes and Domino

Root-cause:
ODME creates inline attachments for the messages in the HTML format, though Exchange 2010, 2013, 2016 and Office 365 do not support this attachment type. As a result, corrupted attachments are created.

Fix:
Now ODME converts inline attachments to common attachments, so a user will be able to download or view these attachments after migration. Links to inline attachments are removed from the message body.

Release 1.9.0.5299 (01/25/2017)
PT120189193

ODME cannot migrate European non-English specific symbols, e.g. Spanish orthographic symbols.

Scope:
Migration from IBM Notes and Domino

Root-cause:
The symbols from the extended ASCII table were corrupted.

Fix:
Now ODME can process all the extended ASCII symbols correctly.

Release 1.9.0.5001 (01/12/2017)
PT118279347

The Gmail labels that include some special symbols (like ',' or ';') in its name are not migrated. The messages marked only by such labels are not be migrated too.

Scope:
Migration from G Suite

Fix:
Now ODME can process these special symbols correctly. So, both the labels with these symbols in its name and the messages marked only by such labels will be migrated successfully.

Release 1.9.0.3955 (12/16/2016)
PT135513479

Email items from the source mailbox are moved to the incorrect target mailbox.

Scope:
Migration from IBM Notes and Domino

Fix:
Now ODME can guarantee that the content from the source mailbox is correctly migrated to the corresponding target mailbox when the Quest Domino Web Service is upgraded on the customer side during the migration.

PT136170335

Embedded attachments are not migrated.

Scope:
Migration from G Suite

Root-cause:
If the Gmail client uses G Suite Sync for Microsoft Outlook (GSSMO), some content might be corrupted. Specifically, the MIME representation of an embedded attachment might have incorrect header and body.
Fix:
By default, ODME uses the standard IMAP protocol to get the content from Gmail. Now, in case of corrupted header or body, the migration of this message is retried via Gmail API.

Release 1.9.0.3831 (12/09/2016)
PT132145429

A part of migrated content may fail with the "Invalid XML character..." error.

Scope:
Migration from Exchange or Office 365 to Exchange 2007, 2010, 2013, 2016 or Office 365

Impact:
Mailbox is not migrated completely.

Root-cause:
The migrated content might have invalid XML characters, and so it could not pass through XML schema validation on the Exchange side.

Workaround:
Remove invalid symbols from the source items manually.

Fix: ODME removes invalid XML characters during the migration process.

PT135343291

The target log contains the "Failed to create an embedded item attachment. Details:Attachment name not found" error and the attachment called "Attachment name not found" appears in the target. The content of this attachment is a string of characters.

Scope:
Migration from Gmail

Impact:
The email message that is attached to another email is not migrated correctly.

Root-cause:
MIME message that was received via the IMAP protocol contains attachments with encoding that does not correspond to the Content-Transfer-Encoding header. Such messages are created using the G Suite Sync for Microsoft Outlook tool (Google ticket #10679648).

Fix:
By default, the standard IMAP protocol is used to get the content from Gmail. Now, in case of disconnection between the Content-Transfer-Encoding header and the actual content of the message, the migration of this message is retried via Gmail API.

PT135496899

Migration log contains the following errors: "An internal server error occurred. The operation failed" and "Failed to create an embedded item attachment".

Scope:
Migration to Exchange 2007, 2010, 2013, 2016 or Office 365

Impact:
The email message that is attached to another email is not migrated if its name includes the special symbols.

Root-cause:
Some symbols in the name of the attachment (like " < > |) are not supported by the Exchange Web Services (EWS) protocol.

Fix: Remove such symbols from the attachment name.

Release 1.9.0.3342 (11/16/2016)
PT133666667

The confusing "Exchange Server doesn't support the requested version" error message can be found in the logs.

Scope:
Migration from Exchange or Office 365; migration to Exchange or Office 365.

Impact:
There is no impact to the migration process, only confusing error message in the logs.

Root-cause:
Defect introduced in the recent release.

PT130958301

ODME web role traces may not be logged under the load condition.

Scope:
All customers in all regions.

Impact:
There is no impact to the migration process, but it may complicate the product support.

Release 1.9.0.3074 (10/31/2016)
PT131949243

A recurrent Note item created in GroupWise is migrated to Exchange or Office 365 as a number of separate events or generates a recurrent meeting in the target for every Note occurrence in the source.

Scope:
Migration from GroupWise 7.0.4, 8.0.3, 12.0.2 or 2014 to Exchange 2010, 2013, 2016 or Office 365.

Impact:
Exchange 2010 or 2013 as a target: a recurrent Note item generates a recurrent meeting in the target for every Note occurrence in the source.
Exchange 2016 or Office 365 as a target: a recurrent Note item is migrated as a number of separate events .

Root-cause:
The migration of recurrent Notes from GroupWise was implemented differently than migration of recurrent Appointments.

Fix: After the fix installation, ODME handles GroupWise calendar Notes in the same way as it handles GroupWise calendar Appointments.

PT131232211

There is an attachment icon in the target mail message after migration even if there is no attachment inserted in the header of the source message.

Scope:
Migration from Exchange 2010, 2013 or Office 365 to Exchange 2010, 2013, 2016 or Office 365.

Impact:
The attachment icon is shown in the target mail message after migration of the source message that does not have an attachment.

Root-cause:
The inline property of attachment item is not migrated correctly.

Fix: After the fix, ODME updates the "inline attachment" property, so that the attachment icon is not shown if no actual attachment is linked.

PT132144171

Mailbox migration can be interrupted with the following errors: "Error creating source session", "The remote server returned an error: (503) Server Unavailable" or "The remote server returned an error: (404) Not Found".

Scope:
All migration scenarios from Exchange 2010, 2013 or Office 365 to Exchange 2010, 2013, 2016 or Office 365.

Impact:
The manual actions to restart the interrupted mailbox might be required.

Root-cause:
These errors were not considered as transient and ODME did not try to resume the connection to the source or target server.

Fix: After the fix installation, these errors are considered as transient and connections to the servers will be repeated.

Release 1.9.0.2885 (10/24/2016)
PT130449193 Mailbox may stuck in the Queued, Running or Rescheduling state because of some exception during migration initialization. The exception occurs when accessing the Microsoft Azure storage.
PT126301501 GroupWise distribution groups are not migrated if an address book contains contacts with invalid XML characters.
PT131337527 The migration task stops with the "MigratorNotResponding" exception.
PT120572569 When migrating from GroupWise, ODME sets "flat" forwarding instead of "delegated to" forwarding according to the Novel recommendations.
Release 1.9.0.2628 (10/05/2016)
PT130724565

Migrations to / from Exchange or Office 365:

Some items can be skipped during migration because of the following transient error "Active Directory is unavailable". In this case, you should repeat the migration for these items manually.

Now ODME stops the migration and reschedules the session automatically when the error is gone.

PT131078987 If you use G Suite Sync for Microsoft Outlook, some attachments cannot be migrated via Internet Message Access Protocol (IMAP) with Base64 decoding failures.
PT130925497

Cannot migrate a folder from GroupWise in case of transient connection error.

Now ODME stops the migration and reschedules the session automatically when the error is gone.

Release 1.9.0.2554 (09/28/2016)
PT128636975

When migrating to/from Exchange or Office 365, a mailbox may stuck in the "errors threshold exceeded" state due to the transient error that occurs when getting some folder: "Microsoft.Exchange.WebServices.Data.ServiceResponseException: Active Directory is unavailable". ODME treats all the items in this folder as Errors and does not make any additional attempts to get this folder.

Now the retry mechanism is implemented to resolve this issue.

PT130521287 When migrating from IBM Notes and Domino, each attendee of a migrated meeting becomes an organizer and can cancel the meeting, for example.
PT128310165 When migrating from GroupWise, contact items are not migrated if the Notes property of these contacts includes Unicode characters.
Release 1.9.0.2363 (09/09/2016)
PT127966717 When migrating to Microsoft Office 365, ODME does not retry to remove forwarding at target if it has previously failed to do that and Office 365 web service returned the error "Your request is too frequent. Please wait for few minutes and retry again". Note that in this case, the completion status of the operation will always be Success despite the fact that the operation actually failed.
Release 1.9.0.2250 (08/30/2016)
PT120338525

In migration from IBM Notes and Domino, the recurring meetings for meeting rooms lead to the duplicate appointments at the Target side.

PT126756529 In all the supported migration scenarios, the messages of the certain content (multipart message without a boundary in header) cannot be migrated.
PT127788897 In all the supported migration scenarios, the messages with attachments that contain the files with empty names cannot be migrated.
PT120275365 For migrations to Exchange 2010/2013/2016 or Office 365, the limits for migrated message size and the total size of the message attachments are adjusted to the Outlook Web App limits. The default value for both limits now is set to 35 MB.
Release 1.9.0.1937 (08/03/2016)
PT127545665 If ODME fails to create an attachment for a migrated message due to the exception returned by the target Office 365, additional attempts to create the attachment are not made.
Now ODME makes additional attempts (up to 5) to create an attachment in the above circumstances.
Release 1.9.0.1875 (07/26/2016)
PT126116609 When migrating Calendar items from Gmail to Exchange Server or Office 365, tracking statuses of attendees "Yes/Maybe/No" in the source meeting are not migrated to the corresponding statuses "Accepted/Tentative/Declined" for the meeting in the target organizer’s Calendar. This problem occurs because ODME incorrectly converts the source data to the target data during migration of Calendar items.
Release 1.9.0.1866 (07/25/2016)
PT122924231 When migrating Calendar items from Gmail to Exchange Server or Office 365, some of recurring meetings with exceptions may not be migrated correctly with the following errors in the logs: "Failed to find the meeting occurrence for appointment...". This problem occurs because ODME incorrectly converts recurrence UNTIL rules to COUNT rules in some specific meeting configurations.
PT122974991,
PT120820819
When migrating Calendar items from Gmail to Exchange Server or Office 365, some of recurring meetings with exceptions may not be migrated correctly with the following errors in the logs: "Failed to find the meeting occurrence for appointment...". This issue is caused by invalid source meeting exceptions when these exceptions fall out of recurrence range.
PT122984081 When migrating Calendar items from Gmail to Exchange Server or Office 365, the primary calendar time zone is not preserved if source Google time zone has no corresponding time zone in the Windows list.
PT125820641 When migrating Calendar items from Gmail to Exchange Server or Office 365, some of modified meetings may not be migrated correctly with the following errors in the logs: "MIME content conversion failed." This problem occurs because ODME incorrectly process particular modifications of meetings.
PT126215809 When migrating items to Exchange or Office 365, you may get the following error: "Failed to process attachment <attachment name> on item <message subject>". As a result, the item is migrated partially. This issue is caused by incorrect conflict resolution rule that is applied by ODME during migration.
Release 1.9.0.1783 (07/14/2016)
PT121667391

Migration from Gmail to Exchange Server or Office 365:
You may get errors when migrating Calendar items that are not visible in Gmail GUI but still available via Gmail API.

PT122925181 When migrating Calendar items from Gmail to Exchange Server or Office 365, the following exception may occur: "System.ArgumentException hexadecimal value 0x0C, is an invalid character". As a result, the item is not migrated. This issue is caused by the "form feed" character (commonly used as page or section separator) in the appointment description.
PT122972631 When migrating Calendar items from Gmail to Exchange Server or Office 365, the following exception may occur: "The operation can't be performed because the item is out of date. Reload the item and try again". As a result, the item is not migrated. This issue is caused by incorrect conflict resolution rule that is applied by ODME during appointment migration.
PT122972801

When migrating Calendar items from Gmail to Exchange Server or Office 365, the following exception may occur: "MIME content conversion failed". As a result, the item is not migrated. This issue is caused by several MIME rules which are not supported by Office 365:

  • 'BYYEARDAY' statement in the recurrence rule (RRULE)
  • 'UNTIL' date/time in the recurrence rule (RRULE) is set earlier than 'Start' date/time of the meeting
PT122973381 When migrating a public primary calendar that is shared by other users, events from the source primary calendar are duplicated in the target calendars of the migrated users.
Release 1.9.0.1514 (06/20/2016)
PT119618479 Email addresses of contacts are not migrated correctly from IBM Notes and Domino to Office 365.
PT120189751 Cannot migrate an appointment with the following error messages: "Could not save: "MIME content conversion failed." and "Recurrence Rule: EXDATE".
PT111683662 ODME cannot correctly migrate mailbox folder structure for some Zimbra versions.
PT120071007 The parameter of disabled forwarding rule is missed after migration of a GroupWise mailbox if ODME forwarding is configured for this mailbox.
Release 1.9.0.1409 (06/10/2016)
PT108464782 GUI user experience is significantly improved: loading migration plans on the initial page and starting migrations accelerated.
PT120649793 When migrating Calendar items from Gmail to Exchange Server or Office 365, the primary calendar time zone is not preserved for some recently created time zones.
Release 1.9.0.1296 (06/01/2016)
PT119055261 ODME cannot create a CPUU switch message if a custom domain name is used for the target Office 365.
PT120552825

ODME marks migration as successfully completed even if post-migration tasks failed.

There are two post-migration tasks available:

  • Set GroupWise visibility
  • Create CPUU switch message
PT120172303 ODME does not create a CPUU switch message if migration completed with errors.
Release 1.9.0.1260 (05/27/2016)
PT120087495 After migration, a meeting is not updated in an attendee’s Calendar. When the meeting is updated in organizer's Calendar, the attendee receives a meeting update notification, but this notification cannot be accepted or declined.
Release 1.9.0.1100 (05/13/2016)
PT119268395 In rare cases, the migration may be interrupted with the "System.ArgumentException: Destination array was not long enough. Check destIndex and length, and the array's lower bounds." exception because ODME cannot create a migration session.
Release 1.9.0.1077 (05/12/2016)
PT118373465 Drafts are not migrated from the IBM Notes and Domino server.
PT116013655 ODME cannot migrate multiple "Sent messages" and "Deleted messages" folders from a source mailbox.
Release 1.9.0.917 (04/28/2016)
PT117141231 An all day calendar event that spans multiple days is migrated only for the first day.
PT109254390 The total number of migrated items and total number of errors do not match the data on the migration plan page.
Release 1.9.0.877 (04/22/2016)
PT117674789 Rendering of the Per Mailbox Statistics report may take a very long time.
PT114932327 When a user changes an account name in the ODME portal, this account cannot be found in the dashboard by new name after migration.
Release 1.9.0.841 (04/19/2016)
PT115324511 During GroupWise migration, some folders of a mailbox may be skipped if messages inside them contain corrupted data.
PT111427526 When migrating a large number of mailboxes from GroupWise, some mailboxes may have the "Interrupted" status until the migration is completed.
PT117618431 Fixed all dead links to Support Portal in the ODME user interface.
PT116470551 Improved user interface performance by running AJAX queries in parallel.
Release 1.9.0.598 (03/31/2016)
PT116470779 Optimize initial time to load servers, options, mailboxes and pages - remove redundant requests.
Release 1.9.0.547 (03/24/2016)
PT115319833 It takes too much time to load a list of migration plans on the Dashboard page.
PT115319875 The Migration Status page works very slowly.

Known Issues

Known issues

The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.

Table 2: General

Defect ID Issue Description
TF439747 Migrations Plans screen might not display correctly if the browser is not set to US-English.
PT101067484 Acceptance messages from the appointment attendees are not shown for the target appointment after migration.
PT110062664

If you migrate data within the specified date range, you should take into account that the end date is not included in this range. For example, if the date range for migration is started on 07/03/2015 and ended on 07/13/2015, ODME migrates all messages from 07/03/2015 00:00 to 07/13/2015 00:00 and no messages from 07/13/2015 00:01 to 07/13/2015 23:59.

PT136683327 Now, the values of "Errors" fields in the Per Mailbox Statistics report ("Message Errors", "Contact Errors", "Group Errors", "Appt. Errors", "Task Errors") are the sums of errors that were detected during all migration executions - not the number of mailbox items which were not migrated.
PT134836227 If a part of an item is not migrated, the statistics report shows a number that is greater than 1.
PT140282307 General errors (connection issues or issues related to setting forwarding) are logged as message errors.
PT136683327 If ODME cannot identify which migrated item causes an error, it cannot aggregate this error for multiple migration executions, and the Per Mailbox Statistics report will show duplicated errors.

 

Table 3: G Suite migration

Defect ID Issue Description
TF315445 Google recently added 4 new built-in labels: Social, Promotions, Updates, and Forums. ODME cannot currently migrate these labels.
TF316366 If migrating a G Suite mailbox using an alias rather than the primary email address, users will receive an error that results in the migration being interrupted. Using the primary email address will allow the migration to proceed normally.
PT107025886 When migrating from Google Calendar to Office 365, the target appointment may not contain information about which appointment attendees had accepted the meeting invitation. Then, if you update the target appointment, the changes do not synchronize on the source.
PT110062664

If the start date and end date of the migration date range are the same, ODME migrates all data from the G Suite source.

PT140984675

When migrating G Suite contacts to Office 365, contacts show LegacyExchangeDN instead of email address if open the target contacts in Google Chrome. And the target GAL (Office 365) contains contacts with the same email addresses as the corresponding source contacts.

Workaround:

  • Open the target contact in Google Chrome, then click Edit and Save.

    -OR-

  • Open the target contacts via Microsoft Outlook.
PT151844601 If IMAP is disabled, ODME migrates 'Important' and 'Starred' labels as 'Important' and 'Starred' regardless of locale. For example, if we migrate from the Spain locale, these labels will be migrated as 'Important' and 'Starred' instead of 'Importantes' and 'Destacados'.
PT151916847 We strongly discourage to enable or disable IMAP access for a G Suite organization after migration start. In this case folders and messages may get duplicated on the target after migration. Also, migration statistics may be incorrect.

 

Table 4: Exchange migration

Defect ID Issue Description
TF318402 When migrating appointments from Exchange, x.500 information is displayed in place of the meeting organizer's name if the meeting organizer no longer has an account on the Exchange source at the time of the migration.
TF344583 Recurring appointments are limited to at most 999 instances on Exchange targets. ODME converts recurrence rules based on an "Until end date" setting to use a count of instances, due to compatibility issues with Exchange. If the number of instances of a recurring appointment exceeds 999, it will be reduced to 999. This applies if either the appointment recurrence was set up using an explicit count of instances, or if the recurrence end date would result in that many instances being generated. This limit does not apply for appointments that do not have an end recurrence applied. (Neither an until date, nor a count). Any reduction in instances is noted in the log for that mailbox. How far out the appointment can go is controlled by how often the appointment occurs. An appointment that happens once a week can go for 999 weeks. An appointment that happens once a month can go for 999 months, etc. An appointment that meets every weekday (~260 per year) can go for ~199 weeks (~3.8 years). Again, this limit is not applied to appointments that do not have an end defined.
TF356232 Categories for posted items in non-public folders are not being migrated from Exchange 2007.
PT109260050

Items from the root folder of an archive mailbox are not shown on the target after migration when you use Microsoft Outlook (Outlook Web Access works fine).

Workaround: In the Outlook settings, disable Cached mode and disable default dashboard which is shown on the mailbox root.

PT150334190 If an item from the Recoverable Items folder was restored on the target during migration, this item will be migrated once again from the source.
PT150334265 Items from the Recoverable Items folder are not restored to its origin folders - the destination folder will be chosen automatically by the item class.

 

Table 5: GroupWise migration

Defect ID Issue Description
TF195359 Tasks completed on the same day as the migration currently appear in the target mailbox as if they were completed the day before the migration.
TF220219 Reminder notes stored in the mailbox migrate as messages. Also, reminder notes within the calendar migrate as all day calendar items.
TF235443 GroupWise tasks do not always contain time zone information. ODME infers a time zone based on the migrated mail data, which allows most tasks to appear on the correct day and time. However, in rare instances, a task may appear one day earlier after migration.
TF266283 With GroupWise 7, display names and email addresses of distribution lists and contacts do not migrate correctly.
TF443386 Recurring tasks are migrated to the target, but each occurrence is migrated as its own standalone task and is not linked to the other tasks on the target.
TF442867 If the Forward new items as they arrive option is selected in the Options tab and the GroupWise is selected as the source, ODME may forward new items as attachments rather just forwarding them.
TF459463 For GroupWise 2014, primary contact on an organization does not migrate. Primary contact specified on an organization in GroupWise does not migrate. If an Owner is specified on a resource, it displays under the 'Notes' on the target.
TF459462 For GroupWise 2014, categories and comments on groups do not migrate.
TF459461

For GroupWise 2014, some contact properties do not migrate correctly:

  • Display As migrates to Exchange with the format Last Name, First Name
  • Organizational ID migrates to the Customer ID field
  • Customer ID migrates to the Organizational ID field
TF459435 For GroupWise 2014, reminder notes do not migrate. Notes added to contact items end up as reminder notes on the calendar. These reminder notes do not get migrated.
TF457014 For GroupWise 2014, recurring appointment on the 30th that spans February migrates differently. The appointment does not have an occurrence in February in GroupWise. However after migrating the recurring appointment, there is an instance on the last day of February.
ODME-5157 If an occurrence in a recurring event is proposed and accepted to move to a day of another occurrence, and the new time is later than the original occurrence on that day, after migration to Office 365, the moved occurrence is included into the recurring event as an instance while the original one on that day becomes a non-recurring meeting.
ODME-5155

For non-English GroupWise 2014 and 2014 R2 clients:

If you create a sub folder named "Frequent Contacts" under the default frequent contacts folder (for example, "Häufige benutzte Kontakte" in German), then the contacts in the sub folder “Frequent Contacts” will not be migrated.

 

Table 6: Zimbra migration

Defect ID Known Issue
PT107292620

During synchronization from the Zimbra source, all contact items will be re-migrated to the target. This problem occurs because contacts in Zimbra do not store the time of last modification. As a result, statistical data for contact items is incorrect: re-migrated contacts are considered "Migrated" instead of "Skipped".

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents