The last screen of the wizard attempts to create an Outlook profile pointing to a mailbox on each source and target database based on the accounts you selected for migration. The test is no more complicated than creating a new profile manually and seeing if you can open a mailbox.
So, a failure in the wizard can just as easily be validated by creating an outlook profile. I suggest doing that – creating a new profile – and seeing about what Outlook complains.
Historically, such issues fall into 1 of the 3 following issues:
- Permissions
a. The account you logged on with, on the host running the Priasoft tools, does not have sufficient permission
b. Not enough time has passed since setting permissions. System privileges on databases are re-cached every 4 hours; if you migrate too soon after setting permissions, exchange may not yet recognize them.
c. MAPI uses RPC and as such depends upon windows security models. Specifically, your logged on account. However, mapi will use cached credentials first if any exist. Check your Credential Manager (search in control panel) and see if you have an domain credentials for any of your exchange servers and if those credentials are correct.
d. Many deployments require the use of cached credentials to access the source mailbox databases. In this case you need to make sure that you have cached credentials for each source exchange server and source DC and all entries should be using the same account and one specifically created for accessing mailbox databases – this would NOT be the same account you logged on with nor would it be a Domain Admin or other elevated account used for Active Directory. This should have been explained in the setup guide. - DNS and NetBIOS
a. The migration host MUST be able to resolve server names to IP addresses.
b. Windows always tries NetBIOS resolution first, for single-label names (e.g. ex01 would use NetBIOS while ex01.corp.com would use DNS)
c. MAPI, being an RPC based protocol often will work with NetBIOS server names and such is out of your control.
d. When a NetBIOS broadcast for a name fails, windows will then enumerate all the configured DNS suffixes for the host, appending the suffix to the name and sending the now fully qualified name to a DNS server. However, it is very often found that the host does not have suffixes for the source environment. Make sure that the host has suffixes for both environments.
e. Hosts and LMHosts files: do not use this without direct instruction from Priasoft support.
f. Target exchange servers may need to perform name resolution to source environment servers. Suffixes should be applied to target exchange servers as well.
g. DNS servers in both the source and target environments should have an ability to handle lookups for the other side. Conditional forwarders are the best option. The source DNS servers should have CFs pointing ‘target.domain.com’ at a target DNS server, and vice-versa. - Outlook version
a. When migrating to Exchange 2013 or Office365, you MUST have Outlook 2007 SP3 and the November 2012 Rollup in order to properly connect.
b. You should also ensure that all windows updates have been applied. We have seen many cases where issues are resolved simply due to patches and updates.
