Quest recommends you set these parameters as suggested here:
1 |
If a MAPI call fails with one of the errors listed in the MAPIErrorsToRetry list, the API call is made again after pausing for the number of seconds specified by MessageRetryWait. MNE keeps retrying for a maximum of MAPIRetryCount times. |
3 |
If the attempt to open a new MAPI session fails, MNE waits for the number of second specified by MessageRetryWait and tries opening a new session again. MNE keeps trying to reconnect for a maximum of MaxSessionReconnectCount times. |
6 |
MNE attempts to migrate each object using the algorithm above up to a maximum of MessageRetryCount times. If MNE reaches the MessageRetryCount limit, it assumes that there is something wrong with the object itself and it proceeds to the next object to be migrated. |
IMPORTANT: If you set the MessageRetry parameters to values higher than their defaults, consider also adjusting the WatchDogMinutes parameter as described in the next Important note below. |
• |
WatchDogMinutes parameter |
IMPORTANT: If you set the MessageRetry parameters (see above) to values higher than their defaults, consider also adjusting the WatchDogMinutes parameter. Quest recommends you set WatchDogMinutes at the greater of: its 180-minute default, or a setting of 10 minutes for every 30 seconds of retry waiting (MessageRetryCount x MessageRetryWait). |
Conditional Substep: This substep applies only if you will provision Office 365 from a local AD. |
In Migrator for Notes to Exchange’s Global Defaults: If you intend to provision Office 365 from a local AD (only), Quest recommends you set these parameters as suggested here:
Conditional Substep: This substep applies only if you are migrating to Office 365 Wave 15. |
• |
Configurable limit for PowerShell connections: This parameter lets an admin specify a per-server limit for the number of concurrent PowerShell connections Migrator for Notes to Exchange can open. For example: |
• |
Configurable "wait" for idle remote PowerShell connections: This parameter lets an admin specify how long (in seconds) Migrator for Notes to Exchange will hold open an idle remote PowerShell connection before closing it. The default: |
Conditional Substep: This substep applies only if you intend to 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. Migrator for Notes to Exchange’s 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 someone map these source-to-target attribute associations in a tsv data file, before the migration, so the migration apps can refer to that file to migrate the attributes.
This 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), and also in the folder containing notesdtapp.exe if you want to migrate Notes custom attributes via the SSDM. Either or both migrator applications can refer to this file to map the source attributes to free (unused) properties in the MAPI target mailboxes.
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.
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: |
• |
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). |
• |
TargetPropertyType: The data type of the MAPI property, which must logically correspond to the data type used in Notes. Valid values are: STRING, MV_STRING, LONG, SYSTIME, BOOLEAN. |
3 |
Save and close the updated customattrs.tsv file. |
For example, a typical customattrs.tsv file might look something like this:
Archive ID |
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 that 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 (position the cursor at the end of the last line and press 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. |
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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center