Migration Manager for Exchange 8.10 Migrating to Exchange...

Migration Manager for Exchange 8.10Migrating to Exchange 2013

How to Diagnose & Troubleshoot

2Technical Support Training

• Product Summary

• Calendar Synchronization

• Free Busy Sync

• Public Folder Sync

• Mailbox Sync

• Remote User Collections (RUC)

• Native Mailbox Move

• Deploying CPUU (Client Profile Updating Utility)

• Switching Mailboxes to the Target Environment

• Prerequisites for Contacting Support

Slide Index


Legacy Agent Migration workflow – Product Summary

Workflows can vary from project to project, depending on requirements. Here is a basic example.

1. Calendar Synchronization

2. Free/busy Synchronization (if prior to 2010 Exchange is involved

3. Public Folder Synchronization

4. Mailbox Synchronization

5. Deploy CPUU

6. Switch mailboxes to the target environment


Migration Manager for EX Architecture – Legacy Agents

QMM Console

Agent Host(MTA)

SQL

Agent Host(MSA,NTA)

Agent Host (CSA)

Source Exchange Servers Target Exchange Servers

.PRV files

Config.ini/Config.MDB


1. Calendar Synchronization• More susceptible to latency issues vs. mail sync

– Use ping to check latency between source and target EX servers

• More susceptible to firewall issues vs. mail sync

• MAPI connections opened to source and target mailboxes simultaneously

– Test with MFCMAPI from CSA server to both mailboxes if you see logon failures. This will reveal any networking or permissions issues.

• 1-way source->target sync switches to target->source after mailbox switch

• Required connectivity:

– LDAP to QMM ADAM server

– LDAP to source and target DCs

– MAPI to source and target EX servers

• Log files accessible via the GUI, or at this location:

– \\agenthost\qmmex$agenthost$\Calendar Synchronization Agent\agent#\emwcsa%.log


Common Issues (Calendar Synchronization)

• Errors "SYNC_E_IGNORE" logged by the Calendar Synchronization Agent.https://support.software.dell.com/exchange-migration-wizard/kb/78244

• Duplicate calendar folder (e.g. Calendar1) being createdhttps://support.software.dell.com/migration-manager-for-exchange/kb/76909

• How to use MFCMAPI to troubleshoot MAPI_E_LOGON_FAILED and various other errorshttps://support.software.dell.com/exchange-migration-wizard/kb/23502

https://support.software.dell.com/exchange-migration-wizard/kb/78244

https://support.software.dell.com/migration-manager-for-exchange/kb/76909



2. Free/Busy Sync

• Synchronizes only messages in “Schedule+ Free busy” system public folder

• Not compatible with Exchange 2010 or newer

• MAPI logons to source and target administrative mailboxes simultaneously

– Test with MFCMAPI from CSA server to both mailboxes if you see logon failures.



– LDAP to source and target DCs


• Log files accessible via the GUI, or at:

– \\agenthost\qmmex$agenthost$\Freebusy Synchronization Agent\agent#\emwfbsa%.log


Common Issues (Free/busy Synchronization)

• Synchronizing Free/Busy when migrating to Exchange 2010https://support.software.dell.com/migration-manager-for-ad/kb/72612

• Some important considerations when synchronizing F/B (Free/Busy) information into Exchange 2007/2010 Outlook 2007/2010(+sp1) target organizationhttps://support.software.dell.com/migration-manager-for-ad/kb/72612

• How can MFCMAPI be used to look up Free/Busy messages?https://support.software.dell.com/exchange-migration-wizard/kb/42612

https://support.software.dell.com/migration-manager-for-ad/kb/72612

https://support.software.dell.com/migration-manager-for-ad/kb/72612



3. Public Folder Synchronization• Uses PUB files to synchronize public folder data

• Log files accessible via the GUI, or at this location: This is the one agent you cannot have multiples of to spread the synchronization load. To change where these agents are installed, you must change the default agent host associated with the Source & Target Exchange servers.

– \\agenthost\qmmex$agenthost$\PF Source Agent\emwpfsa.log

– \\agenthost\qmmex$agenthost$\PF Target Agent\emwpfta.log


– PF Source Agent (PFSA) host:


– LDAP to source DCs


– Filesystem access to target agent host (via QMMEX share)

– PF Target Agent (PFTA) host:


– LDAP to target DCs

– MAPI to target EX servers

• Important: Deleting target public folders is strongly not recommended. This will create tombstones and prevent the folders from resynchronizing.


Common Issues (Public Folder Synchronization)

• How do you delete or cleanup Public Folder tombstones in Exchange 2007.https://support.software.dell.com/exchange-migration-wizard/kb/34024

• How to use MFCMAPI to troubleshoot MAPI_E_LOGON_FAILEDhttps://support.software.dell.com/exchange-migration-wizard/kb/23502




4. Mailbox Synchronization• Uses PRV files to synchronize mail data – source->target only.

Multiple of each agent (excluding the Mail Transmission Agent) can be assigned to a Mail Synchronization job by creating multiple collections and assigning different agents to each.

Log files accessible via the GUI, or at this location:

– \\agenthost\qmmex$agenthost$\Mail Source Agent\agent#\emwmsa%.log

– \\source_agenthost\qmmex$source_agenthost$\Transmission Agent\emwnta.log

– \\Target_agenthost\qmmex$Target_agenthost$\Mail Target Agent\agent#\emwmta%.log


– Mail Source Agent (MSA) host:


– LDAP to source DCs


– Filesystem access to target agent host (via QMMEX share)

– Mail Target Agent (MTA) host:


– LDAP to target DCs

– MAPI to target EX servers


Mailbox Synchronization - Remote User Collections (RUC)• One widely-used Microsoft Outlook feature is offline access to a user’s mailbox

folders. The offline folders (OST) file is stored on a user’s computer and keeps a local replica of Quest Migration Manager for Exchange 8.10 - User Guide

• the corresponding folders in the user’s Exchange mailbox. In this document, users who typically work with the offline folder (OST) files and occasionally connect to their Exchange mailboxes are referred to as remote users.

• Because each OST file is associated with only one Exchange mailbox and cannot be used with any other mailbox, a user cannot continue using the same OST file with the new mailbox after migration.

• Therefore, Migration Manager for Exchange offers the Remote Users Collection feature, which allows for transparent migration for the remote and laptop users. The mailboxes of remote users should be grouped in Remote Users Collections and processed separately from other mailbox collections after the directory synchronization has been completed and before the mailbox synchronization is started. You can create one or several Remote Users Collections depending on the number of remote users.


Common Issues (Mailbox Synchronization)

• How to use MFCMAPI to troubleshoot MAPI_E_LOGON_FAILEDhttps://support.software.dell.com/exchange-migration-wizard/kb/23502

• Exchange 2010 throttling policieshttps://support.software.dell.com/migration-manager-for-exchange/kb/67327

• MSA Error - "CSession::Logon Error -2147221219 You do not have permission to log on. - MAPI_E_FAILONEPROVIDERhttps://support.software.dell.com/migration-manager-for-exchange/kb/61782

• Error -2147023495 SetMailboxInfo failed Invalid menu handlehttps://support.software.dell.com/migration-manager-for-exchange/kb/96774

• Switching a mailbox fails with: CSession::Logon| Number: -2147467259 -Unspecified error https://support.software.dell.com/migration-manager-for-exchange/kb/83125







“Native Mailbox Move”

• Native Mailbox Move

• For migrations that involve Exchange 2010 organizations, the native move job is an alternative to the mailbox synchronization job. Native move jobs rely on PowerShell-based tools native to Exchange 2010 and act as a front-end to those tools.

• When using a native move job, you have the option to automatically switch the users' mailboxes after the move. If you use this option, the switch will be performed by Exchange 2010, and you will not need to additionally use Client Profile Updating Utility to change users' Outlook profiles.

• For details about the technology used by native move jobs, see the Microsoft documentation for the New-MoveRequest PowerShell cmdlet.

• Native move jobs are handled by the Migration Agent for Exchange. (MAGE agent)


5. Deploying CPUU (Client Profile Updating Utility)

• CPUU needs to be deployed to run when users log in. If their mailbox has been switched, CPUU detects this and updates the Outlook profile.

• Must run as an account with full access to both source and target mailboxes

• Checks the source mailbox for hidden switch message placed by switch process. Aborts if message is not found.

• Log file is written to the same location as CPUU.exe by default or to a network location specified in the command line

• Search log for “Rolling Back” to find the point of failure


Common Issues (Deploying CPUU)

• CPUU fails with error "Cannot retrieve data from the profile" followed by MAPI_E_NOT_FOUNDhttps://support.software.dell.com/exchange-migration-wizard/kb/48794

• CPUU fails with "[Error] Cannot open default message store. MAPI error. Error code: 0x80040113“https://support.software.dell.com/exchange-migration-wizard/kb/22161

• CPUU does not update a profile showing "Switch message was not found" message in the log filehttps://support.software.dell.com/migration-manager-for-exchange/kb/28383





6. Switching mailboxes to the target environment

• Switching redirects incoming mail to the target environment and places the hidden switch message for CPUU

• Automatic switch (via collection properties)

– Performed by the Mail Source Agent

– Check emwmsa.log for “isreadytoswitch” to troubleshoot failed switches

• Manual switch (via console)

– Check the c:\program files%\quest software\migration manager\Exchange Data\emwmigration.log


– MAPI access to source and target mailboxes

– LDAP access to the source and target domain controllers


Common Issues (Switching Mailboxes)

• Manual Mailbox Switch fails - Error in log file: "MAPI_E_FAILONEPROVIDER“https://support.software.dell.com/migration-manager-for-exchange/kb/117270

• MSA behind firewall fails to switch mailbox https://support.software.dell.com/migration-manager-for-exchange/kb/117270




Prerequisites for Contacting Support


Prerequisites for Contacting Support

• Check if the error or issue you’re experiencing is documented at www.support.software.dell.com

• Collect all relevant logs and configuration files:

• Migration Manager version

• Environment details such as Windows version (console, Domain controllers), Exchange versions

• Deployment documentation, if available

http://www.support.software.dell.com/


DELL CONFIDENTIAL AND PROPRIETARY

This document (the “Document”) contains confidential information of Dell and embodies trade secret and proprietary intellectual property of Dell. It is legally protected and shall not be copied, modified, reverse engineered, published, disclosed, disseminated outside of Dell or otherwise used, in whole or in part, without Dell’s written consent, provided, however, that you have the right to use the Document solely for your internal use and solely as necessary for you to enjoy the benefit of Services under the applicable SOW (or other agreement) you have entered into with Dell. Copyright 2012 by Dell Inc. The copyright notice does not imply publication of this document or its contents.

DELL, the E (Stylized in a sphere) logo, Dell Compellent, OpenManage, EqualLogic, PowerEdge, PowerVault and other Dell trademarks are the trademarks or registered trademarks of Dell Inc. in the U.S. and certain other countries.

Migration Manager for Exchange 8.10 Migrating to Exchange...

Documents

Transcript of Migration Manager for Exchange 8.10 Migrating to Exchange...