About the Migrator for Notes to Exchange documentation
Notes Migration Manager
Basic operating principles
NABS Discovery Wizard
Internet Domains Discovery Wizard
Directory Export Wizard
Navigation within Notes Migration Manager
About wizards and tasks
About Migrator for Notes to Exchange statistics
Notes Migration Manager navigation drawer
Project management features
Project view
View documentation
Edit Default Settings: SQL Server Configuration
Edit Default Settings: Shared Directories Configuration
Edit Default Settings: Notes Server Configuration
Edit Default Settings: Exchange Server Configuration
Exchange Server Configuration: Migrating to an on-premises (proprietary)
Exchange Server Configuration: Migrating to Office 365
Edit Default Settings: Active Directory Configuration
Discover Notes Information
Discover Notes Information: Find NABs
Discover Notes Information: Find Domains
Discover Notes Information: Export Notes Directory
Group Collections
User Collections
User Collections: Manage Users
User Collections: Manage Design Classes
User Collections: Send PAB Replicator
User Collections: Locate Notes Data Stores
User Collections: Provision Users
User Collections: Migrate User Data
Monitor Migration Progress
Gather Desktop Statistics
Manage Scheduled Operations
View Summaries
View Logs
Introduction
Wizard process screens
Collection Wizard
Groups Provisioning Wizard
Notes Data Locator Wizard
Customize Configuration
Configure Directory Export Updates of TSV-Imported Values
Specify Notes Login Information
Generating Task
Configuration Summary
Creating Task
Set Task Schedule
Schedule Summary
Task Progress
Task Completed
Exported data elements in the SQL database
Introduction
Wizard process screens
Provisioning Wizard
Send PAB Replicator Wizard
Data Migration Wizard
Select User Collection
Customize Configuration
Configure Updates of TSV-Imported Values
Specify Notes Login Information
Select Notes Data Store Types to Locate
Specify How to Find Notes Mail Files
Specify Notes Mail File Directories
Specify How to Find Notes Personal Address Books
Specify Notes Personal Address Book Replica Directory
Specify Notes PAB Directories
Specify How to Find Notes Archives
Specify Notes Archive Replica Directory
Specify Notes Archive Directories
Specify How to Determine Owner Using ACL
Select Administrative Users to Ignore
Generating Task
Configuration Summary
Creating Task
Specify Task Schedule
Task Progress
Task Completed
Introduction
Wizard process screens
SSDM Statistics Collection Wizard
The Log Viewer
Qsched.exe task-scheduling utility
Select Configuration
Select User Collection
Customize Configuration
Operations
Operations screen when migrating to a local, proprietary Exchange, or a "hosted Exchange"
Operations screen when migrating to Office 365, with Microsoft's AD sync
Operations screen when migrating to Office 365, without Microsoft's AD sync
Select Office 365 Administrative Operations
Configure Migration Notification Messages
Select Notes Administrative Operations
Specify Data for Migration
Specify How To Migrate Notes DocLinks
Notes Mail Files
Select Destinations for Migrated Data
Specify Mail Routing Options
Specify Notes to Exchange Mail Forwarding
Specify Remove Exchange Forwarding Settings
Specify Exchange to Notes Mail Forwarding
Specify Remove Notes Forwarding Settings
Select Notes User Visibility
Specify Active Directory Information
How Were Accounts Loaded into Active Directory
Specify Exchange Mailbox Information
Specify Notes Login Information
Select Date and Size Filters
Select Destination Exchange Server
Personal Archive Location
Specify Migration Run Information
Generating Task
Configuration Summary
Creating Task
Specify Task Schedule
Schedule Summary
Task Progress
Task Completed
Post-installation configuration
SSDM Scheduling Administration utility
Configuration for migration to on-premises Exchange
Configuration for migration to Office 365 without Migrator for Notes to Exchange's Admin Account Pool features
Configuration for migration to Office 365 using Migrator for Notes to Exchange's Admin Account Pool features
Log files
About SSDM Scheduling Administration
Before you can use the SSDM Scheduling Administration utility
Office 365 Admin Account Pool utility
To install and configure IIS version 7 or higher and the SSDM Scheduling Administration Web Service
To install and configure IIS 6 and the SSDM Scheduling Administration Web Service
Scheduling SSDM runs and limiting concurrent runs
Monitoring SSDM usage status
About the Account Pool utility
Necessary preparations for the Admin Account Pooling utility
PowerShell cmdlets for Migrator for Notes to Exchange
Appendix A: How do I ...?
Before you use the Admin Account Pool for the first time
For each Migrator for Notes to Exchange task you want to schedule
Managing the Admin Account Pool
Post-installation configuration
How do I set the account permissions necessary for migration?
How do I configure Migrator for Notes to Exchange for a non-English Notes locale?
Pre-migration preparations
Reconfiguring Outlook Categories
Renaming the Orphaned Documents folder
Defining new language sections
How do I enable remote management on an Exchange 2010 or later server?
How do I add or edit program parameters?
How do I migrate from a Notes environment with Symantec E-Vault?
How do I migrate to an Exchange environment with a CAS Array?
How do I prepare the SQL database for mailbox-enabling (if AD is configured for a resource forest and a user forest)?
How do I add to the list of AD attributes available for the merge function?
How do I configure AD to replicate an AD attribute to the Global Catalog?
How do I specify per-user locations for Notes source data?
How do I specify per-user destination locations for users' PST files?
How do I specify whether to migrate to a single PST file (per user) or multiple PST files?
How do I migrate Notes custom attributes?
How do I customize the placeholder message that the Data Migration Wizard substitutes for encrypted messages?
How do I customize the placeholder message that the Data Migration Wizard substitutes for filtered attachments?
How do I create or edit a template for personalized user-notification emails?
Batch-migration process
Other features
How do I schedule tasks?
How do I troubleshoot service startup permissions?
How to configure user rights
How to configure service logon information
How to configure the service to start up with the built-in system account
How do I send pre- or post-migration notification emails to end users?
How do I perform an offline migration?
How do I migrate resources?
How do I migrate mail-in databases?
How do I save and restore all Migrator for Notes to Exchange-defined collections from TSV files?
How do I prepare the SQL database for mailbox-enabling (if AD is configured for a resource forest and a user forest)?
This section applies only if your AD/Exchange environment is configured for a resource forest and a user forest, with corresponding user accounts. In that case, you must configure the Global Default Settings in Notes Migration Manager, and then prepare (or verify) the values in a column of the exported directory data, for the Data Migration Wizard to properly associate the resource accounts with the user accounts and properly enable mailboxes.
Before you begin, you must determine which column in the SQL database will correspond to which AD attribute, for the wizard to match corresponding user accounts in the resource forest and user forest. The column (AdSearchCol) and attribute (AdAttribute) are both specified in the [ActiveDirectory2] section of the Global Default Settings of Notes Migration Manager:
|
• |
AdSearchCol: The column in the SQL database whose values the program should search for each particular AdAttribute value, to match corresponding user accounts in the resource forest and user forest. Note that the column specified here and its per-user values must exist before the Data Migration Wizard is run. |
|
IMPORTANT: In the current Migrator for Notes to Exchange version, this AdSearchCol parameter value must be set to SearchKey2 (the default for this parameter) for the mailbox-enabling process to succeed. |
|
• |
AdAttribute: The AD attribute whose values the program should read in the AdSearchCol column of the SQL database, to match corresponding user accounts in the resource and user forests. For example: |
... tells the wizard to match AD objects with users such that the value of each AD object’s userPrincipalName attribute matches the value of the corresponding user’s SearchKey2 column in the SQL database.
|
1 |
Within Notes Migration Manager, select File | Global Default Settings. The program then opens the program’s configuration settings into Windows Notepad. Within Notepad, the settings look like the contents of an INI file, but they are actually saved as a part of the SQL database rather than as an independent INI file. |
|
1 |
Within Notes Migration Manager, in the Export Notes Directory screen: Click Export objects to TSV. A dialog box will prompt you for a destination folder and filename for the exported file. |
|
3 |
In the Export Notes Directory screen: Click Import objects from TSV to import the edited .tsv file into the SQL database. A dialog box will prompt you for the filename and its location. |
How do I add to the list of AD attributes available for the merge function?
The Provisioning Wizard associates contacts with AD objects by comparing the unique values of a particular AD object attribute to the unique values of a corresponding column in the SQL database. Where these values match, the associated contact and AD object are assumed to represent the same entity, and the two are therefore merged. During the wizard's run, the Choose Your Method... screen requires that you specify the AD attribute and the database column to use for these comparisons. The designations on that screen are accomplished by drop-down list boxes that list available options for the database column and AD attribute, respectively.
By default, the list of choices for the AD attribute contains these 26 options:
|
extensionAttribute1 |
The 26 defaults are defined by a series of ADML[#] parameters in the [ActiveDirectoryMatchList] section of the Global Defaults and Task Parameters:
If the AD attribute you want to use is not among the 26 defaults, you can add one or more other attributes to the list by defining each addition in the Global Defaults or Task Parameters. See How do I add or edit program parameters? above for the procedure to add and edit these parameter(s):
Each ADML[#] parameter names an AD attribute that the Provisioning Wizard will include in its list of options, from which one attribute must be chosen to facilitate the matching of contacts with AD objects. The digit(s) appended to an ADML[#] key name differentiate one parameter from another. The multiple ADML[#] parameters need not appear in numerical order, and need not form an uninterrupted numerical sequence. But the wizard will read only ADML[#] parameters whose differentiating digits are less than a value specified by a Count parameter (see below).
A limit to the number of ADML[#] parameters (see above) that the Provisioning Wizard will process in this section. The wizard will read only ADML[#] parameters whose differentiating digits are less than the Count parameter value. For example, if:
... then the wizard will read all of the parameters except ADML6 and ADML7, since Count=6, and neither 6 nor 7 is less than 6.
If unspecified, the Count parameter defaults to 26. If specified, the parameter must occur as the first line of the section, as shown above.
For example: If the ADML[#] parameters are set for only their 26 defaults, and you want to add a single new AD attribute option, you would add an ADML26 parameter and change the Count parameter to 27, like this:
How do I configure AD to replicate an AD attribute to the Global Catalog?
If the AD attribute you want to use for the Provisioning Wizard is not among the 26 defaults, you can add one or more other attributes to the list by defining each addition in the Global Defaults or Task Parameters. This procedure is explained elsewhere in this Appendix (see How do I add to the list of AD attributes available for the merge function?).
|
CAUTION: This procedure manipulates AD configuration parameters, and an error could generate adverse consequences throughout the Active Directory environment. Use extreme caution whenever manipulating AD configuration parameters in this way. |
|
2 |
|
3 |
|
4 |
|
5 |
Click Attributes, and wait for the list to expand. |
|
7 |
How do I specify per-user locations for Notes source data?
For PABs: To designate the locations of user PABs, enter the appropriate per-user values into one of these columns (not both):
|
• |
PABPaths column: The specific UNC path and filename for a user's Notes address book(s). Multiple address books can be designated by separating them with a pipe ( | ) character. Ordinarily the full path and file name are given, and file ownership is not checked. If a directory (only) is specified, all PABs found in the directory are assumed to be owned by the user. Examples: |
|
• |
SharedPabDirs column: A file system directory or Notes server directory that contains NSF files for multiple users. This column can be used to specify a more specific set of directories to scan for a user's data, so the application can scan a subset of a larger shared directory structure and determine the owner based on profile documents and/or ACLs. This is useful if a group of users to be migrated shares a directory structure and you can't be certain that all address books belong to just one user. If a file system path is specified here, ownership is checked based on the profile documents and/or ACLs. Examples: |
For Archives: To designate the locations of user archives, enter the appropriate per-user values into one of these columns (not both):
|
• |
ArchivePaths column: The specific UNC path and filename for a user's Notes archive file(s). Multiple archives can be designated by separating them with a pipe ( | ) character. Ordinarily the full path and file name are given, and file ownership is not checked. If a directory (only) is specified, all archives found in the directory are assumed to be owned by the user. Examples: |
|
• |
SharedArchiveDirs column: A file system directory or Notes server directory that contains NSF files for multiple users. This column can be used to specify a more specific set of directories to scan for a user's data, so the application can scan a subset of a larger shared directory structure and determine the owner based on profile documents and/or ACLs. This is useful if a group of users to be migrated shares a directory structure and you can't be certain that all address books belong to just one user. If a file system path is specified here, ownership is checked based on the profile documents and/or ACLs. Examples: |
For Mail Files: To specify per-user locations and filenames for users’ source mail files in the SQL database rather than from entries in the Data Migration Wizard, enter the appropriate per-user values into this column:
|
• |
MailFilePath column: The specific path and NSF filename to a user's mail file, used when an administrator knows the specific path and NSF file name for each user. Example: |
If the MailFilePath column does not exist or is left empty, the program will look for the user's mail file in the path entered in the Notes Data Locator Wizard (on the Specify Notes Mail File Directories screen).