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 specify per-user destination locations for users' PST files?
|
• |
PSTdir column: The directory where PSTs are stored for the user, used if each user's PST will go to a separate directory. Normally the admin would specify a central location for the wizard to create all PSTs, and the wizard would create a subtree under that. If the admin would rather put each PST in each user's home directory, then each user's home directory can be added here. Example: |
How do I specify whether to migrate to a single PST file (per user) or multiple PST files?
When migrating to .pst files, a program parameter in the Global Defaults and Task Parameters lets you specify whether the Data Migration Wizard should migrate all data into a single .pst file per user, or to multiple .pst files. The boolean parameter that controls this option is UseSeparatePSTs. By default (1), data is migrated to multiple .pst files. But:
... tells the wizard to migrate all data into a single .pst file per user.
If you are unfamiliar with the procedure to edit program parameters, see How do I add or edit program parameters? elsewhere in this Appendix.
How do I migrate Notes custom attributes?
A Notes message contains several standard attributes such as the From, To and Subject fields, and can also include user-defined fields. The Data Migration Wizard and SSDM can migrate custom Notes attributes from email messages and Notes contacts to unused properties in Exchange, but only if the migration app knows which properties in the target correspond to which attributes in the source. The migration of custom attributes therefore requires that these source-to-target attribute associations be mapped in a tsv data file before the migration, so Migrator for Notes to Exchange can refer to that file to migrate the attributes.
The attribute-mapping file must be a unicode (not ANSI) file named customattrs.tsv, in the default installation folder for the Data Migration Wizard (typically C:\Program Files\Quest\Migrator for Notes to Exchange), or in the folder containing notesdtapp.exe if you want to migrate Notes custom attributes via the SSDM. Migrator for Notes to Exchange installs a unicode attrs.tsv file, with the same column headings required for customattrs.tsv, that you can use as a template to create the customattrs.tsv file.
To create and prepare the customattrs.tsv file:
|
1 |
Use a text editor to open attrs.tsv, and save the open copy under the new name customattrs.tsv. Make sure you save customattrs.tsv as a unicode (not ANSI) file, in the folder(s) as noted above, and delete any data rows that may appear in the copy. |
|
• |
ID: Name of the custom attribute—a unique string that distinguishes this row’s custom attribute from all others in the file. |
|
IMPORTANT: If any data row(s) remain in the original attrs.tsv file, make sure that no ID value in customattrs.tsv is the same as any ID value in attrs.tsv. Custom attributes will not migrate correctly if any ID value appears in both files. |
|
• |
SourceProperty: Name of an attribute that has been added to a Notes mail message or a Notes contact, to be migrated to a property in Exchange. |
|
• |
TargetPropertySet: The GUID for the target property set, which must be one of these values: |
If the TargetPropertySet value is PS_PUBLIC_STRINGS or PS_MAPI, the familiar GUID for the set named will be substituted for the string provided.
TargetPropertySet can be left blank, but in that case TargetProperty (see below) must be an integer property ID in the range 0x0000-0x7FFF.
|
• |
TargetProperty: Name of the corresponding MAPI property in Exchange. A hexadecimal user-property value will be created in Exchange on each migrated mail message or contact with the Notes property, which will hold the value. The hexadecimal values of the created properties will be reported in the log (search for "custom attr" in the log file). |
If TargetPropertySet (above) is left blank, this TargetProperty value must be specified as a 16-bit integer in the range 0x0000- 0x7FFF that is not already defined for some other MAPI property.
|
• |
TargetPropertyType: Data type of the MAPI property, which must logically correspond to the data type used in Notes. Valid values are: |
|
3 |
Save and close the updated customattrs.tsv file. |
For example, a typical customattrs.tsv file might look something like this:
|
Archive ID |
Troubleshooting problems in migrating Notes custom attributes
You can use Microsoft’s MfcMapi.exe utility to view the property and its value, if they have been created. (The utility is a free download from Microsoft; Google "mfcmapi" and visit the www.microsoft.com/downloads link.) Most problems in migrating custom attributes can be diagnosed by these quick tests:
|
• |
Verify the target property specified in the customattrs.tsv file does not already exist, and that the target property is in the correct format. See About MAPI properties below for more information about this. |
|
• |
Verify that the customattrs.tsv file is UNICODE, not ANSI. |
|
• |
Verify that the last line in the customattrs.tsv file is followed by a line feed and carriage return (achieved by positioning the cursor at the end of the last line and pressing Enter). |
|
• |
If any data row(s) remain in the original attrs.tsv file, make sure that no ID value in customattrs.tsv is the same as any ID value in attrs.tsv. Custom attributes will not migrate correctly if any ID value appears in both files. |