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.
Determines how long (in seconds) the Migration Wizard will wait after setting admin permissions on an Office 365 mailbox before proceeding with the migration. For example, the default PropagationDelay=40 tells the wizard to wait 40 seconds before proceeding. This can be helpful to resolve permissions issues resulting from an O365 Powershell-Exchange propagation delay.
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.
This value corresponds to a GUI element in the Data Migration Wizard: the Migrate calendar data checkbox in the Migrate mail data section of the Specify Data for Migration 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.
Determines whether the wizard should attempt to migrate the encrypted portions of encrypted messages in the source server. Typical usage is described below. This feature can also be applied to encrypted messages in users' archives, by this same parameter name in the [ArchiveData] section of these parameters. The feature is also available for the SSDM (in notesdtapp.ini), but in SSDM the default is 1.
This MigrateEncryptedMessages parameter lets you choose whether the wizard should even attempt to migrate the encrypted portions of encrypted messages. If access credentials for encrypted messages are more restrictive, the default MigrateEncryptedMessages=0 tells the wizard to not even attempt migrating the encrypted portions, but to just migrate the unencrypted portions with the substitute notice.
If MigrateEncryptedMessages=1, the wizard will attempt to migrate the encrypted portions, and will succeed or fail depending on whether the admin account running the wizard has the necessary credentials. If it fails, the wizard will migrate the message, skip the unencrypted portions and insert the substituted notice—the same outcome as for MigrateEncryptedMessages=0.
A related parameter lets you tell the wizard to skip an entire message (both encrypted and unencrypted portions) if the wizard is already configured to skip the encrypted portion (only) by MigrateEncryptedMessages=0. See SkipEntireEncryptedMessage in this same [ServerData] section for more information.
This value corresponds to a GUI element in the Data Migration Wizard: the Migrate e-mail messages checkbox in the Migrate mail data section of the Specify Data for Migration 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.
This value corresponds to a GUI element in the Data Migration Wizard: the Migrate task data checkbox in the Migrate mail data section of the Specify Data for Migration 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.
This value corresponds to a GUI element in the Data Migration Wizard: the Migrate trash folder checkbox in the Migrate mail data section of the Specify Data for Migration 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.
Determines whether and how the Data Migration Wizard will migrate archive items that occur within Notes views. For example, MigrateViews=1 tells the wizard to migrate items only from the first view in which they are found. Valid parameter values are:
Note that the wizard will initialize this parameter to 1 if it is omitted from the task INI file, even though technically the program default is 1. You must explicitly include the parameter in Global Defaults or Task Parameters if you want the wizard to run with MigrateViews=0 or MigrateViews=2.
Determines whether the wizard will migrate out-of-office messages. For example, OOF=1 tells the wizard to migrate out-of-office messages. By default (OOF=0), the wizard will not migrate out-of-office messages.
If the wizard is set to migrate out-of-office messages (OOF=1), the behavior can be configured using the [Exchange] AllowExternalOOF parameter.
NOTE: Migration of out-of-office messages (OOF=1) is not supported if the migration target is set to Personal folder (.pst). |
Determines whether the Data Migration Wizard will skip entire encrypted messages (skip both encrypted and unencrypted portions) in the source server data if the wizard is already configured to skip the encrypted portions by MigrateEncryptedMessages=0 (also in this [ServerData] section).
SkipEntireEncryptedMessage=1 tells the wizard to skip any encrypted messages entirely if MigrateEncryptedMessages=0. This SkipEntireEncryptedMessage parameter is irrelevant and ignored if MigrateEncryptedMessages=1.
For more information about how encrypted messages are migrated, and how this SkipEntireEncryptedMessage parameter helps control how the wizard processes encrypted messages, see the parameter notes for the MigrateEncryptedMessages parameter earlier in this [ServerData] section.
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:
... 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.
... tells the wizard to apply the filter to the Inbox, while the section name in this example tells the wizard that the filter to be applied should exclude mail items (non-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, like these examples:
~INBOX: Inbox |
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.
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center