Chat now with support
Chat with Support

Binary Tree Migrator for Notes 20.12.1 - 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 About us Technical support resources 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 Third-party Contributions

Local Archive Discovery

4.6. Configuring Archive Settings

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

Legacy Archive Processing

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 for Notes User Guide.

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.

Rooms & Resource Migration Options

4.7. Configuring Rooms & Resources Settings

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

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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating