Dell 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 and enhancements
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 higher. - 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.
Release 1.8.0.418 (3/17/2016)
- Microsoft Exchange Server 2016 is supported as a target only.
Release 1.8.0.183 (11/30/2015)
- Microsoft Exchange Server 2013 is supported as a source, including Service Pack 1
- Support for Archive Mailboxes migration from Exchange Server 2013 and Office 365 to Exchange Server 2013 and Office 365 targets.
Release 1.8.0.59 (8/16/2015)
- General performance improvements
- Integration with Client Profile Updating Utility (CPUU)
Resolved issues
| Resolved Issue | Issue ID |
|---|---|
| Release 1.9.0.2250 (08/30/2016) | |
|
In migration from IBM Notes and Domino, the recurring meetings for meeting rooms lead to the duplicate appointments at the Target side. |
PT120338525 |
| In all the supported migration scenarios, the messages of the certain content (multipart message without a boundary in header) cannot be migrated. | PT126756529 |
| In all the supported migration scenarios, the messages with attachments that contain the files with empty names cannot be migrated. | PT127788897 |
| 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. | PT120275365 |
| Release 1.9.0.1937 (08/03/2016) | |
| 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. |
PT127545665 |
| Release 1.9.0.1875 (07/26/2016) | |
| 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. | PT126116609 |
| Release 1.9.0.1866 (07/25/2016) | |
| 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. | 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 issue is caused by invalid source meeting exceptions when these exceptions fall out of recurrence range. |
PT122974991, |
| 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. | PT122984081 |
| 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. | PT125820641 |
| 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. | PT126215809 |
| Release 1.9.0.1783 (07/14/2016) | |
|
Migration from Gmail to Exchange Server or Office 365: |
PT121667391 |
| 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. | PT122925181 |
| 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. | PT122972631 |
|
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:
|
PT122972801 |
| 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. | PT122973381 |
| Release 1.9.0.1514 (06/20/2016) | |
| Email addresses of contacts are not migrated correctly from IBM Notes and Domino to Office 365. | PT119618479 |
| Cannot migrate an appointment with the following error messages: "Could not save: "MIME content conversion failed." and "Recurrence Rule: EXDATE". | PT120189751 |
| ODME cannot correctly migrate mailbox folder structure for some Zimbra versions. | PT111683662 |
| The parameter of disabled forwarding rule is missed after migration of a GroupWise mailbox if ODME forwarding is configured for this mailbox. | PT120071007 |
| Release 1.9.0.1409 (06/10/2016) | |
| GUI user experience is significantly improved: loading migration plans on the initial page and starting migrations accelerated. | PT108464782 |
| 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. | PT120649793 |
| Release 1.9.0.1296 (06/01/2016) | |
| ODME cannot create a CPUU switch message if a custom domain name is used for the target Office 365. | PT119055261 |
|
ODME marks migration as successfully completed even if post-migration tasks failed. There are two post-migration tasks available:
|
PT120552825 |
| ODME does not create a CPUU switch message if migration completed with errors. | PT120172303 |
| Release 1.9.0.1260 (05/27/2016) | |
| 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. | PT120087495 |
| Release 1.9.0.1100 (05/13/2016) | |
| 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. | PT119268395 |
| Release 1.9.0.1077 (05/12/2016) | |
| Drafts are not migrated from the IBM Notes and Domino server. | PT118373465 |
| ODME cannot migrate multiple "Sent messages" and "Deleted messages" folders from a source mailbox. | PT116013655 |
| Release 1.9.0.917 (04/28/2016) | |
| An all day calendar event that spans multiple days is migrated only for the first day. | PT117141231 |
| The total number of migrated items and total number of errors do not match the data on the migration plan page. | PT109254390 |
| Release 1.9.0.877 (04/22/2016) | |
| Rendering of the Per Mailbox Statistics report may take a very long time. | PT117674789 |
| When a user changes an account name in the ODME portal, this account cannot be found in the dashboard by new name after migration. | PT114932327 |
| Release 1.9.0.841 (04/19/2016) | |
| During GroupWise migration, some folders of a mailbox may be skipped if messages inside them contain corrupted data. | PT115324511 |
| When migrating a large number of mailboxes from GroupWise, some mailboxes may have the "Interrupted" status until the migration is completed. | PT111427526 |
| Fixed all dead links to Support Portal in the ODME user interface. | PT117618431 |
| Improved user interface performance by running AJAX queries in parallel. | PT116470551 |
| Release 1.9.0.598 (03/31/2016) | |
| Optimize initial time to load servers, options, mailboxes and pages - remove redundant requests. | PT116470779 |
| Release 1.9.0.547 (03/24/2016) | |
| It takes too much time to load a list of migration plans on the Dashboard page. | PT115319833 |
| The Migration Status page works very slowly. | PT115319875 |
| Release 1.8.0.538 (03/24/2016) | |
| Migration from the Google Gmail source is interrupted with the "StartIndex cannot be larger than length of string" error. | PT115398661 |
| ODME cannot migrate Appointment 'StartTimeZone' and 'EndTimeZone' items if the source Exchange Server 2003 has the Spanish locale. | PT111850061 |
| Release 1.8.0.418 (03/10/2016) | |
| Cannot switch a profile using the CPUU option if the source is Exchange Server 2007. | PT111976515 |
| ODME stops processing a mailbox (a mailbox has the "Stopped" status) in case of a message with invalid MIME body. | PT115313723 |
| Cannot create a CPUU switch message for the localized Exchange server. | PT114073851 |
| Release 1.8.0.341 (02/26/2016) | |
| ODME cannot migrate MIME messages that start with an empty line. | PT114021913 |
| Folders that have "INBOX/" before the folder name are duplicated on the target. This problem arises if these folder were created in Gmail Inbox via Microsoft Outlook email client. | PT113917461 |
| Release 1.8.0.239 (12/31/2015) | |
| Migration of a primary calendar from Google to Microsoft Outlook: The "Created By" field in the Google Calendar events is mapped to the "Organizer" field in Outlook when migrating an attendee of an event which was created through delegation. |
PT110396178 |
| Some mail items cannot be migrated for mailboxes that have the Conversation historyfolder. | PT109816342 |
| ODME incorrectly migrates label names that contain a slash character (/), e.g. "Monthly Reports/2015/October". In this case, the source content will be migrated to the target folder called "October" - the part of the source folder name that comes after the last slash character. | PT101704000 |
| Release 1.8.0.183 (11/30/2015) | |
| Connection-related errors may occur on the Zimbra source if IMAP and Zimbra's SOAP API reside on different servers. | PT106492518 |
| Release 1.8.0.134 (11/6/2015) | |
|
If a user creates a mail label called "Calendar", ODME cannot migrate the user primary calendar with the 404 error. WORKAROUND:
|
TF439834 |
| If a user creates a mail label called "Sent Items" or "Sent", ODME estimates "Sent Items", "Sent Mail" and "Sent" folders, but after migrating "Sent Items" it does not attempt to migrate "Sent Mail". Possible workaround is to rename the "Sent Items" or "Sent" mail label to something that won't cause this problem, like "EmailSent". | PT102359252 |
| When migrating from Google Calendar to Office 365, ODME does not migrate some calendars if the total number of calendars (owned and shared) more than 100. | PT101146980 |
| Appointments with the Asia/Kolkata timezone on the Zimbra source are migrated as UTC instead of India Standard Time. | PT103222388 |
| Release 1.8.0.109 (10/7/2015) | |
|
After migration from Zimbra to Office 365: When the calendar owner reschedules an appointment in Office 365, the attendee of the appointment receives a new appointment instead of changing the old one. |
PT103215084 |
| The ODME migration engine uses the default IMAP SSL port (993) even if it is customized in the Web UI. | PT104307772 |
| The default port (7191) always appears on the Source Connection screen for the GroupWise connection. | PT100419294 |
| Release 1.8.0.102 (9/30/2015) | |
| The messages from the Important folder cannot be fully migrated when the migration is interrupted due to Google data transfer throttling. | PT102243454 |
| You may experience Google mail migration issues that are caused by the following error: "Unexpected error. Details: 'Inbox' (Index was out of range)". Issues may occur randomly during migration of Google labels and messages. | PT101391888 |
| ODME cannot correctly migrate folder names and contents of the folders from Zimbra 6. After migration, the folder names will contain 'USER_ROOT', for example:USER_ROOT/Inbox. | PT102989264 |
| Release 1.8.0.60 (9/16/2015) | |
| Email drafts are not editable in Office 365 after migration. | PT101065650 |
| The mail forwarding feature does not work for Office 365. | PT101202764 |
| Release 1.8.0.59 (8/16/2015) | |
| If a migrated appointment for which the migrated user is an attendee (not the organizer) is canceled, a cancellation email is sent out to all the attendees. | TF452352 |
| All appointments migrate from IBM Notes with a free/busy status of "Free", regardless of what the status is set to on the source. This issue has been partially resolved in that single instance appointments migrate correctly. Recurring meeting appointments, however, still migrate with a free/busy status of "Free", regardless of what the status is set to on the source. | TF452349 |
| Zimbra 6 appointments that are in the inbox, not yet accepted or declined, will appear in the calendar view as "busy" instead of "tentative". | TF339983 |