Migrator for Notes to Exchange 4.15.2 - Program Parameters Reference Guide

[Outlook] section

This value corresponds to a GUI element in the Data Migration Wizard: the Subdirectories of root directory... vs. Directory specified by the PstDir column... radio-button choice in the Personal Archive Location screen. Valid values are “DN” and “CSV,” where:

The Wizard writes this value to the Task Parameters from an admin's GUI entry; Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

Specifies a PST filename format. The parameter value must be one of the following integers:

This value corresponds to a GUI element in the Data Migration Wizard: the pst output root directory text box in the Personal Archive Location screen. The Wizard writes this value to the Task Parameters from an admin's GUI entry; Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

[OutlookRestApiUrls] section

This section contains a list of URLs for each of the Office 365 clouds that are supported by MNE. These values are used by the Migration Console’s Exchange Server page to set the [Exchange] OutlookServicesUrl setting in the SSDM’s NotesDTApp.ini file.

The values in this section should only be modified at the direction of Quest support.

[PAB] section

Determines whether the Data Migration Wizard will tag migrated PAB entries with the Notes source folder category. For example:

... tells the Data Migration Wizard to tag migrated PAB entries with the Notes source folder category, as it always did in prior releases. By default (0) the wizard will not tag migrated PAB entries.

[PersonDocCustom] section

Determines which PersonDoc<#> parameters (see below) the wizard will process in this [PersonDocCustom] section. If a Count parameter is specified with a value > 0, then the wizard will read only PersonDoc<#> parameters whose differentiating digits are less than the Count parameter value. That is, the keyname digits of multiple PersonDoc<#> parameters need not form an uninterrupted numeric sequence, but if they don't the wizard will read only the parameters whose digits are less than the Count value.

For example, if:

... then the wizard will read PersonDoc0 and PersonDoc2, but not PersonDoc3 or PersonDoc5, since neither 3 nor 5 is less than the value of the Count.

If unspecified, the Count parameter defaults to 0, in which case the wizard will read only the PersonDoc<#> parameters whose differentiating digits form an uninterrupted numeric sequence beginning at 0 (PersonDoc0).

Determines whether a multi-valued assignment to a Notes person-document field (via the <NotesFieldName> parameter) will overwrite the current field contents (MergeMultiValuedProperties=0) or be added to the current contents (1). See the entry for <NotesFieldName> parameters, also in this [PersonDocCustom] section, for information about assigning multiple values to a single Notes field.

Each <NotesFieldName> parameter assigns a value to the named Notes person-document field, but only if the <NotesFieldName> appears as the value of a corresponding PersonDoc<#> parameter (also in this [PersonDocCustom] section). Any such assignment will be ignored if the <NotesFieldName> has not been defined (to the wizard) by a PersonDoc<#> parameter.

The key name for a <NotesFieldName> parameter must match exactly the value of a corresponding PersonDoc<#> parameter that defines the <NotesFieldName> to the wizard. For example, to define these person-document fields and then have the wizard assign values to them:

Value assignments by these <NotesFieldName> parameters will overwrite any other person-document field values set by other features during migration, mail routing or Notes administrative functions. All of the features facilitated by this [PersonDocCustom] section are enabled only if Migrate users is selected on the wizard's Operations screen.

If a Notes field capable of containing multiple values already contains one or more values, the MergeMultiValuedProperties parameter (also in this [PersonDocCustom] section) determines whether a value assignment via a <NotesFieldName> parameter will overwrite or be added to the current field contents.

For a multi-valued Notes field, you may assign multiple values via a <NotesFieldName> parameter by using a pipe character to separate the values, like this:

Any spaces preceding or following a pipe character are ignored.

To clear any existing contents of a Notes person-document field, define the PersonDoc<#> parameter for the field and then add the corresponding <NotesFieldName> parameter with the value left blank, like this:

Each PersonDoc<#> parameter defines (to the wizard) a Notes person-document field to which the wizard may then assign a value. The value assignment is then accomplished by a corresponding <NotesFieldName> parameter (also in this [PersonDocCustom] section).

The Notes field defined by a PersonDoc<#> parameter may or may not already exist in Notes. If the field does not already exist in Notes, the wizard will create it. For example, to define the User Name and Mail Server fields in a person document, you might set:

See the above entry for <NotesFieldName> parameters for an example of how PersonDoc<#> and <NotesFieldName> parameters are used together to define person-document fields and then have the wizard assign values to them.

PersonDoc<#> parameter values are case-insensitive:

The digits appended to PersonDoc<#> key names arbitrarily differentiate one parameter from another. Multiple PersonDoc<#> parameters need not appear in numerical order, and need not form an uninterrupted numeric sequence if a Count parameter is also specified (also in this [PersonDocCustom] section) to determine which parameters to read and which to ignore. If the Count value > 0, the wizard will read only PersonDoc<#> parameters whose differentiating digits are less than the Count value. If no Count parameter is specified (or if Count=0), the wizard will read only PersonDoc<#> parameters whose digits form an uninterrupted numeric sequence beginning with 0.

All of the features facilitated by this [PersonDocCustom] section are enabled only if Migrate users is selected on the wizard's Operations screen.