Introduction
This guide will help you upgrade Migration Manager from version 8.12 or 8.13 to the latest version.
|
|
Caution: Use the native management tools to back up the AD LDS and Microsoft SQL Server databases used by Migration Manager before upgrade. |
The upgrade procedure contains of the following steps:
- Stop Agents
- Upgrade Migration Manager on the console machine.
- Upgrade the Directory Agents.
- Upgrade Resource Updating Manager.
To upgrade Migration Manager for Exchange, complete the following additional steps:
Step 1. Stop Agents
Before you start the Migration Manager for Exchange upgrade operation, perform the following:
- First of all, stop all Migration Agents for Exchange (MAgE) agents on all agent hosts.
- Then 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 treeview, go to Component Services | Computers | My Computer | COM+ Applications, then right-click the Migration Agent for Exchange MAPI Assistant node and select Shut down.
Step 2. Upgrade Migration Manager on the Console Machine
|
|
Note: If you have a standalone Active Directory Processing Wizard and/or standalone SharePoint Processing Wizard installed on the computer with the Migration Manager console, uninstall these wizards before starting the upgrade. |
Before you begin
- Make sure that all computers where Migration Manager components are installed meet the system requirements according to the System Requirements and Access Rights document.
- Ensure that the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 version 6.5.8353.0 or later is installed on the computer with Migration Manager console.
|
|
Caution: Migration Manager requires this software to be installed on the computer where the Migration Manager console will be installed. Since the MAPI CDO setup package is not available for distribution, you should download it from the Microsoft Web site. At the moment of the last document update, the link is http://www.microsoft.com/en-us/download/details.aspx?id=42040. |
- Permissions for all accounts that are used with Migration Manager components must be granted according to the System Requirements and Access Rights document.
-
Since version 8.13 by default Exchange Web Services (EWS) protocol is used instead of MAPI for migrations from Exchange 2010 and 2013 using MAgE. That requires changes in account permissions and different throttling policies. See the corresponding Exchange preparation documents for more information. To use MAPI instead of EWS for avoiding changes in permissions and throttling policies, set the UseEwsProtocolForSourceIfAvailable parameter to false as described in Configuring Migration Using PowerShell.
Upgrade Migration Manager console
To upgrade the Migration Manager console, take the following steps:
- Close the Migration Manager console if it is running.
- Then open the Services MMC snap-in and stop all necessary services provided by Dell.
- After that run autorun.exe from the Migration Manager 8.14 CD.
- On the Install tab, click Upgrade Migration Manager.
- Select the components you need to install.
- Follow the instructions to complete the installation.
- If you stopped any services on step 2, start them again (except MAgE services). Please, pay attention, due to rebranding these services are now provided by Quest.
- Run the Migration Manager console. The SQL database will be updated automatically during the start of the Migration Manager console.
|
|
Caution: If in your environment, the Migration Manager project is stored in an AD LDS or ADAM configuration set with several replicas and several Migration Manager Console machines are configured to be connected to different replicas, we recommend that you first upgrade the Migration Manager Console machine connected to the replica with the Schema Master role. By default it is the first installed replica. For more information, please refer to the AD LDS or ADAM documentation. |
Step 3. Upgrade the Directory Agents
After you upgrade the console, you need to upgrade the Directory Synchronization and Directory Migration Agents as well. The agent upgrade process consists of two major steps: