Chat now with support
Chat with Support

Binary Tree Migrator for Notes 20.12.1 - 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 Notes Migrator Web Services with Windows Authentication Third-party Contributions

Rooms & Resource Settings

4.7. Configuring Rooms & Resources Settings

  1. Click Rooms & Resources; this tab has two sections. Review the general description provided for both the sections.

Rooms & Resource Migration Options

The Rooms & Resource Migration Options section enables you to configure settings to determine how resources are handled during a migration:

The following table describes the values for each setting:

Settings    

Description

Rooms and Resources Target

Specify if you want the room or the resource to be migrated to a Location field, or be appended to the message body, both, or none.

Room Label

Specify the label you wish to be prefixed to the migrated room text.

Resource Label

Specify the label you wish to be prefixed to the migrated resource text.

Online Label

Specify the label you wish to be prefixed to the migrated online text.

Location Detail Indicator

Specify the text you wish to appear when room or resource text is not included in the Location field.

Room Resource Separator

Specify a string that separates the location, room, resource, or online values that are included on the Location field.

 

Configure these settings if you want to migrate Rooms and Resources. The first step of the process involves importing Rooms and Resources into the Notes Migrator database. Lotus Notes stores multiple Rooms/Resources in a single database. Notes Migrator allows you to import and create a separate .nsf for selected Room/Resource and copy its corresponding calendar into the newly created .nsf. Once all the Rooms/Resources that you want to migrate have been separately imported, you can export them to Notes Migrator migration engine and migrate them.

The following table describes the correct values for each setting.

Settings    

Description

Rooms and Resources Import View

Specify the view in the Domino directory that Notes Migrator will use for importing the different Rooms and Resources. Use the Rooms Resources view unless there is a custom view that you have created.

Target Server

Specify the Domino server that Notes Migrator will use when creating separate .nsfs for each Room/Resource. This must not be blank.

Target Path

Specify the destination path where separate .nsfs will be created for selected Rooms/Resources.

 

The path is relative if the destination is a Domino server. If the destination is a file server, full path must be specified.

Database Template

Specify the template that will be used to create the new room or resource database to migrate.

Set Subject to Chair

Set this to ‘Yes’ to enable overwriting the booking subject when importing rooms and resources. This will set the subject to the booking Chair for migration to Outlook (removing the booking subject entirely). This does not impact the existing Notes room and resource bookings. Selecting ‘No’ will retain the original booking subject for migration.

Subject Prefix

This is used if the subject for imported booking will be overwritten with the booking Chair name. The text used will be prefixed in the imported booking subject.

4.8. Configuring Replica Settings

The Replica Settings are used when using a Domino staging server. A staging server is often used when the Domino mail servers are not on the same LAN as Exchange and/or the migration environment to mitigate migration throughput degradation due to the network. Staging servers are also used if you will be using replication formulas to filter the data intended for migration.

The following table describes the values for each setting:

Settings    

Description

Staging Server(s)

The Name of each of the staging servers to be used for creating replicas separated by a new line or a comma.  For Example: Stage01/Contoso

Staging Server File Folder

The folder name in which to place the newly created replicas.

Replication Formula Option

Specify My Own Formula: Use the field below to specify your own selection formula.  Be sure to enter the ENTIRE formula, starting with SELECT (e.g. SELECT @All to replicate all Notes items).

 

Build Formula Via Selections: The number of calendar and email days and select the forms to include in the replica and a replication formula will be built for you.

Replication Formula

If you are specifying your own replication formula, enter it here.

*Note: You must be familiar with Notes formula language.

Number of Calendar Days

If you selected Build Formula Via Selections enter the number of calendar days to include in the replica. You will be prompted for a date upon replica creation and it will use this date and the number you specify to calculate the number of calendar days to include.

Number of Email Days

If you selected Build Formula Via Selections enter the number of email days to include in the replica. You will be prompted for a date upon replica creation and it will use this date and the number you specify to calculate the number of email days to include.

Forms to include in Replica

Select or enter all of the different forms to be included in the replication formula.  If the form name is not listed here, it will NOT be included in the replication formula and will not be in the replica.

Replicate Each Replica at Creation

Selecting “Yes” will replicate each newly created replica as it is created. It will also cause the agent to run very slowly depending on the replica settings. It is recommended to use this as a one-off replica creation rather than for the entire list of users/mail-in databases.

Exclude Trash from Replica Comparison

Set to Yes to exclude Trash (Soft Deletion) document counts from the replica comparison total document counts. Set to No for default processing to count all documents.

4.9. Configuring Delegation

4.9.    Configuring Delegation

  1. Click the Delegation tab.

  2. Validate Yes is selected for the Audit Delegates option. If set to No, set to Yes and save and close the document, then reopen the document to view the other configuration settings.

  1. The PowerShell application impersonation set option is a prompt to set application impersonation. Set application impersonation using the steps below and then set this option to Yes.

    1. Open the Exchange Management Shell or configure a PowerShell session to connect to either an on-premise or the appropriate Office365 server.

    2. In the shell, enter the following command to configure application impersonation:

New-ManagementRoleAssignment –Name:impersonationAssignmentName –Role:ApplicationImpersonation –User:CMTMigrationAdmin@myDomain.org

Where CMTMigrationAdmin@myDomain.org is the SMTP or login name of the migration account, or the name of security-enabled group used for migration.

  1. To run delegation migrations as a scheduled process, set Run delegation as a scheduled process to Yes (default).

  2. Click the Enable scheduled agent button and select the Domino server that will perform the migration. The agent will run in the background of the local Notes client if the Local option is selected.

Scheduled delegation migration runs in the background on a workstation or server. If running locally, Notes must be running and background agents must be enabled on the client.

The scheduled delegation migration agent runs once a day at 3:00 AM.  Note that if the agent is changed to run at a time interval that is too short, the PowerShell tasks may not have time to complete.

  1. Click the Delegate Settings tab:

  1. After auditing the user's mail files with Active Delegation enabled, you are able to send an email that displays the user's current delegation settings, so they can decide whether they are still valid for migration to Outlook. You should allow the users a period of time to review before rerunning the mail file audit to collect any updated settings.

The options below allow you to customize the message to exclude certain users and groups that delegation does not need to be reported to the users about. Typical exclusions are standard Administrative groups or administrative IDs that are by default listed in the HCL Domino Mail files within the environment.

4.10. Configuring Source Updates

The Source Updates Settings are used to configure the Fix Folders agent.

 

The following table describes the values for each setting.

Settings    

Description

Replace Blank Folder Names With

The folder name to be used when updating Blank folder names. This will update blank (Null) folders at the folder root, blank folders within the folder hierarchy and blank folders at the end of the folder hierarchy. This will numerically increment (1, 2, 3, etc.) if more than one blank folder exists. Replacements will be done for: "", " ", " \", "\ \","\\" "\ "

Append Personal System Folders With

The folder name to be appended to Outlook system folders that have been created at the folder root of the Notes personal folders. This will not update the Notes system folders. The folder names will be appended with a hyphen "-" and then the name to be used.

Check for Duplicate Folders Names

Option to check for duplicate personal folder names. If enabled, the agent will check each folder to determine if there is a duplicate and then append "-" and an incremented number to make the name unique.

Check Duplicate Folders on Remediation Only

Option to have the duplicate checks be performed on the first Fix Folders processing or only on second processing runs. This requires the option for duplicate checking to be enabled. Set to "No" to disable this and have the Fix Folders agent always check on the first pass for duplicates or set to "Yes" to have the duplicate checking skipped on the first pass and only be run on subsequent updates. This is enabled as the default configuration.

Maximum Duplicates Checks per Folder

Numeric setting for the number of duplicates to be checked on a single personal folder. If there are more duplicates of a single folder name than the number specified, the duplicate checking for that folder will be skipped. Requires duplicate checking to be enabled.

Remove Personal Folder Aliases

Option to remove hidden Alias from Notes Personal folders. This will remove all aliases in the Notes folders except for the system folders. This should only be used if an issue with an alias is found to cause a problem with migrations.

Email end users with Folder Renames

Option to send an email to the end users with a list of the folder names that were changed. The email will include the original folder names and the new folder names.

Enable Replacement of Specific Characters

If enabled, this will allow for a defined set of characters to be removed from all personal folder names and to have those replaced with a different character. This will not update system folders and should only be used if a specific character is found to cause an issue with migrations.

System Folders

The list of folder names corresponding to system folders in Notes. These folders will not be altered by the Fix Folders process unless the user has created a personal folder with the same name.

Replacement characters in

Personal Folders

This is a text list of characters to be replaced and should be a comma separated list if more than one character should be replaced. This requires the character replacement to be enabled and should not contain a backslash "\" as that will replace the Notes folder hierarchy or be Null (blank).

Character to be used for replacements

This should be a valid character that is not known to cause migration issues and should not be Null (blank). Typically, a hyphen "-" is recommended.

Remove obsolete local group members

This can be enabled to verify any local personal group membership (not system groups membership) and remove notes formatted (Canonical) membership addresses that are no longer in Domino (e.g. user accounts for leavers that were removed from Domino). The Email Repliability in Notes Migrator is used for these checks and should be populated prior to running the processing, if enabled. Note that these members cannot be automatically replaced once they are removed.

Rename local canonical group names

This can be enabled to validate local personal group names created by end users to check if these have a canonical (Domino) format (e.g. Personal Group/Local). If enabled, the processing will rename these by replacing the “/” with a “-“ to prevent Notes treating the local group name as canonical for migration.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating