[ArchiveMailFolderFilter] 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 parameter value. For example, if:
... the wizard will read all 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:
Within each such section, each parameter identifies a single source folder to which the filter will be applied. For example:
... 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.
[Categories] section
These [Categories] parameters are all auto-set parameters (see GUI-set and other “auto-set” parameters) 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.
See the explanatory note at the beginning of this [Categories] section. The English equivalent (default) for this parameter is: C=Clients
See the explanatory note at the beginning of this [Categories] section. The English equivalent (default) for this parameter is: H=Holiday
See the explanatory note at the beginning of this [Categories] section. The English equivalent (default) for this parameter is: P=Projects
See the explanatory note at the beginning of this [Categories] section. The English equivalent (default) for this parameter is: PC=Phone Calls
See the explanatory note at the beginning of this [Categories] section. The English equivalent (default) for this parameter is: T=Travel
See the explanatory note at the beginning of this [Categories] section. The English equivalent (default) for this parameter is: V=Vacation
[Coexistence] section
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:
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 Using ActiveMail processing check box in the Specify Mail Routing Options screen. A marked check box (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 check box (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 check box 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 check box appears grayed-out (unavailable).
The wizard writes this value to the Task Parameters depending on whether the associated check box is marked (1) or unmarked (0). Quest recommends you do not manually enter or change this value except at the direction of Quest Support.
[DirectoryExport] section
Quest recommends that you do not manually enter or change this value except at the direction of Quest Support. When set to 1, this parameter allows MNE to export Notes mail-in databases that have duplicate Notes addresses from a Notes directory. This parameter should be used only in special migration projects with the assistance from Quest PSO.
Determines whether the Directory Export Wizard will (1) or will not (0) support other forms of SMTP addresses for distribution group members in addition to the "bare" SMTP addresses (e.g., user@sitraka.com). For example:
... tells the wizard to also accept SMTP addresses for distribution group members in either of these forms:
Determines whether the Directory Export Wizard will create a TSV file to capture the data for Notes objects that had addresses which were auto-resolved by the wizard. An Address Issues Report button appears on Task Completed screen if the TSV file is created. The administrator can click the button to open the TSV file to confirm the addresses. This parameter controls only whether the wizard generates a TSV file for the auto-resolved addresses.
Quest recommends that you do not manually enter or change this value except at the direction of Quest Support. This parameter is used to specify the default Domino Notes Domain name for address resolution when the Notes property FromDomain is empty and Notes domain name was not found in a mail message during migration. This parameter is needed only when duplicate Notes addresses are allowed in the MNE database in special migration projects.
Determines whether the Directory Export Wizard will create a TSV file to capture data for Notes objects that the wizard skipped due to conflicting (duplicate) primary SMTP addresses. The administrator can use the TSV file to script and/or otherwise make corrections to data in the Migrator for Notes to Exchange database. Migrator for Notes to Exchange always skips such objects. This parameter controls only whether the wizard generates a TSV file for the skipped object data.
Determines if MNE generates secondary addresses based on the enabled domains on the Find Domains page of the MNE console. By default (GenerateAliases=1), MNE generates secondary addresses. When set to (0), MNE does not generate secondary addresses for the user. Regardless of the INI setting, if the user document on the Domino server contains secondary internet addresses, MNE always adds them to the MNE database as secondary addresses.
Determines whether the wizard will (1) or will not (0) extract objects with a Notes canonical forwarding address set to forward to another user.
Determines which of two methods the Directory Export Wizard uses for NSF queries. This parameter lets you configure the wizard to be more "forgiving" if it encounters a rare Field is too large error that can occur when querying certain unreadable NSF files. By default. (NoSummary=0), the error would prevent the wizard from retrieving data from the remaining Notes source documents and the export would fail. But if:
... the wizard opens all Notes object records one at a time, rather than opening all non-group object records at once to facilitate a continuous stream of data from all open records. Quest recommends you leave this feature off (NoSummary=0) unless you have encountered the Field is too large error, since program performance is likely to suffer (perhaps dramatically) if the wizard has to open and close many object records individually.
In either case, the wizard reports such errors in its log file, but if NoSummary=1 the wizard ignores the error and resumes reading the remaining source data.
Determines whether the Directory Export Wizard will clear stale secondary addresses in the MNE database. By default (ResolveStaleAliases=0), MNE keeps all the secondary addresses generated in every Directory Export run. When set to (1), MNE replaces the stale secondary addresses with the latest address for each user to accommodate Domino directory updates during the transition.
Determines whether the wizard will suppress Domino catalog lookups during the export process, but still leave all other data sources online. This is an alternative to a completely offline migration, and may improve performance in some environments. For example:
… tells the wizard to enable the feature, to suppress Domino catalog lookups. The default (SkipCatalogSearch=0) leaves this option disabled.
Determines whether the Directory Export Wizard will export or skip group member information. For example:
… tells the wizard to skip (not export) group member information.
Determines whether the Directory Export Wizard will write export data directly to the Bulk Import folder rather than to the temp directory, which yields significant performance improvements in many environments. If that newer method is unsuitable to your configuration, this boolean program parameter lets you revert to the prior method. For example:
... tells the wizard to use the older method. Quest recommends this setting if the bulk directory is not located on the migration server or if the admin's migration server is running Windows XP.
