Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.15.2 - Pre-Migration Planning Guide

About the Migrator for Notes to Exchange documentation Introduction Critical considerations Other strategic planning issues Appendix A: Known limitations of the migration process

Post-migration issues

Outlook archiving of migrated messages is delayed. Outlook archiving is not applied to migrated messages within the age range set for auto-archiving, because Outlook determines message age by Last Modified time, which it updates to the migration date/time upon migration. Since all migrated messages become zero days old as soon as they are migrated, and Outlook won't let the Data Migration Wizard reset that property to its true pre-migration date/time, the Outlook archiving feature skips the messages until they have "re-aged" to the archive age (typically 30 days) following migration, at which time all of the migrated messages will be archived.
Changes to some migrated appointments may produce duplicates. Some instances of meetings scheduled in Outlook with a Notes attendee and updated prior to the Notes attendee's migration to Exchange, may appear twice in the attendee's Outlook calendar if further updates occur after the attendee is migrated to Exchange.
Outlook cannot add a logon-disabled account to an ACL list. This is a limitation of Microsoft Exchange, not of Migrator for Notes to Exchange.

Miscellaneous issues

MAPI bug prevents connection to on-premises Exchange: A known MAPI bug in Windows Vista, and in Server 2008 R2 and later, may prevent Migrator for Notes to Exchange from connecting to an on-premises Exchange server if the Region and Language Format is set to Japanese. The same bug also prevents a user from creating new Outlook profiles using Exchange auto-discovery. The bug can be avoided if the sorting method for Japanese format is changed from default XJIS to Radical\Stroke. This change lets Migrator for Notes to Exchange create new profiles and subsequently migrate mail, but should have no other effect on the migration process.
Variations in message body formatting in OWA: Since messages are rendered by the Outlook client, and the Outlook Web Access (OWA) client omits images embedded in an RTF message body, body formatting may vary in messages viewed in OWA vs. the regular desktop Outlook client. This is a function of OWA, not of Migrator for Notes to Exchange.
Encrypted mail migrated by SSDM is not re-encrypted. Encrypted mail is migrated via the Self-Service Desktop Migrator, but cannot be re-encrypted in Exchange/Outlook.
Groups cannot be added to security groups in mixed mode. When provisioning distribution groups to a server running mixed mode and creating security groups instead of distribution lists, an attempt to add a group to the security group will fail and generate an error to the program log.
PAB Replicator template option "SyncAndCopyToMailFile" merges multiple Notes address books into single Outlook Contacts folder. The address books are merged even if the admin leaves the Merge into folder... checkbox unmarked (Data Migration Wizard, Specify Data for Migration screen). To migrate multiple address books to separate folders in Outlook, use the CopyToServer template option in the PAB Replicator Wizard, and leave the Merge into folder... checkbox unmarked in the Data Migration Wizard.
Blank attachment icons in messages viewed in OWA: Migrated Notes messages with attachments display the attachments in OWA, but blank attachment icons also appear at the end of the message.

Office 365 issues

Migrator for Notes to Exchange cannot support a secure proxy that requires explicit authentication, although Migrator for Notes to Exchange works fine with secure proxies that rely on Windows domain trust. This limitation is caused by multiple Microsoft APIs and components that cannot be configured to supply authentication credentials to a proxy. Microsoft does not recommend connecting to Office 365 via proxies that use destination-based filtering (see this Microsoft link). Migrator for Notes to Exchange should work fine with a non-domain-trust authentication proxy with exceptions added to satisfy the Microsoft requirements, since all Microsoft components will bypass proxy without authentication. But Migrator for Notes to Exchange must conform to the Microsoft requirements.
If migrating to Office 365 with directory coexistence: An object that is synched to Office 365 with proxyAddresses will lose the proxyAddresses upon the next sync if the UPN is changed to match the Office 365 login—which disables mail routing from Domino to Exchange.
Provisioning nested groups into Office 365: Microsoft's AD sync tool must be run twice to completely provision nested Notes groups (i.e., Group A contains Group B) in Office 365.
Group delegates do not migrate to Office 365: When migrating Notes mail-in databases to Office 365 with an on-premises Active Directory, group delegates in Notes do not appear in the O365 delegations list. This appears to be a limitation of Office 365.

 

Related Documents