• |
The Data Migration Wizard (batch migrator) usually cannot decrypt messages because decryption requires per-user access credentials that usually are unavailable to the wizard. The wizard can migrate encrypted mail as Active Mail (see Migrating Notes “Active Mail”), but the messages are encapsulated and migrated in their encrypted state. On the Exchange side the user must use a local copy of Notes to decrypt the message contents. |
NOTE: Encrypted mail in Notes is not decrypted by the SSDM before it is migrated to Exchange. Encrypted mail in Notes is kept in an encrypted state and decrypted as it is migrated. At no time is encrypted mail left in a decrypted state in Notes. Even after the mail is migrated the encrypted email left in Notes remains in an encrypted state. |
Alternatively, the Data Migration Wizard can be configured to not migrate encrypted messages as Active Mail (as described in Migrating Notes “Active Mail” above), and in that case will migrate an encrypted message unencrypted portions, and skip the encrypted portions, inserting a text notice in the message body to explain that the encrypted portions could not be migrated.
These options are set independently for server and archive data, by different combinations of the MigrateEncryptedMessages and SkipEntireEncryptedMessage parameters, in the [ServerData] and [ArchiveData] sections (respectively) of Migrator for Notes to Exchange Task Parameters and Global Defaults. For more information these parameters, see the associated entries in the Migrator for Notes to Exchange Program Parameters Reference.
The MessageStats Notes Migration Report Pack report Migration Status by User can help you determine who has encrypted data. Use the filters in this report to narrow your search to users that have been migrated by the bulk migrator and who have Encrypted Data either skipped or migrated. Those users should run the Self-Service Desktop Migrator to migrate their own encrypted data. Since the Data Migration Wizard does not migrate encrypted messages, it will substitute placeholder messages for encrypted messages in your users’ Exchange mailboxes. The Self-Service Desktop Migrator (SSDM) replaces the placeholder messages with the real messages as it decrypts and migrates them. (The SSDM can do the same thing for encrypted messages that the Data Migration Wizard has processed as Active Mail, replacing the encapsulated-encrypted messages with the real messages as it decrypts and migrates them.)
The placeholder message content is configurable. If you set up a share for your users with an SSDM configured to migrate the Mail file for your users, you can add the location to this package along with instructions for migrating encrypted messages. For more information see “How Do I Customize the Placeholder Message ... for Encrypted Messages?” in Appendix A of the Migrator for Notes to Exchange Administration Guide.
This TSV file contains following columns:
• |
• |
• |
The Domino/Notes environment can be configured to handle message attachments by saving only one copy of the attachment on the Domino server, and making the single attachment available to the sender and all recipients. This Domino Attachment and Object Service (DAOS) is transparent to end users and can save some storage space compared to the alternate method: replicating the attachment for each recipient. However, DAOS tends to slow down migration speed. If speed is critical, the replicated attachments method is preferred.
When migrating messages to Office 365, the Data Migration Wizard does not migrate message attachments if the attachment size exceeds the limit as defined in the [Filter] AttachSize settings. Instead, a placeholder attachment file is created with text that indicates the original attachment cannot be migrated due to the size limit. This action is to handle various limits set for Exchange Online, especially the message limits such as the attachment size limit (maximum file size of a single attachment) and the message size limit (including attachments). For details, see Exchange Online limits.
When defining the [Filter] AttachSize settings, it is recommended that you use the default message attachment size, which is 25,088 KB for Office 365 targets. Most inline or embedded attachments for Rich Text Format (RTF) or HTML format messages will be smaller than this limit and will be migrated as attachments in Exchange, resulting in the best user experience for migrated messages with Outlook or OWA clients.
Before you migrate mailbox data with the feature to migrate oversized attachments enabled, it is recommended that you run the following PowerShell command to provision the OneDrive stores for all the users in the user collection:
This command is available in Quest.MNE.PowerShell module that is installed on the migration server.
For more information about the Migrate oversized attachments option, see the chapter titled “Exchange Server Configuration: Migrating to Office 365” in the Migrator for Notes to Exchange Administration Guide.
Mail-in databases in Notes work like shared folders in Outlook—as a repository for items that can be accessed by multiple users. Migrator for Notes to Exchange migrates Notes mail-in databases like resources. The Directory Export Wizard recognizes mail-in databases as distinct from other (user) mailboxes, and identifies them as "mail-in database"s in Notes Migration Manager, in the Object Type column of the Objects found table.
When migrating a mail-in database, verify that the source address in the TSV file matches the name associated with the mail-in database folder to be migrated. The name can be verified in the Notes admin account under the Mail-In Database section. The mail-in database will be matched up using either of:
• |
SourceAddress: The Notes address for the resource. |
• |
TargetAddress: The SMTP address of the target account in Exchange. |
NOTE: The Data Migration Wizard will set forwarding on a mail-in database if it is told to do so, by setting the ForwardingAddress attribute in Notes’ Document Properties for the mail-in database. |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center