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 parameter 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.
Identifies a Notes source folder from which archived non-calendar mail will be excluded from the migration. The Data Migration Wizard can discriminate between emails associated with calendar items (invitations, acceptance notifications, etc.), and other (non-calendar) emails, and can optionally exclude from the migration either type that originate from one or more designated source folders. Filter parameters in this [ArchiveMailFolderFilter] section identify the source folders from which archived non-calendar emails will be excluded. Other sections in this same Default Settings list may contain parameters to exclude other item types from certain source folders:
... 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 archived mail items (non-calendar-associated emails). 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 (see above) in the first line of the section.
This section contains a list of PowerShell URLs for each of the Office 365 clouds that are supported by MNE. These values are used by the Migration Console Exchange Server page to set the [Exchange] AzureADAuthorizationEndPointUri setting.
These [Categories] parameters are all auto-set parameters (see ) that define the Outlook categories that correspond to various English equivalents. The Setup program automatically sets these parameters to their English defaults. If a default is not correct for your locale, be sure to change it before you run the Data Migration Wizard.
This value corresponds to a GUI element in the Data Migration Wizard: the Calendar Co-Existence is using radio buttons in the Specify Mail Routing Options screen. 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 Mail Co-Existence is using radio buttons in the Specify Mail Routing Options screen. The parameter value is a single digit, 0, 1, 2 or 3, that determines how mail routing will be accomplished during coexistence:
This value corresponds to a GUI element in the Data Migration Wizard: the Using ActiveMail processing checkbox in the Specify Mail Routing Options screen. A marked checkbox (UsingActiveMail=1) tells the wizard to in turn set another parameter (NotesFormatPreference, documented separately in the [Notes] section below) for "Keep senders' format," which is the correct setting to enable Active Mail processing via CMN. An unmarked checkbox (UsingActiveMail=0) tells the wizard to set NotesFormatPreference for its "Prefers MIME" option, which is the correct setting when not using ActiveMail processing.
The Using ActiveMail processing checkbox is available only when the Quest Coexistence Manager for Notes radio button has been selected to specify that mail coexistence method. If some other coexistence method is selected, the Using ActiveMail processing checkbox appears grayed-out (unavailable).
The wizard writes this value to the Task Parameters depending on whether the associated checkbox is marked (1) or unmarked (0). Quest recommends you do not manually enter or change this value except at the direction of Quest Support.