What's in the Migration Manager for Exchange 8.13 Latest Hotfix

What's in the Migration Manager for Exchange 8.13 Latest Hotfix

In order to view fixes available with the latest cumulative hotfix for Migration Manager for Exchange please see below.

Update 20171025EX Readme /* GENERIC */ body { background-color: #ffffff; color: #000000; font-family: Arial, Verdana, Geneva, Helvetica, sans-serif; font-size: 1.0em; margin: 1.7em; } hr { height: 1px; color: #aaaaaa; background-color:#aaaaaa; border:0px none; } /* HEADING */ h1 { color: #0078b6; font-size: 1.1em; font-weight: bold; letter-spacing: 0.03em; margin-top: 0.5em; margin-bottom: 0.5em; } h2 { color: #0078b6; font-size: 0.95em; font-weight: bold; letter-spacing: 0.03em; margin-top: 0.9em; margin-bottom: 0.4em; } h3 { color: #0078b6; font-size: 0.8em; font-weight: bold; letter-spacing: 0.03em; margin-top: 0.5em; margin-bottom: 0.5em; } h4 { color: #0078b6; font-size: 0.8em; font-weight: bold; font-style: italic; letter-spacing: 0.03em; margin-top: 0.5em; margin-bottom: 0.5em; } /* PARAGRAPH */ p { font-size: 0.8em; margin-top: 0.2em; margin-bottom: 0.3em; } p.product { color: #0085c3; font-size: 1.3em; font-weight: bold; letter-spacing: 0.03em; margin-top: 0.5em; margin-bottom: 0.5em; } p.version { color: #0078b6; font-size: 0.85em; font-weight: bold; letter-spacing: 0.03em; margin-top: 0.5em; margin-bottom: 0.5em; } p.title { color: #444444; font-size: 1.1em; font-weight: bold; margin-top: 1em; margin-bottom: 0.2em; } p.date { font-size: 0.8em; margin-top: 0; margin-bottom: 1.0em; } p.toc { margin-left: 1.8em; } p.nav { font-size: 0.7em; text-align: right; margin-bottom: 0.7em; } p.dummy { font-size: 0.4em; margin-top: 0.2; margin-bottom: 0.2em; } p.syntax { font-family: "Courier New", Courier, monospace; } p.path { font-family: "Lucida Console", Monaco, monospace; } p.writernote { color: #ff0000; } /* LINK */ a:link { color: #0078b6; text-decoration: none; } a:active { color: #0078b6; text-decoration: underline; } a:visited { color: #0078b6; text-decoration: none; } a:hover { color: #0078b6; text-decoration: underline; } /* SPAN */ span.syntax { font-family: "Courier New", Courier, monospace; } span.writernote { color: #ff0000; } /* LIST */ ul { font-size: 0.8em; margin-top: 0.7em; margin-bottom: 0.7em; margin-left: 2.0em; } ul.writernote { color: #ff0000; } ul ul { font-size: 1.0em; margin-top: 0.3em; margin-bottom: 0.3em; margin-left: 1.8em; } ul ol { font-size: 1.0em; margin-top: 0.3em; margin-bottom: 0.3em; margin-left: 1.8em; } ol { font-size: 0.8em; margin-top: 0.7em; margin-bottom: 0.7em; margin-left: 2.6em; } ol.writernote { color: #ff0000; } ol ol { font-size: 1.0em; margin-top: 0.3em; margin-bottom: 0.3em; margin-left: 1.2em; list-style: lower-alpha; } ol ul { font-size: 1.0em; margin-top: 0.3em; margin-bottom: 0.3em; margin-left: 1.2em; } li { font-size: 1.0em; margin-bottom: 0.2em; } li p { font-size: 1.0em; } li.syntax { font-family: "Courier New", Courier, monospace; } li.writernote { color: #ff0000; } /* TABLE */ table { border: 1px solid #444444; border-collapse: collapse; background-color: #ffffff; width: 85%; margin-top: 0.7em; margin-bottom: 1em; } table.details { border: 0; width: 100%; margin-top: 0; margin-bottom: 0; } table.contact { border: 0; width: 85%; margin-top: 0.7em; margin-bottom: 1em; background-color: #ffffff; } td { font-size: 0.75em; border: solid 1px #444444; padding: 0.5em; text-align: left; vertical-align: top; } td ul { font-size: 1.0em; } td ol { font-size: 1.0em; } td p { font-size: 1.0em; } td.header { font-weight: bold; background-color: #eeeeee; padding: 0.5em; text-align: left; vertical-align: middle; } td.section { font-weight: bold; } td.container { border: none; padding: 0; } td.spacer { background-color: #ffffff; font-size: 0.01em; padding: 0; }

Dell Migration Manager for Exchange 8.13

Update 20171025EX—Readme

October 26, 2017

 

Contents

Read This First

New in This Update

New in Previous Updates

Known Issues

Applicability of This Update

Contents of This Package

Files Updated

How to Install This Update

How to Determine If This Update Is Installed

For More Information

 

---

Read This First

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.13.

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.
• It is strongly recommended to create a backup of SQL database before you install this update.
• After you install this update, and then update the SQL database, it is NOT recommended to start the MAgE agent instances that are not updated. If you do not follow this recommendation, you may experience some problems with your migration database and other undesirable side effects.
• After installing this update, you will need to use Client Profile Updating Utility (CPUU) version 5.6.4 or higher. It is recommended to use the latest available version.

 

Back to Top

---

New in This Update

Resolved Issues

The following is a list of issues resolved by this update:

Defect ID

Issue Description

MMEX-2675

Migration process is not started for new mailboxes with the following message: Error Microsoft.Exchange.WebServices.Data.AutodiscoverLocalException: The Autodiscover service couldn't be located. Exchange 2010 SP1 is displayed in the log file instead of correct Exchange 2003 version. Scope: Migration from Exchange 2003 after installing the Dell Migration Manager for Exchange 8.13 Update 20170801EX Root-cause: Soft fault of exchange server version identification algorithm. Fix: Exchange server version identification algorithm is now fixed. After installing this update all mailboxes will be processed correctly.

Updates the following components: all Migration Manager for Exchange components.

New in Previous Updates

Features and Enhancements

• The following Exchange versions have been verified and confirmed as completely supported migration sources and targets:
  1. Microsoft Exchange 2013 with the recently released Cumulative Update 17
  2. Microsoft Exchange 2016 with the recently released Cumulative Update 6
• PT134132925
  User setting handling for Public folder synchronization agents (Exchange 2016 or later) is now improved. Public folder synchronization agent now uses user settings from pre-configured Outlook profile instead of using Exchange Autodiscover service. This approach allows for getting round time-consuming Autodiscover calls and related connectivity issues, ensuring faster and more reliable synchronization.
• PT142692877
  Load Balancer support for NativeMove scenarios is now improved. Now you can add a remote host to the project database using new Add-ExchangeRemoteHost cmdlet. The host should be added if it is not included in project database and / or in case of this host is not an Exchange Server, e.g., in case of specified FQDN is used as Load Balancer solution in Exchange organization. The added remote host can be later specified as SourceRemoteHostName or TargetRemoteHostName for NativeMove collection.
• New MoveRequestSourceGlobalCatalog and MoveRequestTargetGlobalCatalog parameters were provided to improve Global catalog discovery.
  PT136681939: Global catalog discovery (for native mailbox move) may take too much time, depending on the number of GCs and their geographical locations.
  Scope:
  Mailbox migration using native move job.
  Root-cause:
  MAgE checks all existing global catalogs in alphabetical order.
  Fix:
  It is recommended to manually specify the nearest source / target global catalog for each collection via PowerShell command. For details see Collection parameters.
• Migrating mailboxes to Microsoft Exchange 2016 using the native mailbox move is now supported.
• The following Exchange versions have been verified and confirmed as completely supported migration sources and targets:
  1. Microsoft Exchange 2007 including released Update Rollup 23
  2. Microsoft Exchange 2010 including released Update Rollup 17
  3. Microsoft Exchange 2013 including released Cumulative Update 16
  4. Microsoft Exchange 2016 including released Cumulative Update 5
• The following Exchange versions have been verified and confirmed as completely supported migration sources and targets:
  1. Microsoft Exchange 2007 with the recently released Update Rollup 22
  2. Microsoft Exchange 2010 with the recently released Update Rollup 16
  3. Microsoft Exchange 2013 with the recently released Cumulative Update 15
  4. Microsoft Exchange 2016 with the recently released Cumulative Update 4
• Microsoft Windows Server 2016 is now supported as an agent host operating system for Migration Agent for Exchange.
• Microsoft Exchange 2016 is now completely supported migration source for all the scenarios using MAgE.
• PT134190679: Now if you disable and then enable a collection in Migration Manager for Exchange console, its mailboxes are taken for processing as soon as possible ignoring delays set by the minimal processing intervals described in Adjusting minimum processing intervals for MAgE. That provides ability to troubleshoot migration of certain mailboxes without affecting performance of the whole migration project.
  Scope: Migration to Office 365
• PT131870051: Synchronization statistics of collections and mailboxes within collections can be now obtained through Powershell using the new Get-DMMExCollectionStatistics and Get-DMMExMailboxStatistics cmdlets, respectively. For details, see Configuring Migration Using PowerShell.
• PT131544799: There is now an ability to explicitly define the FQDN of Client Access server on which the instance of the Microsoft Exchange Mailbox Replication service (MRS) runs for a native move collection.
  For details, see description of the MRSServer parameter in Configuring Migration Using PowerShell and at New-MoveRequest TechNet article.
• Migration to Exchange 2010 Using MAgE
  Now for mailbox and calendar synchronization you can use modern Migration Agent for Exchange instead of legacy agents in migration scenarios from Exchange 2010 or 2013 to Exchange 2010. This approach has lots of benefits including detailed migration statistics right from the console, more transparent set of required permissions, configuration, update and troubleshooting processes are simplified, improved scalabity, etc.
  Detailed instructions how to prepare environment for such migration scenario are provided in the Target Exchange 2010 Environment Preparation (MAgE) document.
  Note that the following specifics apply:
  1. Unlike legacy agents, if you migrate using MAgE to Exchange 2010 it is not possible to keep existing offline folders (OST) files. If Outlook runs in cached mode, after CPUU processing of the Outlook profile is completed a new OST file will be created for it and then populated with content of the corresponding target mailbox.
  2. In case migration to a mixed target Exchange 2010 and 2013 is performed using MAgE, if in collection settings it is configured to create mailboxes in Exchange 2010, but DSA has previously created mailboxes for mailbox-enabled users in Exchange 2013 mailbox database, MAgE will not be able to automatically move mailbox from Exchange 2013 to Exchange 2010 database. To avoid this issue in the described scenario you need to configure DSA to create mailboxes for mailbox-enabled users in Exchange 2010 mailbox database. If you already encountered this issue, you can move mailboxes manually from Exchange 2013 to Exchange 2010 database.
  3. MAgE always works with source Exchange through EWS in case of migration from Exchange 2010 or 2013 to Exchange 2010 using MAgE, regardless of the UseEwsProtocolForSourceIfAvailable parameter value.
  4. Once migration of a mailbox has been started using legacy agents, it has to be completed with them as well. If you try to continue migration of the mailbox using MAgE, duplicates in the target mailbox will occur. To avoid this issue, delete the target mailbox and start migration of the mailbox from scratch.
  5. MAgE setup program requires Microsoft Exchange MAPI and CDO 1.2.1 to be installed on the agent host during installation of the agent for Exchange 2010/2013 to Exchange 2010 synchronization jobs. This happens because setup prerequisites are generalized for different types of synchronization jobs.
• PT3007691: Now you can configure migration project to support scenarios where Active Directory syncrhonization is performed using third-party tools instead of Migration Manager for Active Directory. For details, see description of the SupportADSyncThroughThirdPartyTools parameter in Configuring Migration Using PowerShell.
• PT107027980: Now if you disable and then enable a collection in Migration Manager for Exchange console, its mailboxes are taken for processing as soon as possible ignoring delays set by the minimal processing intervals described in Adjusting minimum processing intervals for MAgE. That provides ability to troubleshoot migration of certain mailboxes without affecting performance of the whole migration project.
  Scope:
  Mailbox synchronization from Exchange 2003-2013 to Exchange 2013-2016
  Native mailbox move from Exchange 2003-2013 to Exchange 2003-2013
• Configure whether to apply filter settings for calendar items synced from target to source for a switched mailbox or during two-way calendar synchronization (PT127186953). For more information, see description for the UseFilteringInBackwardSync in Configuring Migration Using PowerShell.
• Microsoft Exchange 2013 with the recently released Cumulative Update 14 is verified and confirmed as a completely supported migration source and migration target.
• Microsoft Exchange 2016 with the recently released Cumulative Update 3 is verified and confirmed as a completely supported migration target.
• The maximum possible values of SizeLimitInMbPerBatchUploadToExchange and SizeLimitInMbPerBatchUploadToO365 have been decreased to 112MB. If current parameter value exceeds that limit, it will be automatically changed to 112MB. Also, the default value of the MaxItemCountPerBatchUploadToO365 parameter has been decreased to 32. For details, see Configuring Migration Using PowerShell.

IMPORTANT:

Specifically, for migration to the Office 365, after installing the public update 20170530EX, please ensure you will use Collection Management Utility (CMU) version 3.10 or later. In Office 365 collection settings the Subscription column now should use subscription ID (for example cb4f3c81-2751-4b0a-8877-55cf5a0f44b3), instead of account Sku ID (for example tenant::AAD_PREMIUM). This change is mandatory.

Resolved Issues

This cumulative update package contains all hotfixes for Dell Migration Manager 8.13 issues that have been included in the earlier updates:

Defect ID	Issue Description
MMEX-2675	Migration from partly supported Exchange Server versions (Exchange 2010 prior to SP2 and from Exchange 2013 prior to SP1) is not allowed. Scope: Migration from Exchange 2010 prior to SP2 and from Exchange 2013 prior to SP1. Root-cause: Exchange Server version detection procedure cannot handle Exchange 2010 prior to SP2 and Exchange 2013 prior to SP1 correctly. Fix: Now migration from partly supported Exchange Server versions (Exchange 2010 prior to SP2 and from Exchange 2013 prior to SP1) is allowed.
MMEX-2314	Mailbox migration process may hang for the specific mailbox (other mailboxes in the collection are correctly processed.) The following error is displayed: Operation is not valid due to the current state of the object. Scope: All migration scenarios supported by MAgE Root-cause: The problematic mailbox contains the message that is very close to the maximum size allowed by Migration Manager for Exchange settings (specified in SizeLimitInMbPerBatchUploadToO365, SizeLimitInMbPerBatchUploadToExchange.) In some cases, it may result in producing MAgE batch that exceeds the maximum allowed size. Fix: MAgE now try to upload messages with critical size to target mailbox. In case this attempt will be unsuccessful due to target Exchange settings, the error returned with target Exchange will be logged.
MMEX-3014	The Error during check connect to database or update version database message can appear when you try to run Migration Manager Console after installing of 20170530EX product update. Scope: Mailbox migration using the Native Move job. Projects where the EXCH_SERVER_PROPERTY table of SQL database was manually edited by user (e.g. under Running Native Move with MMEX when Load Balancers are used in source or target Exchange organizations) Root-cause: Previous version of UpdateDB.sql cannot process such EXCH_SERVER_PROPERTY table entries. Fix: Now the SQL database updating procedure was improved to process such entries correctly.
MMEX-2700	The Object reference not set to an instance of an object message can appear in case restarting of Migration Manager Console after agent host deleting. Scope: All supported migration scenarios Root-cause: Agent host can be deleted from Agent Management in specific case of agent instance installed on it is assigned as the Default agent for any synchronization job. Fix: Now the agent host deletion processing have been modified to avoid the issue. Agent host cannot be deleted from Agent Management in the case of agent instance installed on it is involved in some job. To remove the agent host from database using Agent Manager, you need to delete all associations with this server in mailbox and calendar synchronization collections, and replace it in the Default Collection Options | Default agent settings of each affected mailbox/calendar synchronization job.
MMEX-2494	Manual mailbox switch may be unsuccessful for particular cases of load balancer solutions at target. Scope: Mailbox migration in case of load balancer solutions in target Exchange environment, in case of SupportADSyncThroughThirdPartyTools is set to True. Root-cause: By default, PowerShell session is created with the Exchange server that has been used to add the target Exchange organization. In case of load balancer solutions the FQDN of the target Exchange server cannot be found and need to be specified manually for successful completion of manual mailbox switch. Fix: PSConnectionServer now also specifies FQDN of the target Exchange server or load balancer to find target mailbox information for manual switch.
MMEX-1722; PT142210619	Migration Manager for Exchange is configured to assign a license of subscription A, but MAgE fails to assign that license to a Microsoft Office 365 user who already has a license of subscription B. Scope: All migrations to Office 365 Root-cause: MAgE was not configured to assign selected license in case of Microsoft Office 365 user had multiple licenses from different subscription plans, and by default the license that is already registered in project is used. Fix: To use improved license assigning mechanism of MAgE for multiple license usage is recommended to reconfigure subscription settings through Migration Manager console UI.
MMEX-1727; PT143029371	Ready to switch status for migrated mailbox cannot be achieved if there are any folders of IPF.Files class at source. Scope: Mailbox migration from Exchange 2016 Root-cause: MAgE consider the migration of folders of IPF.Files class as required to achieve the Ready to switch status for migrated mailbox. Fix: Any folder of IPF.Files class including subfolders will be skipped under migration process to avoid the situation.
MMEX-2495	Display Name is not shown in migrated contacts at target only for users who access them using Outlook Web Access. Scope: Migration scenarios supported by MAgE from Exchange 2010 at source to Exchange 2013 or higher at target, in case of UseEwsProtocolForSourceIfAvailable is set to True (default value). Root-cause: Issue is caused by property set differencies between Exchange 2010 and Exchange 2013 or higher only in case of Outlook Web Access is used. Fix: Display Name is now generated and displayed correctly for Outlook Web Access.
MMEX-1730; PT143484607	An unquoted service path used by Migration Manager services is inconsistent with CVE-2013-1609, CVE-2014-0759 and CVE-2014-5455 vulnerability requirements . Scope: Migrations performed by MAgE Root-cause: Services installed by Migration Manager software may use an unquoted service path, which contains at least one white space that is inconsistent with CVE-2013-1609, CVE-2014-0759 and CVE-2014-5455 vulnerability requirements. Fix: Now MAgE sets the quotes at the beginning and end of the server path.
MMEX-1769	PFTA stops processing when it tries to compact PST file in case of content cannot be fully synchronized. The last log message is the following: MailContainer::Compact TraceMsg 1702 Starting to compact PST file. Scope: Public Folders migration to Exchange 2016 Fix: Now the PST file compacting and archiving completes successfully and does not stop migration process.
PT143310703	If JunkEmail is specified in the list of WellKnownFoldersToSkip (see details at Configuring Migration Using PowerShell) mailbox processing might hang at migration stage "In Progress" and so can’t be switched automatically. A message The folder 'Junk-E-Mail' was not processed. Messages in folder: '2'. Probably the given folder does not exist in target mailbox. If the problem is persistent, please resync mailbox with ClearAllSyncDataOnResync. is displayed. Scope: Mail synchronization jobs at the following scenarios: Migration scenarios from Exchange 2003 or from Exchange 2007. All migration scenarios supported by MAgE, started from 8.11 either from 8.12 and continued in 8.13. All migration scenarios supported by MAgE, in case of UseEwsProtocolForSourceIfAvailable is set to False. Root-cause: MAgE mechanism to detect JunkEmail folder might fail under the certain circumstances. Fix: To avoid the issue MAgE mechanism for detecting JunkEmail was improved.
PT134353545	The Contact item properties can be corrupted after migration. Scope: Migration scenarios from Exchange 2003 or from Exchange 2007. All migration scenarios supported by MAgE, started from 8.11 either from 8.12 and continued in 8.13. All migration scenarios supported by MAgE, in case of UseEwsProtocolForSourceIfAvailable is set to False. Root-cause: The properties ID, used in processing of the Contact items, have not been hardcoded – so we have the risk of corrupting these properties during migration. Fix: The algorithm of processing of the Contact items has been improved to avoid using hardcoded IDs.
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 the Native Move job. Root-cause: MAgE was not able to get information required for New-MoveRequest in case of 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.
PT139013717	Migration of a mailbox fails if there is a user-created folder named 'Files' at source. Scope: Mailbox migration from any supported source to Microsoft Office 365 or Exchange 2016 with Cumulative Update 4. Root-cause: MAgE was not able to handle folders of IPF.Files class properly. Fix: The algorithm of duplicate avoidance has been enhanced to handle a user folder named 'Files' properly.
PT139013717	Migration of a mailbox always fails for the described scope. Scope: Mailbox migration from Microsoft Exchange 2016 with Cumulative Update 4 to Microsoft Office 365 or Exchange 2016 with Cumulative Update 4. Root-cause: MAgE was not able to handle folders of IPF.Files class properly. Fix: A system folder Files introduced for Exchange 2016 is now excluded from mail migration using WellKnownFoldersToSkip parameter.
PT136661617	An excessive memory consumption may occur in case of large messages migration. Scope: Mailbox migration scenarios where connection to source Exchange is performed through EWS Backward calendar synchronization using MAgE Root-cause: The number and size of messages to be downloaded at once was not limited neither by size nor by number of items. Fix: Parameters MaxItemCountPerBatchExportViaEws and SizeLimitInMbPerBatchExportViaEws that set size and count limits for downloading mailbox items have been introduced. For more information, see Configuring Migration Using PowerShell. Also, a mechanism preventing excessive memory consumption in case of encountering extra large mailbox items has been implemented.
PT135220929	Migration of mailboxes fails if connection to Exchange server is required to be performed through a hardware load balancer. Scope: All migrations performed by Migration Agent for Exchange when a third-party tool is used for directory synchronization. For details, see SupportADSyncThroughThirdPartyTools description in Configuring Migration Using PowerShell. Root-cause: MAgE was unable to connect to Exchange servers in organization where only hardware load balancer had been exposed externally. Fix: New PSConnectionServer parameter that specifies Exchange server with which MAgE and Console will establish PowerShell session. To resolve the described issue, specify the load balanced namespace in this parameter.
PT138400461	Custom folder permissions may be set incorrectly in a target mailbox during mailbox synchronization if SupportADSyncThroughThirdPartyTools is set to true. Scope: All migrations performed by Migration Agent for Exchange when a third-party tool is used for directory synchronization. For details, see SupportADSyncThroughThirdPartyTools description in Configuring Migration Using PowerShell. Root-cause: An issue related to user matching caching was introduced in Update 20170117EX for Migration Manager for Exchange 8.13. Fix: The issue with user matching has been fixed so that now custom folder permissions are synchronized properly in the described case.
PT137793117	Migration Agent for Exchange may create item duplicates in the source mailbox during backward calendar synchronization. Scope: Calendar synchronization in case of migration from Exchange 2013 using MAPI. Root-cause: During backward calendar synchronization Migration Agent for Exchange attempted to modify the asfReceived flag of PidLidAppointmentStateFlags appointments' property, which caused data corruption and creation of duplicates due to automatic retries. Fix: Now Migration Agent for Exchange does not modify the asfReceived flag of PidLidAppointmentStateFlags appointments' property in the described case.
PT137157685	Migration of a mailbox fails if its proxyAddresses attribute has multiple X500 addresses and the first one does not belong to the corresponding target mailbox. Scope: All migrations performed by Migration Agent for Exchange Root-cause: MAgE failed to find a target mailbox's legacyExchangeDN matching address of the source mailbox. Fix: MAgE mechanism of finding matching target mailbox's legacyExchangeDN has been improved.
PT135206169	Migration halts for target Exchange organizations that include DAG if migration project has the SupportADSyncThroughThirdPartyTools parameter set as true. Scope: All migrations to on-premises Exchange organizations performed by MAgE Root-cause: MAgE was unable to gather information from a target Exchange organization in case DAG was deployed there and the SupportADSyncThroughThirdPartyTools parameter was set as true.
PT133017559	Migration of mailboxes in which one or more contacts do not have the Subject field fails. Scope: Migration from Exchange 2007 or 2010 to Exchange 2010, 2013, 2016 or Office 365 using MAgE Root-cause: MAgE failed to handle the situation when any contact lacked the Subject property. Fix: Now MAgE can migrate such mailboxes properly.
PT132648487	Duplicates appear in the target mailbox after retrying migration of messages for which EWS upload has previously failed. Scope: Migration from Exchange 2010 or 2013 to Exchange 2013, 2016 or Office 365 in case the EWS protocol is used to communicate with source (default behavior) Root-cause: MAgE was not properly detecting already migrated messages in case EWS was used to communicate with a source mailbox. Fix: Now MAgE properly detects already migrated messages which prevents creation of duplicates in the described case.
PT132341609	Out of Office automatic replies messages are not synchronized before mailbox switch Scope: Migration to Exchange 2013, Exchange 2016 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.
PT134681549	A mailbox might not be processed in case of target Exchange organization includes several Exchange servers. Scope: Migration from Exchange 2010 or 2013 to Exchange 2013, 2016 or Office 365. Root-cause: To get the server information from the target Exchange organization, MAgE used the component which have the following issue: resulting XML data returned by the SQL server are truncated by the certain length. So, in case of several Exchange servers in the target Exchange organization, the mailbox processing might be stopped. Fix: Now MAgE uses a different method to get the necessary data, thereby avoiding the problem.
PT13167525	Mailbox or calendar synchronization fails to process folder permissions that are granted to non-migrated users or users that have not been assigned an Office 365 license yet. Scope: Migration to Microsoft Office 365 Root-cause: MAgE had a bug in a mechanism of processing folder permissions in the described case. Fix: Now MAgE ignores folder permissions that are assigned to non-migrated users or users that have not been assigned an Office 365 license yet. Therefore, such folder permissions will not be migrated, which is the expected behavior. A corresponding warning message will appear in MAgE logs in this case.
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: Source mailbox has well-known folders with localized non-English name and user folders with the same name. For instance, 'Calendar' and 'Agenda' (stands for 'Calendar' in Dutch). Source mailbox has folders with names that differ only by their suffix and one of folders is a well-known folder. For instance, folders 'Calendar' and 'Calendar1', where 'Calendar1' is acting as a well-known folder. Scope: Migration to Exchange 2013, 2016 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: The most recently created folder from the source mailbox was matched to the corresponded folder at target. Content of the other folders with that name was not taken for processing. This caused the mailbox to stuck at 'In Progress' state and therefore it could not be switched. 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 <Source folder name>_<FOLDER_SOURCE_KEY> 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: Clear all content of the mailbox at target. Do not skip this step, otherwise subfolders of the same-named folders may not be resynchronized properly. Perform full resynchronization of the mailbox with the ClearAllSyncDataOnResync parameter set as TRUE. See also KB article 213779.
PT131649893	Content of Sync Issues folder and its subfolders Conflicts, Local Failures, Server Failures is not skipped even if the Sync Issues folder is specified in the WellKnownFoldersToSkip parameter. Scope: Mailbox migration from Exchange 2010 to Exchange 2013, 2016 or Office 365 initiated from Migration Manager for Exchange 8.13. Root-cause: Starting version 8.13, MAgE uses EWS managed API to support migration scenarios from Exchange 2010 and 2013. The Sync Issues folder has not been identified as well-known folder through EWS managed API in case of source Exchange 2010. Fix: MAgE mechanism of well-known folder detection now identifies the Sync Issues folder as well-known folder properly in the described case. The Sync Issues folder along with its subfolders are now always skipped as their content is not meaningful at target. Note that Sync Issues folder will be skipped even if before this update WellKnownFoldersToSkip parameter did not include it. Note that value of the WellKnownFoldersToSkip parameter will not be preserved during update installation. You need to restore its value manually after update installation if necesssary.
PT132760481	If MAgE fails to log on to source or target mailbox through EWS due to the Mailbox move in progress error, migration of that mailbox fails. Scope: Migration to Exchange 2013, 2016 or Office 365 Root-cause: By variety of reasons source or target Exchange may perform a mailbox move operation during which a mailbox cannot be logged into using Exchange Web Services. If MAgE encounters such problem, it is considered as a critical error and thus migration of the mailbox fails (migration stage becomes Failed). Fix: Now MAgE treats the described problem as transient, so if it happens the current migration session will just be aborted without changing the migration stage and MAgE will attempt to continue migration of the mailbox in the next migration session.
PT131298645	Messages which content includes properties of the WM_BINARY type cannot be migrated. For instance, such properties exist if message recipients expose their public key for message encryption. In the Statistics pane such items are treated as Failed. Scope: Migration to Exchange 2013, 2016 or Office 365 Root-cause: MAgE did not support migration of messages with WM_BINARY properties. Fix: Now messages that have properties of the WM_BINARY type are successfully synchronized by MAgE in both forward and reverse directions
PT131980477	Some of dynamic collection members might not be taken for processing for a long time. Scope: Migration to Exchange 2013, 2016 or Office 365 Impact: Some of mailboxes for dynamic collections (collections populated through organization group or OU), might require a lot of time to complete the initial sync stage or might have a huge synchronization latency. Root-cause: MAgE had a bug in a mechanism of selecting a mailbox to process from a dynamic collection. Fix: Now the bug has been resolved. Also, mailboxes recently added to a dynamic collection will be taken for processing at the first place.
PT132242543	If you perform resynchronization of a mailbox with the UseSmartResync parameter configured to be TRUE, it may stuck. For details on UseSmartResync parameter, see Configuring Migration Using PowerShell. Scope: Mailbox migration from Exchange 2010, 2013 to Exchange 2013, 2016 or Office 365 initialized from Migration Manager for Exchange 8.13. Root-cause: A bug in the resynchronization mechanism. Fix: The bug in the MAgE resynchronization mechanism that caused the issue has been fixed.
PT127354679	Migration performance may degrade due to well-known folder detection failures Scope: Migration to Exchange 2013, 2016 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, 2016 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.
PT130522047	Most of specific settings of mailboxes cannot be processed by CPUU if MAgE connects to source through EWS. Scope: Migration from Exchange 2010 or 2013 to Exchange 2010, 2013, 2016 or Office 365 Impact: Most of specific settings of mailboxes such as Favorites, Calendar Pane, Contacts Pane, etc., are not processed by Client Profile Updating Utility if MAgE connects to source Exchange through EWS. Root-cause: MAgE did not mark migrated content properly in case MAgE connected to source through EWS. Fix: Now content migrated by MAgE from source is marked properly in the described case. Note that in order to process by CPUU specific settings of mailboxes previously migrated through EWS, a resynchronization of those mailboxes is required.
PT127804371	SQL Server performance may drop over time in case of two-way calendar synchronization Scope: Migration to Exchange 2013, 2016 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.
PT126610849	Reverse calendar sync may fail in case the default calendar has been changed Scope: Migration to Exchange 2013, 2016 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.
PT129943875	Skipped items counter is reset after the product update installation Scope: Migration to Exchange 2013, 2016 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.
PT127370119	Migration performance may decrease as well as agent host disk space utilization increases after MAPI logon failures Scope: Migration to Exchange 2013, 2016 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.
PT119263439	Migration to a recreated mailbox database fails Scope: Migration to Exchange 2013, 2016 or Office 365 Impact: Migration fails if a mailbox database has been deleted and then created again with the same DisplayName. Root-cause: MAgE tries to work with a deleted mailbox database. Fix: MAgE algorithm is improved to use a newly created mailbox database instead of the deleted one.

Updates the following components: all Migration Manager for Exchange components.

 

Back to Top

---

Known Issues

The following known issue exists at the time of the update release:

Defect ID

Issue Description

PT133202635

Synchronization of a mailbox might stuck at 'In Progress' in the following case: A source mailbox has a user folder with the same name as the one of the well-known folders in a target mailbox. This also means there is a duplicate folder acting as well-known folder at source. The source well-known folder is listed as a well-known folder to skip using the WellKnownFoldersToSkip parameter. 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 WellKnownFoldersToSkip parameter. Scope: Migration to Exchange 2013, 2016 or Office 365 Root-cause: In the described case when MAgE attempts to clarify whether the current source well-known folder is matched to the corresponding target well-known folder, the mailbox processing might be halted. It stucks at 'In Progress' state and therefore cannot be switched.

 

Back to Top

---

Applicability of This Update

Product Name	Product Version	Platform
Migration Manager for Exchange	8.13	All supported

 

Back to Top

---

Contents of This Package

The following files are shipped:

1. DellMigrationManager_8.13_Update20171025EX.msp—update package.
2. MigrationManager_8.13_Update_20171025EX.htm—this file.
3. FilesUpdatedReport.html

 

Back to Top

---

Files Updated

For the list of updated files, see the FilesUpdatedReport.html file shipped with the update.

 

Back to Top

---

How to Install This Update

To install the update, complete the following steps:

1. It is strongly recommended to create a backup of SQL database before you install this update.
2. Ensure that you have .NET Framework 4.5 installed on all agent hosts running Migration Agent for Exchange.
3. Stop all Migration Agents for Exchange (MAgE) agents on all agent hosts.
4. Stop all COM+ applications that are used by MAgE agents. For that, go to Start | Administrative Tools | Component Services to open the Component Services console. In the console tree view, go to Component Services | Computers | My Computer | COM+ Applications, then right-click the Dell Migration Agent for Exchange MAPI Assistant node and select Shut down.
5. On the computer where the Migration Manager console is installed, complete the following steps:
1. Close the Migration Manager console if it is running.
2. Open the Services MMC snap-in and stop all services provided by Dell.
3. Run the DellMigrationManager_8.13_Update20171025EX.msp file and complete the update setup wizard.
4. If you stopped any services on step b, start them again (except MAgE services).
5. Run the Migration Manager console. The SQL database will be updated automatically during the start of the Migration Manager console.
6. To update the legacy agents, do the following: in the Migration Manager console, right-click Exchange Migration Project on the Exchange Data tab and select the Hotfix Installation Wizard from the shortcut menu.
7. Follow the wizard steps to install the update on all computers with the components that need to be updated. The list of updated components is different depending on the updates that are already installed in your environment.
6. If you use Native Move or migrate to Office 365 or Exchange Server 2013, update all MAgE agents. For that, go to the Agents Management section in the Migration Manager console, and perform the Repair Agents action on every agent host that has Migration Agent for Exchange installed.

   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.

Back to Top

---

How to Determine If This Update Is Installed

To determine if this update is installed, complete the following steps:

• On each MAgE agent host
  1. Open Programs and Features in the Control Panel and check the version of MAgE: 8.13.0.3745.
  2. Open the list of installed updates in the Installed Updates section and check the current MagE update: Dell Migration Agent for Exchange 8.13 Update 20171025EX. Be advised that the list of installed updates contains only the latest installed update. All previous updates that were applied to the MagE agent earlier are not displayed.
• On the computer where Migration Manager console is installed
  1. Open Programs and Features in the Control Panel and check the version of Migration Manager: 8.13.0.3745.
  2. Open the list of installed updates in the Installed Updates section and check the current Migration Manager update version: Dell Migration Manager 8.13 Update 20171025EX.
  3. Check whether the MAgE.msp file exists in the following location: <DMMEx install folder>\Exchange Data\Hotfixes.
• After this update installation, check the agent log: the Product Version in the agent log is 8.13.0.3745, the version of the SQL database is 3604.

Back to Top

---

For More Information

Contact Information

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.

About Support

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:

• Create, update, and manage Service Requests (cases)
• Knowledge Base
• Product notifications
• Software downloads¹
• How-to videos
• Community discussions
• Chat option

¹ For trial users please use the Trial Downloads to get the latest generally available version of the software.

 

---

 

Copyright 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.

 

Trademarks

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.