Chat now with support
Chat with Support

Binary Tree Migrator for Notes 20.11 - 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 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

Section 1. Introduction

Binary Tree Migrator for Notes features a new name and logo, but is the same, trusted product previously known as CMT for Exchange (CMTe).

1.1.    Purpose & Audience

The purpose of this document is to provide information on how to install and configure Migrator for Notes to perform a migration from HCL Lotus Domino and Notes to Microsoft Exchange and Outlook.

This document assumes the reader has a minimum of one-year experience using a Notes Client and some basic Domino Administration skills, as well as Exchange or Office 365 (also known as Microsoft 365) and PowerShell for mailbox provisioning. If Domino/Notes Administration topics mentioned in this document are not understood, please reference the Lotus Notes or Lotus System Administration documentation.

1.2.    About Binary Tree Migrator for Notes

Migrator for Notes is the most comprehensive software available for migrating from Lotus Domino to Microsoft Exchange or Office 365.

Migrator for Notes not only supports migrations to on-premises Microsoft Outlook and Exchange, but also to online versions of Microsoft Outlook and hosted Exchange, including Office 365. Please note that Active Directory requires the Exchange schema update or extension to have the mail attributes in on-premise Active Directory. Refer to Microsoft documentation for more information.

Migrator for Notes, which is a part of Binary Tree’s CMT suite of migration solutions, offers unmatched data fidelity, migration management, and migration throughput.

Data Fidelity

Migrator for Notes migrates Lotus Notes email messages, calendar entries, contacts, to-do lists, journal entries and more to Microsoft Outlook and Exchange while retaining the original text formatting, images, attachments, and links. Migrator for Notes also ensures that custom recurring meetings are properly migrated so that any subsequent changes, reschedules, or cancellations can be entered for all instances of the meeting. The data fidelity of Migrator for Notes significantly reduces the risk that your users will experience business process disruptions, data loss, or corruption.

Migration Management

Migrator for Notes allows you to manage the entire migration project. Migrator for Notes enables you to schedule users for migration, monitor the status of their migration, and to configure pre- and post-processing actions, such as decrypting encrypted email items, collecting rules and Access Control Lists. Migrator for Notes also enables you to control the data being migrated by enabling you to filter it by data type and to set quotas on the amount of data migrated per mailbox. Acting as a centralized migration management system, Migrator for Notes reduces the risk of forgotten tasks and provides an audit trail of tasks both completed as well as pending.

Migration Throughput

Migrator for Notes can scale to meet the migration requirements of any organization. Under optimal conditions, a single Migrator for Notes migration workstation can migrate up to 8 GB of data per hour. For smaller organizations, one Migrator for Notes workstation may be appropriate. For larger migrations, multiple Migrator for Notes workstations, whether on virtual machines or individual workstations, will coordinate the work effortlessly. Adding additional workstations is a simple and painless process. These additional workstations use a technology called Automated Workload Distribution (AWD) to ensure that each workstation is kept busy continuously.

Binary Tree has performed multiple laboratory tests to evaluate Migrator for Notes migration throughput. We have observed migration speeds of up to 8 GB of data per hour. Migration throughput will vary widely depending upon the source system, migration environment and target system. Review the list of testing details below.

 


For testing the throughput of the migration system, we recommend that you migrate to .pst for a baseline of migration worker performance.

 


Review any data throughput or throttling restrictions on the target messaging system. These are typically applied through Exchange system throttling policies, restricting items such as burst allowances and maximum allowed user and MAPI connections. Additional information on Exchange throttling can be requested from Microsoft support.

Migrator for Notes does allow for multiple Outlook migration accounts to be used and spread over multiple migration workers to prevent throttling on a single Outlook account from impacting all migrations. Binary Tree recommend configuring one Outlook migration account for every five migration workers with Exchange on-premise or for every two migration workers with Office 365 if AWD is used.

Lab Throughput Testing Details:

  • Lab migrations are performed over a high-speed LAN (1000 mbps)

  • Lab Domino and Exchange Servers support very few active users

  • Lab Migration workstation(s) normally have 2 GB of RAM or higher (often 4 GB). Although Binary Tree specifies a minimum acceptable amount of RAM as 4 GB is strongly recommended. Also, processor speeds and number of processors increase migration throughput.

  • Higher migration speeds have been observed on physical workstations versus virtual ones

  • Migration throughput is higher when migrating smaller number of messages with larger attachments than larger number of messages with smaller attachments. Additionally, disk I/O speeds greatly impact the throughput when migrating messages with attachments.

  • Migration throughput is lower when migrating calendar data, especially repeating calendar events. Large number of reschedules of repeating calendar events dramatically decreases migration throughput as all meeting updates must be processed prior to the data being migrated.

  • Large number of entries in the name translation table used to resolve source recipient lists decreases migration throughput

  • Large numbers of personal contact distribution lists, and especially distribution lists with many members, dramatically decreases migration throughput. Lab migration performance does not necessarily provide accurate estimates for production migration performance. The only way of determining the throughput you may achieve in your own environment is to set up and run a proof-of-concept project.

 

Key Features and Functions

Migrated Data

  • Mail Messages

  • Subject, Date, Body, Recipients

  • Mail Archives (server & local)

  • Mail-in Databases

  • Follow-up Flags

  • File Attachments

  • Doc Links, View Links and Database Links

  • Folders and Nested Folders

  • Calendar Entries

  • Personal Contacts

  • Personal Distribution Lists

  • Private Distribution Lists

  • To-do Lists / Personal Journal Data

Data Fidelity

  • Names Resolution

  • Name Translation

  • All Messages Reply-able in Outlook

  • Migrates Embedded Images

  • Migrates Encrypted Emails (after decrypting them or migrated the encrypted content attached in an .nsf)

  • Migrates Attachments

  • Retains Formatting of Tables

  • Retains Original HTML Formatting

Calendar Fidelity

  • Migrates Single and Recurring Meetings

  • Migrates Custom and Complex Recurring Meetings

  • Migrates all Past and Present Calendar Entries

  • Migrates all Rescheduled Calendar Entries

Data Filtering Options

  • Filter by Document Type (Mail, Contact, Calendar, Task)

  • Filter by Absolute/Relative Dates or Ranges

  • Select to Skip a List of Folders (excluding system folders)

  • Select to Skip Notes Links

  • Filter by Data Quota Limits

Migration Management

  • Advanced User Management

  • Selective User Migration

  • Migration-related Communications

  • Scheduled Migrations

  • Email Archive Migration Options

  • Migration Destination Options

  • Room and Resource Migration Options

  • Mail File Access and Size Verification

  • Migration Pre-processing

  • Migration Post-Processing

  • Automated or Manual User Provisioning

  • Detailed Activity Logging

Migration Throughput

  • Built-in Automated Workload Distribution (AWD) Functionality

  • Up to 8 GB/hour Migration Throughput per Migration Workstation (actual throughput may vary depending on the environment).

1.3.    Product Overview

Migrator for Notes is an application that migrates HCL Lotus Domino/Notes mail, calendar, contacts, and other databases, such as Rooms & Resources, to Microsoft Exchange. There are two major activities involved in a migration:

  • Pre-migration activities

  • Actual data conversion

 

The Migrator for Notes application contains all the required tools to give you complete control of these two activities.

Pre-Migration

The Migrator for Notes database provides centralized control and management of all pre-migration activities.

The database provides all the steps necessary to manage the migration of the following data contained within a user mail file:

  • Mail Messages

  • Message Attachments

  • Encrypted Messages

  • Folders and Sub-Folders

  • Single and Recurring Calendar Entries

  • Personal Contacts

  • Journal Entries

  • To Do Entries

In addition, Migrator for Notes can also migrate the following items:

  • Local Mail Archives

  • Personal groups (in the user's mail file)

  • Mail-In Databases

  • Rooms and Resources

Migration

Once pre-migration activities are complete, migration can be queued for the selected databases from Migrator for Notes. The migration destination can be either an Exchange Server or .pst files.

1.1. Purpose & Audience

Binary Tree Migrator for Notes features a new name and logo, but is the same, trusted product previously known as CMT for Exchange (CMTe).

1.1.    Purpose & Audience

The purpose of this document is to provide information on how to install and configure Migrator for Notes to perform a migration from HCL Lotus Domino and Notes to Microsoft Exchange and Outlook.

This document assumes the reader has a minimum of one-year experience using a Notes Client and some basic Domino Administration skills, as well as Exchange or Office 365 (also known as Microsoft 365) and PowerShell for mailbox provisioning. If Domino/Notes Administration topics mentioned in this document are not understood, please reference the Lotus Notes or Lotus System Administration documentation.

1.2.    About Binary Tree Migrator for Notes

Migrator for Notes is the most comprehensive software available for migrating from Lotus Domino to Microsoft Exchange or Office 365.

Migrator for Notes not only supports migrations to on-premises Microsoft Outlook and Exchange, but also to online versions of Microsoft Outlook and hosted Exchange, including Office 365. Please note that Active Directory requires the Exchange schema update or extension to have the mail attributes in on-premise Active Directory. Refer to Microsoft documentation for more information.

Migrator for Notes, which is a part of Binary Tree’s CMT suite of migration solutions, offers unmatched data fidelity, migration management, and migration throughput.

Data Fidelity

Migrator for Notes migrates Lotus Notes email messages, calendar entries, contacts, to-do lists, journal entries and more to Microsoft Outlook and Exchange while retaining the original text formatting, images, attachments, and links. Migrator for Notes also ensures that custom recurring meetings are properly migrated so that any subsequent changes, reschedules, or cancellations can be entered for all instances of the meeting. The data fidelity of Migrator for Notes significantly reduces the risk that your users will experience business process disruptions, data loss, or corruption.

Migration Management

Migrator for Notes allows you to manage the entire migration project. Migrator for Notes enables you to schedule users for migration, monitor the status of their migration, and to configure pre- and post-processing actions, such as decrypting encrypted email items, collecting rules and Access Control Lists. Migrator for Notes also enables you to control the data being migrated by enabling you to filter it by data type and to set quotas on the amount of data migrated per mailbox. Acting as a centralized migration management system, Migrator for Notes reduces the risk of forgotten tasks and provides an audit trail of tasks both completed as well as pending.

Migration Throughput

Migrator for Notes can scale to meet the migration requirements of any organization. Under optimal conditions, a single Migrator for Notes migration workstation can migrate up to 8 GB of data per hour. For smaller organizations, one Migrator for Notes workstation may be appropriate. For larger migrations, multiple Migrator for Notes workstations, whether on virtual machines or individual workstations, will coordinate the work effortlessly. Adding additional workstations is a simple and painless process. These additional workstations use a technology called Automated Workload Distribution (AWD) to ensure that each workstation is kept busy continuously.

Binary Tree has performed multiple laboratory tests to evaluate Migrator for Notes migration throughput. We have observed migration speeds of up to 8 GB of data per hour. Migration throughput will vary widely depending upon the source system, migration environment and target system. Review the list of testing details below.

 


For testing the throughput of the migration system, we recommend that you migrate to .pst for a baseline of migration worker performance.

 


Review any data throughput or throttling restrictions on the target messaging system. These are typically applied through Exchange system throttling policies, restricting items such as burst allowances and maximum allowed user and MAPI connections. Additional information on Exchange throttling can be requested from Microsoft support.

Migrator for Notes does allow for multiple Outlook migration accounts to be used and spread over multiple migration workers to prevent throttling on a single Outlook account from impacting all migrations. Binary Tree recommend configuring one Outlook migration account for every five migration workers with Exchange on-premise or for every two migration workers with Office 365 if AWD is used.

Lab Throughput Testing Details:

  • Lab migrations are performed over a high-speed LAN (1000 mbps)

  • Lab Domino and Exchange Servers support very few active users

  • Lab Migration workstation(s) normally have 2 GB of RAM or higher (often 4 GB). Although Binary Tree specifies a minimum acceptable amount of RAM as 4 GB is strongly recommended. Also, processor speeds and number of processors increase migration throughput.

  • Higher migration speeds have been observed on physical workstations versus virtual ones

  • Migration throughput is higher when migrating smaller number of messages with larger attachments than larger number of messages with smaller attachments. Additionally, disk I/O speeds greatly impact the throughput when migrating messages with attachments.

  • Migration throughput is lower when migrating calendar data, especially repeating calendar events. Large number of reschedules of repeating calendar events dramatically decreases migration throughput as all meeting updates must be processed prior to the data being migrated.

  • Large number of entries in the name translation table used to resolve source recipient lists decreases migration throughput

  • Large numbers of personal contact distribution lists, and especially distribution lists with many members, dramatically decreases migration throughput. Lab migration performance does not necessarily provide accurate estimates for production migration performance. The only way of determining the throughput you may achieve in your own environment is to set up and run a proof-of-concept project.

 

Key Features and Functions

Migrated Data

  • Mail Messages

  • Subject, Date, Body, Recipients

  • Mail Archives (server & local)

  • Mail-in Databases

  • Follow-up Flags

  • File Attachments

  • Doc Links, View Links and Database Links

  • Folders and Nested Folders

  • Calendar Entries

  • Personal Contacts

  • Personal Distribution Lists

  • Private Distribution Lists

  • To-do Lists / Personal Journal Data

Data Fidelity

  • Names Resolution

  • Name Translation

  • All Messages Reply-able in Outlook

  • Migrates Embedded Images

  • Migrates Encrypted Emails (after decrypting them or migrated the encrypted content attached in an .nsf)

  • Migrates Attachments

  • Retains Formatting of Tables

  • Retains Original HTML Formatting

Calendar Fidelity

  • Migrates Single and Recurring Meetings

  • Migrates Custom and Complex Recurring Meetings

  • Migrates all Past and Present Calendar Entries

  • Migrates all Rescheduled Calendar Entries

Data Filtering Options

  • Filter by Document Type (Mail, Contact, Calendar, Task)

  • Filter by Absolute/Relative Dates or Ranges

  • Select to Skip a List of Folders (excluding system folders)

  • Select to Skip Notes Links

  • Filter by Data Quota Limits

Migration Management

  • Advanced User Management

  • Selective User Migration

  • Migration-related Communications

  • Scheduled Migrations

  • Email Archive Migration Options

  • Migration Destination Options

  • Room and Resource Migration Options

  • Mail File Access and Size Verification

  • Migration Pre-processing

  • Migration Post-Processing

  • Automated or Manual User Provisioning

  • Detailed Activity Logging

Migration Throughput

  • Built-in Automated Workload Distribution (AWD) Functionality

  • Up to 8 GB/hour Migration Throughput per Migration Workstation (actual throughput may vary depending on the environment).

1.3.    Product Overview

Migrator for Notes is an application that migrates HCL Lotus Domino/Notes mail, calendar, contacts, and other databases, such as Rooms & Resources, to Microsoft Exchange. There are two major activities involved in a migration:

  • Pre-migration activities

  • Actual data conversion

 

The Migrator for Notes application contains all the required tools to give you complete control of these two activities.

Pre-Migration

The Migrator for Notes database provides centralized control and management of all pre-migration activities.

The database provides all the steps necessary to manage the migration of the following data contained within a user mail file:

  • Mail Messages

  • Message Attachments

  • Encrypted Messages

  • Folders and Sub-Folders

  • Single and Recurring Calendar Entries

  • Personal Contacts

  • Journal Entries

  • To Do Entries

In addition, Migrator for Notes can also migrate the following items:

  • Local Mail Archives

  • Personal groups (in the user's mail file)

  • Mail-In Databases

  • Rooms and Resources

Migration

Once pre-migration activities are complete, migration can be queued for the selected databases from Migrator for Notes. The migration destination can be either an Exchange Server or .pst files.

1.2. About Binary Tree Migrator for Notes

Binary Tree Migrator for Notes features a new name and logo, but is the same, trusted product previously known as CMT for Exchange (CMTe).

1.1.    Purpose & Audience

The purpose of this document is to provide information on how to install and configure Migrator for Notes to perform a migration from HCL Lotus Domino and Notes to Microsoft Exchange and Outlook.

This document assumes the reader has a minimum of one-year experience using a Notes Client and some basic Domino Administration skills, as well as Exchange or Office 365 (also known as Microsoft 365) and PowerShell for mailbox provisioning. If Domino/Notes Administration topics mentioned in this document are not understood, please reference the Lotus Notes or Lotus System Administration documentation.

1.2.    About Binary Tree Migrator for Notes

Migrator for Notes is the most comprehensive software available for migrating from Lotus Domino to Microsoft Exchange or Office 365.

Migrator for Notes not only supports migrations to on-premises Microsoft Outlook and Exchange, but also to online versions of Microsoft Outlook and hosted Exchange, including Office 365. Please note that Active Directory requires the Exchange schema update or extension to have the mail attributes in on-premise Active Directory. Refer to Microsoft documentation for more information.

Migrator for Notes, which is a part of Binary Tree’s CMT suite of migration solutions, offers unmatched data fidelity, migration management, and migration throughput.

Data Fidelity

Migrator for Notes migrates Lotus Notes email messages, calendar entries, contacts, to-do lists, journal entries and more to Microsoft Outlook and Exchange while retaining the original text formatting, images, attachments, and links. Migrator for Notes also ensures that custom recurring meetings are properly migrated so that any subsequent changes, reschedules, or cancellations can be entered for all instances of the meeting. The data fidelity of Migrator for Notes significantly reduces the risk that your users will experience business process disruptions, data loss, or corruption.

Migration Management

Migrator for Notes allows you to manage the entire migration project. Migrator for Notes enables you to schedule users for migration, monitor the status of their migration, and to configure pre- and post-processing actions, such as decrypting encrypted email items, collecting rules and Access Control Lists. Migrator for Notes also enables you to control the data being migrated by enabling you to filter it by data type and to set quotas on the amount of data migrated per mailbox. Acting as a centralized migration management system, Migrator for Notes reduces the risk of forgotten tasks and provides an audit trail of tasks both completed as well as pending.

Migration Throughput

Migrator for Notes can scale to meet the migration requirements of any organization. Under optimal conditions, a single Migrator for Notes migration workstation can migrate up to 8 GB of data per hour. For smaller organizations, one Migrator for Notes workstation may be appropriate. For larger migrations, multiple Migrator for Notes workstations, whether on virtual machines or individual workstations, will coordinate the work effortlessly. Adding additional workstations is a simple and painless process. These additional workstations use a technology called Automated Workload Distribution (AWD) to ensure that each workstation is kept busy continuously.

Binary Tree has performed multiple laboratory tests to evaluate Migrator for Notes migration throughput. We have observed migration speeds of up to 8 GB of data per hour. Migration throughput will vary widely depending upon the source system, migration environment and target system. Review the list of testing details below.

 


For testing the throughput of the migration system, we recommend that you migrate to .pst for a baseline of migration worker performance.

 


Review any data throughput or throttling restrictions on the target messaging system. These are typically applied through Exchange system throttling policies, restricting items such as burst allowances and maximum allowed user and MAPI connections. Additional information on Exchange throttling can be requested from Microsoft support.

Migrator for Notes does allow for multiple Outlook migration accounts to be used and spread over multiple migration workers to prevent throttling on a single Outlook account from impacting all migrations. Binary Tree recommend configuring one Outlook migration account for every five migration workers with Exchange on-premise or for every two migration workers with Office 365 if AWD is used.

Lab Throughput Testing Details:

  • Lab migrations are performed over a high-speed LAN (1000 mbps)

  • Lab Domino and Exchange Servers support very few active users

  • Lab Migration workstation(s) normally have 2 GB of RAM or higher (often 4 GB). Although Binary Tree specifies a minimum acceptable amount of RAM as 4 GB is strongly recommended. Also, processor speeds and number of processors increase migration throughput.

  • Higher migration speeds have been observed on physical workstations versus virtual ones

  • Migration throughput is higher when migrating smaller number of messages with larger attachments than larger number of messages with smaller attachments. Additionally, disk I/O speeds greatly impact the throughput when migrating messages with attachments.

  • Migration throughput is lower when migrating calendar data, especially repeating calendar events. Large number of reschedules of repeating calendar events dramatically decreases migration throughput as all meeting updates must be processed prior to the data being migrated.

  • Large number of entries in the name translation table used to resolve source recipient lists decreases migration throughput

  • Large numbers of personal contact distribution lists, and especially distribution lists with many members, dramatically decreases migration throughput. Lab migration performance does not necessarily provide accurate estimates for production migration performance. The only way of determining the throughput you may achieve in your own environment is to set up and run a proof-of-concept project.

 

Key Features and Functions

Migrated Data

  • Mail Messages

  • Subject, Date, Body, Recipients

  • Mail Archives (server & local)

  • Mail-in Databases

  • Follow-up Flags

  • File Attachments

  • Doc Links, View Links and Database Links

  • Folders and Nested Folders

  • Calendar Entries

  • Personal Contacts

  • Personal Distribution Lists

  • Private Distribution Lists

  • To-do Lists / Personal Journal Data

Data Fidelity

  • Names Resolution

  • Name Translation

  • All Messages Reply-able in Outlook

  • Migrates Embedded Images

  • Migrates Encrypted Emails (after decrypting them or migrated the encrypted content attached in an .nsf)

  • Migrates Attachments

  • Retains Formatting of Tables

  • Retains Original HTML Formatting

Calendar Fidelity

  • Migrates Single and Recurring Meetings

  • Migrates Custom and Complex Recurring Meetings

  • Migrates all Past and Present Calendar Entries

  • Migrates all Rescheduled Calendar Entries

Data Filtering Options

  • Filter by Document Type (Mail, Contact, Calendar, Task)

  • Filter by Absolute/Relative Dates or Ranges

  • Select to Skip a List of Folders (excluding system folders)

  • Select to Skip Notes Links

  • Filter by Data Quota Limits

Migration Management

  • Advanced User Management

  • Selective User Migration

  • Migration-related Communications

  • Scheduled Migrations

  • Email Archive Migration Options

  • Migration Destination Options

  • Room and Resource Migration Options

  • Mail File Access and Size Verification

  • Migration Pre-processing

  • Migration Post-Processing

  • Automated or Manual User Provisioning

  • Detailed Activity Logging

Migration Throughput

  • Built-in Automated Workload Distribution (AWD) Functionality

  • Up to 8 GB/hour Migration Throughput per Migration Workstation (actual throughput may vary depending on the environment).

1.3.    Product Overview

Migrator for Notes is an application that migrates HCL Lotus Domino/Notes mail, calendar, contacts, and other databases, such as Rooms & Resources, to Microsoft Exchange. There are two major activities involved in a migration:

  • Pre-migration activities

  • Actual data conversion

 

The Migrator for Notes application contains all the required tools to give you complete control of these two activities.

Pre-Migration

The Migrator for Notes database provides centralized control and management of all pre-migration activities.

The database provides all the steps necessary to manage the migration of the following data contained within a user mail file:

  • Mail Messages

  • Message Attachments

  • Encrypted Messages

  • Folders and Sub-Folders

  • Single and Recurring Calendar Entries

  • Personal Contacts

  • Journal Entries

  • To Do Entries

In addition, Migrator for Notes can also migrate the following items:

  • Local Mail Archives

  • Personal groups (in the user's mail file)

  • Mail-In Databases

  • Rooms and Resources

Migration

Once pre-migration activities are complete, migration can be queued for the selected databases from Migrator for Notes. The migration destination can be either an Exchange Server or .pst files.

Section 2. Installing Binary Tree Migrator for Notes

Migrator for Notes consists of a frontend HCL Lotus Notes database. This and other software components of Migrator for Notes are provided in an InstallShield installation package.

Migrator for Notes should be completely installed and configured on one migration workstation first. If more than one workstation is needed, you must then deploy Migrator for Notes to all other migration workstations, and each migration workstation should use one (same) Domino server-based database called Migrator for Notes instead of a local copy. Reference the Automated Workload Distribution section of this guide for more information.

 


Binary Tree recommends testing and verifying the migration system using test accounts and Notes data to confirm the expected migration processing prior to completing production migrations.

2.1. Before Installation

Before Migrator for Notes is installed, all hardware and software requirements must be completed. Refer to the Migrator for Notes Requirements document for the complete list of hardware and software requirements.

During installation, several of the software requirements are verified. In some cases, the InstallShield installation package helps install missing software. However, it is recommended that the required software is installed prior to the product installation and to not to rely upon the aid of the InstallShield installation package.


The installer does not replace the Notes Migrator.nsf database in the local notes data directory on the Migration Control Center when doing an upgrade from a previous release of Migrator for Notes. When upgrading from a previous version of Migrator for Notes, you must complete one of the following tasks:

  • Manually rename the file name of the existing “Notes Migrator.nsf” database to something other than this reserved name. After the upgrade, the newly installed Notes Migrator.nsf database is located in the notes data directory so you can configure it from the settings of the renamed database.

Or

  • Copy the newly installed database from the C:\Program Files\Binary Tree\CMT for Exchange\Notes Tools directory on the Migration Control Center to the Notes client data directory, renaming the file to a Notes database template “Notes Migrator.ntf”. Remember to sign the template if required. Replace the design of your existing Notes Migrator.nsf database from the new template “Notes Migrator.ntf” to get any updated design changes.

2.2. Downloading Migrator for Notes

Binary Tree maintains the latest release of the Migrator for Notes Installation Package on a secure FTP web site. The address to the FTP site is ftp://cftp.binarytree.com. To download a copy, Binary Tree provides a username and password. Log on to the web site using the given credentials and download CMT for Exchange.exe to the migration workstation’s Desktop. If you are installing on more than one workstation and plan to use a software management or GPO to deploy, download the CMTeWorker.msi.

2.3. Installing Software on the Migration Control Center

  1. To launch the InstallShield install kit, double-click the CMT for Exchange Setup.exe file from the desktop:

  1. Click Run to start the wizard

 

  1. If required software is not installed, a dialog box shown below will be displayed. To allow the wizard to install the required software, click Install.

 


The installation of the prerequisite software through the installer requires the workstation to have Internet access. This software can be installed prior to running the setup if Internet access is not available.

 


The installer does require TLS 1.0 to be enabled on the Migration Controller in order to configure the SQL database.

 

Several dialog boxes, similar to the ones shown below, are displayed during requirement downloading and installation:

 

  1. When completed, the wizard displays the Welcome screen; click Next:

The wizard displays the License Agreement screen. Review the License Agreement and accept it; click Yes:

 

  1. Select the destination path for installing Migrator for Notes in the Choose Destination Location screen. It is strongly recommended that you keep the default destination folder; click Next:

  1. Enter the database server location and the credential information, and then click Next to continue. When SQL Server Express is installed by the installer, the password is set to “Password1” by default:

  1. Several screens similar to the one below appear while the database and IIS is installed and configured:

  1. The Ready to Install Screen appears; click Install to begin the installation:

 

  1. The wizard notifies when the software is successfully installed and configured on your system; click Finish to close the wizard:

  1. The wizard creates the CMT for Exchange subfolder in the Program Files folder. Within this folder is another subfolder Notes Tools that also contains a copy of the Migrator for Notes Domino database. This copy can be used as a backup if needed.

In addition, a shortcut is added to the All Programs menu; click Start -> All Programs -> Binary Tree -> Notes Migrator.

2.4. Setting the CMTE App Pool to Enable 32-bit Applications

  1. After the installation, open the IIS Manager and navigate to Application Pools

  2. Right-click on .Net v4.5 in the Application Pools list and select Advanced Settings

  3. Set the Enable 32-bit Applications setting to True

  4. Restart the IIS Services

2.5. Repairing, or Uninstalling Migrator for Notes

The Migrator for Notes software can be modified, repaired, or removed after it has been installed by executing CMT Exchange Setup from the Control Panel.

  1. In the Add or Remove Programs applet, locate the Binary Tree Migrator for Notes icon in the Control Panel and select it. To repair the application, select Repair; if you wish to remove the application, select Remove:

2.5.1     Repairing Migrator for Notes

  1. To repair the currently installed software, select Repair and then click Next:

 

  1. Several Setup Status screens display:

  1. The Maintenance Complete screen displays when the restore is complete; click Finish:

2.5.2     Uninstalling Migrator for Notes

  1. To remove or uninstall the software, select Remove and then click Next

  1. To remove the Migrator for Notes application, click Yes:

  1. When the uninstall process is complete, the Uninstall Complete screen displays; click Finish.

The Migrator for Notes application is removed:

 

 


For AWD configurations, migration workers should be un-installed prior to removing the Migration Controller installation.

 

 

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating