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.
2 |
If a unique match is not found, a list of preferred time zones (configured in the [TimeZoneInfo] section) is compared to the list of potential matches. The first successful compatible match from the list of preferred time zones is selected. |
The [TimeZoneInfo] section lists your preferred time zones from the Windows Time Zone database. Each time zone is specified with its unique identifier. You can retrieve a full list of Windows time zone identifiers using the following PowerShell cmdlet:
The cmdlet returns a table of time zone DisplayName and Id values.
The Id value is used in the [TimeZoneInfo] section. The [TimeZoneInfo] collection is configured by providing the Id values of the preferred time zones. Each value in the [TimeZoneInfo] section should be prefixed with the name TimeZoneN, where N represents a counter starting at 0. Below is a sample configuration of the [TimeZoneInfo] section:
For most migrations, configuring the [TimeZoneInfo] section should be sufficient to determine the correct time zone for scheduled meetings and appointments. However, if two very similar time zones are being used, the migration may have difficulty identifying the correct time zone. Configuring the [TimeZoneNames] section can provide additional guidance.
Each Notes meeting and appointment contains a time zone description string similar to the following:
The ZN parameter of the string identifies the name of the time zone. If the appointment was scheduled from a Windows client or browser, the name corresponds to a name in the Windows time zone database and a unique time zone match is assured. If the appointment was scheduled from a mobile device or a non-Windows operating system, the time zone name will not match a Windows time zone and additional steps must be taken.
In the example shown above, scheduled from an Android device, the time zone America/New_York corresponds to the Windows time zone identifier Eastern Standard Time. You can configure the [TimeZoneNames] section to map non-Windows time zone names to their Windows equivalent. For example:
The value on the right corresponds to the identifier of the Windows time zone. See the [TimeZoneInfo] section for details on retrieving the correct time zone identifier.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy