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

4.1. Configuring Required Settings

Migrator for Notes collects and manages the settings essential in performing a successful migration. These settings are located under Configuration in the Navigation Pane.


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 Migrator for Notes User Guide for Office 365 Migrations for additional information.

Domino Settings

The Migrator for Notes Settings document displays. In the Settings document, the Required Settings -> Domino tab displays by default.


You can view the description of each field in each tab by clicking its corresponding question mark icon . For example, click and hold the mouse pointer on the question mark icon next to the Mail Server field to read its description.

Before any migration can be performed, the Required Settings tab must be completed. Two of the most important entries in this tab are the Mail Server and the Domino Directory. The specified Mail Server name is used to access the Domino Directory. The Domino Directory is used to retrieve the information required to import and create the User Mail, Rooms & Resources Databases, Mail-in Databases, and Discussion & Document Library Databases control documents.

These control documents are critical to the migration process and in their absence, migration information cannot be collected for a given item, and therefore, the item cannot be migrated. The control documents are used extensively during the remaining migration processes.

The following table describes the values for each setting.

Settings    

Description

Mail Server

The Domino server that Migrator for Notes will use for importing users and for sending Migration Messages.

Domino Directory

The Domino Directory name that Migrator for Notes will use for importing users, as found on the Domino server. Up to five additional Domino directories can be set by checking the box.

Server Mailbox

The mailbox filename that Migrator for Notes uses for sending Migration-related messages to selected users (for example, mail.box).

Audit Domino Encrypted Items

When running Audit on user mail file, specifying Yes will check for encrypted items in the mail file. If encrypted items are found, you can either send the user an email message with a button that decrypts encrypted items so that they can be migrated, or you can send the user a message with document links to the encrypted items so that they can print them prior to migration. You can even do both if you have some reason to want a list of messages that had been encrypted before the decryption agent was run.

Audit Domino Mail Rules

When running Audit on user mail file, specifying Yes will check for the number of rules in the mail file. If rules are found, you can send users a list of their Rules that will help them in creating the rules in Outlook after migration.

Audit Exchange Migrated Data

Enables auditing of migrated data in Exchange. Exchange Auditing should be enabled before data is migrated. Audit reports can be found the \logs directory on the migration workstation(s).

This is a post-migration validation process that indicates the state of documents which have been migrated by Migrator for Notes. This feature can be useful in environments as a validation check for data integrity. In addition, this can be used to audit results to reduce the size of user Domino mail files or archive databases after the migration phase on the Domino servers and user's workstation replicas. For example, removing documents with a Migration Status of 1 would leave only non-migrated data or documents that could not be migrated completely due to malformation or size restrictions in Exchange from a source database.  

Important: Consult your organizations data retention policies and regulatory compliance requirements before modifying source data. Full backups of the original source data may be required (and maintained post migration) before modifying working replicas to ensure regulatory compliance.

Audit embedded eml attachments

Enables auditing of eml attachments inside the message bodies to assist with migration troubleshooting. Results will be reported on the user document in EMM. This is not required for migration processing unless directed to enable this by Binary Tree's Product Support.

Additionally, a flag can be enabled and adds the field BTFoundEML to documents in source mail files where auditing finds eml attachments inside the message bodies.

Audit calendar unsupported patterns

Enables auditing of calendar items where the user is the Chair for Notes custom repeating meetings and generates document links for meetings that are not supported by Outlook. This will use the Migration Date if set or the current date and include meetings from the date specified and future meetings. The audit adds the reported data to the Calendar audit RTF report for the account and can be sent to end users with the Remediation Summary Message Template.

If enabled the audit can be specified to verify meetings where the user is the Chair, an Invitee or both. Additionally, label text can be added to the reported data to specify if the user is the Chair or the Invitee.

User Notification Style

Individual Notifications: Select if you want to send individual notification to each user and each mail/form will only have script for one action.

 

Combined Notifications: Select if you want to send one migration notification to each user and the notification/message to contain multiple selected forms, such as decrypting encrypted messages and synchronizing contacts and journals with mail file.

Enable this CMT db for Notifications

Click this button to create a Mail-In database document on the Domino Server for the Migrator for Notes database, and enable the database to receive User Notification responses. This database must be hosted on a Domino server.

 

Mail-enabling Migrator for Notes Database

A Mail-in Database Document is required for mail to be delivered to the newly created server copy of the Migrator for Notes database. The procedure copies the database to the server and creates a Mail-In database document for the Migrator for Notes database.

  1. Create a mail-in database for Migrator for Notes database. Click on the Server Db Copy and Mail-In Db Doc button to create a copy of the Migrator for Notes database on the Domino server and configure the Mail in Database document

  1. The Does Migrator for Notes already exist? dialog box opens; click Yes (and skip to step 5):

  1. If you are working with a local copy of the Migrator for Notes database, then click No. The Create a db copy? dialog box opens.

  2. Click Yes to create a copy of the local Migrator for Notes database on the server:

  1. If you clicked Yes in the Does Migrator for Notes CMT already exist? dialog box, the Choose Application dialog box opens. Locate the Migrator for Notes database in the CMT folder on the server, and then click Open.

The Fullname for the mail-in db doc dialog box confirms that the mail-in database for the selected server-based Migrator for Notes database does not exist, and prompts you to specify a name for the mail-in database. After specifying the name, click OK.

 

  1. In the Open the new mail-in doc? dialog box, click Yes to open the mail-in database.

The mail-in database document for Migrator for Notes opens.

  1. To verify the creation of the mail-in database, you can also launch Domino Administrator, open the Domino server, and access the Mail-In Databases and Resources folder under the People & Groups tab:

  1. Double-click the document to open and review

  2. Once the mail-in database is successfully created, the Open Mail-In Db Doc button replaces the Server Db Copy and Mail-In Db Doc button. Clicking it opens the database document for a review. Clicking the button with the X sign on it will remove all pointers to the location of the mail-in database.

    

 


The Notes ID that is used to sign the Notes Migrator database must have rights to add a new Mail-In Database Document to the server Domino directory. If the following error message is displayed, the Notes ID does not have appropriate rights.

Wor154

If you do not have the appropriate access rights to perform this action, see the onsite Domino System Administrator for help.

 

  1. It is recommended that after copying the database to the server, you delete the database from the local client folder. To remove it, right-click on Notes Migrator on Local. Select Database, and then Delete. The Lotus Notes client prompts that the database and related documents will be permanently deleted. Click Yes to delete the local database.

Modifying the Inbound Processing Agent

Once you have mail-enabled the database, you need to modify the Inbound Processing agent to view the updates. Perform the following steps to run the agent.

  1. Install Domino Designer on the workstation where Notes Migrator Domino database is located

  2. Launch Notes Migrator Domino database in Domino Designer

  3. Expand Shared Code and select Agents

  4. Select the InboundProcessing agent as shown below:

  1. Double-click InboundProcessing to open the InboundProcessing Agent Properties

  2. Click the Security tab

  3. The Administrator should be listed in the Run on behalf of section

  4. In the Set Runtime security level: field, select Allow Restricted Operations with full administration rights

  5. Once you've edited the agent, close the Properties box

  6. Close the Inbound Processing – Agent tab

  7. Save the changes

  8. Click Sign


This agent runs before new mail arrives and the Domino router must be set to allow these types of agents to run. To enable this option, go to Router/SMTP -> Restrictions and Controls -> Delivery Controls tab and set the Pre-delivery agents option to Enabled.


The Notes ID that signs this agent does require security rights on the Domino server to run agents.

 

LDAP Settings

  1. Click LDAP under the Required Settings tab:

In this tab, specify the Active Directory information to resolve users by matching them between source and destination platforms via Lightweight Directory Access Protocol (LDAP). To use this option, specify the required details.


LDAP configuration is not specifically required for Office 365 only migrations.

Use the following table to enter the correct values for each field:

Settings    

Description

Domain

The common name of the Active Directory domain. For example, binarytree rather than binarytree.com.

LDAP IP Address or Host Name

The fully qualified LDAP server name, IP Address, or resolvable DNS name of the Active Directory server. (e.g. PC-XP-01. binarytree.com or 192.163.15.12).

LDAP Port

Specify the LDAP port.

The default port for LDAP is 389.

The default port for SSL LDAP is 636.

Login ID

The AD domain account that has read rights to the target AD domain.

For example: administrator and not <domain>\administrator

Password

The password associated with the ID specified in Login ID.

Validate Settings

Click to validate the specified values to ensure that you are able to connect to the domain in Exchange where the end users will be eventually migrated.

LDAP Directory Base (Base DN)

If LDAP settings result in a successful connection, then this field is automatically updated.

Specify the directory base for all LDAP queries. The query settings will enable the search in AD to ensure that users are getting resolved against the right container ‘directory’ within AD.

Example: DC=btexchange2k7,DC=com

Quick Check

Full Check

If you want to search only the first ten users, select Quick Check; and if you want to search all the users, select Full Check.

Validate Query Settings

Click to validate the values specified in LDAP Directory Base to ensure that query string is resolving users and returning the number of resolved users.

 

  1. Specify the connection settings and then validate them by clicking the Validate Settings button:

  1. The LDAP Connection Settings Test Results message box displays indicating that the settings were validated and the connection was successful; click OK:

  1. Notice that the LDAP Directory Base (Base DN) field is automatically populated

To ensure that the specified directory base, where all LDAP searches will be conducted, is correct; you should validate this setting as well; click the Validate Query Settings button:

  1. The LDAP Query User Settings Test Results message box displays; the query setting is validated and some records are returned; in a production environment, ten records should be returned always; click OK:

Additional Settings

  1. Click the Additional tab under Required Settings

 

  1. Configure these settings with the names of the views to locate and import User and Mail-in Databases information. Also, specify the Migration Status Codes that can be assigned to users’ mail and databases control documents. You can assign a code to a user to update its status and view users based on their status codes. This helps in providing a better picture of the migration progress.

The following table describes the values for each setting:

Settings    

Description

CMT Migration Server

Specify the network hostname or IP address of the machine that is running the migration server.

CMT Program Directory

Specify the complete program directory path to Notes Migrator installation. This location will be used to launch the migration engine when the migration is triggered off.

 

Note: During the installation of Notes Migrator, if you had specified a destination folder path other than the default (C:\Program Files\Binary Tree\CMT Exchange), then you must replace the default path specified in the CMT Program Directory field with the modified path. In failing to do so, the migration engine will not launch when the migrations are set to go off.

Use Secure Web Services

Specify whether the web service calls are made to an XML server configured for secure access. Note that additional steps are required to secure the web services. The default selection is “Yes” which uses the CMT eService COM object to access the XML server.

 

Refer to Appendix E: Securing Notes Migrator Web Services with Windows Authentication for additional steps if you select Yes.

I have multiple control Centers

This option appears if the multiple Migration Control Center advanced feature is enabled on the Other Setting tab. Check this option to define the IP addresses of the Control Centers.  When enabled, the Set Migration Status options include Set Migration MCC and Clear Migration MCC options.

Migration Server Control Center IPs

Appears if “I have multiple control Centers” is checked. This field is used by the Set Migration Status agent.

Values must be entered as follows:

Workstation#=IP address of Notes Migrator Control Center

For example:

1=192.168.1.0

2=192.168.1.1

3=192.168.1.2

User Import View

Specify the view in the Domino directory that Notes Migrator database will use for importing users. Use the People view unless there is a custom view that you have created.

Mail-In Databases Import View

Specify the view in the Domino directory that Notes Migrator database will use for importing mail-in databases and resources. Use the Mail-In Databases view unless there is a custom view that you have created.

Mail-In Databases View Category

This is the NAB Mail-In database view category used for importing Mail-in Databases and Resources. Use the “Databases” default unless Domino is using a language other than English. Change this value to what is displayed in the NAB Mail-in Databases view.

Migration Status Codes

Specify a personalized list of status codes that will be used during the migration project. These codes can be assigned to users’ mail and databases control documents. If these status codes are assigned during the different phases of the migration process, timely status reports can be produced. These status reports will help provide a better picture of the migration progress. With this type of information, you have more control over the migration project and can react quickly to any identified issue. Adjustments can be made to help fine tune the migration schedule by adding more or different resources. Status codes must be separated by a new line. A list of status codes has been specified for you. You can either retain or change these status codes depending on your need.

CAS Server

Specify the Exchange Client Access Server (CAS) name. If a name is specified, then the matching process will use the following URL to resolve users. https://[servername]/autodiscover/autodiscover.xml

 

However, if you have specified the full URL to the Autodiscover service, then the URL will be used to resolve users.

 

This field is required for delegation migrations.

Username

If only the CAS Server name or IP address is specified in the CAS Server field, then you must specify a valid username for the authentication process that takes place on the CAS server. Note that the username should be in the following format for on-premises Exchange: <domain>\<username>. For Office 365 the format should be username@domain.com.

 

