Chat now with support
Chat with Support

Please note, you may experience access issues between 6am - 7am Eastern time on Saturday, May 28 2022 due to planned maintenance

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

Lotus Notes Migration ID

4.3. Configuring Mail File Processing

Click the Mail File Processing tab to specify the appropriate values for the Domino environment.


Mail File Processing works with the assumption that Notes Integration | CMT is configured between Domino and Exchange. The Email Forwarding Only option can be used if Notes Integration | CMT is not deployed. This allows for standard Domino email forwarding functions.

You must configure this section prior to using the Maintain Transitional Calendar Workflow (MTCW) agent. This agent gathers recurrence pattern information for meetings and copies that information into the BTCache.nsf, which allows calendar workflow to behave as expected regardless of migration status of the chairperson or attendees.

Refer to the table given below for a brief description of all the settings in the Mail File Processing tab:

Email Routing

Settings    

Description

Present Domino Domain

Specify the existing Domino domain.

Exchange Foreign Domain

Appears if Notes Integration is in use

This is the name of the Lotus Notes foreign domain that was configured to route mail from the Domino infrastructure to Exchange.

Write Person Doc Changes to

Select which server you want to use when writing changes after a user is created in Exchange. Whether you choose the Domino Admin Server or the Home Mail Server depends on the existing infrastructure and replication frequency.

Enable alternate server NAB

If the filename of the Name and Address Book (NAB) listed on the Required Settings tab is different, enter the alternate filename in this field. If enabled, this value will be used for all mail routing change operations. This is common when an organization is using a global directory from multiple domains and address books. In these cases, the global directory’s filename may not be names.nsf.

Enabled Calendar Domain?

Appears if Notes Integration is in use

Select Yes to update the CalendarDomain field in the selected Person document. A selection of No will result in no change occurring to that field. 

Retain Mail File & Server Info?

Appears if Notes Integration is in use

When running Routing Update functions, the Mail File Name and Mail Server information is removed from the Person Documents for the selected users. If you wish to retain this information, select Yes. If you select No, if Mail Routing is reverted back to Notes then the data will be restored from the values recorded in the Notes Migrator Person document. Otherwise, the Mail File and Mail Server will not be updated assuming the values already exist in the NAB Person document.

Apply ShortName?

Default is ‘No.’ When running Routing Update functions, the ShortName maybe used for mail forwarding in Coexistence. The Person, Mail-In and Resource Documents can be checked for this field and updated if this is not set. If you wish to have the ShortName check please select Yes. If you select No this will be checked assuming the values already exist in the NAB documents or are not used for Coexistence. Not: this will not alter the ShortName in any cases if the field is present and has an existing value.

ShortName Data Source?

When ‘Apply ShortName?’ is set to ‘Yes,’ this field will appear. When checking the ShortName and applying a value, if that is not set on the Domino Directory Documents, choose the method to create a ShortName. This can be automatically generated as a unique value using (@Unique), taken from the Internet Address Local Part (left of the @ sign) or set to the Full Name.

Disable Directory Synchronization?

When running Routing Update functions, the Directory Synchronization is disabled. If you wish this to remain enabled, select No. By selecting Yes, the person document will be disabled from directory synchronization operations.

 

 

Email Forwarding Only

Settings    

Description

Modify Forwarding Address?

If using mail forwarding for mail routing to Office 365 or Exchange during the coexistence period without Integration, then select this option. This option will only update the Mail Forwarding Address in the selected Person document(s) rather than the Domain and Mail Type as the above operation performs. If No is selected then no changes will occur and the normal operations will be executed.

Enter New Address Parameters

Appears if Modify Forwarding Address is set to Yes

If using mail forwarding for mail routing to Office 365 or Exchange during the coexistence period the address will need to be built correctly. Enter the new domain and select the correct address name part. If selecting custom field then the forwarding address will be built based on the value of this custom field in the Domino Directory. If the field value contains a valid RFC 821 Internet address then that address will be used otherwise it will use whatever value plus the configured domain.

 

 

Domino Directory Replication Options

Settings    

Description

Enable Replication

Appears if Office 365 migration is enabled

If you wish replication to be executed after the changes are made to the Domino Directory select Yes. By selecting No, updates will occur on the selected Domino Directory but replication of these changes will happen during normal scheduled replication between servers.

Replication Type

Appears if Office 365 migration is enabled

If you select to enable replication, select One Way Sync or Two Way Sync.

 

 

 

 

Enable Replication default is ‘No.’ When set to ‘Yes,’ options will expand:

Migration History Settings

Settings    

Description

Migration History Method

Select the method for determining migration history. The Classic – NoteID option uses Notes Migrator migration history table, stored on the XML server. The Discover History from Migrated Data option scans the migrated data (mailbox, archives, etc.) to find messages previously migrated from Notes. The default selection is ‘Discover History from Migrated Data’.

Additional sources for Migration History

Appears if Discover History from Migrated Data is clicked; choose the checkboxes of the data courses to be scanned when the migration history is discovered from previously migrated data:

 

Mailbox – user’s main mailbox

Archive – archive message store

PSTs – filenames or path to PST files

 

The target will always be searched for migration history.

 

Note: When migrating archives ensure that the Archive option is enabled.

 

Note: If Modern Authentication is enabled for the data migration then the discovered history will only use the target mailbox, archive or PST for migration history.

 

For accounts that are re-migrated any previously migrated Notes items that were deleted in Outlook and removed from the Outlook Trash will be migrated again.

 

Notes Archive Database Processing

Settings    

Description

Create Migration Docs in this Stage

Specify whether you want to create migration documents during the Audit, Match, Notify, or Migration stage.

 

Exchange Archive Migration

Settings    

Description

Create Exchange Archive Documents

Select Yes to create Exchange Archive Migration documents during the matching phase if you will be migrating data to Exchange Archives. Exchange Archive Migration documents will only be created if the user has an archive in Exchange or Office 365.

 

 

 

Settings    

Description

Notes ID used to access mail files

Specify the Notes ID file to use during the migration process. This is the ID configured for all migration workstations.

4.4. Configuring User Provisioning

Click the User Provisioning tab to define how Exchange accounts are created and matched to the original Domino accounts.

Figure A: User Provisioning Settings with Office 365 migration disabled.

Figure B: User Provisioning Settings with Office 365 migration enabled.

Refer to the table below for a brief description of all the settings in the User Provisioning tab.

Settings    

Description

Exchange Version

Specify the version of Exchange to which you are migrating.

Hide Mailboxes from GAL

After a new Exchange user is created, you have the option to hide that account from displaying in the GAL. Select Yes if you want to hide the new mail users.

Match AD Account to

This option allows you to select the field used to map with the AD user’s sAMAccountName There are four options:

  • Shortname – This will match the Domino short name to the AD logon field.

  • Local Part of Internet address – This matches the first part of a user’s Internet address between Domino in AD.

  • Other Domino field – This allows you to choose a specific Domino field from the Domino directory to match with the AD SAMAccount name entry.

  • Custom Match – This allows you to define the field in Notes and AD that you wish to use to complete the match.

 

When using Other or Custom match, you will be asked for the field names you wish to use in this section of the configuration; for example, Notes InternetAddress to AD mail attribute.

Log Folder

Specify the path where the scripts and processes should create their log files.

Force Changes on this DC

This is the domain controller (DC) on which Notes Migrator will write its changes.

Account Performing Migrations

Specify the Windows account name that will be logged in on the Migration farm.

DC For Contacts

Specify the name of the domain controller that hosts the Domino contacts.

LDAP Path of Contact Container

If Contact objects were created for Domino user, specify the LDAP path to the container housing those contacts.

Resource Forest Settings

On occasion, the Exchange environment will be hosted in a different forest than its users’. To accommodate for this type of configuration, you can enable the Resource Forest Settings feature. When enabled, you will need to specify the following information:

  • Linked Master DC – Specify the name of the domain controller that is the master DC for the user forests.

  • Linked Master Domain – Specify the linked master domain name in common format (for example, myLinkedDomain).

PowerShell Run Delay

The delay before executing PowerShell functions.  This allows for LDAP operations to replicate in AD prior to cmd-lets running.

Remote PowerShell URL

Enter the URL of the remote PowerShell host (i.e. http://ExchangeHost/powershell).  Set to “https://outlook.office365.com/powershell” to return the username@domain.onMicrosoft.com address when configuring to match against an Office 365 or hybrid domain. The matching agent will return username@mydomain.com in on-premise installations where the remote PowerShell URL is an on-premise server.

Remote PowerShell access must be granted to the logged on user and Enable-PSRemoting must have been run on the remote host.

Exchange Environment

Specify the Exchange environment name. This is only required for Microsoft national and secure tenants (for example, O365GermantCLoud, O365USGovGCCHigh). This setting corresponds to the Connect-ExchangeOnline -ExchangeEnvironmentName parameter. This setting can be left blank for standard tenants.

Remote Azure AD Endpoint

Enter the URL of the remote Azure AD authentication endpoint if required. This is only required for Microsoft national tenants that would not use the default connection such as Germany or China (21Vianet) tenants (for example, https://login.chinacloudapi.cn

Azure AD Environment

Enter the tenant Azure AD environment name if required. This is only required for Microsoft national tenants that would not use the default Azure authentication environment such as Germany or China (21Vianet) tenants (for example, AzureGermanyCloud.

Create New Users

Select Yes to create users that do not already exist in Active Directory.

Active Directory Domain

Appears if Create New Users is set to Yes. Active Directory Domain name in domain.com format.

OU for new users

Appears if Create New Users is set to Yes. Organizational Unit to create new users in.  Leave blank for the default OU.

Default Password

Appears if Create New Users is set to Yes. This will be the default password assigned to any newly created users.

Force Password Change

Appears if Create New Users is set to Yes. Force newly created users to change their password on first login.

Create New Accounts

Select Yes to create rooms/resource/MIDB accounts that do not already exist in Active Directory.

Active Directory Domain

Appears if Create New Accounts is set to Yes. Active Directory Domain name in domain.com format. Used to create the UPN.

OU for Rooms

Appears if Create New Accounts is set to Yes. Organizational Unit to create new Room objects. This must be DN format. Leave blank for the default user container defined in Exchange.

OU for Resources/Equipment

Appears if Create New Accounts is set to Yes. Organizational Unit to create new Equipment objects. This must be DN format. Leave blank for the default user container defined in Exchange.

OU for MIDB/Shared Mailbox

Appears if Create New Accounts is set to Yes. Organizational Unit to create new Shared Mailbox objects.  This must be DN format. Leave blank for the default user container defined in Exchange.

Separate X500 Address Function

In very large or highly latent Active Directories, the time between creating an Exchange mailbox and setting the X500 address within the (EnableMailbox) agent can be too short.  This results in the code trying to set the X500 address on a mailbox that has not been fully initialized within the environment, and subsequently a failure to set the X500 address.  Selecting Yes splits the X500 address into a separate button.

4.5. Configuring Office 365 Settings


If you are planning to migrate to Office 365, you should first enable Office 365 migrations on the Office 365 tab.  Doing this will display additional settings for Office 365 migrations in various tabs. Refer to the Notes Migrator | CMT User Guide for Office 365 Migrations for additional information.

  1. Click the Office 365 tab; configure these settings when migrating to Office 365:

  1. Configure these settings if you want to migrate to Office 365

Use the following table to help enter the correct values for each setting:

Settings    

Description

Migrate to Office 365

Select Yes to enable migration to Office 365 and display the Office 365 settings below.

Office 365 Global Administrator

Appears if Office 365 migration is enabled

Specify the Office 365 Admin SMTP address used to pass credentials to Office 365 for remote access.

Office 365 Security Group

Appears if Office 365 migration is enabled

Specify the Office 365 Security Group Name used to set mailbox permission for migration purposes.

Office 365 License Type

Appears if Office 365 migration is enabled

Select the license type. All accounts will be activated under the selected license. Select “Multiple License Types” if you have multiple types to choose from.

Override existing license

Appears if Office 365 migration is enabled

If the user already has an applied license, the provisioning process can override it with the specified type.

Yes – change the existing license to the selected type

No – leave license type unchanged.

Office 365 Account Sku ID Prefix

Appears if Office 365 migration is enabled

Specify the tenant name of the client which is used to build the folder structure for reporting and activation. The required naming convention is to duplicate the given tenant name. For example, @contoso.onmicrosoft.com would have an Account Sku ID of “contoso”.

PowerShell Logging Path

Appears if Office 365 migration is enabled

Specify the PowerShell logging path used when generating, executing, and logging PowerShell scripts.

Default Reporting Path for Validation

Appears if Office 365 migration is enabled

Specify the reporting path used by the validation process.

Default Reporting Path for Activation

Appears if Office 365 migration is enabled

Specify the reporting path used by the activation process.

Default Reporting Path for Permission

Appears if Office 365 migration is enabled

Specify the reporting path used by the permission process.

O365 Location Country Codes

Appears if Office 365 migration is enabled

Specify the ISO Country Codes that will be assigned to the account in Office 365. These values will be used during the activation process.

4.6. Configuring Archive Settings

Local Archive Discovery

The preferred method of migrating end user archives is to configure the Local Archive Discovery settings and sending the Local Archive Discovery application to users to identify the local archives on the user’s workstation. Detailed information for configuring and using the Local Archive Discovery application is available in the Archive Migrator for Notes User Guide.

Legacy Archive Processing

If you are using the Lotus Script agent instead of the Local Archive Discovery application (Notes Archive Migrator), configure the settings in the Legacy Archive Processing section.

  1. On the End user archives tab, configure the following settings to copy local Notes archives to a server for centralized migration:

Use the following table to help enter the correct values for each setting:

Settings    

Description

Archive Processing

Specify where Archive data will be copied; to a specified Archive server OR into user’s existing Domino mail file.

Create Archive Copy or Replica

Specify whether you want to create a copy or replica of the Archive database. It is recommended that you create a replica. This will ensure that your archives will remain updated even if there is a time lapse between the preprocessing phase and actual migration.

Archive Destination Server

Specify the destination Domino server where the copy/replica of the Archive Database will be stored.

 

Leave it blank if you are copying them to a file server or a local workstation.

Archive Destination Path

Specify the destination path where the copy/replica of the Archive database will be stored.

 

Ensure that the path is relative if destination is a Domino server. However, if destination is a file server, full path must be specified

Local Archive Discovery

Specify how Notes Migrator will look for Archive databases on the end user machine. You can either select Auto Discover or Prompt User.

 

Configure these settings if you want to send an email to end users that will contain instructions and a button, which when clicked will copy their Archive database to the Domino server. Once on the server, the Archive databases can be migrated either to .pst files or to Microsoft Exchange.

  1. Once you click on the button to perform the copy/replicate your local archives to the Domino server, a new archive Person Document is created for each archive database copied to the server. The archive Person Documents are then listed in the Set Migration Profile view.

  1. To view which archive database will be migrated, double-click and open the username archive Person document:

  1. Assign a migration profile and the user will be promoted to the Migrate view to perform the migration.

 

  1. The Archive Processing field can copy the archive data to either the end user’s existing mailbox or a specified archive server:

  1. If you select Copy Data to End User’s Existing Mail, the form changes to display the Archive Folder Name field and remove the following three fields (Create Archive Copy or Replica, Archive Destination Server and Archive Destination Path). The added field specifies the folder name where all the archived data will be copied in users’ mailbox. You can specify any name in this field:

  1. Retain the default selection of Copy to Specified Archive Server in the Archive Processing field and click OK:

  1. Click the down-arrow next to the Create Archive Copy or Replica field. Select Replica and click OK:

  1. In the Archive Destination Server field, specify the IP address of the server where either copies or replicas of end users’ Archive databases will be stored. Leave the field blank since you are copying archives to a local workstation.

  2. Specify the destination path where end user .pst files will be stored in the Archive Destination Path field. In the field, specify Archives.

  3. Click the down-arrow next to the Local Archive Discovery field. You can either auto discover or prompt the user; click OK:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating