Dell Migration Manager for Exchange 8.12
Update 20170207EX—Readme
February 7, 2017
How to Determine If This Update Is Installed
This update may require additional testing.
This cumulative update package contains hotfixes for Dell Migration Manager for Exchange issues that have been fixed since the release of Dell Migration Manager for Exchange 8.12.
For complete product information, please refer to the Migration Manager for Exchange product documentation.
IMPORTANT:
You should install the latest Migration Manager for Active Directory update in order that the product works properly with this Migration Manager for Exchange update.
The following is a list of issues resolved by this update:
Defect ID | Issue Description |
PT134954401 |
Native mailbox move may fail in case CAS arrays or load balancers are used in either source or target Exchange organization.
Scope: Mailbox migration using native move job Root-cause: MAgE was unable to get information required for New-MoveRequest in case customer environment contained CAS arrays or load balancers.
Fix: Now all required information about Exchange organization is obtained when that organization is added in the console and then it is saved to the database. MAgE then uses that information for constructing a proper New-MoveRequest .
See also KB Article 225817. |
Updates the following components: all Migration Manager for Exchange components.
Microsoft Exchange 2013 with the recently released Cumulative Update 14 is verified and confirmed as a completely supported migration target.
This cumulative update package contains all hotfixes for Dell Migration Manager 8.12 issues that have been included in the earlier updates:
Defect ID | Issue Description |
PT130379445 |
Synchronization of a mailbox might stuck at ‘In Progress’ if source mailbox has folders with the same names. Also this issue may occur in the following cases:
Scope: Migration to Exchange 2013 or Office 365 Root-cause: If MAgE mechanism of folder matching encountered folders with the same name in a source mailbox, it treated them in the following way:
Fix: MAgE mechanism of folder matching has been improved. The most recently created folder is still matched to the corresponding target folder. However, for each other folder with the same name at source MAgE now creates a corresponding target folder named _ and matches folders accordingly. This ensures that all the folders are processed properly and therefore mailbox synchronization succeeds. If you already encountered the described issue, take the following steps for each affected mailbox to apply fix:
See also KB article 213779. |
PT127993043 | Out of Office automatic replies messages are not synchronized before mailbox switch Scope: Migration to Exchange 2013 or Office 365 Impact: Out of Office automatic replies messages are not synchronized before mailbox switch. That impacts calendar co-existence as those messages may not stay in sync between source and target mailbox. Root-cause: MAgE synced Out of Office automatic replies messages only after mailbox has been switched but before mailbox sync is completed. Fix: Now sync of Out of Office automatic replies is guaranteed to be performed in every mail synchronization session. |
PT127354679 | Migration performance may degrade due to well-known folder detection failures Scope: Migration to Exchange 2013 or Office 365 Impact: In case either source or target Exchange server is highly loaded, the well-known folder detection may fail. This causes migration performance to degrade. Root-cause: Under certain conditions MAgE might not able to detect well-known folders and as a result exceptions occurred. That leaded to wasted migration sessions. Fix: Now the mechanism of well-known folder detection is improved so no more migration sessions will be wasted because of the described problem. |
PT125844991 | Mailbox synchronization may fail if any well-known folder selected to be skipped has subfolders. Scope: Migration to Exchange 2013 or Office 365 Impact: A mailbox synchronization may fail if any well-known folder selected to be skipped has subfolders. In this case the "System.Exception: Matching parent folder not found" error is traced. For details on skipping well-known folders, see the description of 'WellKnownFoldersToSkip' parameter at the User’s Guide). Root-cause: MAgE has not properly managed skipping of subfolders of the well-known folders selected to be skipped via ‘WellKnownFoldersToSkip’ parameter. Fix: Mechanism of skipping subfolders of the well-known folders has been improved so mailbox synchronization no longer fails for this reason. |
PT126610849 | Reverse calendar sync may fail in case the default calendar has been changed Scope: Migration to Exchange 2013 or Office 365 Impact: If the default calendar have been changed either at source or target, calendar sync may fail with the Object Reference not set error. Root-cause: MAgE matched folders to sync incorrectly in the described case. Fix: MAgE now matches folders to sync properly. |
PT125844991 | Mailbox synchronization may fail if any folder selected to be skipped has subfolders. Scope: Migration to Exchange 2013 or Office 365 Impact: A mailbox synchronization may fail if any well-known folder selected to be skipped has subfolders. In this case the System.Exception: Matching parent folder not found error is traced. For details on skipping well-known folders, see the description of WellKnownFoldersToSkip parameter in Configuring Migration Using PowerShell. Root-cause: MAgE has not processed subfolders properly when skipping well-known folders. Fix: MAgE now skips well-known folders with subfolders properly. |
PT129943875 | Skipped items counter is reset after the product update installation Scope: Migration to Exchange 2013 or Office 365 Impact: Skipped items counter in the Statistics pane is reset after the product update installation. This causes Progress to be recalculated assuming that skipped items count is zero. Note that this does not affect actual skipped items. Root-cause: Information about skipped items is dropped from the SQL database on update installation. Fix: Now that information is not dropped, so that mailbox migration statistics remains consistent after product update installation. |
PT127804371 | SQL Server performance may drop over time in case of two-way calendar syncrhonization Scope: Migration to Exchange 2013 or Office 365 Impact: In case of two-way calendar synchronization, size of SQL database may tangibly grow over time resulting in significant SQL Server performance drop. In this case MAgE logs the error 'System.Data.SqlClient.SqlException: Timeout expired'. Root-cause: MAgE does not clear obsolete information from the SQL database. Fix: MAgE algorithm is improved to clear obsolete information from the SQL database. |
PT127370119 | Migration performance may decrease as well as agent host disk space utilization increases after MAPI logon failures Scope: Migration to Exchange 2013 or Office 365 Impact: If MAPI logon to source Exchange fails for any reason, that leads to migration performance drop and also agent host disk space utilization drastically increases. Root-cause: Each time MAPI logon fails for any reason, MAgE creates a crash dump. Fix: Now MAPI logoff operation is reworked to avoid the described situation. |
PT126965247, PT127077223 |
Skip filter settings may be cleared for a collection after a sequence of changes in the collection properties and console restarts. Scope: Mailbox and calendar synchronization to Exchange 2013 or later Impact: If you disable (enable) a collection, restart the console and then enable (disable) that collection or if you rename the collection after restarting console, skip filters configured for that collection may be cleared. Root-cause: Console does not read and write skip filter information properly to the database. Fix: Now console reads and writes skip filter information to the database properly. |
PT126211173 |
MAgE fails to perform native mailbox move from or to an Exchange server located in the child domain. Scope: All scenarios of native mailbox move Impact: MAgE throws out the error message "Server Name = '' not found in the DB" when performing native mailbox move from or to an Exchange server located in the child domain. Root-cause: MAgE searches for an incorrect server name in database when the Exchange server belongs to a child domain. Fix: Now MAgE uses a correct Exchange server name when performing database search. |
N/A |
Migration may slow down if a large number of migration agents run simultaneously Scope: Migration to Exchange 2013 and Office 365 Impact: If more than 100 migration agents run simultaneously, the overall migration performance may significantly drop. Root-cause: The frequently used data has not been indexed; lots of parallel calls performed by migration agents to SQL database resulted in the database deadlocks. That, in turn, caused overall migration slowdowns. Fix: The frequently used data is now indexed. That reduced the probability of database deadlocks and increased speed of communication between migration agents and SQL database. |
PT118561179 | The Most recent error field in Statistics pane may display already resolved error Scope: Migration to Exchange 2013 or Office 365 Impact: The Most recent error field in Statistics pane may display an obsolete error that occurred with a mailbox in the past but has been resolved since then. The mailbox processing state is Processing now in this case. Root-cause: The Most recent error field is not cleaned up properly. Fix: Now the Most recent error field is cleaned up at the beginning of each new session so that it never displays outdated obsolete errors. |
PT115759729 | Native mailbox move fails if processed mailbox is moved to a collection with a different target database. Scope: All scenarios of native mailbox move Impact: Migration stops because MAgE is unable to determine a correct remote PowerShell server and thus creates a move request with wrong parameters. Root-cause: If a processed mailbox is moved to a collection with a different target database, MAgE continues to use the target database of the original collection. Fix: Now after a mailbox is moved to another collection or collection properties are changed, the information in the database is updated accordingly. Therefore, MAgE is able to create a correct move request. |
PT12594301 | You may experience slow migration performance in case of a large number of migration agents are running simultaneously. Scope: Migration to Exchange 2013 and Office 365 Impact: If more than 50 migration agents are running simultaneously, the overall migration slowdown may be observed. Root-cause: In accordance with the current algorithm that is used to process statistical data, each migration statistics update is stored in the SQL database immediately. This may lead to the deadlock in the certain SQL tables in case of many simultaneous migrations. Fix: Now the possibility of deadlock in the SQL database is tangibly reduced. |
PT107723690 |
Critical warning messages are not shown in the Issue Details field if a native move job is completed with warning
Scope: Native move job for all Exchange versions Impact: Even if a native move request managed by a native move job completed with warning, the Issue Details field is empty in the Statistics pane. The occurred warning appears only in MAgE log. Root-cause: Such critical warning messages were not processed properly. Fix: A new level of log called Critical Warning is introduced. Warnings of this level appear in the MAgE log file and are shown in the Issue Details field. Note that in this case the Migration Stage will be Completed. |
PT114380721 | Out of Office automatic replies messages may not be synced to Office 365 Scope: Migration to Office 365 Impact: Out of Office automatic replies messages are not synced by Migration Agent for Exchange in most cases. They are synced only if mailbox sync in general takes a very long time (more than 23 hours). It happens in case of huge mailbox size, slow access to source or target Exchange servers, MAgE agent host overload, etc. Root-cause: Conditions under which Out of Office automatic replies are synced were too rarely fulfilled. Fix: Now sync of Out of Office automatic replies is guaranteed to be performed in the period after mailbox switch but before mailbox sync completion. |
PT110834266 | A migrated exception to a recurrent meeting may show LEDN as meeting organizer's name. Scope: Mailbox synchronization to Exchange 2013 or Office 365 Impact: An organizer's LEDN instead of a name may be shown as a meeting organizer's name to attendees of a migrated exception to a recurrent meeting. Root-cause: The MAPI properties of an exception meeting related to displaying organizer's name are not properly migrated by MAgE. Fix: MAgE has been improved to be able migrating exceptions to recurrent meetings properly. |
PT114760039 | Mailboxes may not be processed due to lack of date format conversion. Scope: Migration to Exchange 2013 and Office 365 Impact: Mailboxes added to dynamic collections may not be processed if date formats on MAgE agent host and on SQL configuration database server are different. Root-cause: The lack of date format conversion among product components. Fix: The proper date and time conversion algorithm is implemented to resolve the issue. |
PT112784581, PT107590264 | Mailbox migration to Office 365 may suddenly stop
Scope: Migration to Office 365 Impact: Migration of a mailbox to Office 365 may suddenly stop if a mailbox store in the source Exchange organization where that mailbox has been stored originally is removed. Root-cause: Gathering mailbox processing information was not performed correctly. Fix: The mechanism of mailbox processing is now updated to use mailbox LEDN instead of mailbox cache. |
PT116122611 | After mailbox switch reverse calendar sync may throw 'Object Reference not set' error Scope: Migration to Exchange 2013 or Office 365 Impact: A reverse calendar sync may fail with the 'Object Reference not set' error after a mailbox switch. Root-cause: Lack of error handling for certain network connectivity issues. Fix: MAgE has been improved to handle that error properly and prevent sync failure. |
PT115939387 | Unable to add new mailboxes to a mailbox collection; processing of some existing mailboxes has stopped. Scope: Migration from Exchange 2007 to Exchange 2013 or Office 365 Impact: After performing the Refresh operation for the source Exchange organization, you may experience that new mailboxes cannot be added to a mailbox collection explicitly because of No objects were returned from the configuration database error. In addition, processing of mailboxes added to a collection implicitly (for instance, through OU membership) has stopped. Root-cause: The mechanism of refreshing organization information does not update mailbox database information properly. Fix: The process of updating mailbox database information has been fixed. |
PT116060405 | MAgE may create New-MoveRequest with wrong parameters when migrating from mixed Exchange organization Scope: Migration from mixed Exchange 2007 and Exchange 2010 organization to Exchange 2013 Impact: If a source Exchange organization is a mixed Exchange 2007 and Exchange 2010 organization, MAgE constructs New-MoveRequest cmdlet with wrong parameters. The parameters are specified as if migration is performed from an Exchange 2007 organization in a non-mixed mode. Root-cause: MAgE ignores the highest version of Exchange servers in a mixed source organization and considers that version of organization equals to version of Exchange server that stores mailboxes. Fix: Now MAgE constructs New-MoveRequest cmdlet properly for mixed Exchange organizations. |
Updates the following components: all Migration Manager for Exchange components.
The following known issue exists at the time of the update release:
Defect ID | Issue Description |
N/A | The Native Move job fails to migrate a mailbox from the Exchange 2007 source organization to the Exchange 2013 target with Service Pack 1 Cumulative Update 6 (build number: 15.0.995.29). In the log you can find the "Recipient '' isn't a mailbox." error. Microsoft has confirmed that this is a problem in New-MoveRequest. This problem appears after installation of Cumulative Update 6 for Microsoft Exchange Server 2013 Service Pack 1. Resolution: Microsoft plans to address this problem at further Cumulative Updates for Microsoft Exchange Server 2013 Service Pack 1 and recommends that you use Microsoft Exchange Server 2013 Service Pack 1 Cumulative Update 5 as a target for this configuration. For more details, see the following article: https://support.quest.com/migration-manager-for-exchange/kb/133684. |
PT133202635 | Synchronization of a mailbox might stuck at 'In Progress' in the following case:
For instance, the issue occurs if source user folder and target well-known folder are both named 'RecipientCache' and also there is a duplicate folder 'RecipientCache1' at source which acts as a well-known folder and is specified in the |
Product Name | Product Version | Platform |
Migration Manager for Exchange | 8.12 | All supported |
The following files are shipped:
For the list of updated files, see the FilesUpdatedReport.html file shipped with the update.
To install the update, complete the following steps:
NOTE: During the Repair operation for an instance of MAgE agent or for the certain agent role, this update will be installed on all instances of all MAgE agent roles that reside on the agent host.
The installation does not affect existing settings. All your projects remain intact and can be continued after installation.
To determine if this update is installed, complete the following steps:
Dell listens to customers and delivers worldwide innovative technology, business solutions and services they trust and value. For more information, visit
www.quest.com.
For sales or other inquiries, visit http://quest.com/company/contact-us.aspx or call 1-949-754-8000.
Support is available to customers who have a trial version or who have purchased Dell software and have a valid maintenance contract. The Support Portal at http://quest.com/support/ is the definitive resource for technical support with self-help capabilities so you can solve problems quickly and independently 24 hours a day, 365 days a year. The portal also provides direct access to our support engineers through an online service request facility. From one central location, you will find everything you need - support offerings, policies and procedures, contact information, as well as:
1 For trial users please use the Trial Downloads to get the latest generally available version of the software.
Quest Software is now Dell.
© 2017 Dell Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Dell Inc.
The information in this document is provided in connection with Dell products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Dell products. EXCEPT AS SET FORTH IN DELL'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, DELL ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL DELL BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF DELL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Dell makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Dell does not make any commitment to update the information contained in this document.
If you have any questions regarding your potential use of this material, contact:
Dell Inc.
Attn: LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
Refer to our Web site (www.quest.com) for regional and international office information.
Dell and the Dell logo are trademarks of Dell Inc. and/or its affiliates. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims any proprietary interest in the marks and names of others.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center