Migration Controller
Additional Procedures
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
-
Install-Module -Name MSOnline
-
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.
|
|
|
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
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.
Migration Worker
Additional Procedures
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
-
Install-Module -Name MSOnline
-
Enable WinRM Basic Authentication:
-
Launch Command Prompt as an administrator. At the prompt, type:
-
winrm set winrm/config/client/auth @{Basic="true"}
-
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.
|
|
|
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
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.
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.