- Migrations to Office 365 are now done using the MAPI over HTTP protocol:
• MAPI/HTTP protocol is used for migration to O365 targets.
• RPC/HTTP protocol is used for migrations to OnPremises targets.
Note: There are two known issues that might occur with MAPI/HTTP protocol, please click here for further details. If you encounter one of these issues, MNE will crash with an access violation exception.
- MNE now supports Microsoft National Clouds (i.e. German and Chinese clouds):
[MsOnlinePSConnectionUris]
Important: When migrating to a National Cloud, the minimum version of the Azure AD Module for Windows PowerShell has to be version 1.1.166 or later.
- The SSDM now supports both the .NET 4 runtime as well as the .NET 2 runtime. Previously the .NET 2 runtime was a requirement.
- MAPI profiles are now configured automatically using the Autodiscover service:
• By default, MNE version 4.15.1 automatically configures MAPI profiles using the Exchange Autodiscover service for all migration targets.
• For on-premises targets, automatic profile configuration can optionally be disabled with the new INI setting [Exchange] UseAutodiscoverCreateProfile, which is exposed in the Migration Console on the Exchange Server page with the new setting Automatically configure profile.
• For Office 365 targets, automatic profile configuration cannot be disabled.
• A number of new INI settings have been introduced in version 4.15.1 that affect how the call to the Autodiscover service is made:
- Static MAPI profiles:
Please be aware that below parameters used to specify a pre-created MAPI profile have been depreciated on this version:
RPCAdminMapiProfile=“Outlook Profile”
Above parameters have been replaced with a single parameter that implements the same functionality:
MapiAdminProfile=“Outlook Profile”
Note: The old parameters still work in the 4.15.1 release, but they will generate a warning in the log file indicating that these parameters have been deprecated, and the new parameter should be used instead. They will be removed in a future version of MNE.
IMPORTANT: If any customers are migrating to Office 365 with a static MAPI profile, they will likely have created an RPC/HTTP profile by setting the following registry key:
“MapiHttpDisabled”=dword:00000001
Since RPC/HTTP connections will no longer be accepted by Office 365 after October 31, 2017, migrations using these static profiles will begin failing, even after upgrading to MNE 4.15.1.
Customers migrating with static RPC/HTTP MAPI profiles will need to recreate these profiles as MAPI/HTTP profiles after upgrading to MNE version 4.15.1. This can be done by following this procedure:
4.- Edit the MNE Global Default Options, renaming the RPCAdminMapiProfile parameter to MapiAdminProfile. The RPCUseAdminMapiProfile parameter should be deleted.
How to configure MAPIoHTTP for Exchange OnPremises:
The following parameters need to be set:
AutodiscoverDisableMapiHttp=0
MapiUserSharedProfile=0
- Outlook 2016 is not supported yet. Our Dev team is working to support this version of Outlook soon.
- If a self-signed certificate is used in a lab environment for the Autodiscover service to work, then you will need to set the following parameter otherwise the Autodiscover service will fail:
AllowSelfSignedCerts=1
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center