What are the software and configuration requirements for Exchange Migrator? (NETIQKB2202)

goal
What are the software and configuration requirements for Exchange Migrator?

goal

What permissions does the log account need to successfully run Exchange Migrator?

goal
How do I set up the account to log in with to perform the Exchange migration?

fact
Exchange Migrator 1.x

fact
Exchange Migrator 2.x

fix

Software Requirements:

• Microsoft Windows 2000 Server or Microsoft Windows 2000 Professional with SP1 or later, Microsoft Windows XP, or Microsoft Windows 2003.
• Only EM version 2.3 supports Microsoft Windows XP and Microsoft Windows 2003 as a migration console.
• Microsoft SQL Server 7, Microsoft SQL Server 2000 or MSDE (MSDE is included with Exchange Migrator).
• SQL / MSDE must be running with SQL Authentication enabled.
• Microsoft Outlook 2000, Outlook XP, or Outlook 2003.
• Only EM version 2.3 supports Microsoft Outlook 2003 on the migration console.
• NetBIOS Protocol support.
• Microsoft Internet Explorer 5.0 or later.
• Microsoft Exchange 2000 System Manager or later and Microsoft Exchange 2000 SP 2 or later.
• If you are migrating to Microsoft Exchange 2000, Microsoft Exchange 2000 SP2 or later must be applied to the console as well.
• Microsoft Exchange 5.5 Administrator
• This MUST be installed from the Microsoft Exchange 2000/2003 CD if you are migrating to Microsoft Exchange 2000/2003.
• If you are migrating from 5.5 to 5.5 the Exchange Admin tools from the 5.5 installation will do. 

The account you are logging in with to perform the migration must have the following permissions:

When you log on to the computer to run Exchange Migrator, ensure the logon user account has the following Microsoft Windows NT, Microsoft Windows 2000, and Microsoft Exchange permissions:

• Local Administrator permissions on the source domain.
• Local Administrator permissions on the target domain.
• If the target is Microsoft Windows 2000/2003 and you are unable to grant Domain Admin permissions, you can delegate Full Control for the logon account to the target OU where you will be migrating accounts.
• Please keep in mind that if you only have permissions to AD OU A and you are migrating a mailbox that is a member of a Group in AD OU B, you may need to delegate additional permissions to OU B in order to update the DL membership.
• Local Administrator permissions on the source and target Microsoft Exchange servers.
• Local Administrator permissions on the local com.
  puter running Exchange Migrator.
• Exchange Permissions Admin permissions on the Microsoft Exchange 5.5 source and target sites, configuration container, and on any sites that contain objects referenced by migrated objects.
• Exchange Full Administrator permissions on the target Microsoft Exchange 2000/2003 organization.
• If you are unable to grant Full Administrator at the organization level, delegating Full Administrator to the target Administrative Group is acceptable.
• SQL Administrator rights.
• Default sa account or a SQL account with equivalent permissions.

WARNING:  If you have the Active Directory Connector (ADC) running you will need to disable it in order to avoid problematic interactions between your migration and the ADC tool. Depending on how the connection agreements are defined, ADC can end up deleting the source mailbox.

The user account you log on with to run Exchange Migrator must have access to the Global Address List (GAL) on the source and target Microsoft Exchange servers. In order to have access to the GAL you need to create a mailbox on both the source and target server for which the logged in account has permission.

To create these mailboxes:

1. Create a mailbox on the target Microsoft Exchange server called $targetservername (just an example).
2. Create a mailbox on the source server called $sourceservername.
• Select the target $targetservername account as the Primary Microsoft Windows NT account for this mailbox.
3. Create a MAPI profile for both the mailboxes on the machine running Exchange Migrator.

To create a MAPI profile:

1. Click Start | Settings | Control Panel.
2. Double-click the Mail icon.
3. Under theServices tab click Show Profiles.
4. Click Add and follow the wizard to create a profile for both the source server mailbox as well as the target server mailbox.
5. When you have set up the MAPI profile click Properties for the newly created MAPI profile.
6. Click Properties again under the $targetservername Properties screen.
7. Under the General tab click Check Name and make sure that the server and mailbox names get resolved (underlined).
8. Repeat this process to create the MAPI profile for the source mailbox on the console machine. Also make sure that the logged in account has permission on both mailboxes (source and target).

To ensure your logon user account has the required access:

1. Create a mailbox on both the source and target Microsoft Exchange servers for the logon user account.
   .
2. Create a mail profile for these mailboxes on the computer where you install Exchange Migrator (source, target, or console). Use the Mail utility in Control Panel. Click Show Profiles and then click Add. Follow the instructions for creating the profiles.
3. Assign access permissions to the mailboxes for the logon account using Microsoft Exchange Administrator.
4. Grant the source mailbox Owner permissions for all public folders to be migrated on the source Microsoft Exchange server. Note: This is not required if you have installed EM 2.2 Service Pack 1 or later.
5. Grant Top Level Folder Creation permission to the target mailbox on the target Microsoft Exchange server.

.


note

Regarding Alternate Credentials

Generally speaking, there have been several issues that appear to be linked to the use of alternate credentials. When encountering issues even though the correct permissions appear to be applied, we recommend using the logon account to perform your migration to see if it resolves the issue.  NetIQ does not recommend the use of alternate credentials and is looking into possibly removing this option from Exchange Migrator in a future release.  Although specific errors have not been confirmed, the issues are intermittent and are believed to be a result of credentials not being passed correctly between multiple threads.

note

Related Articles

• NETIQKB2181 - What are the Exchange migration scenarios supported by NetIQ?
  

• NETIQKB1292 - What permissions are needed to migrate Public Folders successfully and how do I set them up?

• NETIQKB15740 - What are the Exchange DLLs that Exchange Migrator requires?
  

Formerly known as NETIQKB2202