If you have specified a full URL (with https://) in the CAS Server field, then you can leave this field blank for on-premise migrations.

Password

Specify the password associated with the username provided in the previous field.

 

If you specified a full URL (with https://), then you can leave this field blank for on-premise migrations.

Powershell Admin Credentials

For on-premise Exchange servers, the credentials are of the form [Domain]\[Username].

For Office 365, the credentials are the SMTP address used to pass credentials to Office365 for remote access, for example o365Admin@tenant.onmicrosoft.com

Powershell Admin Password

Appears if Office 365 is in use

Use the Set PowerShell Password button to update this field. This will request the password and record it using the AsSecure PowerShell method.

This is not required for clicking the Notes Migrator PowerShell buttons, if this is not entered the buttons (such as Set Full Acccess) will ask for the password when processed.

PowerShell Logging Path

The MS PowerShell used when generating, executing, and logging PS1 script. This path can be edited on User Provisioning tab.

Default Reporting Path for Matching

Specify the reporting path used by the matching process. The default path is C:\Matching\.

Enable PowerShell Modern Auth

Appears if Office 365 is in use

Set to Yes to enable the use of the Exchange Online module for PowerShell processing. This will use Modern Auth connectivity to Microsoft Online services, removing the Basic Auth connection processing.

Enable Modern Auth for Migration

Appears if Office 365 is in use

Set to Yes to enable the use of Modern Authentication for Migrations. The Office 365 tenant must be configured to use Modern Authentication.

Autodiscover Username

Autodiscover credentials to be used during creation of the profile used by the migration engine.

For on-premise Exchange servers, the credentials entered should be the UPN (User Principal Name), for example: UserName@Example.Microsoft.com

For Office 365, the credentials are the SMTP address of an account in the Office 365 domain, for example: o365Admin@tenant.onmicrosoft.com.

 

Note: This is used if a migration worker does not have an account specified and is a fall back option. This is not required if a migration farm is being built using AWD.

Autodiscover Password

Enter the password associated with the Autodiscover account entered above.

Customer Name

Specify the Customer name that you would like in the status report.

Send Customer Status Report To

Specify the Group Name or SMTP addresses of the persons that should receive the status report.

Send Operator Status Report To

Specify the Group Name or SMTP addresses of the persons that should receive the full status report.

Migration Status Report Path

Specify the working path for migration status reports.

Create a combined report for multiple Migration Management databases (up to 5 additional)

Check this option to specify up to five additional migration management databases to include in a combined report.

 

4.2. Configuring Email Repliability

Click the Email Repliability tab to specify the appropriate values for the Domino environment:

Refer to the table given below for a brief description of all the settings in the Email Repliability tab.

Settings    

Description

Past and Present Domino Domains

The Domino domain names that are stripped from the email addresses and result in a valid and reply-able address regardless of domain name changes over the years. Enter a comma-separated list of all domain names in Domino, including the Notes Integration domain – no @ character is necessary.

Note: These are Domino domains, not SMTP or Internet domains, so it would more likely be ACME or ACME-NOTES, rather than acme.com.

Last Name Translation Update

This field is automatically populated during the Name Translation Update Process. This value will indicate the last time the Domino Directory was searched for updates.

Name Translation Database

The Name Translation Database field allows you to browse for the primary database to use for Name Translation lookups. This would typically be the current Notes Migrator.nsf. A warning will appear if you attempt to save the configuration without defining the Name Translation Database.

Name Translation Failover

The Name Translation Failover field allows you to optionally set the path to the primary failover database used for Name Translation lookups. The failover database is used if the primary database is inaccessible. This database should reside on the Domino server.  If a local (workspace) path is used, the EMM database must be replicated to the same relative path on all workstations.

Powershell bulk matching batch size

When using the two-step bulk PowerShell matching process for address translation entries, this is the number of records that will be presented in each matching .csv file. The default value is “2000”.

Note: this option is only available to Exchange on-premise migrations.

Table

The Name Translation Database table allows you to set the Name Translation Databases and Name Translation Failover Databases on multiple workstations. Click Set selected to define a Name Translation Database and Name Translation Failover for the selected workstation to use instead of the primary (default) databases defined above.

 

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: 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.

 

 

 

Lotus Notes Migration ID

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.

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.

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.

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 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:

4.7. Configuring Rooms & Resources Settings

  1. Click Rooms & Resources; this tab has two sections. Review the general description provided for both the sections.

Rooms & Resource Migration Options

The Rooms & Resource Migration Options section enables you to configure settings to determine how resources are handled during a migration:

The following table describes the values for each setting:

Settings    

Description

Rooms and Resources Target

Specify if you want the room or the resource to be migrated to a Location field, or be appended to the message body, both, or none.

Room Label

Specify the label you wish to be prefixed to the migrated room text.

Resource Label

Specify the label you wish to be prefixed to the migrated resource text.

Online Label

Specify the label you wish to be prefixed to the migrated online text.

Location Detail Indicator

Specify the text you wish to appear when room or resource text is not included in the Location field.

Room Resource Separator

Specify a string that separates the location, room, resource, or online values that are included on the Location field.

 

Rooms & Resource Settings

Configure these settings if you want to migrate Rooms and Resources. The first step of the process involves importing Rooms and Resources into the Notes Migrator database. Lotus Notes stores multiple Rooms/Resources in a single database. Notes Migrator allows you to import and create a separate .nsf for selected Room/Resource and copy its corresponding calendar into the newly created .nsf. Once all the Rooms/Resources that you want to migrate have been separately imported, you can export them to Notes Migrator migration engine and migrate them.

The following table describes the correct values for each setting.

Settings    

Description

Rooms and Resources Import View

Specify the view in the Domino directory that Notes Migrator will use for importing the different Rooms and Resources. Use the Rooms Resources view unless there is a custom view that you have created.

Target Server

Specify the Domino server that Notes Migrator will use when creating separate .nsfs for each Room/Resource. This must not be blank.

Target Path

Specify the destination path where separate .nsfs will be created for selected Rooms/Resources.

 

The path is relative if the destination is a Domino server. If the destination is a file server, full path must be specified.

Database Template

Specify the template that will be used to create the new room or resource database to migrate.

Set Subject to Chair

Set this to ‘Yes’ to enable overwriting the booking subject when importing rooms and resources. This will set the subject to the booking Chair for migration to Outlook (removing the booking subject entirely). This does not impact the existing Notes room and resource bookings. Selecting ‘No’ will retain the original booking subject for migration.

Subject Prefix

This is used if the subject for imported booking will be overwritten with the booking Chair name. The text used will be prefixed in the imported booking subject.

4.8. Configuring Replica Settings

The Replica Settings are used when using a Domino staging server. A staging server is often used when the Domino mail servers are not on the same LAN as Exchange and/or the migration environment to mitigate migration throughput degradation due to the network. Staging servers are also used if you will be using replication formulas to filter the data intended for migration.

The following table describes the values for each setting:

Settings    

Description

Staging Server(s)

The Name of each of the staging servers to be used for creating replicas separated by a new line or a comma.  For Example: Stage01/Contoso

Staging Server File Folder

The folder name in which to place the newly created replicas.

Replication Formula Option

Specify My Own Formula: Use the field below to specify your own selection formula.  Be sure to enter the ENTIRE formula, starting with SELECT (e.g. SELECT @All to replicate all Notes items).

 

Build Formula Via Selections: The number of calendar and email days and select the forms to include in the replica and a replication formula will be built for you.

Replication Formula

If you are specifying your own replication formula, enter it here.

*Note: You must be familiar with Notes formula language.

Number of Calendar Days

If you selected Build Formula Via Selections enter the number of calendar days to include in the replica. You will be prompted for a date upon replica creation and it will use this date and the number you specify to calculate the number of calendar days to include.

Number of Email Days

If you selected Build Formula Via Selections enter the number of email days to include in the replica. You will be prompted for a date upon replica creation and it will use this date and the number you specify to calculate the number of email days to include.

Forms to include in Replica

Select or enter all of the different forms to be included in the replication formula.  If the form name is not listed here, it will NOT be included in the replication formula and will not be in the replica.

Replicate Each Replica at Creation

Selecting “Yes” will replicate each newly created replica as it is created. It will also cause the agent to run very slowly depending on the replica settings. It is recommended to use this as a one-off replica creation rather than for the entire list of users/mail-in databases.

Exclude Trash from Replica Comparison

Set to Yes to exclude Trash (Soft Deletion) document counts from the replica comparison total document counts. Set to No for default processing to count all documents.

4.9.    Configuring Delegation

  1. Click the Delegation tab.

  2. Validate Yes is selected for the Audit Delegates option. If set to No, set to Yes and save and close the document, then reopen the document to view the other configuration settings.

  1. The PowerShell application impersonation set option is a prompt to set application impersonation. Set application impersonation using the steps below and then set this option to Yes.

    1. Open the Exchange Management Shell or configure a PowerShell session to connect to either an on-premise or the appropriate Office365 server.

    2. In the shell, enter the following command to configure application impersonation:

New-ManagementRoleAssignment –Name:impersonationAssignmentName –Role:ApplicationImpersonation –User:CMTMigrationAdmin@myDomain.org

Where CMTMigrationAdmin@myDomain.org is the SMTP or login name of the migration account, or the name of security-enabled group used for migration.

  1. To run delegation migrations as a scheduled process, set Run delegation as a scheduled process to Yes (default).

  2. Click the Enable scheduled agent button and select the Domino server that will perform the migration. The agent will run in the background of the local Notes client if the Local option is selected.

Scheduled delegation migration runs in the background on a workstation or server. If running locally, Notes must be running and background agents must be enabled on the client.

The scheduled delegation migration agent runs once a day at 3:00 AM.  Note that if the agent is changed to run at a time interval that is too short, the PowerShell tasks may not have time to complete.

  1. Click the Delegate Settings tab:

  1. After auditing the user's mail files with Active Delegation enabled, you are able to send an email that displays the user's current delegation settings, so they can decide whether they are still valid for migration to Outlook. You should allow the users a period of time to review before rerunning the mail file audit to collect any updated settings.

The options below allow you to customize the message to exclude certain users and groups that delegation does not need to be reported to the users about. Typical exclusions are standard Administrative groups or administrative IDs that are by default listed in the HCL Domino Mail files within the environment.

4.10. Configuring Source Updates

The Source Updates Settings are used to configure the Fix Folders agent.

 

The following table describes the values for each setting.

Settings    

Description

Replace Blank Folder Names With

The folder name to be used when updating Blank folder names. This will update blank (Null) folders at the folder root, blank folders within the folder hierarchy and blank folders at the end of the folder hierarchy. This will numerically increment (1, 2, 3, etc.) if more than one blank folder exists. Replacements will be done for: "", " ", " \", "\ \","\\" "\ "

Append Personal System Folders With

The folder name to be appended to Outlook system folders that have been created at the folder root of the Notes personal folders. This will not update the Notes system folders. The folder names will be appended with a hyphen "-" and then the name to be used.

Check for Duplicate Folders Names

Option to check for duplicate personal folder names. If enabled, the agent will check each folder to determine if there is a duplicate and then append "-" and an incremented number to make the name unique.

Check Duplicate Folders on Remediation Only

Option to have the duplicate checks be performed on the first Fix Folders processing or only on second processing runs. This requires the option for duplicate checking to be enabled. Set to "No" to disable this and have the Fix Folders agent always check on the first pass for duplicates or set to "Yes" to have the duplicate checking skipped on the first pass and only be run on subsequent updates. This is enabled as the default configuration.

Maximum Duplicates Checks per Folder

Numeric setting for the number of duplicates to be checked on a single personal folder. If there are more duplicates of a single folder name than the number specified, the duplicate checking for that folder will be skipped. Requires duplicate checking to be enabled.

Remove Personal Folder Aliases

Option to remove hidden Alias from Notes Personal folders. This will remove all aliases in the Notes folders except for the system folders. This should only be used if an issue with an alias is found to cause a problem with migrations.

Email end users with Folder Renames

Option to send an email to the end users with a list of the folder names that were changed. The email will include the original folder names and the new folder names.

Enable Replacement of Specific Characters

If enabled, this will allow for a defined set of characters to be removed from all personal folder names and to have those replaced with a different character. This will not update system folders and should only be used if a specific character is found to cause an issue with migrations.

Replacement characters in

Personal Folders

This is a text list of characters to be replaced and should be a comma separated list if more than one character should be replaced. This requires the character replacement to be enabled and should not contain a backslash "\" as that will replace the Notes folder hierarchy or be Null (blank).

Character to be used for replacements

This should be a valid character that is not known to cause migration issues and should not be Null (blank). Typically, a hyphen "-" is recommended.

Remove obsolete local group members

This can be enabled to verify any local personal group membership (not system groups membership) and remove notes formatted (Canonical) membership addresses that are no longer in Domino (e.g. user accounts for leavers that were removed from Domino). The Email Repliability in Notes Migrator is used for these checks and should be populated prior to running the processing, if enabled. Note that these members cannot be automatically replaced once they are removed.

Rename local canonical group names

This can be enabled to validate local personal group names created by end users to check if these have a canonical (Domino) format (e.g. Personal Group/Local). If enabled, the processing will rename these by replacing the “/” with a “-“ to prevent Notes treating the local group name as canonical for migration.

 

4.11. Configuring Other Settings

Click the Other Settings tab to configure settings to control how encrypted items are handled or mail rules found in the user mail file. In this tab, the Migration Checklist and Advanced settings can also be configured:

The following table describes the values for each setting:

Settings    

Description

Send Rules Email

Configure these settings if you will be sending users their mailbox rules before migration.

From

Contains the profile name that will send the mail regarding mailbox rules to users. Migration Coordinator is specified as default.

Subject

Contains a subject that briefly describes the purpose of the mail. Your Mail Box Rules is specified as the subject by default.

Body

Can contain any information that you may want to share with the end user about this procedure.

Rules to Include

Includes all rules or only the rules that are enabled. Select All Rules.

Encrypted Items Migration

Choose how to migrate encrypted messages. Valid options are:

  • Require decryption action and migrate into the body

  • Migrate into a Notes database as an attachment

Note: Enabling the Migrate into a Notes database as an attachment option will increase the size of each migrated item containing encrypted content. The Lotus Notes client, original Notes ID, and decryption keys are required on the workstation used to view the encrypted content of the migrated items.

Send Encrypted Items Summary Email

Configure these settings if you will be emailing users a summary of their encrypted items.

The fields in this section display only when Require decryption action and migrate into the body option is selected.

From

Contains the profile name that will send users the mail with a summary of encrypted items. Migration Coordinator is specified as default.

Subject

Contains a subject that briefly describes the purpose of the mail. Your Encrypted Items is specified as the subject by default.

Body

Can contain any information that you may want to share with the end user about this procedure.

Template Name (.ntf)

This appears if you have selected Migrate into a Notes database as an attachment. Specify the template name in this format:  filename.ntf

 

EncryptedContent.ntf is the default template that ships with Notes Migrator. This template will be installed on every migration workstation during the product installation. This template will need to be signed with the appropriate Lotus Notes Administrative ID on all workstations. 

 

You can use any database template; however, you will need to manually distribute the template to all migration workstations.

 

Binary Tree recommends that use of an alternative template or any changes to EncryptedContent.ntf be thoroughly validated prior to production use.

Attachment name in Exchange

This field displays only when the Migrate into a Notes database as an attachment option is selected.  Specify the database name in this format:  filename.nsf

Text included with attachment

This field displays only when the Migrate into a Notes database as an attachment option is selected. Customized text can be added to the migrated item to provide end-user instructions or information. The default text is as follows:

 

Portions of this document were encrypted with Lotus Notes encryption. This content has been stored in the attached Lotus Notes database during migration to preserve security. You may view this content by opening the attached file on a workstation that has a Lotus Notes Client and the recipient’s Notes ID.

Migration Checklist

The Migration Checklist is a personalized list of tasks which can be used to help manage the migration project. Determine, then classify or group the major steps you consider necessary to manage your migration project. Determine the sequence, timeline, and description for each migration task and enter them into the Migration Checklist.

Enable Recovery

This setting defines the default value for the Enable Recovery setting in the migration profiles’ Advanced tab.

 

If the Enable Recovery setting is set to Yes in the Advanced tab of a migration profile, it enables tracking of processed messages during migration. So, if the migration process terminates unexpectedly, this feature prevents the application from reprocessing messages that were migrated during the initial run of the migration. Click here to learn more about configuring the Enable Recovery setting.

Disable MIME Cache

Specify Yes to disable the local cache database when processing messages using MIME.

Disabling this feature significantly impacts throughput when migrating MIME content from a Domino server.

Migrate Unfiled Documents

This option determines if “unfiled” documents will be migrated. “Unfiled documents are documents in Notes that do not appear in any folder and can only be accessed from the “All Documents” view within the mail file. Documents may be unfiled if a user deletes a folder without deleting the documents or removes a folder it resided within. The unfiled folder name can be defined.

MAPI Custom Settings

Select Specify advanced MAPI parameters to override the default values for MAPI retry count and MAPI retry delay.

When configured, retries are attempted when the MAPI_E_NETWORK_ERROR (0x80040115) result code is encountered during any of the following MAPI calls:

  • Create attachment

  • Create folder

  • Create message

  • Modify recipients

  • Save folder changes

  • Save message changes

  • Save attachment changes

 

If the configured retry limit is exceeded, the migration is cancelled and Notes Migrator will begin the migration of the next user. If the migration is canceled in the middle of writing a document, the document will be partially written to Exchange. The default retry limit is set to 30 seconds.

 

Specify the Number of retries that will be attempted when the MAPI_E_NETWORK_ERROR (0x80040115) result code is encountered. Values ranging from 1 to 999 can be entered. The default number of retries is “9”. Note that entering “0” results in the default “9” retries being used.

 

Specify the Delay between retries in seconds between MAPI calls. The time is progressive. The number of seconds delay for a call is (retry # * delay). For example, if the retry delay is set to 1 second, and the retry count is 5, the delays between calls will be 1, 2, 3, 4, and 5 (progressively longer). If the retry delay is 1.5 seconds, the times will be 1.5, 3.0, 4.5, 6, and 7.5. Values ranging from 1 to 999 can be entered. The default delay is “1” second. Note that entering “0” results in the default delay “1” second being used.

MAPI Retry Failure Limit

When enabled, Notes Migrator tracks documents where one or more MAPI calls could not be completed successfully. If the number of documents where one or more MAPI calls cannot be committed to Exchange, the migration will exit with ‘migration failed’ status.

 

The document retry failure limit feature can be disabled by setting the value to ‘0’ or leaving it blank.

 

MAPI Retry

Notes Migrator makes multiple MAPI calls when migrating a document, such as creating the message header, writing the body, adding attachments, etc. When processing messages, the remote Exchange server may become unresponsive in such a way that MAPI calls to write data do not complete. The call is retried a number of times (using the preexisting feature known as MAPI Retry: the maximum number and delay between retries can be set in EMM) to fully migrate data to Exchange.

 

If any of the MAPI calls cannot be completed, the document will be considered as failed due to MAPI retries, and added to the total of failed documents. Document information is logged, the NoteID is removed from both the in-memory migration history, and the CMTProcessedNoteID-[shortname].txt crash recovery file.

 

Note that other types of failures, such as a corrupt message body which results in a failure, are not counted toward the MAPI retry failure total. These other types of failures are specific to the source data, whereas the MAPI retry failures are related to the ability to write to exchange.

 

If the number of documents with MAPI retry errors exceeds the failure limit, the migration will exit, and return ‘Migration failed’ status. This migration will not automatically requeue and must be requeued by the migration administrator to fully migrate the mailbox. When a migration is requeued, it may be migrated by any workstation. Any documents containing MAPI retry errors on the failed migration will be remigrated during subsequent migrations.   

 

If the migration terminates abnormally (crashes), the document being migrated when the crash occurs will not be retried, which is standard procedure for crash recovery in Notes Migrator. Any other documents containing MAPI Retry Exceeded will be remigrated. In this case, Notes Migrator will automatically restart the migration on the same workstation.

Process attachments greater than

The limit for the size attachments, in MB, that will be detached and processed as file attachment objects. A value of -1 disables this feature, and processes all attachments as MIME streams, similar to Notes Migrator versions 4.6 and earlier. A value of 0 will process all attachments as file attachments. The default value is 0 MB to process all attachments outside the MIME Stream.

Encapsulate special content

When enabled, documents containing special notes functionality or items such as button or stored forms will be migrated as an attachment in addition to being rendered in the message body. End users can then open the NotesMessage.nsf attachment to use the native functionality of the form.

Migrate documents as private

When set to ‘Yes’, the migration will migrate documents designated as private in Notes as Private in Exchange. This will also include messages decrypted in Notes prior to migration.

Convert UNC paths to links

Specify No if you do not wish the body of the documents searched for UNC (Exchange Naming Convention) links during migration.

If you specify Yes, CMT attempts to convert UNC links into actionable links.

Add category to calendar events

Field in Exchange. For example, if you specify Migrated with Notes Migrator in the field, then all the calendar events, such as meetings and appointments, will display this phrase in the categories field after they are migrated. It enables you to visually differentiate calendar events that were migrated into Outlook from those created natively in Outlook before or after the migration. This setting is optional.

 

Note: Any categories that are in the original Notes calendar event will also display in the categories field.

Process meeting with no end date using ICAL information

Specify Yes to use the ICAL recurrence information to determine the repeat pattern when processing repeat calendar meetings with no end date.

 

Specify No to process repeat meetings with no end date without using ICAL recurrence information.

 

Note: When migrating a meeting with No End Date and this option is set to No, the meeting is migrated but limited to 250 occurrences.

Enable Advanced features

Select Yes to enable features used when migrating large environments or to cloud based services.

Enable Hosted features

Appears if Advanced features are enabled. Select Yes to enable features used when migrating hosted environments. This setting should only be enabled under the direction of Advanced Support.

Enable multiple Control Centers

Appears if Advanced features are enabled. Select Yes to enable features used when migrating with multiple Migration Control Center (MCCs). This setting should only be enabled under the direction of Advanced Support.

 

Sending Mail Box Rules

Notes Migrator allows you to send users their Mail Box Rules before migration occurs. You can define the From, Subject, text in the body, and which rules to include in the email sent to users.

Migrating Encrypted Items

Notes Migrator offers two solutions for migrated items that have been encrypted via Lotus Notes. The data may be decrypted as part of the pre-migration process, or the encrypted content may be attached to the migrated message in a Lotus Notes database during migration.

When the Require decryption action and migrate into the body option is selected, additional fields will be visible in the Send Encrypted Items Summary Email section to configure the From, Subject and text in the body of the summary email sent to end users.  If you select Migrate into a Notes database as an attachment option is selected, you will see new fields for the Template name, the Attachment name in Exchange and Text included with attachment.

Creating a Migration Checklist

  1. Click the Migration Checklist button to enter the steps, timelines, and tasks in the Migration Checklist Profile to use for your customized Migration Checklists:

  1. Starting with Step 1, click the down arrow button in the Timeline column.

  1. The Select Keywords dialog box is displayed. Select one of the provided keywords or enter a new one in the New Keyword field at the bottom of the dialog box and click OK to continue:

 

If the predefined keywords do not appropriately describe your timeline, you can specify a new keyword in the New Keyword field.

  1. Enter a description in the Task column and click Save & Close to complete:

  1. If you exit the document without saving, the following dialog box is displayed. Select Yes to save the Migration Checklist. If No is selected all new entries are discarded:

  1. After all the settings have been configured, click Save & Close to save all the configuration settings.

Enabling Recovery

As stated earlier, the Enable Recovery setting in the Other Settings tab defines the default value for the Enable Recovery setting (found under the Advanced tab) in the existing migration profiles as well as the new profiles you may create.

By default, it is set to Yes, so in all the existing migration profiles and the new ones you create, the Enable Recovery setting will also be set to Yes. However, if you were to change this setting to No in the Other Settings tab, and save the changed configuration settings, the following prompt will display.

If you click Yes in this dialog box, the Enable Recovery setting in all the existing migration profiles will change to No, and any new migration profile created will also have No as the default value in this field.

But if you click No in this dialog box, the Enable Recovery setting in all the existing migration profiles will remain Yes (the prior setting), however, when you create a new migration profile now, the Enable Recovery setting will be set to a default No.


It is recommended that you review the description provided for the Enable Recovery setting in the Advanced tab of migration profiles (Section 6.6) for a complete understanding of how this setting works.

4.11. Creating Migration Profiles

Migration Profiles define settings for certain groups of users. For instance, it may be desirable to have a profile where all executives have a filter that only migrates the last four years of mail and calendar to Exchange. Every user must have a Migration Profile set before migration can proceed.

Before you create a migration profile that contains filters to migrate specific user data, you must create a default migration profile. After the default profile has been saved, create migration profiles that will be used to migrate users. These profiles should have descriptive names, such as 90DayMailOnly or 4Years-Calendar-Mail.

Important! – The default migration profile does not have all values and should not be used for migrations. A new profile should be created to prevent problems with corrupting the backend database. This will help avoid problems during production migration.

  1. Click Migrate Profiles in the Navigation Pane:

  1. Click the Create New Profile button:

Each migration profile contains a source and destination setting that determines which mail items are migrated and if the migration is to a Microsoft Exchange server or to a .pst file.

When a migration is carried out, a migration profile must be assigned to specify how the migration should be performed. You can create as many migration profiles as desired.

  1. The Profile dialog box displays; the Source Options tab opens by default:

The following table describes the values for each setting:

Settings    

Description

Message Types

Specify the Migration Options. You can either select all message types or specify the types that you wish to be included in the migration (Mail, Calendar, Task, and Contact).

Date Filter

Specify a range of dates that will ensure that only the data that falls within the specified range is migrated.

 

The Date Filter will apply to all the selected message types. For example, if you select All message types, the specified date filter will apply to Mail, Calendar, Tasks, and Contacts.

Migration Log Level

By default, Notes Migrator creates a log file for every user that is migrated. In this field, you specify the level of detail you want in the logs. There are three levels provided.

  • Minimal

  • Normal (Recommended)

  • Verbose

 

Selecting Verbose significantly increases the size of the log files that are created. This is only recommended for troubleshooting purposes. Log files are located in the Logs subdirectory where CMT Exchange is installed, usually C:\Program Files\Binary Tree\CMT for Exchange\Logs.

Skip folders named

Specify a list of folder names from your Domino mail files that you would like Notes Migrator to bypass during the migration. This feature is useful if you have a customized mail template that may contain folders with non-messaging data. Specify folder names in the Skip folders named field. Separate entries by commas.

Migrate empty folders

Select to migrate empty folders in users’ mailboxes to Outlook.

Migrating Sent Items

In Lotus Notes, a mail message can exist in the Sent Items folder or in the Sent Items folder and a user-defined folder(s). In Outlook, a mail message can only exist in one or the other. This field provides two options.

  • Select Migrate to the Outlook Sent Items Folder, if you prefer the items to be stored in the Sent Items folder in Outlook after migration regardless of what other user-defined folder(s) it may have been stored in Lotus Notes.

  • Select Preserve custom folder name, if possible, if you prefer the items that exist in two locations to be stored in the user-defined folder after the migration.

Audit Notes UNIDs

During Migration

The migration worker will record an audit of the Notes source document UNID [unique identifier] for all items processed in a .csv file. This will be uploaded to the migration controller in the logs folder.

Ignore Privacy Flag

If set to ‘Yes’, this will not migrate any documents as private in Outlook. This will override the Settings | Other Settings option if that is set to ‘Yes’. This is typically useful for shared mailbox migrations.

 

  1. Click Destination Options:

The following table describes the values for each setting:

Settings    

Description

Migrate to Exchange Server

Select if you want the migrated data to go directly to the Exchange server.

Migrate to .PST file

Select if you want the migrated data to go to a .pst file.

 

The PST Folder Path field is added to the form when this option is selected.

PST Folder Path

Specify the path where you want the .pst file(s) to be stored. This must be a Windows drive and folder or mapped drive on the migration workers. A Windows UNC path should not be used.

 

When migrating to a PST file, the file name format will be “<User’s SMTP Address>-Notes Database ID.pst”.

Individual attachment size limit

Specify a size limit in bytes to filter individual attachments. For example, if you specify 1000, each individual attachment that is greater than 1000 bytes in size will be filtered out during migration.

 

Maximum message size cannot exceed 125 MB. This field should be set to 131072000 to avoid memory errors during the migration.

Attachment total size limit

Specify the total size limit of all attachments in a document in bytes. For example, a value of 10000 would allow only a total of 10000 bytes for attachments migrated per message.

 

Maximum message size cannot exceed 150 MB. This field should be set to 157286400 to avoid memory errors during the migration.

 

 


The default size limits for the attachment size limit fields are the maximum size we support.  This limit may differ in your environment.  We recommend testing your migration environment to confirm it supports our product limitations. If you experience memory errors with lower attachment sizes, we recommend lowering the default size limits in the attachment size limit fields until a memory error is not encountered.

  1. Next, click the Advanced tab

  2. Check the Enable Advanced Options box:

Advanced options are now displayed in the dialog box; configure these settings:

The following table describes the values for each setting:

Settings    

Description

Advanced Message Filtering Options

Configure these settings if you wish to filter the messages based on their various age limits.

Mail Age limit

Specify the number of days from the migration date to filter the mail messages. For example, if you specify 30, the application will only migrate messages that were created 30 days prior to the migration date.

Task Age limit

Specify the number of days from the migration date to filter the tasks (To Do Lists). For example, if you specify 30, the application will only migrate tasks that were created 30 days prior to the migration date.

Calendar Age limit

Specify the number of days from the migration date to filter the calendar events. For example, if you specify 30, the application will only migrate calendar events that will occur in the 30 days prior to the migration date.

Filter Repeating meetings

By default, all repeating meetings are migrated. Repeating meetings are filtered based on the specified age limit criteria only when you check the Filter Repeating meetings checkbox.

 

It should be noted that in case of repeating meetings, the filter applies to the date of the parent-meeting document and does not filter the series. This means that if the parent meeting falls within the specified date range, the entire series is migrated and if the parent meeting falls outside the date range, the entire series is skipped. The dates of the meeting recurrences do not matter.

Additional Options

Configure these settings to improve the migration throughput.

Enable Recovery

 

Specify Yes to enable the setting to track processed messages during migration. So, if the migration process terminates unexpectedly, this feature will prevent the application from reprocessing messages that were migrated during the initial run of the migration.

 

To disable this setting, specify No.

 

Refer to the Enable Recovery setting in the Configuring Other Settings section to understand how the default value for the Enable Recovery setting in the Advanced tab is determined.

Process as RTF

Specify Yes to override the default MIME processing and to process native Notes documents as Rich Text.

 

Note: Enabling this feature is not recommended.

Disable MIME Cache

Specify Yes to disable the local cache database when processing messages using MIME.

 

Disabling this feature significantly impacts throughput when migrating MIME content from a Domino server.

Convert UNC paths to links

Specify No if you do not wish the body of the documents searched for UNC (Exchange Naming Convention) links during migration.

 

If you specify Yes, CMT attempts to convert UNC links into actionable links.

Add category to calendar events

Specify a word or phrase in the field to add to the category field in Exchange. For example, if you specify Migrated with Notes Migrator in the field, then all the calendar events, such as meetings and appointments, will display this phrase in the categories field after they are migrated. It enables you to visually differentiate calendar events that were migrated into Outlook from those created natively in Outlook before or after the migration. This setting is optional.

Flush log to disk after

Specify the number of log events (entries) after which you want CMT to close the log file and flush it to the disk.

 

Leave the field blank or specify 0 or 1 to log continuously until the migration completes.

 

Please note that all the logs are flushed to the disk after they close irrespective of the value specified in this field.

 

Note: The specified value in the field only forces CMT to update the log file after a specified number of entries (events). It may improve processing in certain environments but if CMTProxy terminates during a migration, you also run the risk of missing complete information in the log file.

 

 

All the settings in the Advanced tab are pushed to the migration workstation performing the migration through the AdditionalSettings.xml file. If you haven’t changed the default Advanced settings, the .xml file is not used during a migration.

 

  1. A default name is specified in the Profile field. You must specify a descriptive name for the migration profile and do not use Default as the name.

  2. Click OK to save the migration profile settings.

  3. A confirmation box appears; click Yes to save these settings to the Notes Migrator database:

  1. A new profile by the name you specified in the Profile field is created. If you do not see it listed in the Data Pane immediately, you can refresh the Data Pane. Click the Refresh Profiles button.

To delete unused profiles, click the Delete Settings from migration server button. A profile cannot be removed if the profile has been used for end user migration.

4.12. Creating a Message Template

Notes Migrator manages communication with the end users to be migrated via Notes mail messages. These messages can be used for informational purposes only or they may contain action buttons with associated code designed to perform specific pre-migration tasks.

These migration messages are created using the Message Templates. For Message Templates with action included, there are additional settings used to control a workflow process. When an end user executes the action, a status message known as an End User Processed Migration Message is generated and returned to the Notes Migrator database via Notes mail. Once received, the message is used to update the status of the corresponding end user’s Person document. If the status indicates the action was successful, the user can be re-verified and be ready for migration.

For this process to work correctly the Notes Migrator database must be located on a Domino server and a Mail-In Database Document pointing to it should be created.

Notes Migrator comes with several predefined Message Templates designed to perform specific migration tasks. You can use these predefined Message Templates to create custom templates that may better suit your need.

  1. Click Message Templates in the Navigation Pane; the Data Pane displays a list of predefined message templates:

 

Each predefined Message template has a specific purpose. If you wished to create a custom template based on a predefined template, you need to select the predefined template before clicking the New Template button. For example, if you wished to create a custom template based on the Migration Message – Decrypt Encrypted Item template, then you must select the template prior to creating a new template.

  1. Select a predefined template and click the New Template button in the Data Pane.

 

Encrypted Sent Items may contain an encrypted flag but possess no encrypted fields. This means that even though they display as encrypted, they actually aren’t and will migrate without decryption. Encrypted mail fields (including Sent folder) will not be migrated to MS Exchange if they are not decrypted using the decryption tool.

  1. A new tab, CMT Template: Migration Message – Decrypt Encrypted Items, opens and displays a form where you can specify the details of the new Message Template. Notice that the tab clearly specifies that the new CMT template is based on the Migration Message – Decrypt Encrypted Items predefined template. However, when you save this template with a new name, the tab will reflect its new name.

  2. Customize the CMT new template. Refer to the table below for details on settings.

  3. Once all the details have been specified, click Spell Check to ensure there are no spelling errors in the message.

  4. A message box appears to confirm that no misspellings were found. Click OK to close the message box. Next, save the new template. Click Save & Close.

The following table describes the values for each setting.

Settings    

Description

Template Name

Specify a name for the template that best describes the purpose of the new message template.

Template Type

Specify the type of the new message template, such as Email Only or Contact Synchronization. Refer to the Predefined Message Template Types section below.

Return Notification

Specify if you want a return notice to Notes Migrator from the end user when the message is received and the required action is performed.

Requires MSI Attachment

Specify whether the .MSI file is required to be attached prior to sending.

From

Specify the name of the entity sending this migration message to end users (for example, Migration Coordinator).

Subject

Specify a brief description of the purpose of the new template.

User Action Required

Check this box if migration for this user cannot proceed until the user performs the embedded action within the message.

 

This check box also indicates that the user will remain in the Pending Reponses view until they perform the end user action in a particular message template.

Pre-migration

Select this if the new message is sent to the user, and requires the user to perform an action that will prepare user data for migration.

Post-migration

Select this if the new message is for use after a user’s migration has taken place, and is typically informative, no User-Action Required.

Body

Specify a customized message

 

*Note that any buttons in the message template must be edited and saved to sign these with a Notes ID that is part of the Domino system ECL.

 

The new template is saved and it appears in the list of existing templates.

4.13. Types of Predefined Message Templates

Notes Migrator comes with several predefined Message Templates which are designed to perform specific migration tasks. The information contained within these predefined templates can be modified to tailor them to a client’s needs. Predefined Message Templates can be of the following types depending on the actions they perform:

  • Email Only

  • Contact Synchronization

  • Decrypt Encrypted Items

  • Archive Discovery

  • Archive Processing

Email Only

As the name implies, Email Only is designed for informational purposes only and does not include any action buttons. Email Only templates can be used to keep the end users informed on the progress of the migration project. For example, end users can be sent an email with the migration schedule for their department. This can help them plan for when their email will be migrated.

The fields within each predefined message template should be modified to make it specific to the client. An example is shown below.

For a template to be information-only, its Template Type field should contain the value Email-only and Pre-migration option should be selected. Although, if you are sending a message to end users informing them about the successful migration, then you can also use Email Only Template Type and select Post-migration.

Contact Synchronization

When a Contact Synchronization migration message is sent to an end user, the user simply clicks the button in the message. This launches the iNotes_DoSync() agent that ships with Lotus Notes, and pushes/resyncs all contacts in the Personal Name & Address Book (pNAB) to the hidden $PeopleGroupsFlat view. Now that these contacts are in the mail file, they can be migrated.

Decrypt Encrypted Items

When a Decrypt Encrypted Items migration message is sent to an end user, the user simply clicks the button in the message. This initiates an agent that will decrypt any encrypted items in the mail file, so they will migrate as clear text.

Archive Processing

When an Archive Processing migration message is sent to an end user, the user clicks the button in the message and this allows the script to search for the Archive Database Templates locally on the end user machine, find it, and copy/replicate it to a specified location on the Domino server or file server or copy into end user’s existing Domino mail file.

The location to copy is specified in the Notes Migrator Settings document. The script will only search for templates that are specified in the Notes Migrator Settings document. Refer to the End User Migration Settings configured in the Notes Migrator Settings document.

4.14. Signing a Button in a Message Template

  1. Open a Message Template

  2. Click on Edit Document

  3. Right-click on the button and select Edit Button:

  1. A code window will appear, type the word sign, and then delete the text:

  1. Click Save and Close.

The button will now be signed with the appropriate administration ID, and end users will not receive execution security (ECL) alerts when they click the button within the message template.

4.15.    Importing Exchange MDb’s

Notes Migrator will need to have a reference to the Exchange MDbs that are available to be migrated to.  To import these, follow the below steps.

  1. Select 5. Import Exchange MDbs in the Navigation Pane

  2. The Data Pane will display an empty view of Exchange MDbs:

  1. Click the Import Mailbox DBs from AD button to import the available Exchange MDbs

  2. Select the appropriate Mailbox Databases from the list to be used and click the Set Use Flag button.

 


This is not required for Office 365 Migrations.

 

4.2. Configuring Email Repliability

Migrator for Notes collects and manages the settings essential in performing a successful migration. These settings are located under Configuration in the Navigation Pane.


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 Migrator for Notes User Guide for Office 365 Migrations for additional information.

4.1. Configuring Required Settings

Domino Settings

The Migrator for Notes Settings document displays. In the Settings document, the Required Settings -> Domino tab displays by default.


You can view the description of each field in each tab by clicking its corresponding question mark icon . For example, click and hold the mouse pointer on the question mark icon next to the Mail Server field to read its description.

Before any migration can be performed, the Required Settings tab must be completed. Two of the most important entries in this tab are the Mail Server and the Domino Directory. The specified Mail Server name is used to access the Domino Directory. The Domino Directory is used to retrieve the information required to import and create the User Mail, Rooms & Resources Databases, Mail-in Databases, and Discussion & Document Library Databases control documents.

These control documents are critical to the migration process and in their absence, migration information cannot be collected for a given item, and therefore, the item cannot be migrated. The control documents are used extensively during the remaining migration processes.

The following table describes the values for each setting.

Settings    

Description

Mail Server

The Domino server that Migrator for Notes will use for importing users and for sending Migration Messages.

Domino Directory

The Domino Directory name that Migrator for Notes will use for importing users, as found on the Domino server. Up to five additional Domino directories can be set by checking the box.

Server Mailbox

The mailbox filename that Migrator for Notes uses for sending Migration-related messages to selected users (for example, mail.box).

Audit Domino Encrypted Items

When running Audit on user mail file, specifying Yes will check for encrypted items in the mail file. If encrypted items are found, you can either send the user an email message with a button that decrypts encrypted items so that they can be migrated, or you can send the user a message with document links to the encrypted items so that they can print them prior to migration. You can even do both if you have some reason to want a list of messages that had been encrypted before the decryption agent was run.

Audit Domino Mail Rules

When running Audit on user mail file, specifying Yes will check for the number of rules in the mail file. If rules are found, you can send users a list of their Rules that will help them in creating the rules in Outlook after migration.

Audit Exchange Migrated Data

Enables auditing of migrated data in Exchange. Exchange Auditing should be enabled before data is migrated. Audit reports can be found the \logs directory on the migration workstation(s).

This is a post-migration validation process that indicates the state of documents which have been migrated by Migrator for Notes. This feature can be useful in environments as a validation check for data integrity. In addition, this can be used to audit results to reduce the size of user Domino mail files or archive databases after the migration phase on the Domino servers and user's workstation replicas. For example, removing documents with a Migration Status of 1 would leave only non-migrated data or documents that could not be migrated completely due to malformation or size restrictions in Exchange from a source database.  

Important: Consult your organizations data retention policies and regulatory compliance requirements before modifying source data. Full backups of the original source data may be required (and maintained post migration) before modifying working replicas to ensure regulatory compliance.

Audit embedded eml attachments

Enables auditing of eml attachments inside the message bodies to assist with migration troubleshooting. Results will be reported on the user document in EMM. This is not required for migration processing unless directed to enable this by Binary Tree's Product Support.

Additionally, a flag can be enabled and adds the field BTFoundEML to documents in source mail files where auditing finds eml attachments inside the message bodies.

Audit calendar unsupported patterns

Enables auditing of calendar items where the user is the Chair for Notes custom repeating meetings and generates document links for meetings that are not supported by Outlook. This will use the Migration Date if set or the current date and include meetings from the date specified and future meetings. The audit adds the reported data to the Calendar audit RTF report for the account and can be sent to end users with the Remediation Summary Message Template.

If enabled the audit can be specified to verify meetings where the user is the Chair, an Invitee or both. Additionally, label text can be added to the reported data to specify if the user is the Chair or the Invitee.

User Notification Style

Individual Notifications: Select if you want to send individual notification to each user and each mail/form will only have script for one action.

 

Combined Notifications: Select if you want to send one migration notification to each user and the notification/message to contain multiple selected forms, such as decrypting encrypted messages and synchronizing contacts and journals with mail file.

Enable this CMT db for Notifications

Click this button to create a Mail-In database document on the Domino Server for the Migrator for Notes database, and enable the database to receive User Notification responses. This database must be hosted on a Domino server.

 

Mail-enabling Migrator for Notes Database

A Mail-in Database Document is required for mail to be delivered to the newly created server copy of the Migrator for Notes database. The procedure copies the database to the server and creates a Mail-In database document for the Migrator for Notes database.

  1. Create a mail-in database for Migrator for Notes database. Click on the Server Db Copy and Mail-In Db Doc button to create a copy of the Migrator for Notes database on the Domino server and configure the Mail in Database document

  1. The Does Migrator for Notes already exist? dialog box opens; click Yes (and skip to step 5):

  1. If you are working with a local copy of the Migrator for Notes database, then click No. The Create a db copy? dialog box opens.

  2. Click Yes to create a copy of the local Migrator for Notes database on the server:

  1. If you clicked Yes in the Does Migrator for Notes CMT already exist? dialog box, the Choose Application dialog box opens. Locate the Migrator for Notes database in the CMT folder on the server, and then click Open.

The Fullname for the mail-in db doc dialog box confirms that the mail-in database for the selected server-based Migrator for Notes database does not exist, and prompts you to specify a name for the mail-in database. After specifying the name, click OK.

 

  1. In the Open the new mail-in doc? dialog box, click Yes to open the mail-in database.

The mail-in database document for Migrator for Notes opens.

  1. To verify the creation of the mail-in database, you can also launch Domino Administrator, open the Domino server, and access the Mail-In Databases and Resources folder under the People & Groups tab:

  1. Double-click the document to open and review

  2. Once the mail-in database is successfully created, the Open Mail-In Db Doc button replaces the Server Db Copy and Mail-In Db Doc button. Clicking it opens the database document for a review. Clicking the button with the X sign on it will remove all pointers to the location of the mail-in database.

    

 


The Notes ID that is used to sign the Notes Migrator database must have rights to add a new Mail-In Database Document to the server Domino directory. If the following error message is displayed, the Notes ID does not have appropriate rights.

Wor154

If you do not have the appropriate access rights to perform this action, see the onsite Domino System Administrator for help.

 

  1. It is recommended that after copying the database to the server, you delete the database from the local client folder. To remove it, right-click on Notes Migrator on Local. Select Database, and then Delete. The Lotus Notes client prompts that the database and related documents will be permanently deleted. Click Yes to delete the local database.

Modifying the Inbound Processing Agent

Once you have mail-enabled the database, you need to modify the Inbound Processing agent to view the updates. Perform the following steps to run the agent.

  1. Install Domino Designer on the workstation where Notes Migrator Domino database is located

  2. Launch Notes Migrator Domino database in Domino Designer

  3. Expand Shared Code and select Agents

  4. Select the InboundProcessing agent as shown below:

  1. Double-click InboundProcessing to open the InboundProcessing Agent Properties

  2. Click the Security tab

  3. The Administrator should be listed in the Run on behalf of section

  4. In the Set Runtime security level: field, select Allow Restricted Operations with full administration rights

  5. Once you've edited the agent, close the Properties box

  6. Close the Inbound Processing – Agent tab

  7. Save the changes

  8. Click Sign


This agent runs before new mail arrives and the Domino router must be set to allow these types of agents to run. To enable this option, go to Router/SMTP -> Restrictions and Controls -> Delivery Controls tab and set the Pre-delivery agents option to Enabled.


The Notes ID that signs this agent does require security rights on the Domino server to run agents.

 

LDAP Settings

  1. Click LDAP under the Required Settings tab:

In this tab, specify the Active Directory information to resolve users by matching them between source and destination platforms via Lightweight Directory Access Protocol (LDAP). To use this option, specify the required details.


LDAP configuration is not specifically required for Office 365 only migrations.

Use the following table to enter the correct values for each field:

Settings    

Description

Domain

The common name of the Active Directory domain. For example, binarytree rather than binarytree.com.

LDAP IP Address or Host Name

The fully qualified LDAP server name, IP Address, or resolvable DNS name of the Active Directory server. (e.g. PC-XP-01. binarytree.com or 192.163.15.12).

LDAP Port

Specify the LDAP port.

The default port for LDAP is 389.

The default port for SSL LDAP is 636.

Login ID

The AD domain account that has read rights to the target AD domain.

For example: administrator and not <domain>\administrator

Password

The password associated with the ID specified in Login ID.

Validate Settings

Click to validate the specified values to ensure that you are able to connect to the domain in Exchange where the end users will be eventually migrated.

LDAP Directory Base (Base DN)

If LDAP settings result in a successful connection, then this field is automatically updated.

Specify the directory base for all LDAP queries. The query settings will enable the search in AD to ensure that users are getting resolved against the right container ‘directory’ within AD.

Example: DC=btexchange2k7,DC=com

Quick Check

Full Check

If you want to search only the first ten users, select Quick Check; and if you want to search all the users, select Full Check.

Validate Query Settings

Click to validate the values specified in LDAP Directory Base to ensure that query string is resolving users and returning the number of resolved users.

 

  1. Specify the connection settings and then validate them by clicking the Validate Settings button:

  1. The LDAP Connection Settings Test Results message box displays indicating that the settings were validated and the connection was successful; click OK:

  1. Notice that the LDAP Directory Base (Base DN) field is automatically populated

To ensure that the specified directory base, where all LDAP searches will be conducted, is correct; you should validate this setting as well; click the Validate Query Settings button:

  1. The LDAP Query User Settings Test Results message box displays; the query setting is validated and some records are returned; in a production environment, ten records should be returned always; click OK:

Additional Settings

  1. Click the Additional tab under Required Settings

 

  1. Configure these settings with the names of the views to locate and import User and Mail-in Databases information. Also, specify the Migration Status Codes that can be assigned to users’ mail and databases control documents. You can assign a code to a user to update its status and view users based on their status codes. This helps in providing a better picture of the migration progress.

The following table describes the values for each setting:

Settings    

Description

CMT Migration Server

Specify the network hostname or IP address of the machine that is running the migration server.

CMT Program Directory

Specify the complete program directory path to Notes Migrator installation. This location will be used to launch the migration engine when the migration is triggered off.

 

Note: During the installation of Notes Migrator, if you had specified a destination folder path other than the default (C:\Program Files\Binary Tree\CMT Exchange), then you must replace the default path specified in the CMT Program Directory field with the modified path. In failing to do so, the migration engine will not launch when the migrations are set to go off.

Use Secure Web Services

Specify whether the web service calls are made to an XML server configured for secure access. Note that additional steps are required to secure the web services. The default selection is “Yes” which uses the CMT eService COM object to access the XML server.

 

Refer to Appendix E: Securing Notes Migrator Web Services with Windows Authentication for additional steps if you select Yes.

I have multiple control Centers

This option appears if the multiple Migration Control Center advanced feature is enabled on the Other Setting tab. Check this option to define the IP addresses of the Control Centers.  When enabled, the Set Migration Status options include Set Migration MCC and Clear Migration MCC options.

Migration Server Control Center IPs

Appears if “I have multiple control Centers” is checked. This field is used by the Set Migration Status agent.

Values must be entered as follows:

Workstation#=IP address of Notes Migrator Control Center

For example:

1=192.168.1.0

2=192.168.1.1

3=192.168.1.2

User Import View

Specify the view in the Domino directory that Notes Migrator database will use for importing users. Use the People view unless there is a custom view that you have created.

Mail-In Databases Import View

Specify the view in the Domino directory that Notes Migrator database will use for importing mail-in databases and resources. Use the Mail-In Databases view unless there is a custom view that you have created.

Mail-In Databases View Category

This is the NAB Mail-In database view category used for importing Mail-in Databases and Resources. Use the “Databases” default unless Domino is using a language other than English. Change this value to what is displayed in the NAB Mail-in Databases view.

Migration Status Codes

Specify a personalized list of status codes that will be used during the migration project. These codes can be assigned to users’ mail and databases control documents. If these status codes are assigned during the different phases of the migration process, timely status reports can be produced. These status reports will help provide a better picture of the migration progress. With this type of information, you have more control over the migration project and can react quickly to any identified issue. Adjustments can be made to help fine tune the migration schedule by adding more or different resources. Status codes must be separated by a new line. A list of status codes has been specified for you. You can either retain or change these status codes depending on your need.

CAS Server

Specify the Exchange Client Access Server (CAS) name. If a name is specified, then the matching process will use the following URL to resolve users. https://[servername]/autodiscover/autodiscover.xml

 

However, if you have specified the full URL to the Autodiscover service, then the URL will be used to resolve users.

 

This field is required for delegation migrations.

Username

If only the CAS Server name or IP address is specified in the CAS Server field, then you must specify a valid username for the authentication process that takes place on the CAS server. Note that the username should be in the following format for on-premises Exchange: <domain>\<username>. For Office 365 the format should be username@domain.com.

 

If you have specified a full URL (with https://) in the CAS Server field, then you can leave this field blank for on-premise migrations.

Password

Specify the password associated with the username provided in the previous field.

 

If you specified a full URL (with https://), then you can leave this field blank for on-premise migrations.

Powershell Admin Credentials

For on-premise Exchange servers, the credentials are of the form [Domain]\[Username].

For Office 365, the credentials are the SMTP address used to pass credentials to Office365 for remote access, for example o365Admin@tenant.onmicrosoft.com

Powershell Admin Password

Appears if Office 365 is in use

Use the Set PowerShell Password button to update this field. This will request the password and record it using the AsSecure PowerShell method.

This is not required for clicking the Notes Migrator PowerShell buttons, if this is not entered the buttons (such as Set Full Acccess) will ask for the password when processed.

PowerShell Logging Path

The MS PowerShell used when generating, executing, and logging PS1 script. This path can be edited on User Provisioning tab.

Default Reporting Path for Matching

Specify the reporting path used by the matching process. The default path is C:\Matching\.

Enable PowerShell Modern Auth

Appears if Office 365 is in use

Set to Yes to enable the use of the Exchange Online module for PowerShell processing. This will use Modern Auth connectivity to Microsoft Online services, removing the Basic Auth connection processing.

Enable Modern Auth for Migration

Appears if Office 365 is in use

Set to Yes to enable the use of Modern Authentication for Migrations. The Office 365 tenant must be configured to use Modern Authentication.

Autodiscover Username

Autodiscover credentials to be used during creation of the profile used by the migration engine.

For on-premise Exchange servers, the credentials entered should be the UPN (User Principal Name), for example: UserName@Example.Microsoft.com

For Office 365, the credentials are the SMTP address of an account in the Office 365 domain, for example: o365Admin@tenant.onmicrosoft.com.

 

Note: This is used if a migration worker does not have an account specified and is a fall back option. This is not required if a migration farm is being built using AWD.

Autodiscover Password

Enter the password associated with the Autodiscover account entered above.

Customer Name

Specify the Customer name that you would like in the status report.

Send Customer Status Report To

Specify the Group Name or SMTP addresses of the persons that should receive the status report.

Send Operator Status Report To

Specify the Group Name or SMTP addresses of the persons that should receive the full status report.

Migration Status Report Path

Specify the working path for migration status reports.

Create a combined report for multiple Migration Management databases (up to 5 additional)

Check this option to specify up to five additional migration management databases to include in a combined report.

 

Click the Email Repliability tab to specify the appropriate values for the Domino environment:

Refer to the table given below for a brief description of all the settings in the Email Repliability tab.

Settings    

Description

Past and Present Domino Domains

The Domino domain names that are stripped from the email addresses and result in a valid and reply-able address regardless of domain name changes over the years. Enter a comma-separated list of all domain names in Domino, including the Notes Integration domain – no @ character is necessary.

Note: These are Domino domains, not SMTP or Internet domains, so it would more likely be ACME or ACME-NOTES, rather than acme.com.

Last Name Translation Update

This field is automatically populated during the Name Translation Update Process. This value will indicate the last time the Domino Directory was searched for updates.

Name Translation Database

The Name Translation Database field allows you to browse for the primary database to use for Name Translation lookups. This would typically be the current Notes Migrator.nsf. A warning will appear if you attempt to save the configuration without defining the Name Translation Database.

Name Translation Failover

The Name Translation Failover field allows you to optionally set the path to the primary failover database used for Name Translation lookups. The failover database is used if the primary database is inaccessible. This database should reside on the Domino server.  If a local (workspace) path is used, the EMM database must be replicated to the same relative path on all workstations.

Powershell bulk matching batch size

When using the two-step bulk PowerShell matching process for address translation entries, this is the number of records that will be presented in each matching .csv file. The default value is “2000”.

Note: this option is only available to Exchange on-premise migrations.

Table

The Name Translation Database table allows you to set the Name Translation Databases and Name Translation Failover Databases on multiple workstations. Click Set selected to define a Name Translation Database and Name Translation Failover for the selected workstation to use instead of the primary (default) databases defined above.

 

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: 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.

 

 

 

Lotus Notes Migration ID

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.

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.

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.

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 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:

4.7. Configuring Rooms & Resources Settings

  1. Click Rooms & Resources; this tab has two sections. Review the general description provided for both the sections.

Rooms & Resource Migration Options

The Rooms & Resource Migration Options section enables you to configure settings to determine how resources are handled during a migration:

The following table describes the values for each setting:

Settings    

Description

Rooms and Resources Target

Specify if you want the room or the resource to be migrated to a Location field, or be appended to the message body, both, or none.

Room Label

Specify the label you wish to be prefixed to the migrated room text.

Resource Label

Specify the label you wish to be prefixed to the migrated resource text.

Online Label

Specify the label you wish to be prefixed to the migrated online text.

Location Detail Indicator

Specify the text you wish to appear when room or resource text is not included in the Location field.

Room Resource Separator

Specify a string that separates the location, room, resource, or online values that are included on the Location field.

 

Rooms & Resource Settings

Configure these settings if you want to migrate Rooms and Resources. The first step of the process involves importing Rooms and Resources into the Notes Migrator database. Lotus Notes stores multiple Rooms/Resources in a single database. Notes Migrator allows you to import and create a separate .nsf for selected Room/Resource and copy its corresponding calendar into the newly created .nsf. Once all the Rooms/Resources that you want to migrate have been separately imported, you can export them to Notes Migrator migration engine and migrate them.

The following table describes the correct values for each setting.

Settings    

Description

Rooms and Resources Import View

Specify the view in the Domino directory that Notes Migrator will use for importing the different Rooms and Resources. Use the Rooms Resources view unless there is a custom view that you have created.

Target Server

Specify the Domino server that Notes Migrator will use when creating separate .nsfs for each Room/Resource. This must not be blank.

Target Path

Specify the destination path where separate .nsfs will be created for selected Rooms/Resources.

 

The path is relative if the destination is a Domino server. If the destination is a file server, full path must be specified.

Database Template

Specify the template that will be used to create the new room or resource database to migrate.

Set Subject to Chair

Set this to ‘Yes’ to enable overwriting the booking subject when importing rooms and resources. This will set the subject to the booking Chair for migration to Outlook (removing the booking subject entirely). This does not impact the existing Notes room and resource bookings. Selecting ‘No’ will retain the original booking subject for migration.

Subject Prefix

This is used if the subject for imported booking will be overwritten with the booking Chair name. The text used will be prefixed in the imported booking subject.

4.8. Configuring Replica Settings

The Replica Settings are used when using a Domino staging server. A staging server is often used when the Domino mail servers are not on the same LAN as Exchange and/or the migration environment to mitigate migration throughput degradation due to the network. Staging servers are also used if you will be using replication formulas to filter the data intended for migration.

The following table describes the values for each setting:

Settings    

Description

Staging Server(s)

The Name of each of the staging servers to be used for creating replicas separated by a new line or a comma.  For Example: Stage01/Contoso

Staging Server File Folder

The folder name in which to place the newly created replicas.

Replication Formula Option

Specify My Own Formula: Use the field below to specify your own selection formula.  Be sure to enter the ENTIRE formula, starting with SELECT (e.g. SELECT @All to replicate all Notes items).

 

Build Formula Via Selections: The number of calendar and email days and select the forms to include in the replica and a replication formula will be built for you.

Replication Formula

If you are specifying your own replication formula, enter it here.

*Note: You must be familiar with Notes formula language.

Number of Calendar Days

If you selected Build Formula Via Selections enter the number of calendar days to include in the replica. You will be prompted for a date upon replica creation and it will use this date and the number you specify to calculate the number of calendar days to include.

Number of Email Days

If you selected Build Formula Via Selections enter the number of email days to include in the replica. You will be prompted for a date upon replica creation and it will use this date and the number you specify to calculate the number of email days to include.

Forms to include in Replica

Select or enter all of the different forms to be included in the replication formula.  If the form name is not listed here, it will NOT be included in the replication formula and will not be in the replica.

Replicate Each Replica at Creation

Selecting “Yes” will replicate each newly created replica as it is created. It will also cause the agent to run very slowly depending on the replica settings. It is recommended to use this as a one-off replica creation rather than for the entire list of users/mail-in databases.

Exclude Trash from Replica Comparison

Set to Yes to exclude Trash (Soft Deletion) document counts from the replica comparison total document counts. Set to No for default processing to count all documents.

4.9.    Configuring Delegation

  1. Click the Delegation tab.

  2. Validate Yes is selected for the Audit Delegates option. If set to No, set to Yes and save and close the document, then reopen the document to view the other configuration settings.

  1. The PowerShell application impersonation set option is a prompt to set application impersonation. Set application impersonation using the steps below and then set this option to Yes.

    1. Open the Exchange Management Shell or configure a PowerShell session to connect to either an on-premise or the appropriate Office365 server.

    2. In the shell, enter the following command to configure application impersonation:

New-ManagementRoleAssignment –Name:impersonationAssignmentName –Role:ApplicationImpersonation –User:CMTMigrationAdmin@myDomain.org

Where CMTMigrationAdmin@myDomain.org is the SMTP or login name of the migration account, or the name of security-enabled group used for migration.

  1. To run delegation migrations as a scheduled process, set Run delegation as a scheduled process to Yes (default).

  2. Click the Enable scheduled agent button and select the Domino server that will perform the migration. The agent will run in the background of the local Notes client if the Local option is selected.

Scheduled delegation migration runs in the background on a workstation or server. If running locally, Notes must be running and background agents must be enabled on the client.

The scheduled delegation migration agent runs once a day at 3:00 AM.  Note that if the agent is changed to run at a time interval that is too short, the PowerShell tasks may not have time to complete.

  1. Click the Delegate Settings tab:

  1. After auditing the user's mail files with Active Delegation enabled, you are able to send an email that displays the user's current delegation settings, so they can decide whether they are still valid for migration to Outlook. You should allow the users a period of time to review before rerunning the mail file audit to collect any updated settings.

The options below allow you to customize the message to exclude certain users and groups that delegation does not need to be reported to the users about. Typical exclusions are standard Administrative groups or administrative IDs that are by default listed in the HCL Domino Mail files within the environment.

4.10. Configuring Source Updates

The Source Updates Settings are used to configure the Fix Folders agent.

 

The following table describes the values for each setting.

Settings    

Description

Replace Blank Folder Names With

The folder name to be used when updating Blank folder names. This will update blank (Null) folders at the folder root, blank folders within the folder hierarchy and blank folders at the end of the folder hierarchy. This will numerically increment (1, 2, 3, etc.) if more than one blank folder exists. Replacements will be done for: "", " ", " \", "\ \","\\" "\ "

Append Personal System Folders With

The folder name to be appended to Outlook system folders that have been created at the folder root of the Notes personal folders. This will not update the Notes system folders. The folder names will be appended with a hyphen "-" and then the name to be used.

Check for Duplicate Folders Names

Option to check for duplicate personal folder names. If enabled, the agent will check each folder to determine if there is a duplicate and then append "-" and an incremented number to make the name unique.

Check Duplicate Folders on Remediation Only

Option to have the duplicate checks be performed on the first Fix Folders processing or only on second processing runs. This requires the option for duplicate checking to be enabled. Set to "No" to disable this and have the Fix Folders agent always check on the first pass for duplicates or set to "Yes" to have the duplicate checking skipped on the first pass and only be run on subsequent updates. This is enabled as the default configuration.

Maximum Duplicates Checks per Folder

Numeric setting for the number of duplicates to be checked on a single personal folder. If there are more duplicates of a single folder name than the number specified, the duplicate checking for that folder will be skipped. Requires duplicate checking to be enabled.

Remove Personal Folder Aliases

Option to remove hidden Alias from Notes Personal folders. This will remove all aliases in the Notes folders except for the system folders. This should only be used if an issue with an alias is found to cause a problem with migrations.

Email end users with Folder Renames

Option to send an email to the end users with a list of the folder names that were changed. The email will include the original folder names and the new folder names.

Enable Replacement of Specific Characters

If enabled, this will allow for a defined set of characters to be removed from all personal folder names and to have those replaced with a different character. This will not update system folders and should only be used if a specific character is found to cause an issue with migrations.

Replacement characters in

Personal Folders

This is a text list of characters to be replaced and should be a comma separated list if more than one character should be replaced. This requires the character replacement to be enabled and should not contain a backslash "\" as that will replace the Notes folder hierarchy or be Null (blank).

Character to be used for replacements

This should be a valid character that is not known to cause migration issues and should not be Null (blank). Typically, a hyphen "-" is recommended.

Remove obsolete local group members

This can be enabled to verify any local personal group membership (not system groups membership) and remove notes formatted (Canonical) membership addresses that are no longer in Domino (e.g. user accounts for leavers that were removed from Domino). The Email Repliability in Notes Migrator is used for these checks and should be populated prior to running the processing, if enabled. Note that these members cannot be automatically replaced once they are removed.

Rename local canonical group names

This can be enabled to validate local personal group names created by end users to check if these have a canonical (Domino) format (e.g. Personal Group/Local). If enabled, the processing will rename these by replacing the “/” with a “-“ to prevent Notes treating the local group name as canonical for migration.

 

4.11. Configuring Other Settings

Click the Other Settings tab to configure settings to control how encrypted items are handled or mail rules found in the user mail file. In this tab, the Migration Checklist and Advanced settings can also be configured:

The following table describes the values for each setting:

Settings    

Description

Send Rules Email

Configure these settings if you will be sending users their mailbox rules before migration.

From

Contains the profile name that will send the mail regarding mailbox rules to users. Migration Coordinator is specified as default.

Subject

Contains a subject that briefly describes the purpose of the mail. Your Mail Box Rules is specified as the subject by default.

Body

Can contain any information that you may want to share with the end user about this procedure.

Rules to Include

Includes all rules or only the rules that are enabled. Select All Rules.

Encrypted Items Migration

Choose how to migrate encrypted messages. Valid options are:

  • Require decryption action and migrate into the body

  • Migrate into a Notes database as an attachment

Note: Enabling the Migrate into a Notes database as an attachment option will increase the size of each migrated item containing encrypted content. The Lotus Notes client, original Notes ID, and decryption keys are required on the workstation used to view the encrypted content of the migrated items.

Send Encrypted Items Summary Email

Configure these settings if you will be emailing users a summary of their encrypted items.

The fields in this section display only when Require decryption action and migrate into the body option is selected.

From

Contains the profile name that will send users the mail with a summary of encrypted items. Migration Coordinator is specified as default.

Subject

Contains a subject that briefly describes the purpose of the mail. Your Encrypted Items is specified as the subject by default.

Body

Can contain any information that you may want to share with the end user about this procedure.

Template Name (.ntf)

This appears if you have selected Migrate into a Notes database as an attachment. Specify the template name in this format:  filename.ntf

 

EncryptedContent.ntf is the default template that ships with Notes Migrator. This template will be installed on every migration workstation during the product installation. This template will need to be signed with the appropriate Lotus Notes Administrative ID on all workstations. 

 

You can use any database template; however, you will need to manually distribute the template to all migration workstations.

 

Binary Tree recommends that use of an alternative template or any changes to EncryptedContent.ntf be thoroughly validated prior to production use.

Attachment name in Exchange

This field displays only when the Migrate into a Notes database as an attachment option is selected.  Specify the database name in this format:  filename.nsf

Text included with attachment

This field displays only when the Migrate into a Notes database as an attachment option is selected. Customized text can be added to the migrated item to provide end-user instructions or information. The default text is as follows:

 

Portions of this document were encrypted with Lotus Notes encryption. This content has been stored in the attached Lotus Notes database during migration to preserve security. You may view this content by opening the attached file on a workstation that has a Lotus Notes Client and the recipient’s Notes ID.

Migration Checklist

The Migration Checklist is a personalized list of tasks which can be used to help manage the migration project. Determine, then classify or group the major steps you consider necessary to manage your migration project. Determine the sequence, timeline, and description for each migration task and enter them into the Migration Checklist.

Enable Recovery

This setting defines the default value for the Enable Recovery setting in the migration profiles’ Advanced tab.

 

If the Enable Recovery setting is set to Yes in the Advanced tab of a migration profile, it enables tracking of processed messages during migration. So, if the migration process terminates unexpectedly, this feature prevents the application from reprocessing messages that were migrated during the initial run of the migration. Click here to learn more about configuring the Enable Recovery setting.

Disable MIME Cache

Specify Yes to disable the local cache database when processing messages using MIME.

Disabling this feature significantly impacts throughput when migrating MIME content from a Domino server.

Migrate Unfiled Documents

This option determines if “unfiled” documents will be migrated. “Unfiled documents are documents in Notes that do not appear in any folder and can only be accessed from the “All Documents” view within the mail file. Documents may be unfiled if a user deletes a folder without deleting the documents or removes a folder it resided within. The unfiled folder name can be defined.

MAPI Custom Settings

Select Specify advanced MAPI parameters to override the default values for MAPI retry count and MAPI retry delay.

When configured, retries are attempted when the MAPI_E_NETWORK_ERROR (0x80040115) result code is encountered during any of the following MAPI calls:

  • Create attachment

  • Create folder

  • Create message

  • Modify recipients

  • Save folder changes

  • Save message changes

  • Save attachment changes

 

If the configured retry limit is exceeded, the migration is cancelled and Notes Migrator will begin the migration of the next user. If the migration is canceled in the middle of writing a document, the document will be partially written to Exchange. The default retry limit is set to 30 seconds.

 

Specify the Number of retries that will be attempted when the MAPI_E_NETWORK_ERROR (0x80040115) result code is encountered. Values ranging from 1 to 999 can be entered. The default number of retries is “9”. Note that entering “0” results in the default “9” retries being used.

 

Specify the Delay between retries in seconds between MAPI calls. The time is progressive. The number of seconds delay for a call is (retry # * delay). For example, if the retry delay is set to 1 second, and the retry count is 5, the delays between calls will be 1, 2, 3, 4, and 5 (progressively longer). If the retry delay is 1.5 seconds, the times will be 1.5, 3.0, 4.5, 6, and 7.5. Values ranging from 1 to 999 can be entered. The default delay is “1” second. Note that entering “0” results in the default delay “1” second being used.

MAPI Retry Failure Limit

When enabled, Notes Migrator tracks documents where one or more MAPI calls could not be completed successfully. If the number of documents where one or more MAPI calls cannot be committed to Exchange, the migration will exit with ‘migration failed’ status.

 

The document retry failure limit feature can be disabled by setting the value to ‘0’ or leaving it blank.

 

MAPI Retry

Notes Migrator makes multiple MAPI calls when migrating a document, such as creating the message header, writing the body, adding attachments, etc. When processing messages, the remote Exchange server may become unresponsive in such a way that MAPI calls to write data do not complete. The call is retried a number of times (using the preexisting feature known as MAPI Retry: the maximum number and delay between retries can be set in EMM) to fully migrate data to Exchange.

 

If any of the MAPI calls cannot be completed, the document will be considered as failed due to MAPI retries, and added to the total of failed documents. Document information is logged, the NoteID is removed from both the in-memory migration history, and the CMTProcessedNoteID-[shortname].txt crash recovery file.

 

Note that other types of failures, such as a corrupt message body which results in a failure, are not counted toward the MAPI retry failure total. These other types of failures are specific to the source data, whereas the MAPI retry failures are related to the ability to write to exchange.

 

If the number of documents with MAPI retry errors exceeds the failure limit, the migration will exit, and return ‘Migration failed’ status. This migration will not automatically requeue and must be requeued by the migration administrator to fully migrate the mailbox. When a migration is requeued, it may be migrated by any workstation. Any documents containing MAPI retry errors on the failed migration will be remigrated during subsequent migrations.   

 

If the migration terminates abnormally (crashes), the document being migrated when the crash occurs will not be retried, which is standard procedure for crash recovery in Notes Migrator. Any other documents containing MAPI Retry Exceeded will be remigrated. In this case, Notes Migrator will automatically restart the migration on the same workstation.

Process attachments greater than

The limit for the size attachments, in MB, that will be detached and processed as file attachment objects. A value of -1 disables this feature, and processes all attachments as MIME streams, similar to Notes Migrator versions 4.6 and earlier. A value of 0 will process all attachments as file attachments. The default value is 0 MB to process all attachments outside the MIME Stream.

Encapsulate special content

When enabled, documents containing special notes functionality or items such as button or stored forms will be migrated as an attachment in addition to being rendered in the message body. End users can then open the NotesMessage.nsf attachment to use the native functionality of the form.

Migrate documents as private

When set to ‘Yes’, the migration will migrate documents designated as private in Notes as Private in Exchange. This will also include messages decrypted in Notes prior to migration.

Convert UNC paths to links

Specify No if you do not wish the body of the documents searched for UNC (Exchange Naming Convention) links during migration.

If you specify Yes, CMT attempts to convert UNC links into actionable links.

Add category to calendar events

Field in Exchange. For example, if you specify Migrated with Notes Migrator in the field, then all the calendar events, such as meetings and appointments, will display this phrase in the categories field after they are migrated. It enables you to visually differentiate calendar events that were migrated into Outlook from those created natively in Outlook before or after the migration. This setting is optional.

 

Note: Any categories that are in the original Notes calendar event will also display in the categories field.

Process meeting with no end date using ICAL information

Specify Yes to use the ICAL recurrence information to determine the repeat pattern when processing repeat calendar meetings with no end date.

 

Specify No to process repeat meetings with no end date without using ICAL recurrence information.

 

Note: When migrating a meeting with No End Date and this option is set to No, the meeting is migrated but limited to 250 occurrences.

Enable Advanced features

Select Yes to enable features used when migrating large environments or to cloud based services.

Enable Hosted features

Appears if Advanced features are enabled. Select Yes to enable features used when migrating hosted environments. This setting should only be enabled under the direction of Advanced Support.

Enable multiple Control Centers

Appears if Advanced features are enabled. Select Yes to enable features used when migrating with multiple Migration Control Center (MCCs). This setting should only be enabled under the direction of Advanced Support.

 

Sending Mail Box Rules

Notes Migrator allows you to send users their Mail Box Rules before migration occurs. You can define the From, Subject, text in the body, and which rules to include in the email sent to users.

Migrating Encrypted Items

Notes Migrator offers two solutions for migrated items that have been encrypted via Lotus Notes. The data may be decrypted as part of the pre-migration process, or the encrypted content may be attached to the migrated message in a Lotus Notes database during migration.

When the Require decryption action and migrate into the body option is selected, additional fields will be visible in the Send Encrypted Items Summary Email section to configure the From, Subject and text in the body of the summary email sent to end users.  If you select Migrate into a Notes database as an attachment option is selected, you will see new fields for the Template name, the Attachment name in Exchange and Text included with attachment.

Creating a Migration Checklist

  1. Click the Migration Checklist button to enter the steps, timelines, and tasks in the Migration Checklist Profile to use for your customized Migration Checklists:

  1. Starting with Step 1, click the down arrow button in the Timeline column.

  1. The Select Keywords dialog box is displayed. Select one of the provided keywords or enter a new one in the New Keyword field at the bottom of the dialog box and click OK to continue:

 

If the predefined keywords do not appropriately describe your timeline, you can specify a new keyword in the New Keyword field.

  1. Enter a description in the Task column and click Save & Close to complete:

  1. If you exit the document without saving, the following dialog box is displayed. Select Yes to save the Migration Checklist. If No is selected all new entries are discarded:

  1. After all the settings have been configured, click Save & Close to save all the configuration settings.

Enabling Recovery

As stated earlier, the Enable Recovery setting in the Other Settings tab defines the default value for the Enable Recovery setting (found under the Advanced tab) in the existing migration profiles as well as the new profiles you may create.

By default, it is set to Yes, so in all the existing migration profiles and the new ones you create, the Enable Recovery setting will also be set to Yes. However, if you were to change this setting to No in the Other Settings tab, and save the changed configuration settings, the following prompt will display.

If you click Yes in this dialog box, the Enable Recovery setting in all the existing migration profiles will change to No, and any new migration profile created will also have No as the default value in this field.

But if you click No in this dialog box, the Enable Recovery setting in all the existing migration profiles will remain Yes (the prior setting), however, when you create a new migration profile now, the Enable Recovery setting will be set to a default No.


It is recommended that you review the description provided for the Enable Recovery setting in the Advanced tab of migration profiles (Section 6.6) for a complete understanding of how this setting works.

4.11. Creating Migration Profiles

Migration Profiles define settings for certain groups of users. For instance, it may be desirable to have a profile where all executives have a filter that only migrates the last four years of mail and calendar to Exchange. Every user must have a Migration Profile set before migration can proceed.

Before you create a migration profile that contains filters to migrate specific user data, you must create a default migration profile. After the default profile has been saved, create migration profiles that will be used to migrate users. These profiles should have descriptive names, such as 90DayMailOnly or 4Years-Calendar-Mail.

Important! – The default migration profile does not have all values and should not be used for migrations. A new profile should be created to prevent problems with corrupting the backend database. This will help avoid problems during production migration.

  1. Click Migrate Profiles in the Navigation Pane:

  1. Click the Create New Profile button:

Each migration profile contains a source and destination setting that determines which mail items are migrated and if the migration is to a Microsoft Exchange server or to a .pst file.

When a migration is carried out, a migration profile must be assigned to specify how the migration should be performed. You can create as many migration profiles as desired.

  1. The Profile dialog box displays; the Source Options tab opens by default:

The following table describes the values for each setting:

Settings    

Description

Message Types

Specify the Migration Options. You can either select all message types or specify the types that you wish to be included in the migration (Mail, Calendar, Task, and Contact).

Date Filter

Specify a range of dates that will ensure that only the data that falls within the specified range is migrated.

 

The Date Filter will apply to all the selected message types. For example, if you select All message types, the specified date filter will apply to Mail, Calendar, Tasks, and Contacts.

Migration Log Level

By default, Notes Migrator creates a log file for every user that is migrated. In this field, you specify the level of detail you want in the logs. There are three levels provided.

  • Minimal

  • Normal (Recommended)

  • Verbose

 

Selecting Verbose significantly increases the size of the log files that are created. This is only recommended for troubleshooting purposes. Log files are located in the Logs subdirectory where CMT Exchange is installed, usually C:\Program Files\Binary Tree\CMT for Exchange\Logs.

Skip folders named

Specify a list of folder names from your Domino mail files that you would like Notes Migrator to bypass during the migration. This feature is useful if you have a customized mail template that may contain folders with non-messaging data. Specify folder names in the Skip folders named field. Separate entries by commas.

Migrate empty folders

Select to migrate empty folders in users’ mailboxes to Outlook.

Migrating Sent Items

In Lotus Notes, a mail message can exist in the Sent Items folder or in the Sent Items folder and a user-defined folder(s). In Outlook, a mail message can only exist in one or the other. This field provides two options.

  • Select Migrate to the Outlook Sent Items Folder, if you prefer the items to be stored in the Sent Items folder in Outlook after migration regardless of what other user-defined folder(s) it may have been stored in Lotus Notes.

  • Select Preserve custom folder name, if possible, if you prefer the items that exist in two locations to be stored in the user-defined folder after the migration.

Audit Notes UNIDs

During Migration

The migration worker will record an audit of the Notes source document UNID [unique identifier] for all items processed in a .csv file. This will be uploaded to the migration controller in the logs folder.

Ignore Privacy Flag

If set to ‘Yes’, this will not migrate any documents as private in Outlook. This will override the Settings | Other Settings option if that is set to ‘Yes’. This is typically useful for shared mailbox migrations.

 

  1. Click Destination Options:

The following table describes the values for each setting:

Settings    

Description

Migrate to Exchange Server

Select if you want the migrated data to go directly to the Exchange server.

Migrate to .PST file

Select if you want the migrated data to go to a .pst file.

 

The PST Folder Path field is added to the form when this option is selected.

PST Folder Path

Specify the path where you want the .pst file(s) to be stored. This must be a Windows drive and folder or mapped drive on the migration workers. A Windows UNC path should not be used.

 

When migrating to a PST file, the file name format will be “<User’s SMTP Address>-Notes Database ID.pst”.

Individual attachment size limit

Specify a size limit in bytes to filter individual attachments. For example, if you specify 1000, each individual attachment that is greater than 1000 bytes in size will be filtered out during migration.

 

Maximum message size cannot exceed 125 MB. This field should be set to 131072000 to avoid memory errors during the migration.

Attachment total size limit

Specify the total size limit of all attachments in a document in bytes. For example, a value of 10000 would allow only a total of 10000 bytes for attachments migrated per message.

 

Maximum message size cannot exceed 150 MB. This field should be set to 157286400 to avoid memory errors during the migration.

 

 


The default size limits for the attachment size limit fields are the maximum size we support.  This limit may differ in your environment.  We recommend testing your migration environment to confirm it supports our product limitations. If you experience memory errors with lower attachment sizes, we recommend lowering the default size limits in the attachment size limit fields until a memory error is not encountered.

  1. Next, click the Advanced tab

  2. Check the Enable Advanced Options box:

Advanced options are now displayed in the dialog box; configure these settings:

The following table describes the values for each setting:

Settings    

Description

Advanced Message Filtering Options

Configure these settings if you wish to filter the messages based on their various age limits.

Mail Age limit

Specify the number of days from the migration date to filter the mail messages. For example, if you specify 30, the application will only migrate messages that were created 30 days prior to the migration date.

Task Age limit

Specify the number of days from the migration date to filter the tasks (To Do Lists). For example, if you specify 30, the application will only migrate tasks that were created 30 days prior to the migration date.

Calendar Age limit

Specify the number of days from the migration date to filter the calendar events. For example, if you specify 30, the application will only migrate calendar events that will occur in the 30 days prior to the migration date.

Filter Repeating meetings

By default, all repeating meetings are migrated. Repeating meetings are filtered based on the specified age limit criteria only when you check the Filter Repeating meetings checkbox.

 

It should be noted that in case of repeating meetings, the filter applies to the date of the parent-meeting document and does not filter the series. This means that if the parent meeting falls within the specified date range, the entire series is migrated and if the parent meeting falls outside the date range, the entire series is skipped. The dates of the meeting recurrences do not matter.

Additional Options

Configure these settings to improve the migration throughput.

Enable Recovery

 

Specify Yes to enable the setting to track processed messages during migration. So, if the migration process terminates unexpectedly, this feature will prevent the application from reprocessing messages that were migrated during the initial run of the migration.

 

To disable this setting, specify No.

 

Refer to the Enable Recovery setting in the Configuring Other Settings section to understand how the default value for the Enable Recovery setting in the Advanced tab is determined.

Process as RTF

Specify Yes to override the default MIME processing and to process native Notes documents as Rich Text.

 

Note: Enabling this feature is not recommended.

Disable MIME Cache

Specify Yes to disable the local cache database when processing messages using MIME.

 

Disabling this feature significantly impacts throughput when migrating MIME content from a Domino server.

Convert UNC paths to links

Specify No if you do not wish the body of the documents searched for UNC (Exchange Naming Convention) links during migration.

 

If you specify Yes, CMT attempts to convert UNC links into actionable links.

Add category to calendar events

Specify a word or phrase in the field to add to the category field in Exchange. For example, if you specify Migrated with Notes Migrator in the field, then all the calendar events, such as meetings and appointments, will display this phrase in the categories field after they are migrated. It enables you to visually differentiate calendar events that were migrated into Outlook from those created natively in Outlook before or after the migration. This setting is optional.

Flush log to disk after

Specify the number of log events (entries) after which you want CMT to close the log file and flush it to the disk.

 

Leave the field blank or specify 0 or 1 to log continuously until the migration completes.

 

Please note that all the logs are flushed to the disk after they close irrespective of the value specified in this field.

 

Note: The specified value in the field only forces CMT to update the log file after a specified number of entries (events). It may improve processing in certain environments but if CMTProxy terminates during a migration, you also run the risk of missing complete information in the log file.

 

 

All the settings in the Advanced tab are pushed to the migration workstation performing the migration through the AdditionalSettings.xml file. If you haven’t changed the default Advanced settings, the .xml file is not used during a migration.

 

  1. A default name is specified in the Profile field. You must specify a descriptive name for the migration profile and do not use Default as the name.

  2. Click OK to save the migration profile settings.

  3. A confirmation box appears; click Yes to save these settings to the Notes Migrator database:

  1. A new profile by the name you specified in the Profile field is created. If you do not see it listed in the Data Pane immediately, you can refresh the Data Pane. Click the Refresh Profiles button.

To delete unused profiles, click the Delete Settings from migration server button. A profile cannot be removed if the profile has been used for end user migration.

4.12. Creating a Message Template

Notes Migrator manages communication with the end users to be migrated via Notes mail messages. These messages can be used for informational purposes only or they may contain action buttons with associated code designed to perform specific pre-migration tasks.

These migration messages are created using the Message Templates. For Message Templates with action included, there are additional settings used to control a workflow process. When an end user executes the action, a status message known as an End User Processed Migration Message is generated and returned to the Notes Migrator database via Notes mail. Once received, the message is used to update the status of the corresponding end user’s Person document. If the status indicates the action was successful, the user can be re-verified and be ready for migration.

For this process to work correctly the Notes Migrator database must be located on a Domino server and a Mail-In Database Document pointing to it should be created.

Notes Migrator comes with several predefined Message Templates designed to perform specific migration tasks. You can use these predefined Message Templates to create custom templates that may better suit your need.

  1. Click Message Templates in the Navigation Pane; the Data Pane displays a list of predefined message templates:

 

Each predefined Message template has a specific purpose. If you wished to create a custom template based on a predefined template, you need to select the predefined template before clicking the New Template button. For example, if you wished to create a custom template based on the Migration Message – Decrypt Encrypted Item template, then you must select the template prior to creating a new template.

  1. Select a predefined template and click the New Template button in the Data Pane.

 

Encrypted Sent Items may contain an encrypted flag but possess no encrypted fields. This means that even though they display as encrypted, they actually aren’t and will migrate without decryption. Encrypted mail fields (including Sent folder) will not be migrated to MS Exchange if they are not decrypted using the decryption tool.

  1. A new tab, CMT Template: Migration Message – Decrypt Encrypted Items, opens and displays a form where you can specify the details of the new Message Template. Notice that the tab clearly specifies that the new CMT template is based on the Migration Message – Decrypt Encrypted Items predefined template. However, when you save this template with a new name, the tab will reflect its new name.

  2. Customize the CMT new template. Refer to the table below for details on settings.

  3. Once all the details have been specified, click Spell Check to ensure there are no spelling errors in the message.

  4. A message box appears to confirm that no misspellings were found. Click OK to close the message box. Next, save the new template. Click Save & Close.

The following table describes the values for each setting.

Settings    

Description

Template Name

Specify a name for the template that best describes the purpose of the new message template.

Template Type

Specify the type of the new message template, such as Email Only or Contact Synchronization. Refer to the Predefined Message Template Types section below.

Return Notification

Specify if you want a return notice to Notes Migrator from the end user when the message is received and the required action is performed.

Requires MSI Attachment

Specify whether the .MSI file is required to be attached prior to sending.

From

Specify the name of the entity sending this migration message to end users (for example, Migration Coordinator).

Subject

Specify a brief description of the purpose of the new template.

User Action Required

Check this box if migration for this user cannot proceed until the user performs the embedded action within the message.

 

This check box also indicates that the user will remain in the Pending Reponses view until they perform the end user action in a particular message template.

Pre-migration

Select this if the new message is sent to the user, and requires the user to perform an action that will prepare user data for migration.

Post-migration

Select this if the new message is for use after a user’s migration has taken place, and is typically informative, no User-Action Required.

Body

Specify a customized message

 

*Note that any buttons in the message template must be edited and saved to sign these with a Notes ID that is part of the Domino system ECL.

 

The new template is saved and it appears in the list of existing templates.

4.13. Types of Predefined Message Templates

Notes Migrator comes with several predefined Message Templates which are designed to perform specific migration tasks. The information contained within these predefined templates can be modified to tailor them to a client’s needs. Predefined Message Templates can be of the following types depending on the actions they perform:

  • Email Only

  • Contact Synchronization

  • Decrypt Encrypted Items

  • Archive Discovery

  • Archive Processing

Email Only

As the name implies, Email Only is designed for informational purposes only and does not include any action buttons. Email Only templates can be used to keep the end users informed on the progress of the migration project. For example, end users can be sent an email with the migration schedule for their department. This can help them plan for when their email will be migrated.

The fields within each predefined message template should be modified to make it specific to the client. An example is shown below.

For a template to be information-only, its Template Type field should contain the value Email-only and Pre-migration option should be selected. Although, if you are sending a message to end users informing them about the successful migration, then you can also use Email Only Template Type and select Post-migration.

Contact Synchronization

When a Contact Synchronization migration message is sent to an end user, the user simply clicks the button in the message. This launches the iNotes_DoSync() agent that ships with Lotus Notes, and pushes/resyncs all contacts in the Personal Name & Address Book (pNAB) to the hidden $PeopleGroupsFlat view. Now that these contacts are in the mail file, they can be migrated.

Decrypt Encrypted Items

When a Decrypt Encrypted Items migration message is sent to an end user, the user simply clicks the button in the message. This initiates an agent that will decrypt any encrypted items in the mail file, so they will migrate as clear text.

Archive Processing

When an Archive Processing migration message is sent to an end user, the user clicks the button in the message and this allows the script to search for the Archive Database Templates locally on the end user machine, find it, and copy/replicate it to a specified location on the Domino server or file server or copy into end user’s existing Domino mail file.

The location to copy is specified in the Notes Migrator Settings document. The script will only search for templates that are specified in the Notes Migrator Settings document. Refer to the End User Migration Settings configured in the Notes Migrator Settings document.

4.14. Signing a Button in a Message Template

  1. Open a Message Template

  2. Click on Edit Document

  3. Right-click on the button and select Edit Button:

  1. A code window will appear, type the word sign, and then delete the text:

  1. Click Save and Close.

The button will now be signed with the appropriate administration ID, and end users will not receive execution security (ECL) alerts when they click the button within the message template.

4.15.    Importing Exchange MDb’s

Notes Migrator will need to have a reference to the Exchange MDbs that are available to be migrated to.  To import these, follow the below steps.

  1. Select 5. Import Exchange MDbs in the Navigation Pane

  2. The Data Pane will display an empty view of Exchange MDbs:

  1. Click the Import Mailbox DBs from AD button to import the available Exchange MDbs

  2. Select the appropriate Mailbox Databases from the list to be used and click the Set Use Flag button.

 


This is not required for Office 365 Migrations.

 

4.3. Configuring Mail File Processing

Migrator for Notes collects and manages the settings essential in performing a successful migration. These settings are located under Configuration in the Navigation Pane.


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 Migrator for Notes User Guide for Office 365 Migrations for additional information.

4.1. Configuring Required Settings

Domino Settings

The Migrator for Notes Settings document displays. In the Settings document, the Required Settings -> Domino tab displays by default.


You can view the description of each field in each tab by clicking its corresponding question mark icon . For example, click and hold the mouse pointer on the question mark icon next to the Mail Server field to read its description.

Before any migration can be performed, the Required Settings tab must be completed. Two of the most important entries in this tab are the Mail Server and the Domino Directory. The specified Mail Server name is used to access the Domino Directory. The Domino Directory is used to retrieve the information required to import and create the User Mail, Rooms & Resources Databases, Mail-in Databases, and Discussion & Document Library Databases control documents.

These control documents are critical to the migration process and in their absence, migration information cannot be collected for a given item, and therefore, the item cannot be migrated. The control documents are used extensively during the remaining migration processes.

The following table describes the values for each setting.

Settings    

Description

Mail Server

The Domino server that Migrator for Notes will use for importing users and for sending Migration Messages.

Domino Directory

The Domino Directory name that Migrator for Notes will use for importing users, as found on the Domino server. Up to five additional Domino directories can be set by checking the box.

Server Mailbox

The mailbox filename that Migrator for Notes uses for sending Migration-related messages to selected users (for example, mail.box).

Audit Domino Encrypted Items

When running Audit on user mail file, specifying Yes will check for encrypted items in the mail file. If encrypted items are found, you can either send the user an email message with a button that decrypts encrypted items so that they can be migrated, or you can send the user a message with document links to the encrypted items so that they can print them prior to migration. You can even do both if you have some reason to want a list of messages that had been encrypted before the decryption agent was run.

Audit Domino Mail Rules

When running Audit on user mail file, specifying Yes will check for the number of rules in the mail file. If rules are found, you can send users a list of their Rules that will help them in creating the rules in Outlook after migration.

Audit Exchange Migrated Data

Enables auditing of migrated data in Exchange. Exchange Auditing should be enabled before data is migrated. Audit reports can be found the \logs directory on the migration workstation(s).

This is a post-migration validation process that indicates the state of documents which have been migrated by Migrator for Notes. This feature can be useful in environments as a validation check for data integrity. In addition, this can be used to audit results to reduce the size of user Domino mail files or archive databases after the migration phase on the Domino servers and user's workstation replicas. For example, removing documents with a Migration Status of 1 would leave only non-migrated data or documents that could not be migrated completely due to malformation or size restrictions in Exchange from a source database.  

Important: Consult your organizations data retention policies and regulatory compliance requirements before modifying source data. Full backups of the original source data may be required (and maintained post migration) before modifying working replicas to ensure regulatory compliance.

Audit embedded eml attachments

Enables auditing of eml attachments inside the message bodies to assist with migration troubleshooting. Results will be reported on the user document in EMM. This is not required for migration processing unless directed to enable this by Binary Tree's Product Support.

Additionally, a flag can be enabled and adds the field BTFoundEML to documents in source mail files where auditing finds eml attachments inside the message bodies.

Audit calendar unsupported patterns

Enables auditing of calendar items where the user is the Chair for Notes custom repeating meetings and generates document links for meetings that are not supported by Outlook. This will use the Migration Date if set or the current date and include meetings from the date specified and future meetings. The audit adds the reported data to the Calendar audit RTF report for the account and can be sent to end users with the Remediation Summary Message Template.

If enabled the audit can be specified to verify meetings where the user is the Chair, an Invitee or both. Additionally, label text can be added to the reported data to specify if the user is the Chair or the Invitee.

User Notification Style

Individual Notifications: Select if you want to send individual notification to each user and each mail/form will only have script for one action.

 

Combined Notifications: Select if you want to send one migration notification to each user and the notification/message to contain multiple selected forms, such as decrypting encrypted messages and synchronizing contacts and journals with mail file.

Enable this CMT db for Notifications

Click this button to create a Mail-In database document on the Domino Server for the Migrator for Notes database, and enable the database to receive User Notification responses. This database must be hosted on a Domino server.

 

Mail-enabling Migrator for Notes Database

A Mail-in Database Document is required for mail to be delivered to the newly created server copy of the Migrator for Notes database. The procedure copies the database to the server and creates a Mail-In database document for the Migrator for Notes database.

  1. Create a mail-in database for Migrator for Notes database. Click on the Server Db Copy and Mail-In Db Doc button to create a copy of the Migrator for Notes database on the Domino server and configure the Mail in Database document

  1. The Does Migrator for Notes already exist? dialog box opens; click Yes (and skip to step 5):

  1. If you are working with a local copy of the Migrator for Notes database, then click No. The Create a db copy? dialog box opens.

  2. Click Yes to create a copy of the local Migrator for Notes database on the server:

  1. If you clicked Yes in the Does Migrator for Notes CMT already exist? dialog box, the Choose Application dialog box opens. Locate the Migrator for Notes database in the CMT folder on the server, and then click Open.

The Fullname for the mail-in db doc dialog box confirms that the mail-in database for the selected server-based Migrator for Notes database does not exist, and prompts you to specify a name for the mail-in database. After specifying the name, click OK.

 

  1. In the Open the new mail-in doc? dialog box, click Yes to open the mail-in database.

The mail-in database document for Migrator for Notes opens.

  1. To verify the creation of the mail-in database, you can also launch Domino Administrator, open the Domino server, and access the Mail-In Databases and Resources folder under the People & Groups tab:

  1. Double-click the document to open and review

  2. Once the mail-in database is successfully created, the Open Mail-In Db Doc button replaces the Server Db Copy and Mail-In Db Doc button. Clicking it opens the database document for a review. Clicking the button with the X sign on it will remove all pointers to the location of the mail-in database.

    

 


The Notes ID that is used to sign the Notes Migrator database must have rights to add a new Mail-In Database Document to the server Domino directory. If the following error message is displayed, the Notes ID does not have appropriate rights.

Wor154

If you do not have the appropriate access rights to perform this action, see the onsite Domino System Administrator for help.

 

  1. It is recommended that after copying the database to the server, you delete the database from the local client folder. To remove it, right-click on Notes Migrator on Local. Select Database, and then Delete. The Lotus Notes client prompts that the database and related documents will be permanently deleted. Click Yes to delete the local database.

Modifying the Inbound Processing Agent

Once you have mail-enabled the database, you need to modify the Inbound Processing agent to view the updates. Perform the following steps to run the agent.

  1. Install Domino Designer on the workstation where Notes Migrator Domino database is located

  2. Launch Notes Migrator Domino database in Domino Designer

  3. Expand Shared Code and select Agents

  4. Select the InboundProcessing agent as shown below:

  1. Double-click InboundProcessing to open the InboundProcessing Agent Properties

  2. Click the Security tab

  3. The Administrator should be listed in the Run on behalf of section

  4. In the Set Runtime security level: field, select Allow Restricted Operations with full administration rights

  5. Once you've edited the agent, close the Properties box

  6. Close the Inbound Processing – Agent tab

  7. Save the changes

  8. Click Sign


This agent runs before new mail arrives and the Domino router must be set to allow these types of agents to run. To enable this option, go to Router/SMTP -> Restrictions and Controls -> Delivery Controls tab and set the Pre-delivery agents option to Enabled.


The Notes ID that signs this agent does require security rights on the Domino server to run agents.

 

LDAP Settings

  1. Click LDAP under the Required Settings tab:

In this tab, specify the Active Directory information to resolve users by matching them between source and destination platforms via Lightweight Directory Access Protocol (LDAP). To use this option, specify the required details.


LDAP configuration is not specifically required for Office 365 only migrations.

Use the following table to enter the correct values for each field:

Settings    

Description

Domain

The common name of the Active Directory domain. For example, binarytree rather than binarytree.com.

LDAP IP Address or Host Name

The fully qualified LDAP server name, IP Address, or resolvable DNS name of the Active Directory server. (e.g. PC-XP-01. binarytree.com or 192.163.15.12).

LDAP Port

Specify the LDAP port.

The default port for LDAP is 389.

The default port for SSL LDAP is 636.

Login ID

The AD domain account that has read rights to the target AD domain.

For example: administrator and not <domain>\administrator

Password

The password associated with the ID specified in Login ID.

Validate Settings

Click to validate the specified values to ensure that you are able to connect to the domain in Exchange where the end users will be eventually migrated.

LDAP Directory Base (Base DN)

If LDAP settings result in a successful connection, then this field is automatically updated.

Specify the directory base for all LDAP queries. The query settings will enable the search in AD to ensure that users are getting resolved against the right container ‘directory’ within AD.

Example: DC=btexchange2k7,DC=com

Quick Check

Full Check

If you want to search only the first ten users, select Quick Check; and if you want to search all the users, select Full Check.

Validate Query Settings

Click to validate the values specified in LDAP Directory Base to ensure that query string is resolving users and returning the number of resolved users.

 

  1. Specify the connection settings and then validate them by clicking the Validate Settings button:

  1. The LDAP Connection Settings Test Results message box displays indicating that the settings were validated and the connection was successful; click OK:

  1. Notice that the LDAP Directory Base (Base DN) field is automatically populated

To ensure that the specified directory base, where all LDAP searches will be conducted, is correct; you should validate this setting as well; click the Validate Query Settings button:

  1. The LDAP Query User Settings Test Results message box displays; the query setting is validated and some records are returned; in a production environment, ten records should be returned always; click OK:

Additional Settings

  1. Click the Additional tab under Required Settings

 

  1. Configure these settings with the names of the views to locate and import User and Mail-in Databases information. Also, specify the Migration Status Codes that can be assigned to users’ mail and databases control documents. You can assign a code to a user to update its status and view users based on their status codes. This helps in providing a better picture of the migration progress.

The following table describes the values for each setting:

Settings    

Description

CMT Migration Server

Specify the network hostname or IP address of the machine that is running the migration server.

CMT Program Directory

Specify the complete program directory path to Notes Migrator installation. This location will be used to launch the migration engine when the migration is triggered off.

 

Note: During the installation of Notes Migrator, if you had specified a destination folder path other than the default (C:\Program Files\Binary Tree\CMT Exchange), then you must replace the default path specified in the CMT Program Directory field with the modified path. In failing to do so, the migration engine will not launch when the migrations are set to go off.

Use Secure Web Services

Specify whether the web service calls are made to an XML server configured for secure access. Note that additional steps are required to secure the web services. The default selection is “Yes” which uses the CMT eService COM object to access the XML server.

 

Refer to Appendix E: Securing Notes Migrator Web Services with Windows Authentication for additional steps if you select Yes.

I have multiple control Centers

This option appears if the multiple Migration Control Center advanced feature is enabled on the Other Setting tab. Check this option to define the IP addresses of the Control Centers.  When enabled, the Set Migration Status options include Set Migration MCC and Clear Migration MCC options.

Migration Server Control Center IPs

Appears if “I have multiple control Centers” is checked. This field is used by the Set Migration Status agent.

Values must be entered as follows:

Workstation#=IP address of Notes Migrator Control Center

For example:

1=192.168.1.0

2=192.168.1.1

3=192.168.1.2

User Import View

Specify the view in the Domino directory that Notes Migrator database will use for importing users. Use the People view unless there is a custom view that you have created.

Mail-In Databases Import View

Specify the view in the Domino directory that Notes Migrator database will use for importing mail-in databases and resources. Use the Mail-In Databases view unless there is a custom view that you have created.

Mail-In Databases View Category

This is the NAB Mail-In database view category used for importing Mail-in Databases and Resources. Use the “Databases” default unless Domino is using a language other than English. Change this value to what is displayed in the NAB Mail-in Databases view.

Migration Status Codes

Specify a personalized list of status codes that will be used during the migration project. These codes can be assigned to users’ mail and databases control documents. If these status codes are assigned during the different phases of the migration process, timely status reports can be produced. These status reports will help provide a better picture of the migration progress. With this type of information, you have more control over the migration project and can react quickly to any identified issue. Adjustments can be made to help fine tune the migration schedule by adding more or different resources. Status codes must be separated by a new line. A list of status codes has been specified for you. You can either retain or change these status codes depending on your need.

CAS Server

Specify the Exchange Client Access Server (CAS) name. If a name is specified, then the matching process will use the following URL to resolve users. https://[servername]/autodiscover/autodiscover.xml

 

However, if you have specified the full URL to the Autodiscover service, then the URL will be used to resolve users.

 

This field is required for delegation migrations.

Username

If only the CAS Server name or IP address is specified in the CAS Server field, then you must specify a valid username for the authentication process that takes place on the CAS server. Note that the username should be in the following format for on-premises Exchange: <domain>\<username>. For Office 365 the format should be username@domain.com.

 

If you have specified a full URL (with https://) in the CAS Server field, then you can leave this field blank for on-premise migrations.

Password

Specify the password associated with the username provided in the previous field.

 

If you specified a full URL (with https://), then you can leave this field blank for on-premise migrations.

Powershell Admin Credentials

For on-premise Exchange servers, the credentials are of the form [Domain]\[Username].

For Office 365, the credentials are the SMTP address used to pass credentials to Office365 for remote access, for example o365Admin@tenant.onmicrosoft.com

Powershell Admin Password

Appears if Office 365 is in use

Use the Set PowerShell Password button to update this field. This will request the password and record it using the AsSecure PowerShell method.

This is not required for clicking the Notes Migrator PowerShell buttons, if this is not entered the buttons (such as Set Full Acccess) will ask for the password when processed.

PowerShell Logging Path

The MS PowerShell used when generating, executing, and logging PS1 script. This path can be edited on User Provisioning tab.

Default Reporting Path for Matching

Specify the reporting path used by the matching process. The default path is C:\Matching\.

Enable PowerShell Modern Auth

Appears if Office 365 is in use

Set to Yes to enable the use of the Exchange Online module for PowerShell processing. This will use Modern Auth connectivity to Microsoft Online services, removing the Basic Auth connection processing.

Enable Modern Auth for Migration

Appears if Office 365 is in use

Set to Yes to enable the use of Modern Authentication for Migrations. The Office 365 tenant must be configured to use Modern Authentication.

Autodiscover Username

Autodiscover credentials to be used during creation of the profile used by the migration engine.

For on-premise Exchange servers, the credentials entered should be the UPN (User Principal Name), for example: UserName@Example.Microsoft.com

For Office 365, the credentials are the SMTP address of an account in the Office 365 domain, for example: o365Admin@tenant.onmicrosoft.com.

 

Note: This is used if a migration worker does not have an account specified and is a fall back option. This is not required if a migration farm is being built using AWD.

Autodiscover Password

Enter the password associated with the Autodiscover account entered above.

Customer Name

Specify the Customer name that you would like in the status report.

Send Customer Status Report To

Specify the Group Name or SMTP addresses of the persons that should receive the status report.

Send Operator Status Report To

Specify the Group Name or SMTP addresses of the persons that should receive the full status report.

Migration Status Report Path

Specify the working path for migration status reports.

Create a combined report for multiple Migration Management databases (up to 5 additional)

Check this option to specify up to five additional migration management databases to include in a combined report.

 

4.2. Configuring Email Repliability

Click the Email Repliability tab to specify the appropriate values for the Domino environment:

Refer to the table given below for a brief description of all the settings in the Email Repliability tab.

Settings    

Description

Past and Present Domino Domains

The Domino domain names that are stripped from the email addresses and result in a valid and reply-able address regardless of domain name changes over the years. Enter a comma-separated list of all domain names in Domino, including the Notes Integration domain – no @ character is necessary.

Note: These are Domino domains, not SMTP or Internet domains, so it would more likely be ACME or ACME-NOTES, rather than acme.com.

Last Name Translation Update

This field is automatically populated during the Name Translation Update Process. This value will indicate the last time the Domino Directory was searched for updates.

Name Translation Database

The Name Translation Database field allows you to browse for the primary database to use for Name Translation lookups. This would typically be the current Notes Migrator.nsf. A warning will appear if you attempt to save the configuration without defining the Name Translation Database.

Name Translation Failover

The Name Translation Failover field allows you to optionally set the path to the primary failover database used for Name Translation lookups. The failover database is used if the primary database is inaccessible. This database should reside on the Domino server.  If a local (workspace) path is used, the EMM database must be replicated to the same relative path on all workstations.

Powershell bulk matching batch size

When using the two-step bulk PowerShell matching process for address translation entries, this is the number of records that will be presented in each matching .csv file. The default value is “2000”.

Note: this option is only available to Exchange on-premise migrations.

Table

The Name Translation Database table allows you to set the Name Translation Databases and Name Translation Failover Databases on multiple workstations. Click Set selected to define a Name Translation Database and Name Translation Failover for the selected workstation to use instead of the primary (default) databases defined above.

 

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: 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.

 

 

 

Lotus Notes Migration ID

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.

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.

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.

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 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:

4.7. Configuring Rooms & Resources Settings

  1. Click Rooms & Resources; this tab has two sections. Review the general description provided for both the sections.

Rooms & Resource Migration Options

The Rooms & Resource Migration Options section enables you to configure settings to determine how resources are handled during a migration:

The following table describes the values for each setting:

Settings    

Description

Rooms and Resources Target

Specify if you want the room or the resource to be migrated to a Location field, or be appended to the message body, both, or none.

Room Label

Specify the label you wish to be prefixed to the migrated room text.

Resource Label

Specify the label you wish to be prefixed to the migrated resource text.

Online Label

Specify the label you wish to be prefixed to the migrated online text.

Location Detail Indicator

Specify the text you wish to appear when room or resource text is not included in the Location field.

Room Resource Separator

Specify a string that separates the location, room, resource, or online values that are included on the Location field.

 

Rooms & Resource Settings

Configure these settings if you want to migrate Rooms and Resources. The first step of the process involves importing Rooms and Resources into the Notes Migrator database. Lotus Notes stores multiple Rooms/Resources in a single database. Notes Migrator allows you to import and create a separate .nsf for selected Room/Resource and copy its corresponding calendar into the newly created .nsf. Once all the Rooms/Resources that you want to migrate have been separately imported, you can export them to Notes Migrator migration engine and migrate them.

The following table describes the correct values for each setting.

Settings    

Description

Rooms and Resources Import View

Specify the view in the Domino directory that Notes Migrator will use for importing the different Rooms and Resources. Use the Rooms Resources view unless there is a custom view that you have created.

Target Server

Specify the Domino server that Notes Migrator will use when creating separate .nsfs for each Room/Resource. This must not be blank.

Target Path

Specify the destination path where separate .nsfs will be created for selected Rooms/Resources.

 

The path is relative if the destination is a Domino server. If the destination is a file server, full path must be specified.

Database Template

Specify the template that will be used to create the new room or resource database to migrate.

Set Subject to Chair

Set this to ‘Yes’ to enable overwriting the booking subject when importing rooms and resources. This will set the subject to the booking Chair for migration to Outlook (removing the booking subject entirely). This does not impact the existing Notes room and resource bookings. Selecting ‘No’ will retain the original booking subject for migration.

Subject Prefix

This is used if the subject for imported booking will be overwritten with the booking Chair name. The text used will be prefixed in the imported booking subject.

4.8. Configuring Replica Settings

The Replica Settings are used when using a Domino staging server. A staging server is often used when the Domino mail servers are not on the same LAN as Exchange and/or the migration environment to mitigate migration throughput degradation due to the network. Staging servers are also used if you will be using replication formulas to filter the data intended for migration.

The following table describes the values for each setting:

Settings    

Description

Staging Server(s)

The Name of each of the staging servers to be used for creating replicas separated by a new line or a comma.  For Example: Stage01/Contoso

Staging Server File Folder

The folder name in which to place the newly created replicas.

Replication Formula Option

Specify My Own Formula: Use the field below to specify your own selection formula.  Be sure to enter the ENTIRE formula, starting with SELECT (e.g. SELECT @All to replicate all Notes items).

 

Build Formula Via Selections: The number of calendar and email days and select the forms to include in the replica and a replication formula will be built for you.

Replication Formula

If you are specifying your own replication formula, enter it here.

*Note: You must be familiar with Notes formula language.

Number of Calendar Days

If you selected Build Formula Via Selections enter the number of calendar days to include in the replica. You will be prompted for a date upon replica creation and it will use this date and the number you specify to calculate the number of calendar days to include.

Number of Email Days

If you selected Build Formula Via Selections enter the number of email days to include in the replica. You will be prompted for a date upon replica creation and it will use this date and the number you specify to calculate the number of email days to include.

Forms to include in Replica

Select or enter all of the different forms to be included in the replication formula.  If the form name is not listed here, it will NOT be included in the replication formula and will not be in the replica.

Replicate Each Replica at Creation

Selecting “Yes” will replicate each newly created replica as it is created. It will also cause the agent to run very slowly depending on the replica settings. It is recommended to use this as a one-off replica creation rather than for the entire list of users/mail-in databases.

Exclude Trash from Replica Comparison

Set to Yes to exclude Trash (Soft Deletion) document counts from the replica comparison total document counts. Set to No for default processing to count all documents.

4.9.    Configuring Delegation

  1. Click the Delegation tab.

  2. Validate Yes is selected for the Audit Delegates option. If set to No, set to Yes and save and close the document, then reopen the document to view the other configuration settings.

  1. The PowerShell application impersonation set option is a prompt to set application impersonation. Set application impersonation using the steps below and then set this option to Yes.

    1. Open the Exchange Management Shell or configure a PowerShell session to connect to either an on-premise or the appropriate Office365 server.

    2. In the shell, enter the following command to configure application impersonation:

New-ManagementRoleAssignment –Name:impersonationAssignmentName –Role:ApplicationImpersonation –User:CMTMigrationAdmin@myDomain.org

Where CMTMigrationAdmin@myDomain.org is the SMTP or login name of the migration account, or the name of security-enabled group used for migration.

  1. To run delegation migrations as a scheduled process, set Run delegation as a scheduled process to Yes (default).

  2. Click the Enable scheduled agent button and select the Domino server that will perform the migration. The agent will run in the background of the local Notes client if the Local option is selected.

Scheduled delegation migration runs in the background on a workstation or server. If running locally, Notes must be running and background agents must be enabled on the client.

The scheduled delegation migration agent runs once a day at 3:00 AM.  Note that if the agent is changed to run at a time interval that is too short, the PowerShell tasks may not have time to complete.

  1. Click the Delegate Settings tab:

  1. After auditing the user's mail files with Active Delegation enabled, you are able to send an email that displays the user's current delegation settings, so they can decide whether they are still valid for migration to Outlook. You should allow the users a period of time to review before rerunning the mail file audit to collect any updated settings.

The options below allow you to customize the message to exclude certain users and groups that delegation does not need to be reported to the users about. Typical exclusions are standard Administrative groups or administrative IDs that are by default listed in the HCL Domino Mail files within the environment.

4.10. Configuring Source Updates

The Source Updates Settings are used to configure the Fix Folders agent.

 

The following table describes the values for each setting.

Settings    

Description

Replace Blank Folder Names With

The folder name to be used when updating Blank folder names. This will update blank (Null) folders at the folder root, blank folders within the folder hierarchy and blank folders at the end of the folder hierarchy. This will numerically increment (1, 2, 3, etc.) if more than one blank folder exists. Replacements will be done for: "", " ", " \", "\ \","\\" "\ "

Append Personal System Folders With

The folder name to be appended to Outlook system folders that have been created at the folder root of the Notes personal folders. This will not update the Notes system folders. The folder names will be appended with a hyphen "-" and then the name to be used.

Check for Duplicate Folders Names

Option to check for duplicate personal folder names. If enabled, the agent will check each folder to determine if there is a duplicate and then append "-" and an incremented number to make the name unique.

Check Duplicate Folders on Remediation Only

Option to have the duplicate checks be performed on the first Fix Folders processing or only on second processing runs. This requires the option for duplicate checking to be enabled. Set to "No" to disable this and have the Fix Folders agent always check on the first pass for duplicates or set to "Yes" to have the duplicate checking skipped on the first pass and only be run on subsequent updates. This is enabled as the default configuration.

Maximum Duplicates Checks per Folder

Numeric setting for the number of duplicates to be checked on a single personal folder. If there are more duplicates of a single folder name than the number specified, the duplicate checking for that folder will be skipped. Requires duplicate checking to be enabled.

Remove Personal Folder Aliases

Option to remove hidden Alias from Notes Personal folders. This will remove all aliases in the Notes folders except for the system folders. This should only be used if an issue with an alias is found to cause a problem with migrations.

Email end users with Folder Renames

Option to send an email to the end users with a list of the folder names that were changed. The email will include the original folder names and the new folder names.

Enable Replacement of Specific Characters

If enabled, this will allow for a defined set of characters to be removed from all personal folder names and to have those replaced with a different character. This will not update system folders and should only be used if a specific character is found to cause an issue with migrations.

Replacement characters in

Personal Folders

This is a text list of characters to be replaced and should be a comma separated list if more than one character should be replaced. This requires the character replacement to be enabled and should not contain a backslash "\" as that will replace the Notes folder hierarchy or be Null (blank).

Character to be used for replacements

This should be a valid character that is not known to cause migration issues and should not be Null (blank). Typically, a hyphen "-" is recommended.

Remove obsolete local group members

This can be enabled to verify any local personal group membership (not system groups membership) and remove notes formatted (Canonical) membership addresses that are no longer in Domino (e.g. user accounts for leavers that were removed from Domino). The Email Repliability in Notes Migrator is used for these checks and should be populated prior to running the processing, if enabled. Note that these members cannot be automatically replaced once they are removed.

Rename local canonical group names

This can be enabled to validate local personal group names created by end users to check if these have a canonical (Domino) format (e.g. Personal Group/Local). If enabled, the processing will rename these by replacing the “/” with a “-“ to prevent Notes treating the local group name as canonical for migration.

 

4.11. Configuring Other Settings

Click the Other Settings tab to configure settings to control how encrypted items are handled or mail rules found in the user mail file. In this tab, the Migration Checklist and Advanced settings can also be configured:

The following table describes the values for each setting:

Settings    

Description

Send Rules Email

Configure these settings if you will be sending users their mailbox rules before migration.

From

Contains the profile name that will send the mail regarding mailbox rules to users. Migration Coordinator is specified as default.

Subject

Contains a subject that briefly describes the purpose of the mail. Your Mail Box Rules is specified as the subject by default.

Body

Can contain any information that you may want to share with the end user about this procedure.

Rules to Include

Includes all rules or only the rules that are enabled. Select All Rules.

Encrypted Items Migration

Choose how to migrate encrypted messages. Valid options are:

  • Require decryption action and migrate into the body

  • Migrate into a Notes database as an attachment

Note: Enabling the Migrate into a Notes database as an attachment option will increase the size of each migrated item containing encrypted content. The Lotus Notes client, original Notes ID, and decryption keys are required on the workstation used to view the encrypted content of the migrated items.

Send Encrypted Items Summary Email

Configure these settings if you will be emailing users a summary of their encrypted items.

The fields in this section display only when Require decryption action and migrate into the body option is selected.

From

Contains the profile name that will send users the mail with a summary of encrypted items. Migration Coordinator is specified as default.

Subject

Contains a subject that briefly describes the purpose of the mail. Your Encrypted Items is specified as the subject by default.

Body

Can contain any information that you may want to share with the end user about this procedure.

Template Name (.ntf)

This appears if you have selected Migrate into a Notes database as an attachment. Specify the template name in this format:  filename.ntf

 

EncryptedContent.ntf is the default template that ships with Notes Migrator. This template will be installed on every migration workstation during the product installation. This template will need to be signed with the appropriate Lotus Notes Administrative ID on all workstations. 

 

You can use any database template; however, you will need to manually distribute the template to all migration workstations.

 

Binary Tree recommends that use of an alternative template or any changes to EncryptedContent.ntf be thoroughly validated prior to production use.

Attachment name in Exchange

This field displays only when the Migrate into a Notes database as an attachment option is selected.  Specify the database name in this format:  filename.nsf

Text included with attachment

This field displays only when the Migrate into a Notes database as an attachment option is selected. Customized text can be added to the migrated item to provide end-user instructions or information. The default text is as follows:

 

Portions of this document were encrypted with Lotus Notes encryption. This content has been stored in the attached Lotus Notes database during migration to preserve security. You may view this content by opening the attached file on a workstation that has a Lotus Notes Client and the recipient’s Notes ID.

Migration Checklist

The Migration Checklist is a personalized list of tasks which can be used to help manage the migration project. Determine, then classify or group the major steps you consider necessary to manage your migration project. Determine the sequence, timeline, and description for each migration task and enter them into the Migration Checklist.

Enable Recovery

This setting defines the default value for the Enable Recovery setting in the migration profiles’ Advanced tab.

 

If the Enable Recovery setting is set to Yes in the Advanced tab of a migration profile, it enables tracking of processed messages during migration. So, if the migration process terminates unexpectedly, this feature prevents the application from reprocessing messages that were migrated during the initial run of the migration. Click here to learn more about configuring the Enable Recovery setting.

Disable MIME Cache

Specify Yes to disable the local cache database when processing messages using MIME.

Disabling this feature significantly impacts throughput when migrating MIME content from a Domino server.

Migrate Unfiled Documents

This option determines if “unfiled” documents will be migrated. “Unfiled documents are documents in Notes that do not appear in any folder and can only be accessed from the “All Documents” view within the mail file. Documents may be unfiled if a user deletes a folder without deleting the documents or removes a folder it resided within. The unfiled folder name can be defined.

MAPI Custom Settings

Select Specify advanced MAPI parameters to override the default values for MAPI retry count and MAPI retry delay.

When configured, retries are attempted when the MAPI_E_NETWORK_ERROR (0x80040115) result code is encountered during any of the following MAPI calls:

  • Create attachment

  • Create folder

  • Create message

  • Modify recipients

  • Save folder changes

  • Save message changes

  • Save attachment changes

 

If the configured retry limit is exceeded, the migration is cancelled and Notes Migrator will begin the migration of the next user. If the migration is canceled in the middle of writing a document, the document will be partially written to Exchange. The default retry limit is set to 30 seconds.

 

Specify the Number of retries that will be attempted when the MAPI_E_NETWORK_ERROR (0x80040115) result code is encountered. Values ranging from 1 to 999 can be entered. The default number of retries is “9”. Note that entering “0” results in the default “9” retries being used.

 

Specify the Delay between retries in seconds between MAPI calls. The time is progressive. The number of seconds delay for a call is (retry # * delay). For example, if the retry delay is set to 1 second, and the retry count is 5, the delays between calls will be 1, 2, 3, 4, and 5 (progressively longer). If the retry delay is 1.5 seconds, the times will be 1.5, 3.0, 4.5, 6, and 7.5. Values ranging from 1 to 999 can be entered. The default delay is “1” second. Note that entering “0” results in the default delay “1” second being used.

MAPI Retry Failure Limit

When enabled, Notes Migrator tracks documents where one or more MAPI calls could not be completed successfully. If the number of documents where one or more MAPI calls cannot be committed to Exchange, the migration will exit with ‘migration failed’ status.

 

The document retry failure limit feature can be disabled by setting the value to ‘0’ or leaving it blank.

 

MAPI Retry

Notes Migrator makes multiple MAPI calls when migrating a document, such as creating the message header, writing the body, adding attachments, etc. When processing messages, the remote Exchange server may become unresponsive in such a way that MAPI calls to write data do not complete. The call is retried a number of times (using the preexisting feature known as MAPI Retry: the maximum number and delay between retries can be set in EMM) to fully migrate data to Exchange.

 

If any of the MAPI calls cannot be completed, the document will be considered as failed due to MAPI retries, and added to the total of failed documents. Document information is logged, the NoteID is removed from both the in-memory migration history, and the CMTProcessedNoteID-[shortname].txt crash recovery file.

 

Note that other types of failures, such as a corrupt message body which results in a failure, are not counted toward the MAPI retry failure total. These other types of failures are specific to the source data, whereas the MAPI retry failures are related to the ability to write to exchange.

 

If the number of documents with MAPI retry errors exceeds the failure limit, the migration will exit, and return ‘Migration failed’ status. This migration will not automatically requeue and must be requeued by the migration administrator to fully migrate the mailbox. When a migration is requeued, it may be migrated by any workstation. Any documents containing MAPI retry errors on the failed migration will be remigrated during subsequent migrations.   

 

If the migration terminates abnormally (crashes), the document being migrated when the crash occurs will not be retried, which is standard procedure for crash recovery in Notes Migrator. Any other documents containing MAPI Retry Exceeded will be remigrated. In this case, Notes Migrator will automatically restart the migration on the same workstation.

Process attachments greater than

The limit for the size attachments, in MB, that will be detached and processed as file attachment objects. A value of -1 disables this feature, and processes all attachments as MIME streams, similar to Notes Migrator versions 4.6 and earlier. A value of 0 will process all attachments as file attachments. The default value is 0 MB to process all attachments outside the MIME Stream.

Encapsulate special content

When enabled, documents containing special notes functionality or items such as button or stored forms will be migrated as an attachment in addition to being rendered in the message body. End users can then open the NotesMessage.nsf attachment to use the native functionality of the form.

Migrate documents as private

When set to ‘Yes’, the migration will migrate documents designated as private in Notes as Private in Exchange. This will also include messages decrypted in Notes prior to migration.

Convert UNC paths to links

Specify No if you do not wish the body of the documents searched for UNC (Exchange Naming Convention) links during migration.

If you specify Yes, CMT attempts to convert UNC links into actionable links.

Add category to calendar events

Field in Exchange. For example, if you specify Migrated with Notes Migrator in the field, then all the calendar events, such as meetings and appointments, will display this phrase in the categories field after they are migrated. It enables you to visually differentiate calendar events that were migrated into Outlook from those created natively in Outlook before or after the migration. This setting is optional.

 

Note: Any categories that are in the original Notes calendar event will also display in the categories field.

Process meeting with no end date using ICAL information

Specify Yes to use the ICAL recurrence information to determine the repeat pattern when processing repeat calendar meetings with no end date.

 

Specify No to process repeat meetings with no end date without using ICAL recurrence information.

 

Note: When migrating a meeting with No End Date and this option is set to No, the meeting is migrated but limited to 250 occurrences.

Enable Advanced features

Select Yes to enable features used when migrating large environments or to cloud based services.

Enable Hosted features

Appears if Advanced features are enabled. Select Yes to enable features used when migrating hosted environments. This setting should only be enabled under the direction of Advanced Support.

Enable multiple Control Centers

Appears if Advanced features are enabled. Select Yes to enable features used when migrating with multiple Migration Control Center (MCCs). This setting should only be enabled under the direction of Advanced Support.

 

Sending Mail Box Rules

Notes Migrator allows you to send users their Mail Box Rules before migration occurs. You can define the From, Subject, text in the body, and which rules to include in the email sent to users.

Migrating Encrypted Items

Notes Migrator offers two solutions for migrated items that have been encrypted via Lotus Notes. The data may be decrypted as part of the pre-migration process, or the encrypted content may be attached to the migrated message in a Lotus Notes database during migration.

When the Require decryption action and migrate into the body option is selected, additional fields will be visible in the Send Encrypted Items Summary Email section to configure the From, Subject and text in the body of the summary email sent to end users.  If you select Migrate into a Notes database as an attachment option is selected, you will see new fields for the Template name, the Attachment name in Exchange and Text included with attachment.

Creating a Migration Checklist

  1. Click the Migration Checklist button to enter the steps, timelines, and tasks in the Migration Checklist Profile to use for your customized Migration Checklists:

  1. Starting with Step 1, click the down arrow button in the Timeline column.

  1. The Select Keywords dialog box is displayed. Select one of the provided keywords or enter a new one in the New Keyword field at the bottom of the dialog box and click OK to continue:

 

If the predefined keywords do not appropriately describe your timeline, you can specify a new keyword in the New Keyword field.

  1. Enter a description in the Task column and click Save & Close to complete:

  1. If you exit the document without saving, the following dialog box is displayed. Select Yes to save the Migration Checklist. If No is selected all new entries are discarded:

  1. After all the settings have been configured, click Save & Close to save all the configuration settings.

Enabling Recovery

As stated earlier, the Enable Recovery setting in the Other Settings tab defines the default value for the Enable Recovery setting (found under the Advanced tab) in the existing migration profiles as well as the new profiles you may create.

By default, it is set to Yes, so in all the existing migration profiles and the new ones you create, the Enable Recovery setting will also be set to Yes. However, if you were to change this setting to No in the Other Settings tab, and save the changed configuration settings, the following prompt will display.

If you click Yes in this dialog box, the Enable Recovery setting in all the existing migration profiles will change to No, and any new migration profile created will also have No as the default value in this field.

But if you click No in this dialog box, the Enable Recovery setting in all the existing migration profiles will remain Yes (the prior setting), however, when you create a new migration profile now, the Enable Recovery setting will be set to a default No.


It is recommended that you review the description provided for the Enable Recovery setting in the Advanced tab of migration profiles (Section 6.6) for a complete understanding of how this setting works.

4.11. Creating Migration Profiles

Migration Profiles define settings for certain groups of users. For instance, it may be desirable to have a profile where all executives have a filter that only migrates the last four years of mail and calendar to Exchange. Every user must have a Migration Profile set before migration can proceed.

Before you create a migration profile that contains filters to migrate specific user data, you must create a default migration profile. After the default profile has been saved, create migration profiles that will be used to migrate users. These profiles should have descriptive names, such as 90DayMailOnly or 4Years-Calendar-Mail.

Important! – The default migration profile does not have all values and should not be used for migrations. A new profile should be created to prevent problems with corrupting the backend database. This will help avoid problems during production migration.

  1. Click Migrate Profiles in the Navigation Pane:

  1. Click the Create New Profile button:

Each migration profile contains a source and destination setting that determines which mail items are migrated and if the migration is to a Microsoft Exchange server or to a .pst file.

When a migration is carried out, a migration profile must be assigned to specify how the migration should be performed. You can create as many migration profiles as desired.

  1. The Profile dialog box displays; the Source Options tab opens by default:

The following table describes the values for each setting:

Settings    

Description

Message Types

Specify the Migration Options. You can either select all message types or specify the types that you wish to be included in the migration (Mail, Calendar, Task, and Contact).

Date Filter

Specify a range of dates that will ensure that only the data that falls within the specified range is migrated.

 

The Date Filter will apply to all the selected message types. For example, if you select All message types, the specified date filter will apply to Mail, Calendar, Tasks, and Contacts.

Migration Log Level

By default, Notes Migrator creates a log file for every user that is migrated. In this field, you specify the level of detail you want in the logs. There are three levels provided.

  • Minimal

  • Normal (Recommended)

  • Verbose

 

Selecting Verbose significantly increases the size of the log files that are created. This is only recommended for troubleshooting purposes. Log files are located in the Logs subdirectory where CMT Exchange is installed, usually C:\Program Files\Binary Tree\CMT for Exchange\Logs.

Skip folders named

Specify a list of folder names from your Domino mail files that you would like Notes Migrator to bypass during the migration. This feature is useful if you have a customized mail template that may contain folders with non-messaging data. Specify folder names in the Skip folders named field. Separate entries by commas.

Migrate empty folders

Select to migrate empty folders in users’ mailboxes to Outlook.

Migrating Sent Items

In Lotus Notes, a mail message can exist in the Sent Items folder or in the Sent Items folder and a user-defined folder(s). In Outlook, a mail message can only exist in one or the other. This field provides two options.

  • Select Migrate to the Outlook Sent Items Folder, if you prefer the items to be stored in the Sent Items folder in Outlook after migration regardless of what other user-defined folder(s) it may have been stored in Lotus Notes.

  • Select Preserve custom folder name, if possible, if you prefer the items that exist in two locations to be stored in the user-defined folder after the migration.

Audit Notes UNIDs

During Migration

The migration worker will record an audit of the Notes source document UNID [unique identifier] for all items processed in a .csv file. This will be uploaded to the migration controller in the logs folder.

Ignore Privacy Flag

If set to ‘Yes’, this will not migrate any documents as private in Outlook. This will override the Settings | Other Settings option if that is set to ‘Yes’. This is typically useful for shared mailbox migrations.

 

  1. Click Destination Options:

The following table describes the values for each setting:

Settings    

Description

Migrate to Exchange Server

Select if you want the migrated data to go directly to the Exchange server.

Migrate to .PST file

Select if you want the migrated data to go to a .pst file.

 

The PST Folder Path field is added to the form when this option is selected.

PST Folder Path

Specify the path where you want the .pst file(s) to be stored. This must be a Windows drive and folder or mapped drive on the migration workers. A Windows UNC path should not be used.

 

When migrating to a PST file, the file name format will be “<User’s SMTP Address>-Notes Database ID.pst”.

Individual attachment size limit

Specify a size limit in bytes to filter individual attachments. For example, if you specify 1000, each individual attachment that is greater than 1000 bytes in size will be filtered out during migration.

 

Maximum message size cannot exceed 125 MB. This field should be set to 131072000 to avoid memory errors during the migration.

Attachment total size limit

Specify the total size limit of all attachments in a document in bytes. For example, a value of 10000 would allow only a total of 10000 bytes for attachments migrated per message.

 

Maximum message size cannot exceed 150 MB. This field should be set to 157286400 to avoid memory errors during the migration.

 

 


The default size limits for the attachment size limit fields are the maximum size we support.  This limit may differ in your environment.  We recommend testing your migration environment to confirm it supports our product limitations. If you experience memory errors with lower attachment sizes, we recommend lowering the default size limits in the attachment size limit fields until a memory error is not encountered.

  1. Next, click the Advanced tab

  2. Check the Enable Advanced Options box:

Advanced options are now displayed in the dialog box; configure these settings:

The following table describes the values for each setting:

Settings    

Description

Advanced Message Filtering Options

Configure these settings if you wish to filter the messages based on their various age limits.

Mail Age limit

Specify the number of days from the migration date to filter the mail messages. For example, if you specify 30, the application will only migrate messages that were created 30 days prior to the migration date.

Task Age limit

Specify the number of days from the migration date to filter the tasks (To Do Lists). For example, if you specify 30, the application will only migrate tasks that were created 30 days prior to the migration date.

Calendar Age limit

Specify the number of days from the migration date to filter the calendar events. For example, if you specify 30, the application will only migrate calendar events that will occur in the 30 days prior to the migration date.

Filter Repeating meetings

By default, all repeating meetings are migrated. Repeating meetings are filtered based on the specified age limit criteria only when you check the Filter Repeating meetings checkbox.

 

It should be noted that in case of repeating meetings, the filter applies to the date of the parent-meeting document and does not filter the series. This means that if the parent meeting falls within the specified date range, the entire series is migrated and if the parent meeting falls outside the date range, the entire series is skipped. The dates of the meeting recurrences do not matter.

Additional Options

Configure these settings to improve the migration throughput.

Enable Recovery

 

Specify Yes to enable the setting to track processed messages during migration. So, if the migration process terminates unexpectedly, this feature will prevent the application from reprocessing messages that were migrated during the initial run of the migration.

 

To disable this setting, specify No.

 

Refer to the Enable Recovery setting in the Configuring Other Settings section to understand how the default value for the Enable Recovery setting in the Advanced tab is determined.

Process as RTF

Specify Yes to override the default MIME processing and to process native Notes documents as Rich Text.

 

Note: Enabling this feature is not recommended.

Disable MIME Cache

Specify Yes to disable the local cache database when processing messages using MIME.

 

Disabling this feature significantly impacts throughput when migrating MIME content from a Domino server.

Convert UNC paths to links

Specify No if you do not wish the body of the documents searched for UNC (Exchange Naming Convention) links during migration.

 

If you specify Yes, CMT attempts to convert UNC links into actionable links.

Add category to calendar events

Specify a word or phrase in the field to add to the category field in Exchange. For example, if you specify Migrated with Notes Migrator in the field, then all the calendar events, such as meetings and appointments, will display this phrase in the categories field after they are migrated. It enables you to visually differentiate calendar events that were migrated into Outlook from those created natively in Outlook before or after the migration. This setting is optional.

Flush log to disk after

Specify the number of log events (entries) after which you want CMT to close the log file and flush it to the disk.

 

Leave the field blank or specify 0 or 1 to log continuously until the migration completes.

 

Please note that all the logs are flushed to the disk after they close irrespective of the value specified in this field.

 

Note: The specified value in the field only forces CMT to update the log file after a specified number of entries (events). It may improve processing in certain environments but if CMTProxy terminates during a migration, you also run the risk of missing complete information in the log file.

 

 

All the settings in the Advanced tab are pushed to the migration workstation performing the migration through the AdditionalSettings.xml file. If you haven’t changed the default Advanced settings, the .xml file is not used during a migration.

 

  1. A default name is specified in the Profile field. You must specify a descriptive name for the migration profile and do not use Default as the name.

  2. Click OK to save the migration profile settings.

  3. A confirmation box appears; click Yes to save these settings to the Notes Migrator database:

  1. A new profile by the name you specified in the Profile field is created. If you do not see it listed in the Data Pane immediately, you can refresh the Data Pane. Click the Refresh Profiles button.

To delete unused profiles, click the Delete Settings from migration server button. A profile cannot be removed if the profile has been used for end user migration.

4.12. Creating a Message Template

Notes Migrator manages communication with the end users to be migrated via Notes mail messages. These messages can be used for informational purposes only or they may contain action buttons with associated code designed to perform specific pre-migration tasks.

These migration messages are created using the Message Templates. For Message Templates with action included, there are additional settings used to control a workflow process. When an end user executes the action, a status message known as an End User Processed Migration Message is generated and returned to the Notes Migrator database via Notes mail. Once received, the message is used to update the status of the corresponding end user’s Person document. If the status indicates the action was successful, the user can be re-verified and be ready for migration.

For this process to work correctly the Notes Migrator database must be located on a Domino server and a Mail-In Database Document pointing to it should be created.

Notes Migrator comes with several predefined Message Templates designed to perform specific migration tasks. You can use these predefined Message Templates to create custom templates that may better suit your need.

  1. Click Message Templates in the Navigation Pane; the Data Pane displays a list of predefined message templates:

 

Each predefined Message template has a specific purpose. If you wished to create a custom template based on a predefined template, you need to select the predefined template before clicking the New Template button. For example, if you wished to create a custom template based on the Migration Message – Decrypt Encrypted Item template, then you must select the template prior to creating a new template.

  1. Select a predefined template and click the New Template button in the Data Pane.

 

Encrypted Sent Items may contain an encrypted flag but possess no encrypted fields. This means that even though they display as encrypted, they actually aren’t and will migrate without decryption. Encrypted mail fields (including Sent folder) will not be migrated to MS Exchange if they are not decrypted using the decryption tool.

  1. A new tab, CMT Template: Migration Message – Decrypt Encrypted Items, opens and displays a form where you can specify the details of the new Message Template. Notice that the tab clearly specifies that the new CMT template is based on the Migration Message – Decrypt Encrypted Items predefined template. However, when you save this template with a new name, the tab will reflect its new name.

  2. Customize the CMT new template. Refer to the table below for details on settings.

  3. Once all the details have been specified, click Spell Check to ensure there are no spelling errors in the message.

  4. A message box appears to confirm that no misspellings were found. Click OK to close the message box. Next, save the new template. Click Save & Close.

The following table describes the values for each setting.

Settings    

Description

Template Name

Specify a name for the template that best describes the purpose of the new message template.

Template Type

Specify the type of the new message template, such as Email Only or Contact Synchronization. Refer to the Predefined Message Template Types section below.

Return Notification

Specify if you want a return notice to Notes Migrator from the end user when the message is received and the required action is performed.

Requires MSI Attachment

Specify whether the .MSI file is required to be attached prior to sending.

From

Specify the name of the entity sending this migration message to end users (for example, Migration Coordinator).

Subject

Specify a brief description of the purpose of the new template.

User Action Required

Check this box if migration for this user cannot proceed until the user performs the embedded action within the message.

 

This check box also indicates that the user will remain in the Pending Reponses view until they perform the end user action in a particular message template.

Pre-migration

Select this if the new message is sent to the user, and requires the user to perform an action that will prepare user data for migration.

Post-migration

Select this if the new message is for use after a user’s migration has taken place, and is typically informative, no User-Action Required.

Body

Specify a customized message

 

*Note that any buttons in the message template must be edited and saved to sign these with a Notes ID that is part of the Domino system ECL.

 

The new template is saved and it appears in the list of existing templates.

4.13. Types of Predefined Message Templates

Notes Migrator comes with several predefined Message Templates which are designed to perform specific migration tasks. The information contained within these predefined templates can be modified to tailor them to a client’s needs. Predefined Message Templates can be of the following types depending on the actions they perform:

  • Email Only

  • Contact Synchronization

  • Decrypt Encrypted Items

  • Archive Discovery

  • Archive Processing

Email Only

As the name implies, Email Only is designed for informational purposes only and does not include any action buttons. Email Only templates can be used to keep the end users informed on the progress of the migration project. For example, end users can be sent an email with the migration schedule for their department. This can help them plan for when their email will be migrated.

The fields within each predefined message template should be modified to make it specific to the client. An example is shown below.

For a template to be information-only, its Template Type field should contain the value Email-only and Pre-migration option should be selected. Although, if you are sending a message to end users informing them about the successful migration, then you can also use Email Only Template Type and select Post-migration.

Contact Synchronization

When a Contact Synchronization migration message is sent to an end user, the user simply clicks the button in the message. This launches the iNotes_DoSync() agent that ships with Lotus Notes, and pushes/resyncs all contacts in the Personal Name & Address Book (pNAB) to the hidden $PeopleGroupsFlat view. Now that these contacts are in the mail file, they can be migrated.

Decrypt Encrypted Items

When a Decrypt Encrypted Items migration message is sent to an end user, the user simply clicks the button in the message. This initiates an agent that will decrypt any encrypted items in the mail file, so they will migrate as clear text.

Archive Processing

When an Archive Processing migration message is sent to an end user, the user clicks the button in the message and this allows the script to search for the Archive Database Templates locally on the end user machine, find it, and copy/replicate it to a specified location on the Domino server or file server or copy into end user’s existing Domino mail file.

The location to copy is specified in the Notes Migrator Settings document. The script will only search for templates that are specified in the Notes Migrator Settings document. Refer to the End User Migration Settings configured in the Notes Migrator Settings document.

4.14. Signing a Button in a Message Template

  1. Open a Message Template

  2. Click on Edit Document

  3. Right-click on the button and select Edit Button:

  1. A code window will appear, type the word sign, and then delete the text:

  1. Click Save and Close.

The button will now be signed with the appropriate administration ID, and end users will not receive execution security (ECL) alerts when they click the button within the message template.

4.15.    Importing Exchange MDb’s

Notes Migrator will need to have a reference to the Exchange MDbs that are available to be migrated to.  To import these, follow the below steps.

  1. Select 5. Import Exchange MDbs in the Navigation Pane

  2. The Data Pane will display an empty view of Exchange MDbs:

  1. Click the Import Mailbox DBs from AD button to import the available Exchange MDbs

  2. Select the appropriate Mailbox Databases from the list to be used and click the Set Use Flag button.

 


This is not required for Office 365 Migrations.

 

4.4. Configuring User Provisioning

Migrator for Notes collects and manages the settings essential in performing a successful migration. These settings are located under Configuration in the Navigation Pane.


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 Migrator for Notes User Guide for Office 365 Migrations for additional information.

4.1. Configuring Required Settings

Domino Settings

The Migrator for Notes Settings document displays. In the Settings document, the Required Settings -> Domino tab displays by default.


You can view the description of each field in each tab by clicking its corresponding question mark icon . For example, click and hold the mouse pointer on the question mark icon next to the Mail Server field to read its description.

Before any migration can be performed, the Required Settings tab must be completed. Two of the most important entries in this tab are the Mail Server and the Domino Directory. The specified Mail Server name is used to access the Domino Directory. The Domino Directory is used to retrieve the information required to import and create the User Mail, Rooms & Resources Databases, Mail-in Databases, and Discussion & Document Library Databases control documents.

These control documents are critical to the migration process and in their absence, migration information cannot be collected for a given item, and therefore, the item cannot be migrated. The control documents are used extensively during the remaining migration processes.

The following table describes the values for each setting.

Settings    

Description

Mail Server

The Domino server that Migrator for Notes will use for importing users and for sending Migration Messages.

Domino Directory

The Domino Directory name that Migrator for Notes will use for importing users, as found on the Domino server. Up to five additional Domino directories can be set by checking the box.

Server Mailbox

The mailbox filename that Migrator for Notes uses for sending Migration-related messages to selected users (for example, mail.box).

Audit Domino Encrypted Items

When running Audit on user mail file, specifying Yes will check for encrypted items in the mail file. If encrypted items are found, you can either send the user an email message with a button that decrypts encrypted items so that they can be migrated, or you can send the user a message with document links to the encrypted items so that they can print them prior to migration. You can even do both if you have some reason to want a list of messages that had been encrypted before the decryption agent was run.

Audit Domino Mail Rules

When running Audit on user mail file, specifying Yes will check for the number of rules in the mail file. If rules are found, you can send users a list of their Rules that will help them in creating the rules in Outlook after migration.

Audit Exchange Migrated Data

Enables auditing of migrated data in Exchange. Exchange Auditing should be enabled before data is migrated. Audit reports can be found the \logs directory on the migration workstation(s).

This is a post-migration validation process that indicates the state of documents which have been migrated by Migrator for Notes. This feature can be useful in environments as a validation check for data integrity. In addition, this can be used to audit results to reduce the size of user Domino mail files or archive databases after the migration phase on the Domino servers and user's workstation replicas. For example, removing documents with a Migration Status of 1 would leave only non-migrated data or documents that could not be migrated completely due to malformation or size restrictions in Exchange from a source database.  

Important: Consult your organizations data retention policies and regulatory compliance requirements before modifying source data. Full backups of the original source data may be required (and maintained post migration) before modifying working replicas to ensure regulatory compliance.

Audit embedded eml attachments

Enables auditing of eml attachments inside the message bodies to assist with migration troubleshooting. Results will be reported on the user document in EMM. This is not required for migration processing unless directed to enable this by Binary Tree's Product Support.

Additionally, a flag can be enabled and adds the field BTFoundEML to documents in source mail files where auditing finds eml attachments inside the message bodies.

Audit calendar unsupported patterns

Enables auditing of calendar items where the user is the Chair for Notes custom repeating meetings and generates document links for meetings that are not supported by Outlook. This will use the Migration Date if set or the current date and include meetings from the date specified and future meetings. The audit adds the reported data to the Calendar audit RTF report for the account and can be sent to end users with the Remediation Summary Message Template.

If enabled the audit can be specified to verify meetings where the user is the Chair, an Invitee or both. Additionally, label text can be added to the reported data to specify if the user is the Chair or the Invitee.

User Notification Style

Individual Notifications: Select if you want to send individual notification to each user and each mail/form will only have script for one action.

 

Combined Notifications: Select if you want to send one migration notification to each user and the notification/message to contain multiple selected forms, such as decrypting encrypted messages and synchronizing contacts and journals with mail file.

Enable this CMT db for Notifications

Click this button to create a Mail-In database document on the Domino Server for the Migrator for Notes database, and enable the database to receive User Notification responses. This database must be hosted on a Domino server.

 

Mail-enabling Migrator for Notes Database

A Mail-in Database Document is required for mail to be delivered to the newly created server copy of the Migrator for Notes database. The procedure copies the database to the server and creates a Mail-In database document for the Migrator for Notes database.

  1. Create a mail-in database for Migrator for Notes database. Click on the Server Db Copy and Mail-In Db Doc button to create a copy of the Migrator for Notes database on the Domino server and configure the Mail in Database document

  1. The Does Migrator for Notes already exist? dialog box opens; click Yes (and skip to step 5):

  1. If you are working with a local copy of the Migrator for Notes database, then click No. The Create a db copy? dialog box opens.

  2. Click Yes to create a copy of the local Migrator for Notes database on the server:

  1. If you clicked Yes in the Does Migrator for Notes CMT already exist? dialog box, the Choose Application dialog box opens. Locate the Migrator for Notes database in the CMT folder on the server, and then click Open.

The Fullname for the mail-in db doc dialog box confirms that the mail-in database for the selected server-based Migrator for Notes database does not exist, and prompts you to specify a name for the mail-in database. After specifying the name, click OK.

 

  1. In the Open the new mail-in doc? dialog box, click Yes to open the mail-in database.

The mail-in database document for Migrator for Notes opens.

  1. To verify the creation of the mail-in database, you can also launch Domino Administrator, open the Domino server, and access the Mail-In Databases and Resources folder under the People & Groups tab:

  1. Double-click the document to open and review

  2. Once the mail-in database is successfully created, the Open Mail-In Db Doc button replaces the Server Db Copy and Mail-In Db Doc button. Clicking it opens the database document for a review. Clicking the button with the X sign on it will remove all pointers to the location of the mail-in database.

    

 


The Notes ID that is used to sign the Notes Migrator database must have rights to add a new Mail-In Database Document to the server Domino directory. If the following error message is displayed, the Notes ID does not have appropriate rights.

Wor154

If you do not have the appropriate access rights to perform this action, see the onsite Domino System Administrator for help.

 

  1. It is recommended that after copying the database to the server, you delete the database from the local client folder. To remove it, right-click on Notes Migrator on Local. Select Database, and then Delete. The Lotus Notes client prompts that the database and related documents will be permanently deleted. Click Yes to delete the local database.

Modifying the Inbound Processing Agent

Once you have mail-enabled the database, you need to modify the Inbound Processing agent to view the updates. Perform the following steps to run the agent.

  1. Install Domino Designer on the workstation where Notes Migrator Domino database is located

  2. Launch Notes Migrator Domino database in Domino Designer

  3. Expand Shared Code and select Agents

  4. Select the InboundProcessing agent as shown below:

  1. Double-click InboundProcessing to open the InboundProcessing Agent Properties

  2. Click the Security tab

  3. The Administrator should be listed in the Run on behalf of section

  4. In the Set Runtime security level: field, select Allow Restricted Operations with full administration rights

  5. Once you've edited the agent, close the Properties box

  6. Close the Inbound Processing – Agent tab

  7. Save the changes

  8. Click Sign


This agent runs before new mail arrives and the Domino router must be set to allow these types of agents to run. To enable this option, go to Router/SMTP -> Restrictions and Controls -> Delivery Controls tab and set the Pre-delivery agents option to Enabled.


The Notes ID that signs this agent does require security rights on the Domino server to run agents.

 

LDAP Settings

  1. Click LDAP under the Required Settings tab:

In this tab, specify the Active Directory information to resolve users by matching them between source and destination platforms via Lightweight Directory Access Protocol (LDAP). To use this option, specify the required details.


LDAP configuration is not specifically required for Office 365 only migrations.

Use the following table to enter the correct values for each field:

Settings    

Description

Domain

The common name of the Active Directory domain. For example, binarytree rather than binarytree.com.

LDAP IP Address or Host Name

The fully qualified LDAP server name, IP Address, or resolvable DNS name of the Active Directory server. (e.g. PC-XP-01. binarytree.com or 192.163.15.12).

LDAP Port

Specify the LDAP port.

The default port for LDAP is 389.

The default port for SSL LDAP is 636.

Login ID

The AD domain account that has read rights to the target AD domain.

For example: administrator and not <domain>\administrator

Password

The password associated with the ID specified in Login ID.

Validate Settings

Click to validate the specified values to ensure that you are able to connect to the domain in Exchange where the end users will be eventually migrated.

LDAP Directory Base (Base DN)

If LDAP settings result in a successful connection, then this field is automatically updated.

Specify the directory base for all LDAP queries. The query settings will enable the search in AD to ensure that users are getting resolved against the right container ‘directory’ within AD.

Example: DC=btexchange2k7,DC=com

Quick Check

Full Check

If you want to search only the first ten users, select Quick Check; and if you want to search all the users, select Full Check.

Validate Query Settings

Click to validate the values specified in LDAP Directory Base to ensure that query string is resolving users and returning the number of resolved users.

 

  1. Specify the connection settings and then validate them by clicking the Validate Settings button:

  1. The LDAP Connection Settings Test Results message box displays indicating that the settings were validated and the connection was successful; click OK:

  1. Notice that the LDAP Directory Base (Base DN) field is automatically populated

To ensure that the specified directory base, where all LDAP searches will be conducted, is correct; you should validate this setting as well; click the Validate Query Settings button:

  1. The LDAP Query User Settings Test Results message box displays; the query setting is validated and some records are returned; in a production environment, ten records should be returned always; click OK:

Additional Settings

  1. Click the Additional tab under Required Settings

 

  1. Configure these settings with the names of the views to locate and import User and Mail-in Databases information. Also, specify the Migration Status Codes that can be assigned to users’ mail and databases control documents. You can assign a code to a user to update its status and view users based on their status codes. This helps in providing a better picture of the migration progress.

The following table describes the values for each setting:

Settings    

Description

CMT Migration Server

Specify the network hostname or IP address of the machine that is running the migration server.

CMT Program Directory

Specify the complete program directory path to Notes Migrator installation. This location will be used to launch the migration engine when the migration is triggered off.

 

Note: During the installation of Notes Migrator, if you had specified a destination folder path other than the default (C:\Program Files\Binary Tree\CMT Exchange), then you must replace the default path specified in the CMT Program Directory field with the modified path. In failing to do so, the migration engine will not launch when the migrations are set to go off.

Use Secure Web Services

Specify whether the web service calls are made to an XML server configured for secure access. Note that additional steps are required to secure the web services. The default selection is “Yes” which uses the CMT eService COM object to access the XML server.

 

Refer to Appendix E: Securing Notes Migrator Web Services with Windows Authentication for additional steps if you select Yes.

I have multiple control Centers

This option appears if the multiple Migration Control Center advanced feature is enabled on the Other Setting tab. Check this option to define the IP addresses of the Control Centers.  When enabled, the Set Migration Status options include Set Migration MCC and Clear Migration MCC options.

Migration Server Control Center IPs

Appears if “I have multiple control Centers” is checked. This field is used by the Set Migration Status agent.

Values must be entered as follows:

Workstation#=IP address of Notes Migrator Control Center

For example:

1=192.168.1.0

2=192.168.1.1

3=192.168.1.2

User Import View

Specify the view in the Domino directory that Notes Migrator database will use for importing users. Use the People view unless there is a custom view that you have created.

Mail-In Databases Import View

Specify the view in the Domino directory that Notes Migrator database will use for importing mail-in databases and resources. Use the Mail-In Databases view unless there is a custom view that you have created.

Mail-In Databases View Category

This is the NAB Mail-In database view category used for importing Mail-in Databases and Resources. Use the “Databases” default unless Domino is using a language other than English. Change this value to what is displayed in the NAB Mail-in Databases view.

Migration Status Codes

Specify a personalized list of status codes that will be used during the migration project. These codes can be assigned to users’ mail and databases control documents. If these status codes are assigned during the different phases of the migration process, timely status reports can be produced. These status reports will help provide a better picture of the migration progress. With this type of information, you have more control over the migration project and can react quickly to any identified issue. Adjustments can be made to help fine tune the migration schedule by adding more or different resources. Status codes must be separated by a new line. A list of status codes has been specified for you. You can either retain or change these status codes depending on your need.

CAS Server

Specify the Exchange Client Access Server (CAS) name. If a name is specified, then the matching process will use the following URL to resolve users. https://[servername]/autodiscover/autodiscover.xml

 

However, if you have specified the full URL to the Autodiscover service, then the URL will be used to resolve users.

 

This field is required for delegation migrations.

Username

If only the CAS Server name or IP address is specified in the CAS Server field, then you must specify a valid username for the authentication process that takes place on the CAS server. Note that the username should be in the following format for on-premises Exchange: <domain>\<username>. For Office 365 the format should be username@domain.com.

 

If you have specified a full URL (with https://) in the CAS Server field, then you can leave this field blank for on-premise migrations.

Password

Specify the password associated with the username provided in the previous field.

 

If you specified a full URL (with https://), then you can leave this field blank for on-premise migrations.

Powershell Admin Credentials

For on-premise Exchange servers, the credentials are of the form [Domain]\[Username].

For Office 365, the credentials are the SMTP address used to pass credentials to Office365 for remote access, for example o365Admin@tenant.onmicrosoft.com

Powershell Admin Password

Appears if Office 365 is in use

Use the Set PowerShell Password button to update this field. This will request the password and record it using the AsSecure PowerShell method.

This is not required for clicking the Notes Migrator PowerShell buttons, if this is not entered the buttons (such as Set Full Acccess) will ask for the password when processed.

PowerShell Logging Path

The MS PowerShell used when generating, executing, and logging PS1 script. This path can be edited on User Provisioning tab.

Default Reporting Path for Matching

Specify the reporting path used by the matching process. The default path is C:\Matching\.

Enable PowerShell Modern Auth

Appears if Office 365 is in use

Set to Yes to enable the use of the Exchange Online module for PowerShell processing. This will use Modern Auth connectivity to Microsoft Online services, removing the Basic Auth connection processing.

Enable Modern Auth for Migration

Appears if Office 365 is in use

Set to Yes to enable the use of Modern Authentication for Migrations. The Office 365 tenant must be configured to use Modern Authentication.

Autodiscover Username

Autodiscover credentials to be used during creation of the profile used by the migration engine.

For on-premise Exchange servers, the credentials entered should be the UPN (User Principal Name), for example: UserName@Example.Microsoft.com

For Office 365, the credentials are the SMTP address of an account in the Office 365 domain, for example: o365Admin@tenant.onmicrosoft.com.

 

Note: This is used if a migration worker does not have an account specified and is a fall back option. This is not required if a migration farm is being built using AWD.

Autodiscover Password

Enter the password associated with the Autodiscover account entered above.

Customer Name

Specify the Customer name that you would like in the status report.

Send Customer Status Report To

Specify the Group Name or SMTP addresses of the persons that should receive the status report.

Send Operator Status Report To

Specify the Group Name or SMTP addresses of the persons that should receive the full status report.

Migration Status Report Path

Specify the working path for migration status reports.

Create a combined report for multiple Migration Management databases (up to 5 additional)

Check this option to specify up to five additional migration management databases to include in a combined report.

 

4.2. Configuring Email Repliability

Click the Email Repliability tab to specify the appropriate values for the Domino environment:

Refer to the table given below for a brief description of all the settings in the Email Repliability tab.

Settings    

Description

Past and Present Domino Domains

The Domino domain names that are stripped from the email addresses and result in a valid and reply-able address regardless of domain name changes over the years. Enter a comma-separated list of all domain names in Domino, including the Notes Integration domain – no @ character is necessary.

Note: These are Domino domains, not SMTP or Internet domains, so it would more likely be ACME or ACME-NOTES, rather than acme.com.

Last Name Translation Update

This field is automatically populated during the Name Translation Update Process. This value will indicate the last time the Domino Directory was searched for updates.

Name Translation Database

The Name Translation Database field allows you to browse for the primary database to use for Name Translation lookups. This would typically be the current Notes Migrator.nsf. A warning will appear if you attempt to save the configuration without defining the Name Translation Database.

Name Translation Failover

The Name Translation Failover field allows you to optionally set the path to the primary failover database used for Name Translation lookups. The failover database is used if the primary database is inaccessible. This database should reside on the Domino server.  If a local (workspace) path is used, the EMM database must be replicated to the same relative path on all workstations.

Powershell bulk matching batch size

When using the two-step bulk PowerShell matching process for address translation entries, this is the number of records that will be presented in each matching .csv file. The default value is “2000”.

Note: this option is only available to Exchange on-premise migrations.

Table

The Name Translation Database table allows you to set the Name Translation Databases and Name Translation Failover Databases on multiple workstations. Click Set selected to define a Name Translation Database and Name Translation Failover for the selected workstation to use instead of the primary (default) databases defined above.

 

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: 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.

 

 

 

Lotus Notes Migration ID

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.

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

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.

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.

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 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:

4.7. Configuring Rooms & Resources Settings

  1. Click Rooms & Resources; this tab has two sections. Review the general description provided for both the sections.

Rooms & Resource Migration Options

The Rooms & Resource Migration Options section enables you to configure settings to determine how resources are handled during a migration:

The following table describes the values for each setting:

Settings    

Description

Rooms and Resources Target

Specify if you want the room or the resource to be migrated to a Location field, or be appended to the message body, both, or none.

Room Label

Specify the label you wish to be prefixed to the migrated room text.

Resource Label

Specify the label you wish to be prefixed to the migrated resource text.

Online Label

Specify the label you wish to be prefixed to the migrated online text.

Location Detail Indicator

Specify the text you wish to appear when room or resource text is not included in the Location field.

Room Resource Separator

Specify a string that separates the location, room, resource, or online values that are included on the Location field.

 

Rooms & Resource Settings

Configure these settings if you want to migrate Rooms and Resources. The first step of the process involves importing Rooms and Resources into the Notes Migrator database. Lotus Notes stores multiple Rooms/Resources in a single database. Notes Migrator allows you to import and create a separate .nsf for selected Room/Resource and copy its corresponding calendar into the newly created .nsf. Once all the Rooms/Resources that you want to migrate have been separately imported, you can export them to Notes Migrator migration engine and migrate them.

The following table describes the correct values for each setting.

Settings    

Description

Rooms and Resources Import View

Specify the view in the Domino directory that Notes Migrator will use for importing the different Rooms and Resources. Use the Rooms Resources view unless there is a custom view that you have created.

Target Server

Specify the Domino server that Notes Migrator will use when creating separate .nsfs for each Room/Resource. This must not be blank.

Target Path

Specify the destination path where separate .nsfs will be created for selected Rooms/Resources.

 

The path is relative if the destination is a Domino server. If the destination is a file server, full path must be specified.

Database Template

Specify the template that will be used to create the new room or resource database to migrate.

Set Subject to Chair

Set this to ‘Yes’ to enable overwriting the booking subject when importing rooms and resources. This will set the subject to the booking Chair for migration to Outlook (removing the booking subject entirely). This does not impact the existing Notes room and resource bookings. Selecting ‘No’ will retain the original booking subject for migration.

Subject Prefix

This is used if the subject for imported booking will be overwritten with the booking Chair name. The text used will be prefixed in the imported booking subject.

4.8. Configuring Replica Settings

The Replica Settings are used when using a Domino staging server. A staging server is often used when the Domino mail servers are not on the same LAN as Exchange and/or the migration environment to mitigate migration throughput degradation due to the network. Staging servers are also used if you will be using replication formulas to filter the data intended for migration.

The following table describes the values for each setting:

Settings    

Description

Staging Server(s)

The Name of each of the staging servers to be used for creating replicas separated by a new line or a comma.  For Example: Stage01/Contoso

Staging Server File Folder

The folder name in which to place the newly created replicas.

Replication Formula Option

Specify My Own Formula: Use the field below to specify your own selection formula.  Be sure to enter the ENTIRE formula, starting with SELECT (e.g. SELECT @All to replicate all Notes items).

 

Build Formula Via Selections: The number of calendar and email days and select the forms to include in the replica and a replication formula will be built for you.

Replication Formula

If you are specifying your own replication formula, enter it here.

*Note: You must be familiar with Notes formula language.

Number of Calendar Days

If you selected Build Formula Via Selections enter the number of calendar days to include in the replica. You will be prompted for a date upon replica creation and it will use this date and the number you specify to calculate the number of calendar days to include.

Number of Email Days

If you selected Build Formula Via Selections enter the number of email days to include in the replica. You will be prompted for a date upon replica creation and it will use this date and the number you specify to calculate the number of email days to include.

Forms to include in Replica

Select or enter all of the different forms to be included in the replication formula.  If the form name is not listed here, it will NOT be included in the replication formula and will not be in the replica.

Replicate Each Replica at Creation

Selecting “Yes” will replicate each newly created replica as it is created. It will also cause the agent to run very slowly depending on the replica settings. It is recommended to use this as a one-off replica creation rather than for the entire list of users/mail-in databases.

Exclude Trash from Replica Comparison

Set to Yes to exclude Trash (Soft Deletion) document counts from the replica comparison total document counts. Set to No for default processing to count all documents.

4.9.    Configuring Delegation

  1. Click the Delegation tab.

  2. Validate Yes is selected for the Audit Delegates option. If set to No, set to Yes and save and close the document, then reopen the document to view the other configuration settings.

  1. The PowerShell application impersonation set option is a prompt to set application impersonation. Set application impersonation using the steps below and then set this option to Yes.

    1. Open the Exchange Management Shell or configure a PowerShell session to connect to either an on-premise or the appropriate Office365 server.

    2. In the shell, enter the following command to configure application impersonation:

New-ManagementRoleAssignment –Name:impersonationAssignmentName –Role:ApplicationImpersonation –User:CMTMigrationAdmin@myDomain.org

Where CMTMigrationAdmin@myDomain.org is the SMTP or login name of the migration account, or the name of security-enabled group used for migration.

  1. To run delegation migrations as a scheduled process, set Run delegation as a scheduled process to Yes (default).

  2. Click the Enable scheduled agent button and select the Domino server that will perform the migration. The agent will run in the background of the local Notes client if the Local option is selected.

Scheduled delegation migration runs in the background on a workstation or server. If running locally, Notes must be running and background agents must be enabled on the client.

The scheduled delegation migration agent runs once a day at 3:00 AM.  Note that if the agent is changed to run at a time interval that is too short, the PowerShell tasks may not have time to complete.

  1. Click the Delegate Settings tab:

  1. After auditing the user's mail files with Active Delegation enabled, you are able to send an email that displays the user's current delegation settings, so they can decide whether they are still valid for migration to Outlook. You should allow the users a period of time to review before rerunning the mail file audit to collect any updated settings.

The options below allow you to customize the message to exclude certain users and groups that delegation does not need to be reported to the users about. Typical exclusions are standard Administrative groups or administrative IDs that are by default listed in the HCL Domino Mail files within the environment.

4.10. Configuring Source Updates

The Source Updates Settings are used to configure the Fix Folders agent.

 

The following table describes the values for each setting.

Settings    

Description

Replace Blank Folder Names With

The folder name to be used when updating Blank folder names. This will update blank (Null) folders at the folder root, blank folders within the folder hierarchy and blank folders at the end of the folder hierarchy. This will numerically increment (1, 2, 3, etc.) if more than one blank folder exists. Replacements will be done for: "", " ", " \", "\ \","\\" "\ "

Append Personal System Folders With

The folder name to be appended to Outlook system folders that have been created at the folder root of the Notes personal folders. This will not update the Notes system folders. The folder names will be appended with a hyphen "-" and then the name to be used.

Check for Duplicate Folders Names

Option to check for duplicate personal folder names. If enabled, the agent will check each folder to determine if there is a duplicate and then append "-" and an incremented number to make the name unique.

Check Duplicate Folders on Remediation Only

Option to have the duplicate checks be performed on the first Fix Folders processing or only on second processing runs. This requires the option for duplicate checking to be enabled. Set to "No" to disable this and have the Fix Folders agent always check on the first pass for duplicates or set to "Yes" to have the duplicate checking skipped on the first pass and only be run on subsequent updates. This is enabled as the default configuration.

Maximum Duplicates Checks per Folder

Numeric setting for the number of duplicates to be checked on a single personal folder. If there are more duplicates of a single folder name than the number specified, the duplicate checking for that folder will be skipped. Requires duplicate checking to be enabled.

Remove Personal Folder Aliases

Option to remove hidden Alias from Notes Personal folders. This will remove all aliases in the Notes folders except for the system folders. This should only be used if an issue with an alias is found to cause a problem with migrations.

Email end users with Folder Renames

Option to send an email to the end users with a list of the folder names that were changed. The email will include the original folder names and the new folder names.

Enable Replacement of Specific Characters

If enabled, this will allow for a defined set of characters to be removed from all personal folder names and to have those replaced with a different character. This will not update system folders and should only be used if a specific character is found to cause an issue with migrations.

Replacement characters in

Personal Folders

This is a text list of characters to be replaced and should be a comma separated list if more than one character should be replaced. This requires the character replacement to be enabled and should not contain a backslash "\" as that will replace the Notes folder hierarchy or be Null (blank).

Character to be used for replacements

This should be a valid character that is not known to cause migration issues and should not be Null (blank). Typically, a hyphen "-" is recommended.

Remove obsolete local group members

This can be enabled to verify any local personal group membership (not system groups membership) and remove notes formatted (Canonical) membership addresses that are no longer in Domino (e.g. user accounts for leavers that were removed from Domino). The Email Repliability in Notes Migrator is used for these checks and should be populated prior to running the processing, if enabled. Note that these members cannot be automatically replaced once they are removed.

Rename local canonical group names

This can be enabled to validate local personal group names created by end users to check if these have a canonical (Domino) format (e.g. Personal Group/Local). If enabled, the processing will rename these by replacing the “/” with a “-“ to prevent Notes treating the local group name as canonical for migration.

 

4.11. Configuring Other Settings

Click the Other Settings tab to configure settings to control how encrypted items are handled or mail rules found in the user mail file. In this tab, the Migration Checklist and Advanced settings can also be configured:

The following table describes the values for each setting:

Settings    

Description

Send Rules Email

Configure these settings if you will be sending users their mailbox rules before migration.

From

Contains the profile name that will send the mail regarding mailbox rules to users. Migration Coordinator is specified as default.

Subject

Contains a subject that briefly describes the purpose of the mail. Your Mail Box Rules is specified as the subject by default.

Body

Can contain any information that you may want to share with the end user about this procedure.

Rules to Include

Includes all rules or only the rules that are enabled. Select All Rules.

Encrypted Items Migration

Choose how to migrate encrypted messages. Valid options are:

  • Require decryption action and migrate into the body

  • Migrate into a Notes database as an attachment

Note: Enabling the Migrate into a Notes database as an attachment option will increase the size of each migrated item containing encrypted content. The Lotus Notes client, original Notes ID, and decryption keys are required on the workstation used to view the encrypted content of the migrated items.

Send Encrypted Items Summary Email

Configure these settings if you will be emailing users a summary of their encrypted items.

The fields in this section display only when Require decryption action and migrate into the body option is selected.

From

Contains the profile name that will send users the mail with a summary of encrypted items. Migration Coordinator is specified as default.

Subject

Contains a subject that briefly describes the purpose of the mail. Your Encrypted Items is specified as the subject by default.

Body

Can contain any information that you may want to share with the end user about this procedure.

Template Name (.ntf)

This appears if you have selected Migrate into a Notes database as an attachment. Specify the template name in this format:  filename.ntf

 

EncryptedContent.ntf is the default template that ships with Notes Migrator. This template will be installed on every migration workstation during the product installation. This template will need to be signed with the appropriate Lotus Notes Administrative ID on all workstations. 

 

You can use any database template; however, you will need to manually distribute the template to all migration workstations.

 

Binary Tree recommends that use of an alternative template or any changes to EncryptedContent.ntf be thoroughly validated prior to production use.

Attachment name in Exchange

This field displays only when the Migrate into a Notes database as an attachment option is selected.  Specify the database name in this format:  filename.nsf

Text included with attachment

This field displays only when the Migrate into a Notes database as an attachment option is selected. Customized text can be added to the migrated item to provide end-user instructions or information. The default text is as follows:

 

Portions of this document were encrypted with Lotus Notes encryption. This content has been stored in the attached Lotus Notes database during migration to preserve security. You may view this content by opening the attached file on a workstation that has a Lotus Notes Client and the recipient’s Notes ID.

Migration Checklist

The Migration Checklist is a personalized list of tasks which can be used to help manage the migration project. Determine, then classify or group the major steps you consider necessary to manage your migration project. Determine the sequence, timeline, and description for each migration task and enter them into the Migration Checklist.

Enable Recovery

This setting defines the default value for the Enable Recovery setting in the migration profiles’ Advanced tab.

 

If the Enable Recovery setting is set to Yes in the Advanced tab of a migration profile, it enables tracking of processed messages during migration. So, if the migration process terminates unexpectedly, this feature prevents the application from reprocessing messages that were migrated during the initial run of the migration. Click here to learn more about configuring the Enable Recovery setting.

Disable MIME Cache

Specify Yes to disable the local cache database when processing messages using MIME.

Disabling this feature significantly impacts throughput when migrating MIME content from a Domino server.

Migrate Unfiled Documents

This option determines if “unfiled” documents will be migrated. “Unfiled documents are documents in Notes that do not appear in any folder and can only be accessed from the “All Documents” view within the mail file. Documents may be unfiled if a user deletes a folder without deleting the documents or removes a folder it resided within. The unfiled folder name can be defined.

MAPI Custom Settings

Select Specify advanced MAPI parameters to override the default values for MAPI retry count and MAPI retry delay.

When configured, retries are attempted when the MAPI_E_NETWORK_ERROR (0x80040115) result code is encountered during any of the following MAPI calls:

  • Create attachment

  • Create folder

  • Create message

  • Modify recipients

  • Save folder changes

  • Save message changes

  • Save attachment changes

 

If the configured retry limit is exceeded, the migration is cancelled and Notes Migrator will begin the migration of the next user. If the migration is canceled in the middle of writing a document, the document will be partially written to Exchange. The default retry limit is set to 30 seconds.

 

Specify the Number of retries that will be attempted when the MAPI_E_NETWORK_ERROR (0x80040115) result code is encountered. Values ranging from 1 to 999 can be entered. The default number of retries is “9”. Note that entering “0” results in the default “9” retries being used.

 

Specify the Delay between retries in seconds between MAPI calls. The time is progressive. The number of seconds delay for a call is (retry # * delay). For example, if the retry delay is set to 1 second, and the retry count is 5, the delays between calls will be 1, 2, 3, 4, and 5 (progressively longer). If the retry delay is 1.5 seconds, the times will be 1.5, 3.0, 4.5, 6, and 7.5. Values ranging from 1 to 999 can be entered. The default delay is “1” second. Note that entering “0” results in the default delay “1” second being used.

MAPI Retry Failure Limit

When enabled, Notes Migrator tracks documents where one or more MAPI calls could not be completed successfully. If the number of documents where one or more MAPI calls cannot be committed to Exchange, the migration will exit with ‘migration failed’ status.

 

The document retry failure limit feature can be disabled by setting the value to ‘0’ or leaving it blank.

 

MAPI Retry

Notes Migrator makes multiple MAPI calls when migrating a document, such as creating the message header, writing the body, adding attachments, etc. When processing messages, the remote Exchange server may become unresponsive in such a way that MAPI calls to write data do not complete. The call is retried a number of times (using the preexisting feature known as MAPI Retry: the maximum number and delay between retries can be set in EMM) to fully migrate data to Exchange.

 

If any of the MAPI calls cannot be completed, the document will be considered as failed due to MAPI retries, and added to the total of failed documents. Document information is logged, the NoteID is removed from both the in-memory migration history, and the CMTProcessedNoteID-[shortname].txt crash recovery file.

 

Note that other types of failures, such as a corrupt message body which results in a failure, are not counted toward the MAPI retry failure total. These other types of failures are specific to the source data, whereas the MAPI retry failures are related to the ability to write to exchange.

 

If the number of documents with MAPI retry errors exceeds the failure limit, the migration will exit, and return ‘Migration failed’ status. This migration will not automatically requeue and must be requeued by the migration administrator to fully migrate the mailbox. When a migration is requeued, it may be migrated by any workstation. Any documents containing MAPI retry errors on the failed migration will be remigrated during subsequent migrations.   

 

If the migration terminates abnormally (crashes), the document being migrated when the crash occurs will not be retried, which is standard procedure for crash recovery in Notes Migrator. Any other documents containing MAPI Retry Exceeded will be remigrated. In this case, Notes Migrator will automatically restart the migration on the same workstation.

Process attachments greater than

The limit for the size attachments, in MB, that will be detached and processed as file attachment objects. A value of -1 disables this feature, and processes all attachments as MIME streams, similar to Notes Migrator versions 4.6 and earlier. A value of 0 will process all attachments as file attachments. The default value is 0 MB to process all attachments outside the MIME Stream.

Encapsulate special content

When enabled, documents containing special notes functionality or items such as button or stored forms will be migrated as an attachment in addition to being rendered in the message body. End users can then open the NotesMessage.nsf attachment to use the native functionality of the form.

Migrate documents as private

When set to ‘Yes’, the migration will migrate documents designated as private in Notes as Private in Exchange. This will also include messages decrypted in Notes prior to migration.

Convert UNC paths to links

Specify No if you do not wish the body of the documents searched for UNC (Exchange Naming Convention) links during migration.

If you specify Yes, CMT attempts to convert UNC links into actionable links.

Add category to calendar events

Field in Exchange. For example, if you specify Migrated with Notes Migrator in the field, then all the calendar events, such as meetings and appointments, will display this phrase in the categories field after they are migrated. It enables you to visually differentiate calendar events that were migrated into Outlook from those created natively in Outlook before or after the migration. This setting is optional.

 

Note: Any categories that are in the original Notes calendar event will also display in the categories field.

Process meeting with no end date using ICAL information

Specify Yes to use the ICAL recurrence information to determine the repeat pattern when processing repeat calendar meetings with no end date.

 

Specify No to process repeat meetings with no end date without using ICAL recurrence information.

 

Note: When migrating a meeting with No End Date and this option is set to No, the meeting is migrated but limited to 250 occurrences.

Enable Advanced features

Select Yes to enable features used when migrating large environments or to cloud based services.

Enable Hosted features

Appears if Advanced features are enabled. Select Yes to enable features used when migrating hosted environments. This setting should only be enabled under the direction of Advanced Support.

Enable multiple Control Centers

Appears if Advanced features are enabled. Select Yes to enable features used when migrating with multiple Migration Control Center (MCCs). This setting should only be enabled under the direction of Advanced Support.

 

Sending Mail Box Rules

Notes Migrator allows you to send users their Mail Box Rules before migration occurs. You can define the From, Subject, text in the body, and which rules to include in the email sent to users.

Migrating Encrypted Items

Notes Migrator offers two solutions for migrated items that have been encrypted via Lotus Notes. The data may be decrypted as part of the pre-migration process, or the encrypted content may be attached to the migrated message in a Lotus Notes database during migration.

When the Require decryption action and migrate into the body option is selected, additional fields will be visible in the Send Encrypted Items Summary Email section to configure the From, Subject and text in the body of the summary email sent to end users.  If you select Migrate into a Notes database as an attachment option is selected, you will see new fields for the Template name, the Attachment name in Exchange and Text included with attachment.

Creating a Migration Checklist

  1. Click the Migration Checklist button to enter the steps, timelines, and tasks in the Migration Checklist Profile to use for your customized Migration Checklists:

  1. Starting with Step 1, click the down arrow button in the Timeline column.

  1. The Select Keywords dialog box is displayed. Select one of the provided keywords or enter a new one in the New Keyword field at the bottom of the dialog box and click OK to continue:

 

If the predefined keywords do not appropriately describe your timeline, you can specify a new keyword in the New Keyword field.

  1. Enter a description in the Task column and click Save & Close to complete:

  1. If you exit the document without saving, the following dialog box is displayed. Select Yes to save the Migration Checklist. If No is selected all new entries are discarded:

  1. After all the settings have been configured, click Save & Close to save all the configuration settings.

Enabling Recovery

As stated earlier, the Enable Recovery setting in the Other Settings tab defines the default value for the Enable Recovery setting (found under the Advanced tab) in the existing migration profiles as well as the new profiles you may create.

By default, it is set to Yes, so in all the existing migration profiles and the new ones you create, the Enable Recovery setting will also be set to Yes. However, if you were to change this setting to No in the Other Settings tab, and save the changed configuration settings, the following prompt will display.

If you click Yes in this dialog box, the Enable Recovery setting in all the existing migration profiles will change to No, and any new migration profile created will also have No as the default value in this field.

But if you click No in this dialog box, the Enable Recovery setting in all the existing migration profiles will remain Yes (the prior setting), however, when you create a new migration profile now, the Enable Recovery setting will be set to a default No.


It is recommended that you review the description provided for the Enable Recovery setting in the Advanced tab of migration profiles (Section 6.6) for a complete understanding of how this setting works.

4.11. Creating Migration Profiles

Migration Profiles define settings for certain groups of users. For instance, it may be desirable to have a profile where all executives have a filter that only migrates the last four years of mail and calendar to Exchange. Every user must have a Migration Profile set before migration can proceed.

Before you create a migration profile that contains filters to migrate specific user data, you must create a default migration profile. After the default profile has been saved, create migration profiles that will be used to migrate users. These profiles should have descriptive names, such as 90DayMailOnly or 4Years-Calendar-Mail.

Important! – The default migration profile does not have all values and should not be used for migrations. A new profile should be created to prevent problems with corrupting the backend database. This will help avoid problems during production migration.

  1. Click Migrate Profiles in the Navigation Pane:

  1. Click the Create New Profile button:

Each migration profile contains a source and destination setting that determines which mail items are migrated and if the migration is to a Microsoft Exchange server or to a .pst file.

When a migration is carried out, a migration profile must be assigned to specify how the migration should be performed. You can create as many migration profiles as desired.

  1. The Profile dialog box displays; the Source Options tab opens by default:

The following table describes the values for each setting:

Settings    

Description

Message Types

Specify the Migration Options. You can either select all message types or specify the types that you wish to be included in the migration (Mail, Calendar, Task, and Contact).

Date Filter

Specify a range of dates that will ensure that only the data that falls within the specified range is migrated.

 

The Date Filter will apply to all the selected message types. For example, if you select All message types, the specified date filter will apply to Mail, Calendar, Tasks, and Contacts.

Migration Log Level

By default, Notes Migrator creates a log file for every user that is migrated. In this field, you specify the level of detail you want in the logs. There are three levels provided.

  • Minimal

  • Normal (Recommended)

  • Verbose

 

Selecting Verbose significantly increases the size of the log files that are created. This is only recommended for troubleshooting purposes. Log files are located in the Logs subdirectory where CMT Exchange is installed, usually C:\Program Files\Binary Tree\CMT for Exchange\Logs.

Skip folders named

Specify a list of folder names from your Domino mail files that you would like Notes Migrator to bypass during the migration. This feature is useful if you have a customized mail template that may contain folders with non-messaging data. Specify folder names in the Skip folders named field. Separate entries by commas.

Migrate empty folders

Select to migrate empty folders in users’ mailboxes to Outlook.

Migrating Sent Items

In Lotus Notes, a mail message can exist in the Sent Items folder or in the Sent Items folder and a user-defined folder(s). In Outlook, a mail message can only exist in one or the other. This field provides two options.

  • Select Migrate to the Outlook Sent Items Folder, if you prefer the items to be stored in the Sent Items folder in Outlook after migration regardless of what other user-defined folder(s) it may have been stored in Lotus Notes.

  • Select Preserve custom folder name, if possible, if you prefer the items that exist in two locations to be stored in the user-defined folder after the migration.

Audit Notes UNIDs

During Migration

The migration worker will record an audit of the Notes source document UNID [unique identifier] for all items processed in a .csv file. This will be uploaded to the migration controller in the logs folder.

Ignore Privacy Flag

If set to ‘Yes’, this will not migrate any documents as private in Outlook. This will override the Settings | Other Settings option if that is set to ‘Yes’. This is typically useful for shared mailbox migrations.

 

  1. Click Destination Options:

The following table describes the values for each setting:

Settings    

Description

Migrate to Exchange Server

Select if you want the migrated data to go directly to the Exchange server.

Migrate to .PST file

Select if you want the migrated data to go to a .pst file.

 

The PST Folder Path field is added to the form when this option is selected.

PST Folder Path

Specify the path where you want the .pst file(s) to be stored. This must be a Windows drive and folder or mapped drive on the migration workers. A Windows UNC path should not be used.

 

When migrating to a PST file, the file name format will be “<User’s SMTP Address>-Notes Database ID.pst”.

Individual attachment size limit

Specify a size limit in bytes to filter individual attachments. For example, if you specify 1000, each individual attachment that is greater than 1000 bytes in size will be filtered out during migration.

 

Maximum message size cannot exceed 125 MB. This field should be set to 131072000 to avoid memory errors during the migration.

Attachment total size limit

Specify the total size limit of all attachments in a document in bytes. For example, a value of 10000 would allow only a total of 10000 bytes for attachments migrated per message.

 

Maximum message size cannot exceed 150 MB. This field should be set to 157286400 to avoid memory errors during the migration.

 

 


The default size limits for the attachment size limit fields are the maximum size we support.  This limit may differ in your environment.  We recommend testing your migration environment to confirm it supports our product limitations. If you experience memory errors with lower attachment sizes, we recommend lowering the default size limits in the attachment size limit fields until a memory error is not encountered.

  1. Next, click the Advanced tab

  2. Check the Enable Advanced Options box:

Advanced options are now displayed in the dialog box; configure these settings:

The following table describes the values for each setting:

Settings    

Description

Advanced Message Filtering Options

Configure these settings if you wish to filter the messages based on their various age limits.

Mail Age limit

Specify the number of days from the migration date to filter the mail messages. For example, if you specify 30, the application will only migrate messages that were created 30 days prior to the migration date.

Task Age limit

Specify the number of days from the migration date to filter the tasks (To Do Lists). For example, if you specify 30, the application will only migrate tasks that were created 30 days prior to the migration date.

Calendar Age limit

Specify the number of days from the migration date to filter the calendar events. For example, if you specify 30, the application will only migrate calendar events that will occur in the 30 days prior to the migration date.

Filter Repeating meetings

By default, all repeating meetings are migrated. Repeating meetings are filtered based on the specified age limit criteria only when you check the Filter Repeating meetings checkbox.

 

It should be noted that in case of repeating meetings, the filter applies to the date of the parent-meeting document and does not filter the series. This means that if the parent meeting falls within the specified date range, the entire series is migrated and if the parent meeting falls outside the date range, the entire series is skipped. The dates of the meeting recurrences do not matter.

Additional Options

Configure these settings to improve the migration throughput.

Enable Recovery

 

Specify Yes to enable the setting to track processed messages during migration. So, if the migration process terminates unexpectedly, this feature will prevent the application from reprocessing messages that were migrated during the initial run of the migration.

 

To disable this setting, specify No.

 

Refer to the Enable Recovery setting in the Configuring Other Settings section to understand how the default value for the Enable Recovery setting in the Advanced tab is determined.

Process as RTF

Specify Yes to override the default MIME processing and to process native Notes documents as Rich Text.

 

Note: Enabling this feature is not recommended.

Disable MIME Cache

Specify Yes to disable the local cache database when processing messages using MIME.

 

Disabling this feature significantly impacts throughput when migrating MIME content from a Domino server.

Convert UNC paths to links

Specify No if you do not wish the body of the documents searched for UNC (Exchange Naming Convention) links during migration.

 

If you specify Yes, CMT attempts to convert UNC links into actionable links.

Add category to calendar events

Specify a word or phrase in the field to add to the category field in Exchange. For example, if you specify Migrated with Notes Migrator in the field, then all the calendar events, such as meetings and appointments, will display this phrase in the categories field after they are migrated. It enables you to visually differentiate calendar events that were migrated into Outlook from those created natively in Outlook before or after the migration. This setting is optional.

Flush log to disk after

Specify the number of log events (entries) after which you want CMT to close the log file and flush it to the disk.

 

Leave the field blank or specify 0 or 1 to log continuously until the migration completes.

 

Please note that all the logs are flushed to the disk after they close irrespective of the value specified in this field.

 

Note: The specified value in the field only forces CMT to update the log file after a specified number of entries (events). It may improve processing in certain environments but if CMTProxy terminates during a migration, you also run the risk of missing complete information in the log file.

 

 

All the settings in the Advanced tab are pushed to the migration workstation performing the migration through the AdditionalSettings.xml file. If you haven’t changed the default Advanced settings, the .xml file is not used during a migration.

 

  1. A default name is specified in the Profile field. You must specify a descriptive name for the migration profile and do not use Default as the name.

  2. Click OK to save the migration profile settings.

  3. A confirmation box appears; click Yes to save these settings to the Notes Migrator database:

  1. A new profile by the name you specified in the Profile field is created. If you do not see it listed in the Data Pane immediately, you can refresh the Data Pane. Click the Refresh Profiles button.

To delete unused profiles, click the Delete Settings from migration server button. A profile cannot be removed if the profile has been used for end user migration.

4.12. Creating a Message Template

Notes Migrator manages communication with the end users to be migrated via Notes mail messages. These messages can be used for informational purposes only or they may contain action buttons with associated code designed to perform specific pre-migration tasks.

These migration messages are created using the Message Templates. For Message Templates with action included, there are additional settings used to control a workflow process. When an end user executes the action, a status message known as an End User Processed Migration Message is generated and returned to the Notes Migrator database via Notes mail. Once received, the message is used to update the status of the corresponding end user’s Person document. If the status indicates the action was successful, the user can be re-verified and be ready for migration.

For this process to work correctly the Notes Migrator database must be located on a Domino server and a Mail-In Database Document pointing to it should be created.

Notes Migrator comes with several predefined Message Templates designed to perform specific migration tasks. You can use these predefined Message Templates to create custom templates that may better suit your need.

  1. Click Message Templates in the Navigation Pane; the Data Pane displays a list of predefined message templates:

 

Each predefined Message template has a specific purpose. If you wished to create a custom template based on a predefined template, you need to select the predefined template before clicking the New Template button. For example, if you wished to create a custom template based on the Migration Message – Decrypt Encrypted Item template, then you must select the template prior to creating a new template.

  1. Select a predefined template and click the New Template button in the Data Pane.

 

Encrypted Sent Items may contain an encrypted flag but possess no encrypted fields. This means that even though they display as encrypted, they actually aren’t and will migrate without decryption. Encrypted mail fields (including Sent folder) will not be migrated to MS Exchange if they are not decrypted using the decryption tool.

  1. A new tab, CMT Template: Migration Message – Decrypt Encrypted Items, opens and displays a form where you can specify the details of the new Message Template. Notice that the tab clearly specifies that the new CMT template is based on the Migration Message – Decrypt Encrypted Items predefined template. However, when you save this template with a new name, the tab will reflect its new name.

  2. Customize the CMT new template. Refer to the table below for details on settings.

  3. Once all the details have been specified, click Spell Check to ensure there are no spelling errors in the message.

  4. A message box appears to confirm that no misspellings were found. Click OK to close the message box. Next, save the new template. Click Save & Close.

The following table describes the values for each setting.

Settings    

Description

Template Name

Specify a name for the template that best describes the purpose of the new message template.

Template Type

Specify the type of the new message template, such as Email Only or Contact Synchronization. Refer to the Predefined Message Template Types section below.

Return Notification

Specify if you want a return notice to Notes Migrator from the end user when the message is received and the required action is performed.

Requires MSI Attachment

Specify whether the .MSI file is required to be attached prior to sending.

From

Specify the name of the entity sending this migration message to end users (for example, Migration Coordinator).

Subject

Specify a brief description of the purpose of the new template.

User Action Required

Check this box if migration for this user cannot proceed until the user performs the embedded action within the message.

 

This check box also indicates that the user will remain in the Pending Reponses view until they perform the end user action in a particular message template.

Pre-migration

Select this if the new message is sent to the user, and requires the user to perform an action that will prepare user data for migration.

Post-migration

Select this if the new message is for use after a user’s migration has taken place, and is typically informative, no User-Action Required.

Body

Specify a customized message

 

*Note that any buttons in the message template must be edited and saved to sign these with a Notes ID that is part of the Domino system ECL.

 

The new template is saved and it appears in the list of existing templates.

4.13. Types of Predefined Message Templates

Notes Migrator comes with several predefined Message Templates which are designed to perform specific migration tasks. The information contained within these predefined templates can be modified to tailor them to a client’s needs. Predefined Message Templates can be of the following types depending on the actions they perform:

  • Email Only

  • Contact Synchronization

  • Decrypt Encrypted Items

  • Archive Discovery

  • Archive Processing

Email Only

As the name implies, Email Only is designed for informational purposes only and does not include any action buttons. Email Only templates can be used to keep the end users informed on the progress of the migration project. For example, end users can be sent an email with the migration schedule for their department. This can help them plan for when their email will be migrated.

The fields within each predefined message template should be modified to make it specific to the client. An example is shown below.

For a template to be information-only, its Template Type field should contain the value Email-only and Pre-migration option should be selected. Although, if you are sending a message to end users informing them about the successful migration, then you can also use Email Only Template Type and select Post-migration.

Contact Synchronization

When a Contact Synchronization migration message is sent to an end user, the user simply clicks the button in the message. This launches the iNotes_DoSync() agent that ships with Lotus Notes, and pushes/resyncs all contacts in the Personal Name & Address Book (pNAB) to the hidden $PeopleGroupsFlat view. Now that these contacts are in the mail file, they can be migrated.

Decrypt Encrypted Items

When a Decrypt Encrypted Items migration message is sent to an end user, the user simply clicks the button in the message. This initiates an agent that will decrypt any encrypted items in the mail file, so they will migrate as clear text.

Archive Processing

When an Archive Processing migration message is sent to an end user, the user clicks the button in the message and this allows the script to search for the Archive Database Templates locally on the end user machine, find it, and copy/replicate it to a specified location on the Domino server or file server or copy into end user’s existing Domino mail file.

The location to copy is specified in the Notes Migrator Settings document. The script will only search for templates that are specified in the Notes Migrator Settings document. Refer to the End User Migration Settings configured in the Notes Migrator Settings document.

4.14. Signing a Button in a Message Template

  1. Open a Message Template

  2. Click on Edit Document

  3. Right-click on the button and select Edit Button:

  1. A code window will appear, type the word sign, and then delete the text:

  1. Click Save and Close.

The button will now be signed with the appropriate administration ID, and end users will not receive execution security (ECL) alerts when they click the button within the message template.

4.15.    Importing Exchange MDb’s

Notes Migrator will need to have a reference to the Exchange MDbs that are available to be migrated to.  To import these, follow the below steps.

  1. Select 5. Import Exchange MDbs in the Navigation Pane

  2. The Data Pane will display an empty view of Exchange MDbs:

  1. Click the Import Mailbox DBs from AD button to import the available Exchange MDbs

  2. Select the appropriate Mailbox Databases from the list to be used and click the Set Use Flag button.

 


This is not required for Office 365 Migrations.

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating