Chat now with support
Chat with Support

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

How remigrations affect folder ACLs and delegate (Send on Behalf of) rights

Remigrations are handled differently depending on what component is being used to write migrated data to Exchange. MNE utilizes a component for writing migrated data to Exchange with the MAPI over HTTP protocol. This new component replaces the MAPI library provided by Microsoft Outlook. All migrations use this new components by default unless it is explicitly disabled (through the [Exchange] UseMneMapiHttpLib parameter), or if the new component’s minimum requirements are not met.

When migrating using MNE’s MAPI/HTTP library, remigrations can be influenced using the [Exchange] RemigrateMode parameter as described below.

Permissions for individual users are added to the folder permission table in Exchange if a permission for the user on that folder does not currently exist. Permissions are never removed from or overwritten on the Exchange folder.

Users who have the Send on Behalf of permission in Notes who do not currently have the permission in Exchange are granted the access in Exchange. Users who have the Send on Behalf of permission in Exchange who do not have the permission in Notes do not have their Send on Behalf of rights revoked. Users with the rights in both are not affected.

In summary, permissions in Notes are merged with the permissions configured on the folder in Exchange, with any conflicts handled by giving preference to the permissions configured on the Exchange folder.

Permissions for individual users are added to the folder permission table in Exchange if a permission for the user on that folder does not currently exist. Permissions are never removed from the Exchange folder. However, if the user does have permissions already configured on the folder in Exchange, it is overwritten.

Users who have the Send on Behalf of permission in Notes who do not currently have the permission in Exchange are granted the access in Exchange. Users who have the Send on Behalf of permission in Exchange who are not explicitly listed in Notes do not have their Send on Behalf of rights revoked. However users that are explicitly denied Send on Behalf of permission in Notes have their rights revoked in Exchange. Users with the rights in both are not affected.

In summary, permissions in Notes are merged with the permissions configured on the folder in Exchange, with any conflicts handled by giving preference to the permissions configured on the Notes mail file.

If MNE does not migrate data using the new MNE MAPI over HTTP library, it migrates data to Exchange using the legacy Outlook MAPI library. When migrating with the Outlook MAPI library, permissions on the Exchange mailbox folder as well as the list of users who have the Send on Behalf of right are always entirely replaced. Any permissions that may have been migrated by previous migrations or added by users before the remigration takes place are overwritten.

Migrating calendar ACLs and delegation rights

Migrator for Notes to Exchange's Data Migration Wizard offers an assortment of options for mapping some Notes access levels to Exchange, for calendar and to-do items. Specifically, the No Access and the Depositor access levels are mapped as shown in the following table, for selected Read Public and Write Public Notes permissions. Mapping depends on values set for NME Parameters [Notes] MapDefaultAclToReviewer and [Notes] ElevateCalendarAuthorACLtoEditor.

The Data Migration Wizard can also migrate Notes' "send on behalf of" delegation rights. Delegation rights are useful when one user wants to let another user have access to his or her Outlook Calendar, to generate meeting invitations and accept/decline invitations from others, as is common in a boss-secretary relationship. Notes delegation rights correspond to the publicDelegates property in Active Directory. Migration of delegation rights is enabled by default, but can be disabled by setting PublicDelegates=0 in the [General] section of the Global Defaults or Task Parameters.

 

Read Public

Write Public

Migrator for Notes to Exchange Parameter Settings
(defaults are shown here in red)

Exchange
Calendar / ToDo
Access Rights

No

[ — — — — — — — — any combination — — — — — — — — ]

No Access

Yes

No

MapDefaultAclToReviewer=0
ElevateCalendarAuthorACLtoEditor=0

No Access

MapDefaultAclToReviewer=0
ElevateCalendarAuthorACLtoEditor=1

Reviewer

MapDefaultAclToReviewer=1
ElevateCalendarAuthorACLtoEditor=0
or 1

Reviewer

Yes

MapDefaultAclToReviewer=0
ElevateCalendarAuthorACLtoEditor=0

No Access

MapDefaultAclToReviewer=0 or 1
ElevateCalendarAuthorACLtoEditor=1

Editor

MapDefaultAclToReviewer=1
ElevateCalendarAuthorACLtoEditor=0

Author

Migrating DocLinks

Notes DocLinks can be migrated in any of four forms:

NOTES links (default): This option requires the Notes client to be installed and running on end users’ desktops to facilitate the rendering of the Notes document.
Notes .NDL attachment: This option requires the Notes client to be installed and running on end users’ desktops to facilitate the rendering of the Notes document.
HTML links to your Domino webserver: A DocLink migrated as an HTML link will not require the Notes client on the user’s desktop, and will instead open into a web browser if iNotes is enabled.
NOTE: This Domino webserver option is incompatible with an Offline migration, since Migrator for Notes to Exchange cannot connect to an offline Domino server to perform the DocLink translation.
HTML links to your SharePoint Server: A SharePoint server link will point to a document on a separate SharePoint server. This requires that you have Notes Migrator for SharePoint (formerly "Proposion Portal format"). If you select this SharePoint option, you must also specify:
Site Address: URL to these documents on the SharePoint server.

Your Migration Plan should specify the destination format for your migrated Notes DocLinks. The choice of destination format is controlled by a selection on the Specify How To Migrate Notes DocLinks screen, within the Data Migration Wizard. By default, DocLinks will migrate to Exchange as NOTES links.

Migrating Notes "Active Mail"

Migrator for Notes to Exchange can detect and convert Notes rich-content features whereby messages carry "live" or "active" functional content, for things such as:

Stored forms (created in Notes with Store form in document).

These features, which we collectively call "Active Mail," are normally lost or degraded when migrated to Exchange, due to differences between the mail platforms. However, Migrator for Notes to Exchange—both the Data Migration Wizard and the SSDM—can detect and process Active Mail content to preserve its functionality.

Migrator for Notes to Exchange encapsulates Active Mail functionality within an NSF file attachment. Assuming a Notes client is still installed on the migrated user's Outlook computer, and the NSF file type is associated (in Windows) with the Notes client application, the Outlook user can simply double-click the icon to open the attached NSF file into Notes, with the fully functional Active Mail content in view.

Active Mail processing is an optional feature that is disabled by default, but can be enabled by a checkbox on the Data Migration Wizard's Specify Data to Migrate screen:

[P] Migrate mail data.
[P] Migrate e-mail messages.
     [P] Migrate Active Mail [ Configure ]
[ ] Migrate calendar data.
[ ] ...

In the SSDM, the feature can be enabled only by program parameters in the notesdtapp.ini file. These settings are described in chapter 4 of the Migrator for Notes to Exchange Scenarios Guide — see the topic How to customize the SSDM.

In the wizard’s Specify Data to Migrate screen, the Configure button (next to the checkbox field, as shown above) opens a pop-up dialog box in which you can specify your preferences for the Active Mail features. (The dialog box options are described in the Migrator for Notes to Exchange Administration Guide, chapter 10, for the Specify Data to Migrate screen, and also in the wizard’s online Help file).

Part of the configuration requires that you specify a filename and location for a Notification message — a file containing a text string that Migrator for Notes to Exchange inserts at the top of the body of any migrated message containing Active Mail. Migrator for Notes to Exchange installs a default file, ActiveMailNotificationMessage.txt, to the Migrator for Notes to Exchange installation directory, but you can specify a different filename and/or folder. The Notification message text file must be UTF-8 encoded and must contain a placeholder, called $ActiveMailAttachment$, that Migrator for Notes to Exchange will replace with the Active Mail NSF attachment when the message is migrated. Since the contents of this file become part of an RTF body, characters like "\", "{", and "}" must be escaped with a leading "\" (so they become, respectively, "\\", "\{", and "\}").

Related Documents