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.
... 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.
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 execution 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 Office 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.
A limit to the number of Filter<#> parameters (see below) that the Data Migration Wizard will process in this section. the wizard will read only Filter<#> parameters whose differentiating digits are less than the Count value. For example, if:
|
[ServerCalFolderFilter] |
... then the wizard will read all of the parameters except Filter19, since Count=15 and 19 > 15. If unspecified, the Count parameter defaults to 10. If specified, the parameter must occur as the first line of the section, as shown above.
Within each such section, each parameter identifies a single source folder to which the filter will be applied. For example: [ServerCalFolderFilter] Filter0=~INBOX tells the wizard to apply the filter to the Inbox, while the section name in this example tells the wizard that the filter should exclude calendar-associated emails that reside on the server. For each such parameter, the parameter value specifies the mailbox by prepending a tilde character to the mailbox name, as follows:
You may define one or more Filter<#> parameters within the section. The digit(s) appended to a Filter<#> key name differentiate one parameter from another. Multiple Filter<#> parameters need not appear in numerical order, and need not form an uninterrupted numeric sequence. For example, a section may contain only:
But the wizard will read only Filter<#> parameters whose differentiating digits are less than a value specified by a Count parameter in the first line of the section. See the Count parameter above for more information.
© 2020 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy
