Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Migrator for Notes to Exchange 4.16.1 - 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

SSDM issues

Outlook Personal Archive folder must be open to receive migrated items via SSDM when using Outlook MAPI

By default, migration via SSDM is performed with the newer MNE MAPI/HTTP library (provided .Net 4.5 or later is installed). If an end user wants to use the SSDM to migrate items to an Exchange Personal Archive using Outlook MAPI, the user must first open the Personal Archive folder in Outlook before running the SSDM.

SSDM Migration to Office 365 fails due to invalid ADAL credentials if using Outlook MAPI

By default, migration via SSDM is performed with the newer MNE MAPI/HTTP library (provided .Net 4.5 or later is installed). If an end user is migrating using Outlook MAPI, the SSDM uses a MAPI OpenMsgStore call to open the MAPI profile's default mailbox before migration. If Outlook has been enabled using the Active Directory Authentication Library (ADAL) and the ADAL credentials are stored in the cache, MAPI authentication is performed using the ADAL cached credentials. If the cached ADAL credentials are not valid, the MAPI login fails and there is no prompt for credential entry.

When this scenario occurs, the SSDM migration summary window indicates “Migrated 0 objects with two errors and 0 warning(s) from your mail file”. The Error Report Log contains the following errors:

Error: [8874-94-20-8004011D]Unable to open the MAPI profile's default mailbox.
IMAPISession::OpenMsgStore():
MAPI error 8004011D
Error: Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance.
Resolution: Remove the ADAL credentials from the Credential Manager
1
Click Start > Control Panel | User Accounts | Credential Manager.
2
Select Windows Credentials.
3
Locate the set of credentials that has MicrosoftOfficeXX_Data:ADAL in the name and expand the corresponding folder.
4
Click Remove from Vault.
5
Repeat step 3 and 4 for any additional sets of credentials that have the word MicrosoftOfficeXX_Data:ADAL in the name.
6
Restart Outlook.
7
You are prompted for the sign in credentials for your email account.

Admin Account Pooling issues

When running Migrator for Notes to Exchange in a federated Office 365 environment, the Admin Account Pooling Utility cannot use a federated domain.

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 if migrating using Outlook MAPI: 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. This issue does not occur when using the newer MNE MAPI/HTTP library to migrate data.
•
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 administrator leaves the Merge into folder... check box clear (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... check box clear in the Data Migration Wizard.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation