We are currently planing to migrate from an hosted exchange provider to Exchange online (O365). We are planing to do a cutover migration. When creating an migration endpoint the connection fails when trying to connect to the MAPI Server. It seems that in contrast to what https://support.office.com/en-us/article/Cutover-migration-to-Office-365-9496e93c-1e59-41a8-9bb3-6e8df0cd81b4#ID0EAABAAA=Run_a_cutover_migration states the migration client requires MAPI access. The Current Provider does not allow MAPI access. Currently only RPC over HTTP is supported. We might have the option to enable MAPI over HTTP and potentially MRS Proxy. I can not find the information if the migration process support MAPI over HTTP instead of MAPI.
Can you tell me if 1. The Microsoft Migration support MAPI/HTTP 2. The Microsoft Migration support MRS Proxy
Thanks in advance Clemens
UPDATE 22.09.2017: The following Error is shown when trying to connect to the server. I also used the "Remote connectivity analyzer" to test the connection and get the autodiscover XML. I got the exchange and RPC/HTTP server from that xml.
MapiExceptionCallFailed: Unable to make connection to the server. (hr=0x80004005, ec=1249) Diagnostic context: Lid: 49064 dwParam: 0x3 Lid: 59431 EMSMDB.EcDoConnectEx called [length=147] Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x4E1][length=56][latency=31] Lid: 59505 StoreEc: 0x4E1 Lid: 50544 ClientVersion: 188.8.131.52 Lid: 51056 ServerVersion: 14.3.351.4000 Lid: 52080 StoreEc: 0x4E1 Lid: 51152 Lid: 52465 StoreEc: 0x4E1 Lid: 60065 Lid: 33777 StoreEc: 0x4E1 Lid: 59805 Lid: 52487 StoreEc: 0x4E1 Lid: 19778 Lid: 27970 StoreEc: 0x4E1 Lid: 17730 Lid: 25922 StoreEc: 0x4E1
Just some other possible options here, if you do not find a way to do that via MAPI over HTTP.
Option 1 (via IMAP):
However this will not take over the agenda or contacts. That would be an per user approach using the Outlook client (Import & Export).
Option 2 (via two mailboxes and Outlook):
Option 3 (via local PST file):
Note here: This approach often destory the "last changed" timestamp, so an archiving isn´t working as expected for these elements as there is now a new timestamp. This often is confusing a backup software. We saw that this will also destoy re-occouring meetings and a re-schedule is no longer working as expected.
User contributions licensed under CC BY-SA 3.0