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 application knows which properties in the target correspond to which attributes in the source. The migration of custom attributes requires that the source-to-target attribute associations be mapped in a tsv data file before the migration so that Migrator for Notes to Exchange (MNE) can refer to the file to migrate the attributes.
The attribute-mapping file must be a Unicode (not ANSI) file named customattrs.tsv located 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. MNE 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.
|
1 |
Use a text editor to open attrs.tsv, and save the open copy under the new name customattrs.tsv. Ensure you save customattrs.tsv as a unicode (not ANSI) file, in the folder(s) as previously specified. 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 rows remain in the original attrs.tsv file, ensure 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: |
|
• |
TargetProperty: Name of the corresponding MAPI property in Exchange. A hexadecimal user-property value is 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 are reported in the log (search for "custom attr" in the log file). |
|
• |
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:
|
ArchiveId |
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. You can search in Google for "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 E). |
|
• |
If any data rows remain in the original attrs.tsv file, ensure 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. |
About MAPI properties
An unnamed property's name is a 16-bit integer in the range 0x0001 to 0x7FFF. That 16-bit integer is valid in all mailboxes. Examples of unnamed properties are 0x0070 (i.e., PR_CONVERSATION_TOPIC) and 0x6656, both of which happen to be used by MAPI. So these two examples cannot be used as target property values for message attributes since they are already used, although they may be used to map Notes contact attributes to Exchange.
A custom property can be unnamed or named. If it is unnamed, you must select a 16-bit integer TargetProperty in the range 0x0001 to 0x7FFF that is not already in use by MAPI. If it is named, you can select any property-set GUID. If you select a property set that is already in use, you must choose a 32-bit integer or string ID that is not already in use in that property set. If you select a brand new property-set GUID, you need not worry about IDs already in use because there will not be any.