Quest® Migration Manager for Exchange®
Version 8.15
Update 20201221EX - Readme
January 6, 2020
Public folder synchronization feature
Verifying successful completion
This update may require additional testing.
The minimum product version required for installing this hotfix is 8.15.
For complete product information, please refer to the Quest Migration Manager for Exchange product documentation and to the System Requirements and Access Rights document.
IMPORTANT:
· 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.8.3 or higher. It is recommended to use the latest available version.
· After installing this update, you will need to use Collection Management Utility (CMU) version 3.16.1 or higher.
See New Features and Enhancements for new features, enhancements, and system requirement changes, introduced by this update.
Refer to Known Issues for known issues that exist at the time of the update release.
Refer to Public Folder Synchronization Feature for current status of the feature.
The following is a list of issues resolved by this update.
Resolved issue | Issue ID |
If you migrate a public folder from on-premises to Office365 using two-way synchronization, it will generate duplicated public folder items in the on-premises location. Scope: Public Folder synchronization by MAgE Root-cause: MAgE agent will get different unique id when calling Microsoft EWS API even if for the same item or folder. Fix: Now MAgE add FixPublicFolderUniqueId and FixPublicFolderUniqueIdResyncFeature parameters on the cmdlets below to fix this issue · Set-MMExProjectOptions · Get-MMExProjectOptions · Reset-MMExProjectOptions. If FixPublicFolderUniqueId is set to true, MAgE agent will automatically fix the public folder’s unique ID when migrating public folder from on-premise to Office365 using two-way synchronization, otherwise MAgE agent will not adjust public folder item’s unique ID. If FixPublicFolderUniqueIdResyncFeature is set to true, MAgE agent will automatically clean up the existed duplicate public folder items on on-premise side when resyncing public folders from on-premise to Office365 using two-way synchronization, otherwise MAgE agent will not clean up the duplicated items. | MMEX-10634 |
Current feature status:
Category | Feature | Supported | Comments |
Synchronization | 2-way synchronization | yes | |
Migration from Exchange 2007 | NO | ||
Migration from/to Exchange 2019 | yes | Currently the following scenarios are supported: from Exchange 2019 to Exchange 2013/2016/2019 or to Office 365. | |
Migration from Exchange 2010/2013/2016 | yes | Currently the following scenarios are supported: to Exchange 2013/2016/2019 or to Office 365. | |
2-way synchronization for selected folders | NO | Synchronization direction can be set for all folders only. | |
Add, update, delete messages | yes | ||
Update public folders automatically | yes | Permissions including group permissions will be updated; renamed and/or moved public folder will be handled by ID. | |
Handle deleted folders automatically | yes | PublicFolderRecycleBin parameter of migration project can be used to specify whether to move deleted public folders to the Migration Manager Recycle Bin folders or permanently delete them. | |
Add new top-level folders | YES | New top level public folders can be detected and added to migration automatically by MAgE using DetectNewTopLevelFolders parameter. For details refer to Configuring Migration Using PowerShell. | |
Handle new subfolders of synced top-level folders automatically | yes | ||
Synchronize folders’ mail-enabled status | yes | ||
Re-migrate folders deleted on target | yes | If previously migrated folder has been deleted in target and need to be migrated from the scratch, the Remove-MMExPublicFolderMigration cmdlet can be used to remigrate this folder. | |
Resync | yes | ||
Synchronize permissions | yes | With PermissionsOnly switch for Restart-MMExPublicFolderMigration cmdlet you can synchronize permissions only | |
Synchronize SMTP address and advanced folder properties | yes | ||
Configuration | Define migration scope | yes | MigrateOnly parameter can be used to manage migration scope. |
Modify migration scope | yes | Migration can be suspended/resumed for specified public folders. Additional root folders can be added to migration scope. | |
Content filtering | yes | ||
Support for existing content structure on target | yes | ||
GUI | NO, MIGRATION BY MMEX POWERSHELL SCRIPTS ONLY | ||
System requirements | Minimal requirements | 1 host, 1 agent | |
Performance | Overall performance | high | |
Monitoring | Synchronization statistics | yes |
IMPORTANT: This section is for information purposes only, refer to online product documentation for actual information.
IMPORTANT: Before you install this product update, Microsoft .NET Framework 4.5.2 or higher should be installed on all agent hosts running Migration Agent for Exchange, Legacy agents and the Migration Manager console.
The following enhancements are implemented in this release:
Enhancement | Issue ID |
Using new -PermissionOnly switch you can select to resynchronize content and permissions or to resynchronize permissions only. This parameter can be used both with Restart-MMExMailboxMigration and Restart-MMExPublicFolderMigration cmdlets. | MMEX-10017, MMEX-1785 |
Collections can now be created not only from the Migration Manager Console UI, but can also be created using PowerShell. This release introduces the New-MMExCollection cmdlet to create collections. The parameter set for the New-MMExCollection cmdlet has now been updated to handle additional collection properties. For details refer to the Configuring Migration Using PowerShell. | MMEX-10323 |
Get-MMexCollectionMember is now enhanced to return SMTP for collection members. Some parameter names are changed. For details refer to the Configuring Migration Using PowerShell | MMEX-10377, MMEX-10471 |
Collections can now be removed not only from the Migration Manager console UI, but can also be removed using PowerShell. This release introduces the Remove-MMExCollection cmdlet to remove specified collections. | MMEX-10379 |
You can now add members to specified collections using Add-MMExCollectionMember cmdlet. For details refer to the Collection Member Management. | MMEX-10381 |
You can now remove specified members of specified collections using Remove-MMExCollectionMember cmdlet. For details refer to the Collection Member Management | MMEX-10382 |
Support added for the scenario where two source organization names have the same name with different letter case. Now you can provide organization ID to specify unique organization. For details refer to Collection parameters subsection of Configuring Migration Using PowerShell User Guide section. | MMEX-10240 |
Now new top level public folders can be detected and added to migration automatically by MAgE using DetectNewTopLevelFolders parameter for Set-MMExProjectOptions cmdlet. Both of the following conditions should be satisfied: · IPM_SUBTREE should be configured as public folder synchronization root folder. New top-level public folders will be detected on source (and target, respectively) only IPM_SUBTREE is processed by the MAgE · DetectNewTopLevelFolders parameter should be set to True for current project. For details refer to Configuring Migration Using PowerShell. | MMEX-10276 |
A new parameter MinProcessingInterval is introduced for Set-MMExCollection, Get-MMExCollection and Reset-MMExCollection cmdlets. It specifies the minimum time interval in minutes that must pass before an item in collection can be processed again. | MMEX-9689 |
The following is a list of issues resolved by this update.
Resolved issue | Issue ID |
Public folder is not synchronized, and the following error is reported: Error Cannot bind to the root folder %FolderPath%. Inner exception: The specified object was not found in the store., The process failed to get the correct properties. And a manual check shows that the service account has not been granted client permissions for this public folder. | MMEX-10286 |
MAgE failed to synchronize data due to issue with message processing, and the following error is reported for the message: Microsoft.Exchange.WebServices.Data.ServiceResponseException: The specified object was not found in the store. | MMEX-10624 |
Target public folder failed to be created in the specified mailbox using Import-MMExPublicFolderMapping cmdlet, and no event is reported. | MMEX-10581 |
This release introduces the following features and enhancements:
· Migration Manager now supports scenarios supported by MAgE for migration to Microsoft Office 365 tenants where Basic Authentication is turned off. This change is intended to support disabling Basic Authentication announced by Microsoft. By default, the Modern Authentication (based on OAuth 2.0) only will be used after this update is installed.
IMPORTANT: Please consider, after Basic Authentication is deprecated by Microsoft, public folder synchronization by legacy Exchange agents will no longer be supported. We recommend that you start using public folder synchronization by MAgE instead.
· The Microsoft Exchange 2013 organization is now supported as target for public folder synchronization by MAgE for all supported configurations. Refer to Public Folder Synchronization (MAgE) document for details.
The following enhancements are implemented in this release:
Feature | Enhancement | Issue ID |
General | A new parameter PreferInternalEwsUrl is introduced for Set-MMExOrganizationProperties. If AutodiscoverUrl is specified for the Exchange organization and the PreferInternalEwsUrl parameter is set to True, MAgE will first try to use the internal EWS Url. The default is False, this means MAgE first tries the external EWS Url. | MMEX-10098 |
Parameter set for Get-MMExCollection, Reset-MMExCollection, and Set-MMExCollection cmdlets is now updated to handle more collection properties. For details refer to the Configuring Migration Using PowerShell | MMEX-9720, MMEX-9719, MMEX-9628, MMEX-10038 | |
Mailbox Synchronization | Mailbox switch process is now enhanced and MAgE will attempt to complete the mailbox immediately after SyncPeriodAfterSwitch passes. The MinMailProcessingIntervalInSync is not now used as reference, because it may take a long time to complete a mailbox according to the default interval values. | MMEX-9688 |
Public Folder Synchronization | All new subfolders of public folders that are already included in synchronization scope will be detected and automatically added to the project. For working migration projects no action is required. Consider, top-level public folders (not nested to the folders included in the synchronization scope) intentionally cannot be handled automatically and should be added as described in Public Folder Synchronization by MAgE document. | MMEX-9908 |
Public Folder Synchronization feature is enhanced. Refer to Public Folder Synchronization (MAgE) document for job scheduling procedure and for additional information on Set-MMExGroupMatching and Sync-MMExMailPublicFolder cmdlets. | MMEX-9507, MMEX-9508 | |
Set-MMExGroupMatching cmdlet should only be used for the Microsoft Office 365 target, it is not required for on-premises targets. To handle on-premises migration scenarios, Set-MMExGroupMatching is not executed now as part of Start-MMExPublicFolderMigration. | MMEX-10097 |
The following is a list of issues resolved by this update.
Resolved issue | Issue ID |
Ready to switch status for migrated mailbox cannot be achieved and the following error message is reported:MigrationManagerForExchange.General.DotNet.AggrException: Exception of type 'MigrationManagerForExchange.General.DotNet.AggrException' was thrown. ---> MigrationManagerForExchange.Shared.Heart.MigrationManagerException: No mailbox with such guid. . | MMEX-9510, MMEX-9270 |
Sync-MMExMailPublicFolder does not work and the following error is reported: Cannot find path 'HKCU:\Software\Quest Software\Migration Manager for Active Directory\Directory Migration' because it does not exist. | MMEX-9702 |
This release introduced the following features and enhancements:
· Microsoft SQL Server 2019 is now supported. For details refer to System Requirements and Access Rights document.
· The Microsoft Exchange 2016 organization is now supported as http://support.quest.com/technical-documents/migration-manager-for-exchange/8.15/user-guide/appendix-c-migration-of-recoverable-items-subfolders-optionaltarget for public folder synchronization by MAgE for all supported configurations. Refer to Public Folder Synchronization (MAgE) document for details.
· Migration of items from the following subfolders of Recoverable Items folder:
o Deletions
o Purges
o DiscoveryHolds
o Versions
is now supported by MAgE for some scenarios. Consider, that the rest of Recoverable Items content is excluded from the migration scope. Refer to Configuring Migration of Recoverable Items for instructions on how to enable and use this feature.
The following enhancement is implemented in this release.
Feature | Enhancement | Issue ID |
General | The following Exchange versions have been verified and confirmed as completely supported migration sources and targets: 1. Microsoft Exchange 2019 including released Cumulative Update 4 2. Microsoft Exchange 2016 including released Cumulative Update 15 3. Microsoft Exchange 2010 SP3 including released Update Rollup 30 | MMEX-9277 |
LDAP Signing Configuration Requirements subsection is now added to System Requirements and Access Rights document. For details on Network security: LDAP client signing requirements policy refer to LDAP Signing Configuration Requirements. For working migration projects, no action is required. | MMEX-9165 |
The following is a list of issues resolved by this update.
Resolved issue | Issue ID |
If you migrate a public folder from on-premise to Office365 using two-way synchronization, it will generate duplicated public folder items in the on-premise folder.
Root-cause: Fix: MAgE added FixPublicFolderUniqueId and FixPublicFolderUniqueIdResyncFeature parameters on the cmdlets below to resolve this issue · Set-MMExProjectOptions · Get-MMExProjectOptions · Reset-MMExProjectOptions If FixPublicFolderUniqueId is set to true, the MAgE agent will automatically fix the public folder’s unique ID when migrating public folder from on-premise to Office365 using two-way synchronization, otherwise MAgE agent will not adjust public folder item’s unique ID. If FixPublicFolderUniqueIdResyncFeature is set to true, the MAgE agent will automatically clean up the existed duplicate public folder items on on-premise side when resyncing public folders from on-premise to Office365 using two-way synchronization, otherwise MAgE agent will not clean up the duplicated items. | MMEX-10634 |
The following known issue exists at the time of the update release:
Defect ID | Issue Description |
MMEX-10166 | Not suspended public folder is not synchronized, because it is marked as Failed in the project database. |
MMEX-9539 | Quest Migration Manager 8.15 product updates should not be uninstalled from the list of installed updates in the Installed Updates section. The product update removal is not supported. |
Product name | Version | Platform |
Migration Manager for Exchange | 8.15 | All supported |
The following files are shipped:
· QuestMigrationManager_8.15_Update20201221EX.msp - update package
· QuestMigrationManager_8.15_Update20201221EX.htm - this file
· FilesUpdatedReport.html - list of files to be updated
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.2 or higher installed on all agent hosts running Migration Agent for Exchange, Legacy Exchange agents, and the Migration Manager console.
3. Stop all 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 Quest 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:
a. Close the Migration Manager console if it is running.
b. Open the Services MMC snap-in and stop all necessary services provided by Quest.
c. Run the QuestMigrationManager_8.15_Update20201221EX.msp file and complete the update setup wizard.
d. If you stopped any services on step b, start them again (except MAgE services).
e. Run the Migration Manager console. The SQL database will be updated automatically during the start of the Migration Manager console.
6. Update all Migration Agent for Exchange and/or legacy Exchange agents, if any. Go to the Agents Management section in the Migration Manager console, and perform the Repair Agents action on every agent host that has installed agents. Before you start, ensure that these agent hosts have Microsoft .NET Framework 4.5.2 or higher installed.
NOTES:
o During the Repair Agents operation for an instance of legacy Exchange agent /MAgE agent or for the certain agent role, all instances of all agent roles that reside on the agent host will be upgraded.
o Legacy Exchange agents are stopped after Repair operation. Start necessary legacy Exchange agents manually.
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:
· On each MAgE agent host
1. Open Programs and Features in the Control Panel and check the version of MAgE: 8.15.4.6464.
2. Open the list of installed updates in the Installed Updates section and check the current MagE update: Quest Migration Agent for Exchange 8.15 Update 20201221EX. 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.15.4.6464.
2. Open the list of installed updates in the Installed Updates section and check the current Migration Manager update version: Quest Migration Manager 8.15 Update 20201221EX.
3. Check whether the MAgE.msp and LegacyAgents.msp files exist in the following location: <MMEx install folder>\Exchange Data\Hotfixes.
· After this update installation, check the agent log: the Product Version in the agent log is 8.15.4.6464, the version of the SQL database is 5540.
Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit www.quest.com.
Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.
The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:
· Submit and manage a Service Request;
· View Knowledge Base articles;
· Sign up for product notifications;
· Download software and technical documentation;
· View how-to-videos;
· Engage in community discussions;
· Chat with support engineers online;
· View services to assist you with your product.
© 2020 Quest Software 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 Quest Software Inc.
The information in this document is provided in connection with Quest Software 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 Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE 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 QUEST SOFTWARE 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 QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software 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. Quest Software 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:
Quest Software Inc.
Attn: LEGAL Dept
4 Polaris Way
Aliso Viejo, CA 92656
Refer to our Web site, https://www.quest.com, for regional and international office information.
Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at https://www.quest.com/legal.
Quest, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx. All other trademarks and registered trademarks are property of their respective owners.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad