Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.15.2 - Administration Guide

About the Migrator for Notes to Exchange documentation Notes Migration Manager NABS Discovery Wizard Internet Domains Discovery Wizard Directory Export Wizard Collection Wizard Groups Provisioning Wizard Notes Data Locator Wizard Provisioning Wizard Send PAB Replicator Wizard Data Migration Wizard SSDM Statistics Collection Wizard The Log Viewer Qsched.exe task-scheduling utility SSDM Scheduling Administration utility Office 365 Admin Account Pool utility PowerShell cmdlets for Migrator for Notes to Exchange Appendix A: How do I ...?
Post-installation configuration Pre-migration preparations Batch-migration process Other features

How do I specify per-user destination locations for users' PST files?

How do I specify per-user destination locations for users’ PST files?

Per-user destination locations for users’ new PST files are (if necessary) specified in the SQL database. To edit the contents of the SQL database, you must export the data to a .tsv (tab-separated-values format) file, then edit the contents of the table, and then import the edited .tsv file back into the SQL database.

To specify per-user destinations for users’ new PST files in the SQL database rather than from entries in the Data Migration Wizard, enter the appropriate per-user values into this column:

•
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:
\\server\home\user

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:

UseSeparatePSTs=0

... 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.
2
Enter a data row for each Notes custom attribute you want to migrate, as follows:
•
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:
PS_PUBLIC_STRINGS
PS_MAPI
{HHHHHHHH-HHHH-HHHH-HHHH-HHHHHHHHHHHH}
... where each 'H' is a hexadecimal character, with letters capitalized.
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:
STRING
MV_STRING
SYSTIME
BOOLEAN
LONG
Also, "PT_" may be prepended to any of the five types above, so valid values include PT_STRING, PT_MV_STRING, etc.
3
Save and close the updated customattrs.tsv file.

For example, a typical customattrs.tsv file might look something like this:

 

ID

SourceProperty

TargetPropertySet

TargetProperty

TargetPropertyType

Attr1
Attr2
Attr3
Attr4
Attr5

EV26C5E2CCF2B9267C.ArchiveId
EV26C5E2CCF2B9267C.ArchivedDate
EV26C5E2CCF2B9267C.SaveSetId
EV26C5E2CCF2B9267C.RetentionCategory
EV26C5E2CCF2B9267C.HasAttachments

{D0F41A15-9E91-D111-84E6-0000F877D428}
{D0F41A15-9E91-D111-84E6-0000F877D428}
{D0F41A15-9E91-D111-84E6-0000F877D428}
{D0F41A15-9E91-D111-84E6-0000F877D428}
{D0F41A15-9E91-D111-84E6-0000F877D428}

Archive ID
Archived Date
Saveset ID
Retention Category
EVLotus_HasAttachments

STRING
STRING
STRING
STRING
STRING

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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating