Migrator for Notes to Exchange 4.17 - 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:

NOTE: If PstFileNameFormat=0, (Source Notes filename), MNE uses the default value [General] UseSepartatePSTS=1 (migrate to multiple PSTfiles). Naming the PST file after the source Notes file implies that each PST target has a different file name.

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.

[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, 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:

... 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 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 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 add the corresponding <NotesFieldName> parameter with the value left blank, like this:

Each PersonDoc<#> parameter defines a Notes person-document field to which the wizard can assign a value. The value assignment is 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 creates it. For example, to define the User Name and Mail Server fields in a person document, you might set:

See the previous entry for <NotesFieldName> parameters for an example of how PersonDoc<#> and <NotesFieldName> parameters are used together to define person-document fields and 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 the features facilitated by this [PersonDocCustom] section are enabled only if Migrate users is selected on the wizard's Operations screen.

[PowerShell] section

Determines how long (in seconds) Migrator for Notes to Exchange will hold open an idle remote PowerShell connection before closing it. This feature applies only to the duration of an idle state during a connection. Each command run resets this timer to zero, so a series of commands with only short idle periods between commands could keep the connection open indefinitely. The default IdleConnectionTimeoutSeconds=30 is suitable for most environments.

IdleConnectionTimeoutSeconds=0 would tell Migrator for Notes to Exchange to not wait (wait 0 seconds) for a second command after a first, so would close any PowerShell connection immediately after only one command. The default is 30 seconds for migration to a proprietary Exchange, or 60 seconds for migration to Microsoft 365.

Determines the migration-server-wide limit for the number of concurrent PowerShell connections Migrator for Notes to Exchange can open. For example, if MaxPowerShellConnections=2, a four-thread migration might proceed like this:

Note: The default setting (MaxPowerShellConnections=0) is interpreted as "no limit," effectively turning off this limiting feature.

Determines whether Migrator for Notes to Exchange will use a secure socket layer (SSL) connection to connect to the remote PowerShell session of an on-premises Exchange server. By default (0) the parameter does not use SSL to connect.