- Issue 1:
• Previous versions of MNE handle temporary MAPI profiles in one of two ways:
1.- A MAPI profile is created by MigApp.exe. This profile is used by each MigAppWorker.exe process. Once all users have been migrated, MigApp.exe deletes the profile.
2.- Each MigAppWorker.exe process creates its own MAPI profile. The profile is deleted before the MigAppWorker.exe process exits.
• All migrations in previous versions of MNE use method 1 above EXCEPT when migrating to Office 365 using an Admin Account Pool. Admin Account Pool migrations use method 2.
• Method 1 encounters that when a process logs onto a MAPI profile that has been used at least once before, MAPI will crash. The first process to log onto the profile has no issues, but after the first use the profile can’t be used by any other processes.
• Method 2 listed above does not encounter this issue because each profile is used by exactly one process and then it is discarded.
• To avoid this issue, a new parameter called [Exchange] MapiUseSharedProfile was added. This parameter allows you to control which of the two methods listed above are used when running a migration.
• When migrating to Office 365, this new parameter defaults to “0”. This ensures that by default, method 2 is always used for Office 365 migrations, thereby avoiding the MAPI/HTTP crash.
• When migrating to on-premises targets, this parameter defaults to “1”, keeping the same behavior as in previous versions of MNE.
- Issue 2:
• When you click on the Apply button on the Migration Console’s Exchange Server page, a temporary MAPI profile is created to validate the configuration values entered.
• If you click on the Apply button a second time, MAPI crashes.
• To mitigate this issue, the workflow of the Exchange Server page has been modified. In previous versions you were not allowed to manage the Admin Account Pool until after the Exchange account settings were committed by clicking on the Apply button. Once you were finished managing the pool settings, you then had to click click Apply a second time to save the pool changes.
• In MNE 4.15.1 you don’t need to click Apply before you manage the pool settings. You can now complete all of the Exchange Server settings, including managing the pool, and then click the Apply button a single time when you’re done.
• This has been documented as a known issue in the Release Notes. The workaround is to exit the console and open it again if you need to make any additional changes.
• Another workaround for this issue is to configure MNE with a static MAPI profile created through the Control Panel.
Note: Please be aware that this crash only happens when using the MAPI/HTTP protocol. On-premises migrations (which still uses RPC/HTTP by default) won’t have this issue.
