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

Additional Procedures

The following additional configurations and procedures are required when preparing for migrations where the target location is Office 365 and Modern Authentication will be used. These do require the option to migrate to Office 365 to be enabled.

Settings Updates

The Notes Migrator Settings will require the below to be configured on the Required Settings | Additional tab:

  • Enable PowerShell Modern Auth set to Yes

    • This will configure the PowerShell functions to use Modern Authentication processing for account validation, provisioning, setting full access and matching. This enables the use of the MSOnline and ExchangeOnline modules.

  • Enable Modern Auth for Migration set to Yes

    • This will update the Migration Profile to instruct the Migration Worker to use Modern Authentication for its Outlook connection to Office 365. This will use an Outlook profile on the Migration Worker that is configured for Modern Authentication.

 


The PowerShell Admin account password can be entered using the Set PowerShell Password button. This will prompt for the password in PowerShell and enter a hash of the password using the PowerShell As Secure method. This is not required and if left blank the PowerShell processing will ask for the password when the functions are performed.

 

Migration Controller

The use of Modern Authentication with PowerShell requires the ExchangeOnline module to be installed. This also requires TLS 1.2 to be enabled on the Migration Controller for PowerShell connectivity. These may require the installation of the PowerShellGet module, steps for completing the updates are below.

If prompted for updates to be completed these should be accepted.

Set up PowerShell for remote access on the Migration Controller:

  • Launch PowerShell as an administrator. At the prompt, type: 

    • Set-ExecutionPolicy Unrestricted

  • Install PowerShell ExchangeOnline Module and enable TLS 1.2:

    • Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord

    • Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord

    • Install-PackageProvider -Name NuGet -Force

    • Install-Module -Name PowerShellGet -Force

    • Install-Module –Name ExchangeOnlineManagement

Enable WinRM Basic Authentication:

  • Launch Command Prompt as an administrator. At the prompt, type:

    • winrm set winrm/config/client/auth @{Basic="true"}

Migration Worker

The use of Modern Authentication with the Notes Migrator worker application requires an Outlook profile to be configured on the worker machine. This would be configured for an Outlook profile named Migrate and would use the Office 365 account designated for the worker migration access to the target mailboxes.

The Outlook profile created will generate the required access token for Office 365 access to the migration account mailbox and the target account mailboxes. Notes Migrator will then use this token and the refresh token for migrations. Notes Migrator does not generate the token itself.

The below steps show the configuration of an Outlook profile through the process of opening Outlook for the first time. This can also be completed through Control Panel | Mail (Microsoft Outlook Version) (32 Bit) | Show Profiles.

 


This will no longer use the Connectivity Tester account on the migration worker for the Modern Authentication configuration and this can be skipped when installing the migration worker. The Connectivity Tester account is still used if Modern Authentication is not enabled.

To create the Outlook profile for a migration worker:

Open Outlook on the migration worker and choose Options | New

Set the name of the profile to Migrate

Graphical user interface, application

Description automatically generated

Enter the address of the account the would be used for the worker migrations and connect to Office 365

After the profile is configured click on the Properties, select the account used and select Change. Disable Cache Exchange Mode.

Open Outlook with the Migrate profile to validate that it is connected and to ensure that the token is created.

Appendix C: Creating a Migration Farm

Why do I need to create a Migration Farm?

In a large enterprise where thousands of users need to be migrated, using a single Migration Workstation can’t serve the purpose. Like all Binary Tree’s CMT products, Notes Migrator provides a feature that allows you to migrate many users using parallel processing.

Parallel processing is defined as the ability to execute multiple simultaneous migrations using multiple Migration Workstations.

To achieve true parallel processing, the first step is to create a migration farm. Notes Migrator can be easily configured to create a migration farm by configuring a Migration Control Center and multiple Migration Workstations. These workstations can be located, provisioned, managed, and monitored anywhere in the world.

Manual versus Automated Workload Distribution

In a typical set up, Notes Migrator distributes migration load among multiple Migration Workstations that are located at multiple location and communicating with the one Migration Control Center. But if the large enterprise is spread over multiple regions/sites, Notes Migrator can also be configured such that you can run migrations independently at each site to keep migration localized.

Workload can be distributed from the Migration Control Center to Migration Workstations in two ways:

Manual

This type of workload distribution enables migration administrators to fully control time and workstation for each user’s migration.

Automated (Automated Workload Distribution (AWD))

This type of workload distribution ensures continuous migration execution among a group of workstations.

How many migration workstations can be added to a farm?

Up to 140 workstations can be added to a farm before an additional farm must be created.

What are the prerequisites for migration workstations?

The most critical prerequisite is that Notes Migrator, the Lotus Notes Client, and the Microsoft Outlook client must already be installed on each migration workstation. Refer to the Notes Migrator Requirements document form more details.

Additional migration workstations should be configured as recommended for Notes Migrator. The workstation must have the following:

  1. Notes client installed. You will also need a Notes user ID that has permission to access the servers and mailboxes you want to migrate. Open a database on each server you will be accessing and verify that you have a valid certificate for the server.

  2. Outlook client installed.

  3. ALL updates and service packs for Windows and Office.


Coordinated Universal Time (UTC) is not supported as a time zone for the migration controller and workstations.

 

How do I create a migration farm?

Installing a Migration Workstation

Installation of the migration worker can be done via two methods, via GPO MSI installer or through the CMTMonitor web page.

Installing via the CMTMonitor

  1. On one of designated Migration Workstations, (not the Migration Control Center), launch Internet Explorer and go to the Migration Control Center/CMTMonitor website.

  1. Click the Install Workstation Software link and then Run

  1. Click Next on the Welcome screen

  1. Enter the Notes Migrator server name, workstation name, and workstation address and click Next.

  1. Entering user account information is optional on this screen. In smaller farm scenarios, you can continue to use the Migration Administrator account distributed by the MCC. If you wish to use another Migration Administrator account, enter the information in this screen.

This information is encrypted and cached on the Worker.

 


This account can be changed on the Migration Workstation through the Connectivity Tester application.

 

  1. Click Install

  1. Click Finish

  1. The Exchange Connectivity Tester will launch with the information you entered in the installer. Press the Test button to verify the account credentials can connect to Exchange.

IMPORTANT: If the cached password is incorrect, a Windows Security dialog will be displayed. It is critical that you press Cancel and allow the test to fail. Entering the correct password in the Windows Security popup will allow the test to pass but will not change the cached credential information.

 


This is not required if Modern Authentication is used for the migration worker connections and the Migrate Outlook profile has been configured.

Enter a new password and press Test again.

When the account information is correct and verified, the Save button will be enabled to allow you to update the information cached on this Worker.

  1. Press OK to exit the application.

Changing the Cached Account

The Exchange Connectivity Tester is added as a desktop shortcut and to the Start menu on the Worker. You can launch the application to change the cached account information in the Worker.

 

Note that the Save button will only be enabled after a successful test, and the credential information is different than the credentials that are cached in the Worker. Testing the existing cached account will not enable the Save button.

Deploying via MSI file

For automated deployment, send a command line with the following arguments:

  • SERVICEURL The FQDN or IP Address of the CMT_XMLServer. Normally, this is the same machine where the MCC is installed.

  • EXCREDDIALOG_EMAIL: The SMTP address of a MAPI Migration Administrator account.

  • EXCREDDIALOG_UPN: The “User Principal Name” of the MAPI Migration Administrator account. NETBIOS format (domain\user) is not supported.

  • EXCREDDIALOG_PASSWORD: The password for the MAPI Migration Administrator account.

Example:

msiexec /i “CMTeWorker.msi” SERVICEURL=”mcchost.org.dom” EXCREDDIALOG_EMAIL=migadmin@org.dom EXCREDDIALOG_UPN=migadmin@org.dom EXCREDDIALOG_PASSWORD=”Migration admin password” /qn


The “EXCREDDIALOG_xxx” arguments are not needed if you wish to continue using the account distributed by the MCC.


The .MSI installer does not check the workstation environment meets the minimum requirements, and does not install the missing components needed for a successful migration.

Monitoring the Website

The monitor can be accessed from any machine on the LAN to observe the status of the workstations. The workstation named local is the migration engine installed on the Migration Control Center machine.


The Internet Information Server (IIS) included with Windows Client Operating Systems has a 10-connection limit. The additional workstations periodically connect to the master machines IIS to get work and report status, effectively tying up one connection per workstation. Connecting to the monitor website also consumes one connection. If you exceed 10 connections, then the extra workstations may not work correctly. Install the Notes Migrator software on Windows Server operating system if you need more than 10 simultaneous connections.

 

The Machine info page displays an overview of the migration workstations status and performance.

The Migration info page displays what each workstation is currently doing

The Monitor website is refreshed approximately every 30 seconds. Throughput figures are calculated after a migration is completed.

To manage the worker application on any machine, right-click the respective icon in the system tray. If the workstation is currently running a migration, the Finish and Exit selection allows the migration to complete and report its status before shutting down the worker application. The Exit Now option disconnects the worker application. If a migration is in progress, the status is not updated on the server.

 

 

Upgrading a Migration Farm

Perform the following steps to upgrade your existing farm.

  1. Run an in-place upgrade on the controller by clicking the "Notes Migrator Setup XX.XX. This will upgrade the controller machine. Ensure that there are no migrations running during this process.


Make sure to make a backup copy of your Notes Migrator SQL database. This can be done through the SQL Management Studio by right clicking the database and selecting Tasks | Backup.

  1. Make a design template of the "Notes Migrator.nsf" which will be located in C:\Program Files\Binary Tree\CMT for Exchange\Notes Tools after the upgrade.  This can be accomplished by:

    1. Double clicking on the Notes Migrator.nsf file located in the C:\Program Files\Binary Tree\CMT for Exchange\Notes Tools on the controller machine.

    2. This will load the notes client and open the database on the controller.  From the Notes client menu choose File/Application/New copy.  The file copy dialog window will open.  Make a copy of the database giving it a "NTF" extension instead of a "NSF"extension.

    3. Open your Notes Migrator database on your domino server.  With the file open, choose from the Notes client menu, File/Application/Design Replace.  The design template dialog will open, choose your newly created template from the list of templates and hit ok.

    4. Sign the Notes Migrator database with your current Notes ID, this on the Progress Summary page.


Make sure to make a backup copy of your Notes Migrator database on the domino server for safety purposes. This can be a Notes copy of the .nsf database to the Local Notes workstation.

  1. The workers will automatically upgrade.  The workers check in with the controller and when the worker finds it’s at a lower release then the controller, it will automatically upgrade itself by automatically running the Notes Migrator Worker XX.XX MSI.


The existing status for all migration accounts will be retained including the migration system licensing.

 

Upgrading from 4.6.X

The process is the same as above except step 3.  You must manually run the Notes Migrator Worker XX.XX.msi on all workers to upgrade to the latest software.

 

Upgrading from 3.8x, 4.0, 4.5

For these releases,  the worker software will need to be completely removed first, along with uninstalling the controller as well.

  1. Uninstall all the workers by going to each worker and running the uninstall program from the control panel.  This will remove the worker installation and unregister the workers from the controller.

  2. Uninstall the Notes Migrator program the control panel on the controller.  This will remove all the software from the controller machine.   Run the Notes Migrator Setup XX.XX on the controller machine.

 

Why do I need to create a Migration Farm?

In a large enterprise where thousands of users need to be migrated, using a single Migration Workstation can’t serve the purpose. Like all Binary Tree’s CMT products, Notes Migrator provides a feature that allows you to migrate many users using parallel processing.

Parallel processing is defined as the ability to execute multiple simultaneous migrations using multiple Migration Workstations.

To achieve true parallel processing, the first step is to create a migration farm. Notes Migrator can be easily configured to create a migration farm by configuring a Migration Control Center and multiple Migration Workstations. These workstations can be located, provisioned, managed, and monitored anywhere in the world.

Manual versus Automated Workload Distribution

In a typical set up, Notes Migrator distributes migration load among multiple Migration Workstations that are located at multiple location and communicating with the one Migration Control Center. But if the large enterprise is spread over multiple regions/sites, Notes Migrator can also be configured such that you can run migrations independently at each site to keep migration localized.

Workload can be distributed from the Migration Control Center to Migration Workstations in two ways:

Manual

This type of workload distribution enables migration administrators to fully control time and workstation for each user’s migration.

Automated (Automated Workload Distribution (AWD))

This type of workload distribution ensures continuous migration execution among a group of workstations.

How many migration workstations can be added to a farm?

Up to 140 workstations can be added to a farm before an additional farm must be created.

What are the prerequisites for migration workstations?

The most critical prerequisite is that Notes Migrator, the Lotus Notes Client, and the Microsoft Outlook client must already be installed on each migration workstation. Refer to the Notes Migrator Requirements document form more details.

Additional migration workstations should be configured as recommended for Notes Migrator. The workstation must have the following:

  1. Notes client installed. You will also need a Notes user ID that has permission to access the servers and mailboxes you want to migrate. Open a database on each server you will be accessing and verify that you have a valid certificate for the server.

  2. Outlook client installed.

  3. ALL updates and service packs for Windows and Office.


Coordinated Universal Time (UTC) is not supported as a time zone for the migration controller and workstations.

 

How do I create a migration farm?

Installing a Migration Workstation

Installation of the migration worker can be done via two methods, via GPO MSI installer or through the CMTMonitor web page.

Installing via the CMTMonitor

  1. On one of designated Migration Workstations, (not the Migration Control Center), launch Internet Explorer and go to the Migration Control Center/CMTMonitor website.

  1. Click the Install Workstation Software link and then Run

  1. Click Next on the Welcome screen

  1. Enter the Notes Migrator server name, workstation name, and workstation address and click Next.

  1. Entering user account information is optional on this screen. In smaller farm scenarios, you can continue to use the Migration Administrator account distributed by the MCC. If you wish to use another Migration Administrator account, enter the information in this screen.

This information is encrypted and cached on the Worker.

 


This account can be changed on the Migration Workstation through the Connectivity Tester application.

 

  1. Click Install

  1. Click Finish

  1. The Exchange Connectivity Tester will launch with the information you entered in the installer. Press the Test button to verify the account credentials can connect to Exchange.

IMPORTANT: If the cached password is incorrect, a Windows Security dialog will be displayed. It is critical that you press Cancel and allow the test to fail. Entering the correct password in the Windows Security popup will allow the test to pass but will not change the cached credential information.

 


This is not required if Modern Authentication is used for the migration worker connections and the Migrate Outlook profile has been configured.

Enter a new password and press Test again.

When the account information is correct and verified, the Save button will be enabled to allow you to update the information cached on this Worker.

  1. Press OK to exit the application.

Changing the Cached Account

The Exchange Connectivity Tester is added as a desktop shortcut and to the Start menu on the Worker. You can launch the application to change the cached account information in the Worker.

 

Note that the Save button will only be enabled after a successful test, and the credential information is different than the credentials that are cached in the Worker. Testing the existing cached account will not enable the Save button.

Deploying via MSI file

For automated deployment, send a command line with the following arguments:

  • SERVICEURL The FQDN or IP Address of the CMT_XMLServer. Normally, this is the same machine where the MCC is installed.

  • EXCREDDIALOG_EMAIL: The SMTP address of a MAPI Migration Administrator account.

  • EXCREDDIALOG_UPN: The “User Principal Name” of the MAPI Migration Administrator account. NETBIOS format (domain\user) is not supported.

  • EXCREDDIALOG_PASSWORD: The password for the MAPI Migration Administrator account.

Example:

msiexec /i “CMTeWorker.msi” SERVICEURL=”mcchost.org.dom” EXCREDDIALOG_EMAIL=migadmin@org.dom EXCREDDIALOG_UPN=migadmin@org.dom EXCREDDIALOG_PASSWORD=”Migration admin password” /qn


The “EXCREDDIALOG_xxx” arguments are not needed if you wish to continue using the account distributed by the MCC.


The .MSI installer does not check the workstation environment meets the minimum requirements, and does not install the missing components needed for a successful migration.

Monitoring the Website

The monitor can be accessed from any machine on the LAN to observe the status of the workstations. The workstation named local is the migration engine installed on the Migration Control Center machine.


The Internet Information Server (IIS) included with Windows Client Operating Systems has a 10-connection limit. The additional workstations periodically connect to the master machines IIS to get work and report status, effectively tying up one connection per workstation. Connecting to the monitor website also consumes one connection. If you exceed 10 connections, then the extra workstations may not work correctly. Install the Notes Migrator software on Windows Server operating system if you need more than 10 simultaneous connections.

 

The Machine info page displays an overview of the migration workstations status and performance.

The Migration info page displays what each workstation is currently doing

The Monitor website is refreshed approximately every 30 seconds. Throughput figures are calculated after a migration is completed.

To manage the worker application on any machine, right-click the respective icon in the system tray. If the workstation is currently running a migration, the Finish and Exit selection allows the migration to complete and report its status before shutting down the worker application. The Exit Now option disconnects the worker application. If a migration is in progress, the status is not updated on the server.

 

 

Upgrading a Migration Farm

Perform the following steps to upgrade your existing farm.

  1. Run an in-place upgrade on the controller by clicking the "Notes Migrator Setup XX.XX. This will upgrade the controller machine. Ensure that there are no migrations running during this process.


Make sure to make a backup copy of your Notes Migrator SQL database. This can be done through the SQL Management Studio by right clicking the database and selecting Tasks | Backup.

  1. Make a design template of the "Notes Migrator.nsf" which will be located in C:\Program Files\Binary Tree\CMT for Exchange\Notes Tools after the upgrade.  This can be accomplished by:

    1. Double clicking on the Notes Migrator.nsf file located in the C:\Program Files\Binary Tree\CMT for Exchange\Notes Tools on the controller machine.

    2. This will load the notes client and open the database on the controller.  From the Notes client menu choose File/Application/New copy.  The file copy dialog window will open.  Make a copy of the database giving it a "NTF" extension instead of a "NSF"extension.

    3. Open your Notes Migrator database on your domino server.  With the file open, choose from the Notes client menu, File/Application/Design Replace.  The design template dialog will open, choose your newly created template from the list of templates and hit ok.

    4. Sign the Notes Migrator database with your current Notes ID, this on the Progress Summary page.


Make sure to make a backup copy of your Notes Migrator database on the domino server for safety purposes. This can be a Notes copy of the .nsf database to the Local Notes workstation.

  1. The workers will automatically upgrade.  The workers check in with the controller and when the worker finds it’s at a lower release then the controller, it will automatically upgrade itself by automatically running the Notes Migrator Worker XX.XX MSI.


The existing status for all migration accounts will be retained including the migration system licensing.

 

Upgrading from 4.6.X

The process is the same as above except step 3.  You must manually run the Notes Migrator Worker XX.XX.msi on all workers to upgrade to the latest software.

 

Upgrading from 3.8x, 4.0, 4.5

For these releases,  the worker software will need to be completely removed first, along with uninstalling the controller as well.

  1. Uninstall all the workers by going to each worker and running the uninstall program from the control panel.  This will remove the worker installation and unregister the workers from the controller.

  2. Uninstall the Notes Migrator program the control panel on the controller.  This will remove all the software from the controller machine.   Run the Notes Migrator Setup XX.XX on the controller machine.

 

How many migration workstations can be added to a farm?

Why do I need to create a Migration Farm?

In a large enterprise where thousands of users need to be migrated, using a single Migration Workstation can’t serve the purpose. Like all Binary Tree’s CMT products, Notes Migrator provides a feature that allows you to migrate many users using parallel processing.

Parallel processing is defined as the ability to execute multiple simultaneous migrations using multiple Migration Workstations.

To achieve true parallel processing, the first step is to create a migration farm. Notes Migrator can be easily configured to create a migration farm by configuring a Migration Control Center and multiple Migration Workstations. These workstations can be located, provisioned, managed, and monitored anywhere in the world.

Manual versus Automated Workload Distribution

In a typical set up, Notes Migrator distributes migration load among multiple Migration Workstations that are located at multiple location and communicating with the one Migration Control Center. But if the large enterprise is spread over multiple regions/sites, Notes Migrator can also be configured such that you can run migrations independently at each site to keep migration localized.

Workload can be distributed from the Migration Control Center to Migration Workstations in two ways:

Manual

This type of workload distribution enables migration administrators to fully control time and workstation for each user’s migration.

Automated (Automated Workload Distribution (AWD))

This type of workload distribution ensures continuous migration execution among a group of workstations.

Up to 140 workstations can be added to a farm before an additional farm must be created.

What are the prerequisites for migration workstations?

The most critical prerequisite is that Notes Migrator, the Lotus Notes Client, and the Microsoft Outlook client must already be installed on each migration workstation. Refer to the Notes Migrator Requirements document form more details.

Additional migration workstations should be configured as recommended for Notes Migrator. The workstation must have the following:

  1. Notes client installed. You will also need a Notes user ID that has permission to access the servers and mailboxes you want to migrate. Open a database on each server you will be accessing and verify that you have a valid certificate for the server.

  2. Outlook client installed.

  3. ALL updates and service packs for Windows and Office.


Coordinated Universal Time (UTC) is not supported as a time zone for the migration controller and workstations.

 

How do I create a migration farm?

Installing a Migration Workstation

Installation of the migration worker can be done via two methods, via GPO MSI installer or through the CMTMonitor web page.

Installing via the CMTMonitor

  1. On one of designated Migration Workstations, (not the Migration Control Center), launch Internet Explorer and go to the Migration Control Center/CMTMonitor website.

  1. Click the Install Workstation Software link and then Run

  1. Click Next on the Welcome screen

  1. Enter the Notes Migrator server name, workstation name, and workstation address and click Next.

  1. Entering user account information is optional on this screen. In smaller farm scenarios, you can continue to use the Migration Administrator account distributed by the MCC. If you wish to use another Migration Administrator account, enter the information in this screen.

This information is encrypted and cached on the Worker.

 


This account can be changed on the Migration Workstation through the Connectivity Tester application.

 

  1. Click Install

  1. Click Finish

  1. The Exchange Connectivity Tester will launch with the information you entered in the installer. Press the Test button to verify the account credentials can connect to Exchange.

IMPORTANT: If the cached password is incorrect, a Windows Security dialog will be displayed. It is critical that you press Cancel and allow the test to fail. Entering the correct password in the Windows Security popup will allow the test to pass but will not change the cached credential information.

 


This is not required if Modern Authentication is used for the migration worker connections and the Migrate Outlook profile has been configured.

Enter a new password and press Test again.

When the account information is correct and verified, the Save button will be enabled to allow you to update the information cached on this Worker.

  1. Press OK to exit the application.

Changing the Cached Account

The Exchange Connectivity Tester is added as a desktop shortcut and to the Start menu on the Worker. You can launch the application to change the cached account information in the Worker.

 

Note that the Save button will only be enabled after a successful test, and the credential information is different than the credentials that are cached in the Worker. Testing the existing cached account will not enable the Save button.

Deploying via MSI file

For automated deployment, send a command line with the following arguments:

  • SERVICEURL The FQDN or IP Address of the CMT_XMLServer. Normally, this is the same machine where the MCC is installed.

  • EXCREDDIALOG_EMAIL: The SMTP address of a MAPI Migration Administrator account.

  • EXCREDDIALOG_UPN: The “User Principal Name” of the MAPI Migration Administrator account. NETBIOS format (domain\user) is not supported.

  • EXCREDDIALOG_PASSWORD: The password for the MAPI Migration Administrator account.

Example:

msiexec /i “CMTeWorker.msi” SERVICEURL=”mcchost.org.dom” EXCREDDIALOG_EMAIL=migadmin@org.dom EXCREDDIALOG_UPN=migadmin@org.dom EXCREDDIALOG_PASSWORD=”Migration admin password” /qn


The “EXCREDDIALOG_xxx” arguments are not needed if you wish to continue using the account distributed by the MCC.


The .MSI installer does not check the workstation environment meets the minimum requirements, and does not install the missing components needed for a successful migration.

Monitoring the Website

The monitor can be accessed from any machine on the LAN to observe the status of the workstations. The workstation named local is the migration engine installed on the Migration Control Center machine.


The Internet Information Server (IIS) included with Windows Client Operating Systems has a 10-connection limit. The additional workstations periodically connect to the master machines IIS to get work and report status, effectively tying up one connection per workstation. Connecting to the monitor website also consumes one connection. If you exceed 10 connections, then the extra workstations may not work correctly. Install the Notes Migrator software on Windows Server operating system if you need more than 10 simultaneous connections.

 

The Machine info page displays an overview of the migration workstations status and performance.

The Migration info page displays what each workstation is currently doing

The Monitor website is refreshed approximately every 30 seconds. Throughput figures are calculated after a migration is completed.

To manage the worker application on any machine, right-click the respective icon in the system tray. If the workstation is currently running a migration, the Finish and Exit selection allows the migration to complete and report its status before shutting down the worker application. The Exit Now option disconnects the worker application. If a migration is in progress, the status is not updated on the server.

 

 

Upgrading a Migration Farm

Perform the following steps to upgrade your existing farm.

  1. Run an in-place upgrade on the controller by clicking the "Notes Migrator Setup XX.XX. This will upgrade the controller machine. Ensure that there are no migrations running during this process.


Make sure to make a backup copy of your Notes Migrator SQL database. This can be done through the SQL Management Studio by right clicking the database and selecting Tasks | Backup.

  1. Make a design template of the "Notes Migrator.nsf" which will be located in C:\Program Files\Binary Tree\CMT for Exchange\Notes Tools after the upgrade.  This can be accomplished by:

    1. Double clicking on the Notes Migrator.nsf file located in the C:\Program Files\Binary Tree\CMT for Exchange\Notes Tools on the controller machine.

    2. This will load the notes client and open the database on the controller.  From the Notes client menu choose File/Application/New copy.  The file copy dialog window will open.  Make a copy of the database giving it a "NTF" extension instead of a "NSF"extension.

    3. Open your Notes Migrator database on your domino server.  With the file open, choose from the Notes client menu, File/Application/Design Replace.  The design template dialog will open, choose your newly created template from the list of templates and hit ok.

    4. Sign the Notes Migrator database with your current Notes ID, this on the Progress Summary page.


Make sure to make a backup copy of your Notes Migrator database on the domino server for safety purposes. This can be a Notes copy of the .nsf database to the Local Notes workstation.

  1. The workers will automatically upgrade.  The workers check in with the controller and when the worker finds it’s at a lower release then the controller, it will automatically upgrade itself by automatically running the Notes Migrator Worker XX.XX MSI.


The existing status for all migration accounts will be retained including the migration system licensing.

 

Upgrading from 4.6.X

The process is the same as above except step 3.  You must manually run the Notes Migrator Worker XX.XX.msi on all workers to upgrade to the latest software.

 

Upgrading from 3.8x, 4.0, 4.5

For these releases,  the worker software will need to be completely removed first, along with uninstalling the controller as well.

  1. Uninstall all the workers by going to each worker and running the uninstall program from the control panel.  This will remove the worker installation and unregister the workers from the controller.

  2. Uninstall the Notes Migrator program the control panel on the controller.  This will remove all the software from the controller machine.   Run the Notes Migrator Setup XX.XX on the controller machine.

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating