Lotus Notes Accounts
-
Migration accounts created in the customer environment
-
Editor rights to the Domino Directory with the ‘User Modifier’ role; this will be used for the following actions:
-
Import users
-
Perform Routing Flips
-
-
Manager rights to all HCL Notes mailboxes being migrated; the following actions require rights:
-
Audit the mail files
-
Send COMM’s for decrypt and contact sync (when they need to be deposited directory in the mail file)
-
Create staging replicas
-
Replica Audit
-
Contact and group fix
-
If using Rich COEX, update the BTCache Database on the BT Notes Integration server
-
Sync Read/unread marks
-
Set Reader access
-
-
|
|
|
-
Rights to issue Domino server commands on mail servers
-
Issue a command to initiate a PUSH replication command for individual databases.
-
Appendix B: Office 365 Modern Authentication
This section outlines the additional requirements for the use of Microsoft Office 365 / Microsoft 365 Modern Authentication for the Migration Controller and Migration Workers. These are only needed if Modern Authentication is to be used for PowerShell and Outlook connections to the target system.
The target tenant does require Modern Authentication to be enabled to use this migration processing.
|
|
|
Migration Controller Requirements
-
PowerShell 5.1 (part of Windows Management Framework 5.1)
-
.Net 4.7.1
-
WinRM basic authentication allowed
-
TLS 1.2 enabled for .Net Framework
-
ExchangeOnline PowerShell Module
-
MSOnline PowerShell Module
Migration Worker Requirements
-
Outlook 2016 or Outlook 2019 (Outlook 2013 is not supported for migrations with Modern Authentication)
-
Windows Server 2012 R2, Windows Server 2016, Windows Server 2019 or Windows 10
-
Outlook profile configured for the worker migration account and named Migrate
|
|
|
Migration Controller Requirements
This section outlines the additional requirements for the use of Microsoft Office 365 / Microsoft 365 Modern Authentication for the Migration Controller and Migration Workers. These are only needed if Modern Authentication is to be used for PowerShell and Outlook connections to the target system.
The target tenant does require Modern Authentication to be enabled to use this migration processing.
|
|
|
-
PowerShell 5.1 (part of Windows Management Framework 5.1)
-
.Net 4.7.1
-
WinRM basic authentication allowed
-
TLS 1.2 enabled for .Net Framework
-
ExchangeOnline PowerShell Module
-
MSOnline PowerShell Module
Migration Worker Requirements
-
Outlook 2016 or Outlook 2019 (Outlook 2013 is not supported for migrations with Modern Authentication)
-
Windows Server 2012 R2, Windows Server 2016, Windows Server 2019 or Windows 10
-
Outlook profile configured for the worker migration account and named Migrate
|
|
|
Migration Worker Requirements
This section outlines the additional requirements for the use of Microsoft Office 365 / Microsoft 365 Modern Authentication for the Migration Controller and Migration Workers. These are only needed if Modern Authentication is to be used for PowerShell and Outlook connections to the target system.
The target tenant does require Modern Authentication to be enabled to use this migration processing.
|
|
|
Migration Controller Requirements
-
PowerShell 5.1 (part of Windows Management Framework 5.1)
-
.Net 4.7.1
-
WinRM basic authentication allowed
-
TLS 1.2 enabled for .Net Framework
-
ExchangeOnline PowerShell Module
-
MSOnline PowerShell Module
-
Outlook 2016 or Outlook 2019 (Outlook 2013 is not supported for migrations with Modern Authentication)
-
Windows Server 2012 R2, Windows Server 2016, Windows Server 2019 or Windows 10
-
Outlook profile configured for the worker migration account and named Migrate
|
|
|