Chatta subito con l'assistenza
Chat con il supporto

Migrator for Notes 20.14.2 - Installation and Configuration Guide

Section 1. Introduction Section 2. Installing Binary Tree Migrator for Notes Section 3. Setting Up the Migrator for Notes Domino Database Section 4. Configuring Settings in Migrator for Notes About us Technical support resources Appendix A: Preparing for Office 365 Migrations Appendix B: Preparing for Office 365 Modern Authentication Appendix C: Creating a Migration Farm Appendix D: Securing Migrator for Notes Web Services with Windows Authentication Appendix E: Microsoft Graph Application ID Appendix F: Modern Authentication Delegation Migration Third-party Contributions

Decrypt Encrypted Items

4.13. Types of Predefined Message Templates

Migrator for Notes comes with several predefined Message Templates which are designed to perform specific migration tasks. The information contained within these predefined templates can be modified to tailor them to a client’s needs. Predefined Message Templates can be of the following types depending on the actions they perform:

  • Email Only

  • Contact Synchronization

  • Decrypt Encrypted Items

  • Archive Discovery

  • Archive Processing

Email Only

As the name implies, Email Only is designed for informational purposes only and does not include any action buttons. Email Only templates can be used to keep the end users informed on the progress of the migration project. For example, end users can be sent an email with the migration schedule for their department. This can help them plan for when their email will be migrated.

The fields within each predefined message template should be modified to make it specific to the client. An example is shown below.

For a template to be information-only, its Template Type field should contain the value Email-only and Pre-migration option should be selected. Although, if you are sending a message to end users informing them about the successful migration, then you can also use Email Only Template Type and select Post-migration.

Contact Synchronization

When a Contact Synchronization migration message is sent to an end user, the user simply clicks the button in the message. This launches the iNotes_DoSync() agent that ships with Lotus Notes, and pushes/resyncs all contacts in the Personal Name & Address Book (pNAB) to the hidden $PeopleGroupsFlat view. Now that these contacts are in the mail file, they can be migrated.

When a Decrypt Encrypted Items migration message is sent to an end user, the user simply clicks the button in the message. This initiates an agent that will decrypt any encrypted items in the mail file, so they will migrate as clear text.

Archive Processing

When an Archive Processing migration message is sent to an end user, the user clicks the button in the message and this allows the script to search for the Archive Database Templates locally on the end user machine, find it, and copy/replicate it to a specified location on the Domino server or file server or copy into end user’s existing Domino mail file.

The location to copy is specified in the Migrator for Notes Settings document. The script will only search for templates that are specified in the Migrator for Notes Settings document. Refer to the End User Migration Settings configured in the Migrator for Notes Settings document.

Archive Processing

4.13. Types of Predefined Message Templates

Migrator for Notes comes with several predefined Message Templates which are designed to perform specific migration tasks. The information contained within these predefined templates can be modified to tailor them to a client’s needs. Predefined Message Templates can be of the following types depending on the actions they perform:

  • Email Only

  • Contact Synchronization

  • Decrypt Encrypted Items

  • Archive Discovery

  • Archive Processing

Email Only

As the name implies, Email Only is designed for informational purposes only and does not include any action buttons. Email Only templates can be used to keep the end users informed on the progress of the migration project. For example, end users can be sent an email with the migration schedule for their department. This can help them plan for when their email will be migrated.

The fields within each predefined message template should be modified to make it specific to the client. An example is shown below.

For a template to be information-only, its Template Type field should contain the value Email-only and Pre-migration option should be selected. Although, if you are sending a message to end users informing them about the successful migration, then you can also use Email Only Template Type and select Post-migration.

Contact Synchronization

When a Contact Synchronization migration message is sent to an end user, the user simply clicks the button in the message. This launches the iNotes_DoSync() agent that ships with Lotus Notes, and pushes/resyncs all contacts in the Personal Name & Address Book (pNAB) to the hidden $PeopleGroupsFlat view. Now that these contacts are in the mail file, they can be migrated.

Decrypt Encrypted Items

When a Decrypt Encrypted Items migration message is sent to an end user, the user simply clicks the button in the message. This initiates an agent that will decrypt any encrypted items in the mail file, so they will migrate as clear text.

When an Archive Processing migration message is sent to an end user, the user clicks the button in the message and this allows the script to search for the Archive Database Templates locally on the end user machine, find it, and copy/replicate it to a specified location on the Domino server or file server or copy into end user’s existing Domino mail file.

The location to copy is specified in the Migrator for Notes Settings document. The script will only search for templates that are specified in the Migrator for Notes Settings document. Refer to the End User Migration Settings configured in the Migrator for Notes Settings document.

4.14. Signing a Button in a Message Template

  1. Open a Message Template

  2. Click on Edit Document

  3. Right-click on the button and select Edit Button:

  1. A code window will appear, type the word sign, and then delete the text:

  1. Click Save and Close.

The button will now be signed with the appropriate administration ID, and end users will not receive execution security (ECL) alerts when they click the button within the message template.

4.15. Importing Exchange MDb’s

4.15.    Importing Exchange MDb’s

Migrator for Notes will need to have a reference to the Exchange MDbs that are available to be migrated to.  To import these, follow the below steps.

  1. Select 5. Import Exchange MDbs in the Navigation Pane

  2. The Data Pane will display an empty view of Exchange MDbs:

  1. Click the Import Mailbox DBs from AD button to import the available Exchange MDbs

  2. Select the appropriate Mailbox Databases from the list to be used and click the Set Use Flag button.

 


This is not required for Office 365 Migrations.

 

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione