Migrator for Notes to Exchange 4.16.3 - Program Parameters Reference Guide

[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.

[ErrorsToIgnore] section

Each Error<#> parameter identifies a single particular runtime error that the wizard or program should ignore when documenting its activities and outcomes in its log file. Each parameter value:

For example:

The digit(s) appended to an Error<#> key name arbitrarily differentiate one parameter from another. Multiple Error<#> parameters need not appear in numerical order, need not form an uninterrupted numeric sequence, and need not begin at 0. But the wizard will read only Error<#> parameters whose differentiating digits are within the range 0-99 inclusive.

[Exchange] section

This value corresponds to the GUI element in the Notes Migration Manager, the Automatically grant permissions check box in the Exchange Server configuration screen. This parameter is available only for Microsoft 365 (Exchange Online) targets. (When the target is on-premises Exchange, the AddReceiveAsPermission parameter corresponds to the check box.)

When the target is Microsoft 365 and the check box is selected and applied, MNE checks to see if the Migration Account (or assigned Admin Pool account) has Full Access permission on the target mailbox. If it does not, MNE temporarily grants Full Access permission for the duration of the migration.

There can be a significant delay between granting Full Access permission and Microsoft 365 allowing the account to access the mailbox.

The following PowerShell cmdlets can be used to grant Full Access permission before a migration (and to revoke permission after the migration)

This is the recommended method of granting permission to the admin account for the migration. If you are using the PowerShell cmdlets to grant access, disable the built-in mechanism by clearing the check box.

Permits prepending an http scheme to migrated online meeting URLs. The parameter value is a single-digit keyword that specifies which string, if any, to prepend to the URL:

By default (AddOnlineMeetingUrlScheme=0), Migrator for Notes to Exchange prepends nothing to the URL.

This value corresponds to the GUI element in the Notes Migration Manager, the Automatically grant permissions check box in the Exchange Server configuration screen. This parameter is available only for on-premises Exchange targets. (When the target is Microsoft 365, the AddFullAccessPermission parameter corresponds to the check box.)

When the target is on-premises Exchange and the Automatically grant permissions check box is selected and applied, MNE checks whether the Exchange service account has Receive-As permission on the mailbox database container. If it does not have permission, MNE grants the Receive-As permission on the mailbox database container. MNE also verifies that the Exchange service account is not added to any administrative groups that are explicitly denied access to the mail stores. These groups include Enterprise Admins, Domain Admins, and the Organization Management role.

There can be a significant delay between granting Receive-As permission and Exchange allowing the account to access mailboxes, up to 30 minutes. Alternately, you could grant the permissions using the following PowerShell cmdlet:

However, if you grant permissions manually using PowerShell, you must reconfigure the account each time a new database is added. If you use the Automatically grant permissions option, MNE grants permissions on the database container and the permissions are inherited by all databases, even the databases that are added after initial configuration. If you are using the PowerShell cmdlet to grant access, disable the built-in mechanism by clearing the check box.

Specifies the name of the identity parameter for the UpdateAddressList cmdlet, which the wizard will run after mailbox-enabling a collection if UpdateAddressList=1 (also in this [Exchange] section). See the UpdateAddressList parameter description for more information.

Specifies the name of the identity parameter for the UpdateEmailAddressPolicy PowerShell cmdlet, which the wizard runs when mailbox-enabling a collection if UpdateEmailAddressPolicy=1 (also in this [Exchange] section). See the UpdateEmailAddressPolicy parameter description for more information.

In Notes and iNotes, when users set a task reminder to X days, hours, minutes before or after the task start date, the alarm notification is triggered X days, hours, minutes before or after 12:01 PM of the task start date.

When this parameter is set to the default value (1), after migration the alarm notification is triggered X days, hours, minutes before or after 12:00 AM instead of 12:01 PM.

To retain the Notes task alarm behavior and trigger the alarm before or after 12:01 PM, set this parameter to 0.

Associated with Migrator for Notes to Exchange’s Admin Account Pool features (see the chapter “Microsoft 365 Admin Account Pool utility” in the Migrator for Notes to Exchange Administration Guide), this parameter specifies the number to assign to the first of a series of Admin Account Pool accounts grouped under the name specified by the AdminAcctPoolRoleGroupName parameter below.

Associated with MNE’s Admin Account Pool features (see the chapter “Microsoft 365 Admin Account Pool utility” in the MNE Administration Guide), this parameter specifies the name of an Admin Role Group used to assign administration roles to the accounts in the Admin Account Pool. If the role group does not exist, the Microsoft 365 Admin Account Pool utility creates the group and assigns the following roles to the group:

Associated with the MNE Microsoft 365 Admin Account Pool feature, this parameter specifies the prefix of the name of Admin Account Pool users that are assigned administration roles through the Admin Pool Role Group. For more information, see the chapter titled "Microsoft 365 Admin Account Pool utility" in the Migrator for Notes to Exchange Administration Guide.

If parameter is missing or empty, the Microsoft 365 Admin Account Pool utility uses the name of the Exchange Admin user account as prefix with a sequence number suffix. Sequence numbers are specified by the AdminAcctPoolFirstAccountSeq parameter in addition with the prefix to create the Admin pool account name.

This value corresponds to a GUI element in the Notes Migration Manager, the Administrator user domain text box in the Exchange Server configuration screen. The program writes this value to the Task Parameters from a GUI entry; Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

The parameter value documents the Windows domain required for the administrator's MAPI profile. This field is required for silent-mode operation. For example:

This value corresponds to a GUI element in the Notes Migration Manager: the Administrator SMTP address text box in the Exchange Server Configuration screen. The program writes this value to the Task Parameters from a 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 Notes Migration Manager: the Administrator password text box in the Exchange Server Configuration screen. The program 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.

The parameter value documents the Windows password required for the administrator's MAPI profile. This field is required for silent-mode operation. For example:

Occurs in: Data Migr. This is an internal scratch parameter (see Transient “scratch” parameters).

This value corresponds to a GUI element in the Notes Migration Manager: the Administrator user name text box in the Exchange Server Configuration screen. The program 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.

The parameter value documents the Windows username required for the administrator's MAPI profile. This field is required for silent-mode operation. For example:

AdminUsername=WilburBurns

Works in conjunction with [ServerData]OOF which controls if out-of-office messages are migrated from Notes. By default, [ServerData]OOF is set to 0, meaning out-of-office messages are not migrated. When [ServerData]OOF=1, then [Exchange]AllowExternalOOF and its assigned value is applied.

Valid values are the following single-digit integers:

If the value is set to anything but 0, 1 or 2, the setting defaults to 0.

Determines whether HTML information in the Description field of calendar appointments and tasks will migrate. The default:

… tells the wizard to migrate such information. The feature can be disabled by AllowHTMLCalendarBodies=0.

When migrating to Microsoft 365, if you set this parameter to 1, MNE checks the target mailbox settings for message size restrictions against the maximum message size allowed for sending and receiving messages in the Exchange Online mailbox. If the current set message size is smaller than the maximum message size allowed (such as 153600 KB bytes), during the migration MNE temporarily sets the message size to the maximum limit allowed for the target mailbox. MNE restores the original message size restrictions at the end of the migration.

By default, the parameter is set to off (0). If user data migration results in a specific MaxSubmissionExceeded error and a large message cannot be migrated to the Exchange Online mailbox because the message size restriction (default is 35 MB) is smaller than the maximum size limit allowed, it is recommended that you set the maximum size limit allowed well before migration starts (to allow for the propagation delay). You can use the PowerShell command "Set-Mailbox Identity -MaxReceiveSize 150MB -MaxSendSize 150MB" to set the maximum allowed limit before migration starts.

Alternately, you can set the AllowO365MailboxMaxMessageSize parameter and remigrate the message. It is recommended that you use the [Exchange] MigrateOversizedAttachments parameter to migrate large message attachments to the OneDrive store, resulting in smaller message sizes and increasing the chance for the message to be migrated to the target without hitting the size limit.

Determines whether or not the signer of the Exchange server certificate is verified against the list of trusted root certificate authorities. This setting is applied when performing calls to the Autodiscover service, and when connecting with MAPI using the Outlook Anywhere protocol. This setting can be useful when evaluating the product in a test lab where the Exchange servers have not been configured with properly signed certificates.

This parameter is used when migrating with the MNE MAPI/HTTP library or with Outlook MAPI. If you are migrating with Outlook MAPI, this parameter is used only when migrating with Outlook 2010 or 2013.

This value corresponds to a GUI element in the Data Migration Wizard, the Overwrite existing mail forwarding address radio buttons in the Specify Exchange to Notes Mail Forwarding Settings screen. Quest recommends you do not manually enter or change this value except at the direction of Quest Support. The parameter value tells the wizard whether to set, update or remove mail forwarding, per the administrator’s instructions in other program entries, even if the wizard detects an existing forwarding address or rule already in place for a particular user. Valid values are single-digit integer:

This value corresponds to a GUI element in the Data Migration Wizard, the Remove existing forwarding address radio buttons in the Specify Remove Exchange Forwarding Settings screen. Quest recommends you do not manually enter or change this value except at the direction of Quest Support. The boolean parameter value tells the wizard whether it should refrain from removing an existing forwarding address or rule in Exchange if its domain does not match a ForwardingDomain parameter value (also in this [Exchange] section, and also derived from a GUI entry in the same screen):

This value corresponds to a GUI element in the Notes Migration Manager, the Always use these values check box in the Exchange Server configuration screen. The value determines whether the wizards that need this information will always use the access credentials entered into the corresponding Active Directory configuration screen. For example, if:

... a wizard will skip the screen that requests this information, saving the admin the trouble of having to reenter the values and manually dismiss the screen. By default (AlwaysUseDefaults=0), the wizard will take the values entered in Notes Migration Manager as its defaults, but will display the screen to offer the option of accepting or changing the default credentials.

Tells the wizard whether to automatically write the display names of Notes' email 2 and email 3 in the form Display Name (SMTP Address)— e.g., Joe Example (joeex@email.com). This feature, intended to make type-ahead easier to use, is off (0) by default, but can be enabled by:

This setting applies to data being migrated to a PST file. It tells the Data Migration Wizard to do an Exchange GAL lookup of attendees of migrated items to retrieve their Exchange addresses. Successfully resolved attendees are migrated to the target using their Exchange addresses instead of their SMTP addresses. This is required for free-busy lookups to succeed.

You can disable this feature by setting the parameter to 0. For example, to migrate data to PST files without connecting to the Exchange server, set:

... and also, in the [General] section:

Determines an authentication mechanism for remote PowerShell calls by Migrator for Notes to Exchange applications.

Kerberos is the default for on-premises Exchange targets. For Exchange Online, ModernAuthentication is the default. NME supports Basic and ModernAuthentication so if other values are specified, they are ignored and default to ModernAuthentication.

You can specify another method by entering the name as the keyword parameter value (case-insensitive). The valid keyword values are:

You can find descriptions for these keyword values, except for ModernAuthentication, in this Microsoft link.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

When using the Autodiscover service to configure the MAPI profile (i.e. [Exchange] UseAutodiscoverCreateProfile=1), the protocol that the profile is configured to use is selected based on the results of an Autodiscover query performed when the profile is being created. The effect of this parameter depends on the version of Outlook installed on the MNE server:

NOTE: As of October 31 2017, Microsoft 365 no longer supports the RPC/HTTP protocol. MAPI/HTTP is the only MAPI protocol supported by Microsoft 365. NOTE: When migrating with Outlook 2013, Outlook 2016, or Outlook 2019, the registry value [HKEY_CURRENT_USER\Software\Microsoft\Exchange] MapiHttpDisabled is automatically modified by MNE to match the configuration provided by this parameter setting.

This parameter is used when migrating with the MNE MAPI/HTTP library or with Outlook MAPI. If you are migrating with Outlook MAPI, this parameter is used only when migrating with Outlook 2010 or 2013.

When Outlook MAPI is used and you are using the Autodiscover service to configure the MAPI profile (i.e. [Exchange] UseAutodiscoverCreateProfile=1), the Autodiscover endpoint must first be found. When migrating to an on-premises Exchange server, the correct Autodiscover endpoint can be quickly obtained by querying the appropriate Service Connection Point (SCP) object in AD. To bypass the SCP query and immediately fall back to using the domain portion of the admin user SMTP address to infer the Autodiscover endpoint, you can set this parameter to 0.

This parameter is used only if the parameter [Exchange] AutodiscoverUrl is not configured with a value.

Specifies the maximum number of HTTP redirects allowed when resolving the URL of the Autodiscover service. This parameter is ignored if the Autodiscover URL is specified with the [Exchange] AutodiscoverUrl parameter.

This parameter is used when migrating with the MNE MAPI/HTTP library or with Outlook MAPI. If migrating with Outlook MAPI, this parameter is used only when migrating with Outlook 2010 or 2013.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

The Autodiscover service may return two URLs for connecting with RPC over HTTP; one for connecting from within the internal network, and another for connecting from the Internet. By default, MNE selects the internal URL when migrating to an on-premises target. This parameter can be used to override the default behavior. To override the default behavior, set AutodiscoverPreferInternalRpcHttpUrl=0.

This parameter has no impact when migrating to Microsoft 365.

The Exchange Autodiscover service can return two sets of URLs in its query responses:

If this parameter is not configured, MNE selects the URL that is appropriate to the location of the mailbox. If the mailbox is on an on-premises Exchange server, MNE gives preference to the internal URLs. If the mailbox is an online mailbox in Microsoft 365, MNE gives preference to the external URLs.

This default behavior can be overridden by setting this parameter to 1 (prefer internal URL) or 0 (prefer external URL. See the following examples:

NOTE: if the Autodiscover service returns only a single URL, internal or external, that URL is used regardless of this setting.

This parameter is used when migrating with the MNE MAPI/HTTP library or with Outlook MAPI.

If migrating with Outlook MAPI, MNE configures the temporary MAPI profiles that it creates using data obtained through the Exchange Autodiscover service. The URL of the service can be discovered dynamically, but this adds extra overhead to each Autodiscover query. Performance of these queries can be improved by providing the URL of the Autodiscover service through the AutodiscoverUrl parameter.

When migrating to O365, this setting is updated by the Migration Console when the Apply button is clicked on the Exchange Server page. The URL associated with the selected Microsoft 365 Environment is chosen from the list of URLs in the [MsOnlineAutodiscoverUrls] section.

Identifies the URL of the Azure Active Directory authorization endpoint. This setting is updated by the Migration Console when the Apply button is clicked on the Exchange Server page. The URL associated with the selected Microsoft 365 Environment is chosen from the list of URLs in the [AzureADAuthorizationEndPointUris] section.

Identifies the registered application client ID for the Microsoft Azure portal. This setting is updated by the Migration Console when the Apply button is clicked on the Exchange Server page after the user has performed an App Registration and successfully registered Migrator for Notes to Exchange with the Microsoft Azure portal.

To migrate oversized attachments or messages, this parameter is required when [Exchange] MigrateOversizedAttachments is enabled so the tool can access and upload large attachments to the OneDrive store owned by the mailbox user.

The parameter value documents the Microsoft Azure Application client secret that is required when [Exchange] MigrateOversizedAttachments is enabled so that the tool can access the OneDrive store for a user mailbox when the option to migrate oversized attachments is enabled for Microsoft 365 target. This field is required for migration with Admin console. Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

Specifies the method the wizard should use to process a recurring meeting series that contains more occurrences in Notes than the 999 maximum allowed by Exchange. Without this new control, attempts to migrate such meetings to Exchange 2010 would fail when the number of recurring instances exceeded the Exchange maximum. For example:

... tells the wizard to convert the item to a recurring series with no end date, which migrates cleanly.

The parameter value is a keyword that must be one of these single digits:

A migrated appointment will appear in Outlook with the same number of occurrences as in Notes, until the recurrence pattern is edited by the user, at which time it will assume the option set by this parameter.

This parameter is used only when migrating using MNE MAPI/HTTP. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

Tells the Data Migration Wizard to check if the Notes items are already migrated to Exchange based on the folder level or mail store level. This parameter allows you to avoid creating duplicate items in Exchange by using the [Exchange] RemigrateMode parameter.

For example, the default value (CheckMigratedItemsOnFolderLevel=1) tells the data migration wizard to check if the Notes items have already been migrated based on the folder level. CheckMigratedItemsOnFolderLevel=0 tells the data migration wizard to check if the Notes items have already been migrated based on the mail store level.

This value corresponds to a GUI element in the Data Migration Wizard, the Mailbox-enable ... accounts check box in the Operations 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 will delete the IPM.Configuration.Autocompletion message from the Inbox at the end of its data migration run. The AutoCompletion configuration message holds the cache of recently mailed-to users, but will cause errors in Outlook if the auto-completion lookup tables are corrupted—in which case Outlook will mistakenly tell users that valid addresses are invalid. The feature is off by default (DeleteAutocompleteMessages=0), but can be enabled by setting: DeleteAutocompleteMessages=1

This parameter and another (LocalExchangeFederationServer, also in this [Exchange] section) together support hybrid Microsoft 365 migration (O365 provisioned by a local proprietary AD) with a local Exchange server and remote mailboxes (on O365) for some or most users. DirSyncEnableRemoteMailbox is a boolean parameter that, when enabled (1), tells the Data Migration Wizard to read the LocalExchangeFederationServer value to remote-mailbox-enable each principal provisioned during AD prep on the local Exchange. This feature therefore requires a valid FQDN value for LocalExchangeFederationServer, as described in that parameter entry below.

Note that this remote-mailbox-creation feature in preparing AD for AD sync does not support any settings associated with regular mailbox creation. For example, [Exchange] EmailAddressPolicyEnabled is not supported.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

When opening a MAPI connection, Outlook may present a dialog to request login credentials. MNE scans for this login dialog and when it finds it, automatically enters the Exchange Administration account credentials. In certain scenarios it may be useful to temporarily disable this mechanism (DisableCredentialScanner=1) to allow the user to manually enter the login credentials.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

When opening a MAPI connection, there are several dialogs that may be presented by Outlook in specific scenarios. MNE scans for these dialogs and attempts to handle them automatically. Some customers have experienced issues with this mechanism interfering with the Credential Scanner mechanism. If this happens, the Dialog Scanner mechanism can be disabled (DisableDialogScanner=1).

When connecting to the target mailbox, MNE must authenticate with the Exchange Server or Microsoft 365. MNE automatically selects the correct type of authentication to use based on the authentication mechanisms that are enabled on the server. If the server supports Modern Authentication, it is selected as the preferred authentication mechanism.

Disable Modern Authentication by setting DisableModernAuthentication=1. When disabled, MNE will fall back on another one of the mechanisms supported by the server (e.g. Basic Authentication).

Modern Authentication is primarily used when migrating to Microsoft 365. Microsoft does support using Modern Authentication with on-premises Exchange servers in a Hybrid Authentication configuration. However, MNE has not been validated for use with Hybrid Authentication. If you run into issues, you may need to disable Modern Authentication using this parameter.

This value corresponds to a GUI element in the Data Migration Wizard, the Remove mail Forwarding address check box in the Specify Remove Exchange Forwarding Settings 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 Set Mail Forwarding address check box in the Specify Exchange to Notes Mail Forwarding Settings screen. Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

This value corresponds to GUI elements in the Specify Mail Routing Options screen of the Data Migration Wizard, the Notes vs. Exchange radio buttons under All new mail ... will be delivered to. The wizard automatically sets the values of this and three other related parameters (shown below) according to the administrator’s radio-button choice, to tell the wizard which mail-routing screens to display in the current run. This DoShowRmvForwarding value in the [Exchange] section determines whether the wizard will (1) or will not (0) display its Specify Remove Exchange Forwarding Settings screen. The full set of related parameters, and how they are set:

Quest recommends you do not manually enter or change these parameter values except at the direction of Quest Support.

This value corresponds to GUI elements in the Specify Mail Routing Options screen of the Data Migration Wizard, the Notes vs. Exchange radio buttons under All new mail ... will be delivered to. The wizard automatically sets the values of this and three other related parameters (shown below) according to the administrator’s radio-button choice, to tell the wizard which mail-routing screens to display in the current run. This DoShowSetForwarding value in the [Exchange] section determines whether the wizard will (1) or will not (0) display its Specify Exchange to Notes Mail Forwarding Settings screen. The full set of related parameters, and how they are set:

Quest recommends you do not manually enter or change these values except at the direction of Quest Support.

Determines whether the wizard should, after mailbox-creation, set the newly created mailboxes to Automatically update e-mail addresses based on e-mail address policy. This is an Exchange feature offered in the Exchange Management Console, as a check box on the E-Mail Addresses tab of the Data Properties for each mailbox. This Migrator for Notes to Exchange parameter specifies whether the wizard should automatically enable or disable that Exchange feature during mailbox-creation. For example, the default:

… tells the wizard to enable the Exchange automatic-update feature (mark the Exchange check box). To disable the Exchange feature (unmark the Exchange check box), set EmailAddressPolicyEnabled=0. Note: When mailbox-enabling, make sure the setting for this EmailAddressPolicyEnabled parameter matches the setting for [ActiveDirectory] SetRecipPolicy.

Determines whether the Data Migration Wizard will create mailbox archives in a hybrid Microsoft 365 scenario (O365 provisioned by a local proprietary AD) when mailbox-enabling the remote mailboxes (on O365). The feature can be enabled by EnableRemoteArchiveMailbox=1, but only if remote mailbox-enabling is also enabled for this scenario by DirSyncEnableRemoteMailbox (also in this [Exchange] section, described separately above).

Enables or disables the feature to designate all migrating encrypted items as a particular Outlook category, which makes it possible to identify encrypted items in Outlook by a category search. The parameter value is a string that names the Outlook category. The feature is disabled by setting the parameter value to null or omitting the parameter altogether. The parameter is omitted by default.

Enables or disables an option to extract images from Notes messages and replace and migrate the images as OLE Device Independent Bitmap object attachments -OR- migrate the original images to a OneDrive store. Original images are migrated to OneDrive when the following conditions are met:

This option makes images renderable in both OWA and the Office web client and is enabled by default (1). To disable the option, set ExtractEmbeddedImages=0.

This internal parameter is a single alphanumeric character that used to replace invalid characters when MNE builds an Microsoft 365 address. Use this parameter only at the direction of Quest support.

NOTE: SPACE is always replaced by UNDERSCORE; this replacement is not controlled by the FilterAddressReplacementChar parameter.

Occurs in: Data Migr. This is an internal scratch parameter (see Transient “scratch” parameters).

This value corresponds to two GUI elements in the Data Migration Wizard, the Forwarding mail domain text box in the Specify Exchange to Notes Mail Forwarding Settings screen, and the Forwarding mail domain text box in the Specify Remove Exchange Forwarding Settings screen. Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

Specifies the character used to delimit the elements of Exchange-to-Notes forwarding addresses, when the Data Migration Wizard composes forwarding addresses. For example:

... tells the wizard to use a comma to delimit the elements of the forwarding address. By default, the wizard uses a period as the delimiter.

This value corresponds to a GUI element in the Data Migration Wizard, the Build address from drop-down list box in the Specify Exchange to Notes Mail Forwarding Settings screen. Quest recommends you do not manually enter or change this value except at the direction of Quest Support. The parameter specifies the method by which the Data Migration Wizard will compose forwarding addresses from Exchange to Notes. For example:

... specifies the SourceAddress method, as described below. By default the wizard will use the TargetAddress method, which also is the method used in pre-3.1 versions of the program. The three valid parameter values are:

For the TargetAddress and SourceAddress options the delimiter character is usually a "dot" (period), but is configurable by the FwdAddrDelim parameter in this same [Exchange] section.

Determines whether the Data Migration Wizard will add resource-owner permissions to resource delegates in Exchange who are migrating from Notes via the MigrateResourceDelegation parameter (also in this [Exchange] section, see below). This feature is off (0) by default. To add resource-owner permissions to migrating resource delegates, set GrantResourceOwnerFullAccess=1.

Note: This feature requires MigrateResourceDelegation=1, as described in that separate entry below. The wizard will ignore this GrantResourceOwnerFullAccess parameter if MigrateResourceDelegation=0.

This value corresponds to a GUI element in the Notes Migration Manager's Exchange Server Configuration screen: the Microsoft 365 User domain drop-down list, used to specify the Microsoft 365 domain that should be used to compose users’ Microsoft Online Services ID (logon names and email addresses). The program writes this value to the Task Parameters based on an admin's GUI entry; Quest recommends you do not manually enter or change this value except at the direction of Quest Support. The program loads this drop-down list with domains registered in Microsoft 365 for the admin credentials entered elsewhere on the same screen. The Microsoft 365 User domain specified here will be the portion of each user’s email address that follows the @ symbol. The left-hand-side of each user’s ID will be his/her User ID from Migrator for Notes to Exchange’s SQL database.

This parameter and another (DirSyncEnableRemoteMailbox, also in this [Exchange] section) together support hybrid Microsoft 365 migration (O365 provisioned by a local proprietary AD) with a local Exchange server and remote mailboxes (on O365) for some or most users. This LocalExchangeFederationServer value is a string for the FQDN of your local Exchange, which the program will need if DirSyncEnableRemoteMailbox=1 to remote-mailbox-enable each principal provisioned during AD prep on the local Exchange.

AD credentials are used for this feature because Migrator for Notes to Exchange does not ask for separate credentials for the local Exchange. The AD admin must therefore be a member of Organization Management to run EnableRemoteMailbox on the local Exchange.

You can specify [Exchange] LogSkippedTestMapiConnectivity=1 to log warning messages in the GALSearch.wlog log file if the MAPI Connectivity tests are skipped.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

The name of an existing Outlook profile on the Migrator for Notes to Exchange admin migration computer that the Data Migration Wizard should use to access the migration target. You may use this setting when migrating to specify a specific profile to use, rather than dynamically creating a temporary profile to use for the migration. For example:

The quotation marks enclosing the profile name may be omitted if there is no space in the profile name.

IMPORTANT: The specified profile must be configured with the Use Cached Exchange Mode option disabled.

NOTE: This parameter is overridden by the [Exchange] UseAdminAcctPool parameter. When migrating with an account pool, each migration thread will dynamically create a temporary MAPI profile to be used by that migration thread.

NOTE: This parameter replaces the older [Exchange] RPCAdminMapiProfile parameter which has been deprecated. Additionally there is no longer any need to enable the profile through a separate parameter as was previously necessary using the [Exchange] RPCUseAdminMapiProfile parameter. It is sufficient to simply provide the name of the profile to be used.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

Determines the number of additional attempts that MNE will make to recover from a MAPI API function that fails with one of the errors listed in the MAPIErrorsToRetry parameter. If a MAPI retry error occurs, MNE waits for the amount of time specified by the MessageRetryWait parameter, and attempts to run the MAPI API function again.

If the API function continues to fail and returns MAPI retry errors, once the MAPIRetryCount limit is reached MNE makes a new attempt to store the message using a new MAPI session, as described by the MessageRetryCount parameter.

If this parameter is not set, it defaults to the value that is specified by the MessageRetryCount parameter.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

This setting determines whether each migration worker thread shares a single dynamically created MAPI profile or, if separate MAPI profiles are created for each thread. This setting was added as a workaround to a MAPI bug that prevents the re-use of MAPI profiles when the MAPI over HTTP protocol is used. MAPI over HTTP is the only MAPI protocol available for use with Microsoft 365 as of October 31, 2017. When migrating to Microsoft 365, each migration worker thread will create its own temporary MAPI profile for its exclusive use.

By default, migrations to on-premises Exchange servers will continue to use the RPC over HTTP protocol with the MapiUseSharedProfile option enabled. This default value will be changed in the future once Microsoft has released an update to MAPI resolving the MAPI over HTTP issue.

This setting will be overridden by the following parameter settings:

NOTE: The MAPI over HTTP bug does not affect profiles created through the Control Panel.

Recurring-meeting messages from Notes with more than 255 attachments are divided into individual meetings in Exchange, according to the setting for this parameter. The value of this parameter represents the maximum number of attachments the wizard may encounter before creating a new meeting. The wizard will create as many meetings as necessary to migrate the complete series with no more than the specified number of exceptions. For example:

… tells the wizard to create as many meetings as necessary to migrate the series with no more than 200 exceptions per message.

This setting is applied when the [Exchange] ExtractEmbeddedImages parameter is enabled.

During migration, images that are extracted from emails are either converted to BMP images before being stored in Exchange as message attachments -OR- the original images are uploaded to the user's OneDrive store.

Converting an image to BMP format can result in an image that has a data size many times larger than the original image. Due to the technical limitations of RTF format, it is not possible to use other, more efficient image formats that support data compression.

To mitigate the impact to the target mailbox size by emails that contain large embedded images, you can use the MaxExtractedImageArea setting to specify the maximum allowable image area, in pixels, of the generated BMP image. During the conversion, if the limit is exceeded, the embedded image is removed from the email body and is replaced with the original Notes image stored as a standard file attachment on the migrated message.

For example, to specify that images larger than 640 x 480 (307200) pixels should be removed from the email body and migrated as file attachments, set MaxExtractedImageArea=307200. However, if you set extracted images to be migrated to a OneDrive store, the parameter is ignored.

By migrating the source image in its original format and storing it in Exchange as a message attachment, the source image data compression is retained with no loss in image quality. Though the image is no longer displayed in the email body in Outlook or OWA, users can open the images from the email client to view the image content.

Original images are uploaded to OneDrive if the Migrate Oversized Attachments option is enabled for Microsoft 365 mailbox migration and the extracted image sizes exceed the limit specified by the [Filter] AttachSize parameter.

When MaxExtractedImageArea=0, the image is migrated to Exchange with no size limit applied.

When MNE fails to connect to the target mailbox due to an error that might be transient (such as a network communication fault), MNE will make additional attempts to connect to the target mailbox. This parameter imposes a limit on the amount of time that MNE will spend retrying to open the connection.

The maximum time is specified in minutes. If the connection cannot be established within the amount of time specified, the migration to the target mailbox will be abandoned.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

Determines the maximum number of times that MNE will attempt to reconnect the MAPI session if a message fails to migrate due to one of the errors that are specified by the MAPIErrorsToRetry parameter. MNE pauses between each reconnect attempt for the number of seconds specified by the MessageRetryWait parameter.

If MNE is unable to open a new MAPI session after MaxSessionReconnectCount attempts, the migration is abandoned.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

If a message fails to migrate due to one of the MAPI errors specified by the MAPIErrorsToRetry parameter, this parameter determines the maximum number of additional attempts that MNE will make to store the message. When MNE fails to store a migrated message to the target mailbox due to a MAPI retry error, MNE closes the existing MAPI session, opens a new session, and attempts to store the message again.

If MNE is unable to open a new MAPI session, it continues to make additional attempts to connect with MAPI, as described by the MaxSessionReconnectCount parameter. MNE pauses between each reconnect attempt for the number of seconds specified by the MessageRetryWait parameter.

If MNE is able to successfully open new MAPI sessions, but attempts to store the message continue to fail and the MessageRetryCount limit is reached, MNE logs the MAPI error and the failure to migrate the current message. MNE proceeds to the next message to be migrated.

Sets the delay (in seconds) between retry attempts for MAPI API functions that fail with one of the errors specified by the MAPIErrorsToRetry parameter, as documented by the MAPIRetryCount parameter.

The parameter also specifies the delay (in seconds) between MAPI session reconnect attempts, as documented by the MessageRetryCount parameter.

Controls an Active Directory setting for authorized senders to provisioned groups. When the parameter is set to the default value 1, the Exchange distribution group restricts users who can send messages to the group to those users who are authorized senders for the distribution group in Domino/Notes. When set to 0, the restriction is not set which allows this recipient group to accept messages from all senders.

Determines whether the Data Migration Wizard will migrate a Notes document that appears in the Trash view if it also appears in some other Notes view. By default:

... tells the wizard to skip such messages. The alternative (1) tells the wizard to always migrate Notes documents to their corresponding Exchange folders, even if they also appear in the Notes trash view.

Determines whether the Data Migration Wizard will migrate the identities of mail-in database owners when it migrates mail-in DBs. The Directory Export Wizard captures these owner identities to Migrator for Notes to Exchange's SQL database in any case, but the migration of the identities to Exchange is an option that is enabled or disabled by this boolean program parameter.

By default (MigrateMailInDBOwner=1), the wizard will migrate the identities of mail-in DB owners. To disable this feature, set MigrateMailInDBOwner=0.

Determines whether MNE will migrate the FYI attendees of a Notes meeting to the bcc field in Exchange, where they will appear as Resources, instead of to the cc field. This option keeps FYI attendees hidden if the organizer later changes the meeting, since Exchange sends notifications of such changes, and those notices would otherwise disclose the FYI attendees as Optional Attendees.

By default (MigrateMeetingFYIAsResource=1), MNE migrates FYI attendees of a Notes meeting to the bcc field in Exchange. You can disable the feature (0) to make MNE migrate FYI attendees to the cc field.

Used only when migrating with the MNE MAPI/HTTP library, which is used when the [Exchange] UseMneMapiHttpLib parameter is set to the default setting of 1 as in [Exchange] UseMneMapiHttpLib=1.

Tells the Data Migration Wizard whether to migrate an oversized message or an oversized message attachment when target is Microsoft 365. For example:

... tells the wizard to skip migrating the message attachment or the message that exceeds the size limit (such as. 25 MB for message attachments or 150 MB for messages) to the Exchange Online target.

The parameter value is a single-digit integer which must be one of these two valid values:

NOTE: The maximum size limit for attachments is set in the Data Migration Wizard on the Select Date and Size Filters screen. You can modify the maximum attachment size on that screen but the size should not exceed the maximum attachment size allowed by Microsoft 365.

Determines whether the Data Migration Wizard, when it migrates resources, will migrate their designated owners and authorized managers, and Notes' Owner Restrictions settings. The Directory Export Wizard captures this information in any case, but its migration to Exchange is an option that is enabled or disabled by this boolean program parameter.

This feature is off by default (MigrateResourceDelegation=0). To migrate the identities of resource owners and managers, and the associated resource-management access behaviors, set MigrateResourceDelegation=1.

What Notes calls a resource owner corresponds closely to what Exchange calls a delegate, and Migrator for Notes to Exchange migrates Notes' resource owners and behaviors on that basis. A table in the Migrator for Notes to Exchange Pre-Migration Planning Guide (in chapter 3, see Migrating Resources) shows how Notes' Owner Restrictions are mapped to resource behaviors in Exchange.

Another Migrator for Notes to Exchange parameter (also in this [Exchange] section, see GrantResourceOwnerFullAccess above) lets you also optionally add resource-owner permissions to migrated resource delegates in Exchange.

Determines whether MNE converts Notes RTF (rich text format) to HTML format when migrating a Notes message body in RTF. MNE uses a Notes built-in API to convert RTF to HTML. The feature is off (0) by default. The following limitations apply:

MNE will export Notes RTF to MS RTF if MNE fails to convert Notes RTF to HTML or the feature is disabled.

Some special Notes Databases contain a Topic field which works the same as the Category field (Keywords attribute) in Exchange. Currently MNE will migrate the Topic as Subject in Exchange causing multiple messages to have the same Subject value but it is actually the Topic value.

By default (MigrateTopicAsCategory=0), MNE does not change the logic as the source does not contain a Topic field in most cases, If you set this parameter to 1, MNE migrates the Topic as Category, and does not migrate the Topic as Subject. Quest recommends you enable the parameter only when you encounter the issue in which the Topic field is incorrectly migrated as Subject for a special Database.

This value corresponds to a GUI element in the Data Migration Wizard, the Do not connect to an Exchange server check box in the Select Destination Exchange Server 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.

Specifies the folder path relative to the mailbox user’s OneDrive store root to which oversized attachments will be uploaded. The folder name can be separated with / or \ but cannot contain any of the special characters, such as ~ " # % & * : < > ? / \ { | } that are not allowed by OneDrive.

If the specified folder path is found to be invalid when the wizard is uploading oversized files, an error is logged and the default folder is used as the target folder instead. By default, the wizard uses Email_Attachments as the folder path for oversized attachments.

Specifies a single Microsoft 365 account SKU that the Data Migration Wizard should use when licensing end users for Microsoft 365. You can run the Get-MsolAccountSku cmdlet to retrieve the AccountSkuIds for all valid licenses.

The value of this setting is derived from the Product License field on the Select Microsoft 365 Administrative Operations Quest screen in the Data Migration wizard. Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

Determines whether the Provisioning Wizard should preserve or overwrite the AD mail attribute (if any) when merging a CMN-created contact with an AD principal whose mail attribute is not empty.

For example: O365DirsyncPreserveADAttrMail=1 tells the wizard to preserve any existing AD mail attribute. By default (0), the attribute is overwritten.

A coma separated list of license plan services that have been disabled.

The value of this setting is derived from the Product License field on the Select Microsoft 365 Administrative Operations Quest screen in the Data Migration wizard. Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

Identifies the Microsoft 365 environment that is the target of the migration. By default MNE will migrate to the O365 Global Cloud, but this parameter can be used to select one of the available Microsoft National Clouds (e.g. Microsoft 365 Germany). Currently the following values are supported for this parameter:

NOTE: This parameter is associated with the Microsoft 365 Environment UI element on the Migration Console’s Exchange Server page. It is not recommended that you edit this parameter value directly, as there are several parameters that need to be updated to properly support Microsoft National Clouds.

Replaces the obsolete [PowerShell] PropagationDelay parameter. It specifies the maximum number of time (in minutes) to keep retrying mailbox logons when the logon fails with an Access Denied error.

When migrating to Microsoft 365, MNE checks at the beginning of the migration to ensure that the migration account has Full Access rights on the target mailbox. If the account does not have rights, MNE uses PowerShell to grant access. It is common for there to be a delay between granting these permissions and the logon to the target mailbox succeeding. Occasionally, this delay can be significant, taking many minutes for the permission change to take effect.

When MNE logs onto an Microsoft 365 mailbox, if the logon fails with a permission denied error, MNE automatically retries the logon after 30 seconds. It keeps retrying the logon every 30 seconds until the logon succeeds or the O365MaxMailboxConnectionWaitTime has been exceeded.

When the MNE PowerShell module initializes OneDrive, the module assumes that your SharePoint administration URL is 'https://Your_O365_Azure_Organization_Name-admin.sharepoint.com'.

This parameter allows you to replace the default Azure organization name in the SharePoint admin URL with a different name. So if your SharePoint administration URL is 'https://NewOrg-admin.sharepoint.com’ you would enter [Exchange] O365Organization=NewOrg.

Identifies the URL of the Microsoft 365 tenant’s remote PowerShell endpoint. This setting is updated by the Migration Console when the Apply button is clicked on the Exchange Server page. The URL associated with the selected Microsoft 365 Environment is selected from the list of URLs in the [MsOnlinePSConnectionUris] section.

Identifies the Microsoft 365 tenant name (e.g. MyTenant.onmicrosoft.com) when registering the App with the Microsoft Azure portal. This setting is updated by the Migration Console when the Apply button is clicked on the Exchange Server page after the user has performed an App Registration and successfully registered Migrator for Notes to Exchange with the Microsoft Azure portal.

Specifies the Usage Location required by Microsoft for Microsoft 365 licenses, per this Microsoft article. The Usage Location is a two-letter code for the country, as described in ISO 3166-1-alpha-2. Migrator for Notes to Exchange's Admin Account Pooling Utility requires a value for this parameter, and the value must conform to the standardized values listed for ISO 3166-1-alpha-2.

Specifies a common output PST filename for all migrating users, when migrating data to PSTs. This value is used in conjunction with the PSTDir column in the SQL Server database, which specifies a unique PST directory for each user. The combination of a common PstFileName value with unique PSTDir values assures that the newly created PST files will be identifiable by user.

For example: PstFileName=migr-archive.pst combined with PSTDir column values set to \\server\home\user1, user2, user3, etc., would produce these new PST files in these locations:

Otherwise, if the PSTDir column is unspecified and the PstFileName parameter sets the output filename to a common value, the multiple files saved to the same directory would be differentiated only by appended digits: migr archive 1.pst, migr archive 2.pst, migr archive 3.pst, and so forth. Each user in a collection should therefore have a unique directory specified in the PSTDir column, such as the user's home directory on a server.

If PSTDir columns are specified but the PstFileName setting is left unspecified, the [Outlook] PstFileNameFormat parameter is used to determine the PST filenames. If the PstFileNameFormat parameter is using the default setting (1), the new PST filenames are derived from users' display names.

... tells the program to clear the contents of Personal Address Books in Exchange before migrating corresponding PABs from Notes—useful if, for example, you had already migrated PABs, but wanted to migrate them again. The default PurgePABS=0 disables the feature, so no PABs are cleared. This feature clears only Exchange PABs that correspond to Notes PABs about to be migrated, and will not clear any other existing Exchange PABs.

Tells the Data Migration Wizard which of three methods to use, to avoid creating duplicate items in Exchange when an item that has already been migrated to Exchange is queued to migrate again. For example:

... tells the wizard to delete the Exchange copy of the item and remigrate it from Notes.

The parameter value is a single-digit integer, which must be one of these three valid values:

The RemigrateMode parameter also impacts how folder permissions are migrated when a mailbox is migrated again. The following rules apply to the migration of folder permissions regardless of the RemigrateMode parameter setting and how many times the migration has been performed:

The RemigrateMode parameter affects the migration of folder permissions in scenarios where a user exists in both the Notes mail file ACL AND the Exchange Folder ACL. The RemigrateMode setting values affect the migration as described below:

When migrating to Microsoft 365 and provisioning from a local AD using the Microsoft AD sync, this parameter sets the "right side" of each user's remote routing address on the remote mailbox (the portion of the address that follows the "@" symbol) to the value specified here. The left side of the address (preceding the "@" symbol) is the user Alias.

For example, if:

Note that this feature can be enabled only if remote mailbox-enabling is also enabled for this scenario by the DirSyncEnableRemoteMailbox parameter (also in this [Exchange] section, described in a previous entry).

Controls an Active Directory setting for provisioned groups. When set to the default value 1, the Exchange distribution group can accept messages from authenticated (internal) senders. Messages from unauthenticated (external) senders are rejected. When set to 0, all messages for the Exchange distribution group are accepted.

Corresponds to a GUI element in the Data Migration Wizard, the Reset Microsoft 365 Passwords check box on the wizard's Operations screen. The check box and parameter value determine whether, when mailbox-enabling users in Microsoft 365, the wizard will automatically generate random Microsoft 365 passwords, assign them to users' Microsoft 365 accounts, and save them locally so they can later be sent to users within Migrator for Notes to Exchange's You've Been Migrated mail-merge email. Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

A single digit, 0–7, that specifies which (if any) of migrating mail, appointment and task items the wizard should pass through Microsoft’s rich-text converter—which in many cases will refine the exported compound document format from Notes’ own converter. The parameter value must be one of these digits:

When migrating mailbox content, MNE also migrates mail file permissions to the folders within the target mailbox. The permissions are migrated to provide equivalent access in Exchange depending on the type of data contained within the folder. For example, mail folders are assigned permissions equivalent to the access granted to mail data in the source mail file.

Outlook provides a mechanism for opening up folders within other user’s mailboxes. This mechanism only requires access to be granted on the specific folder being opened. For example, to view another mailbox’s Inbox, a user only requires access to the Inbox within that mailbox. However, this mechanism is limited to specific well-known folders, such as the Inbox, Calendar, etc.

To browse other custom folders within another user’s mailbox, you must add the target mailbox to the Outlook Profile. Browsing the folders in this manner only works if permissions are granted on the mailbox’s root folder. Since the root folder does not contain any specific content, it is difficult to determine exactly what level of permissions to grant users on the root folder. There are pros and cons to each approach. This setting can be used to select the approach that is appropriate for each customer’s needs. The following values are supported for this parameter.

The name of an existing Outlook profile on the Migrator for Notes to Exchange admin migration computer that the Data Migration Wizard should use to access Microsoft 365 (when migrating to Microsoft 365). Use this setting, paired with the RPCUseAdminMapiProfile parameter (also documented separately below), when migrating to Microsoft 365:

The quotation marks enclosing the profile name may be omitted if there is no space in the profile name. The wizard will not read this parameter if the RPCUseAdminMapiProfile parameter is omitted or set to 0.

IMPORTANT: This parameter has been deprecated and replaced with the [Exchange] MapiAdminProfile parameter. If this parameter is specified, it will continue to work, but a warning will be logged to the migration log file. Support for this parameter will be removed in a future version of MNE.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

This parameter corresponds to a GUI element (the Principal name for proxy server text box) in the Exchange Proxy Settings dialog box in either the Notes Migration Manager or Data Migration Manager. The value specifies the Exchange proxy server certification server name (URL), when using the RPC protocol to communicate with the Exchange server. For example:

This parameter is required if RPCUseHTTP (see that parameter for more information about the RPC protocol). The program 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 parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

This parameter corresponds to a GUI element (the Use this URL to connect to my proxy server check box) in the Exchange Proxy Settings dialog box in either the Notes Migration Manager or Data Migration Manager. The value specifies the proxy server name (URL), when using the RPC protocol to communicate with the Exchange server. For example: RPCProxyServerURL=ExampleURL

This parameter is required if RPCUseHTTP=1. See the RPCUseHTTP parameter for more information about the RPC protocol. The program 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.

Tells the wizard whether it should use an existing Outlook profile on the Migrator for Notes to Exchange admin migration computer, rather than automatically generate a temporary profile to use for the migration. When migrating to Microsoft 365, you should set this parameter to 1, and specify a profile name with the RPCAdminMapiProfile parameter (also documented separately above):

The wizard will not read the RPCAdminMapiProfile parameter if this RPCUseAdminMapiProfile parameter is omitted or set to 0.

IMPORTANT: This parameter has been deprecated. If this parameter is specified, it will continue to work when used with the RPCAdminMapiProfile parameter (also deprecated), but a warning will be logged to the migration log file. Support for this parameter will be removed in a future version of MNE.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

This parameter corresponds to a GUI element (the Use this authentication… drop-down list box) in the Exchange Proxy Settings dialog box in either the Notes Migration Manager or Data Migration Manager. The value specifies the authentication method the Data Migration Wizard should use when connecting to the Exchange proxy server, when using the RPC protocol to communicate with the Exchange server. For example:

... tells the wizard to use the NTLM method, while the default RPCUseAuthType=1 specifies the basic authentication method. See the RPCUseHTTP parameter for more information about the RPC protocol. The program 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 parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

This parameter corresponds to a GUI element (the On fast networks… check box) in the Exchange Proxy Settings dialog box in either the Notes Migration Manager or Data Migration Manager. The value determines whether the Data Migration Wizard will, when using the RPC protocol to communicate with the Exchange server on a fast network, connect using HTTP first, and connect using TCP/IP. For example:

... tells the wizard to enable this option, while the default (0) disables the option. See the RPCUseHTTP parameter for more information about the RPC protocol. The program 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 parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

This parameter corresponds to a GUI element, the Connect using Outlook Anywhere check box, in the Notes Migration Manager (Exchange Server Configuration screen) and Data Migration Manager (Select Destination Exchange Server screen). The boolean value determines whether the Data Migration Wizard will use Remote Procedure Calls (RPC) within HTTP packets to communicate with the target Exchange Server. For example:

... tells the wizard to use this RPC protocol, while the default (0) tells the wizard to use the default TCP protocol. The RPC protocol is required when migrating to Microsoft 365, and is optional but may improve data throughput when migrating to an proprietary Exchange in a slower network. Note that the target Exchange server must also be configured for the RPC protocol to use it, by the other RPC… parameters in this [Exchange] section. (These other parameters are set by GUI elements in the Exchange Proxy Settings dialog box.)

The program writes this value to the Task Parameters from an admin's GUI entry in either screen; Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

This parameter corresponds to a GUI element (the Mutually authenticate the session when connecting with SSL check box) in the Exchange Proxy Settings dialog box in either the Notes Migration Manager or Data Migration Manager. The value determines whether the Data Migration Wizard will mutually authenticate the session when using the RPC protocol to communicate with the Exchange server. For example:

... tells the wizard to enable this option, while the default (0) disables the option. See the RPCUseHTTP parameter for more information about the RPC protocol. The program 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 parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

This parameter corresponds to a GUI element (the On slow networks… check box) in the Exchange Proxy Settings dialog box in either the Notes Migration Manager or Data Migration Manager. The value determines whether the Data Migration Wizard will, when using the RPC protocol to communicate with the Exchange server on a slow network, connect using HTTP first, and connect using TCP/IP. For example:

... tells the wizard to enable this option, while the default (0) disables the option. See the RPCUseHTTP parameter for more information about the RPC protocol. The program 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 parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

This parameter corresponds to a GUI element (the Connect using SSL only check box) in the Exchange Proxy Settings dialog box in the Notes Migration Manager or Data Migration Manager. The value determines whether the Data Migration Wizard will use a secure socket layer (SSL) to connect to the Exchange proxy server, when using the RPC protocol to communicate with Exchange. For example:

... tells the wizard to not use SSL, while the default (1) tells the wizard to use SSL. This parameter can be set to 0 only if the authentication method is set to NTLM by RPCUseAuthType=2 (see the RPCUseAuthType parameter above). See the RPCUseHTTP parameter for more information about the RPC protocol. The program 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 Notes Migration Manager: the mailbox Exchange Server for Mail Profile text box in the Exchange Server Configuration screen. The role of this configuration item is currently obsolete and is only used as a backup attribute for the Mailbox Server or Exchange CAS for Remote PowerShell, purely for backward compatibility purposes.

The feature is enabled/disabled, and the server name is set, by:

Server=<ServerName>

The value is written to the Task Parameters from an admin's GUI entry. As this value is set via a GUI element, Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

This setting applies to data being migrated to a server mailbox (either primary or archive). It tells the Data Migration Wizard to do an Exchange GAL lookup of attendees of migrated items to retrieve their Exchange addresses. Successfully resolved attendees are migrated to the target using their Exchange addresses instead of their SMTP addresses. This is required for free-busy lookups to succeed.

This feature can be disabled by setting the parameter to 0.

Determines whether the Subject field for migrated meetings in resource calendars will be set to the Subject of the meeting, or to the organizer of the meeting (the person who booked the resource). By default (SetResourceMeetingSubjectToOrganizerName=0) the Subject field for migrated meetings in a resource's calendar is set to the Subject of the meeting, as in prior Migrator for Notes to Exchange releases. But setting the Subject field to the Subject of the meeting (by SetResourceMeetingSubjectToOrganizerName=1) mimics native Exchange/Outlook behavior.

Determines whether the wizard will set the managedBy attribute to the DN of the owner in the user forest (1) or of the owner in the resource forest (0)—for environments configured for a resource and user forest. For example: SetManagedByToUserForest=1 tells the wizard to set managedBy to the DN of the owner in the user forest. The default (SetManagedByTo­UserForest=0) sets the managedBy attribute to the DN of the owner in the resource forest.

NOTE: Setting the managedBy attribute to the DN of the owner in the user forest requires a two-way trust between the two domains, which must be established before the wizard is run. The user/resource forest environment is intended to be a one-way trust, however, so that must be restored after the wizard has run. If the two-way trust is not established prior to running the wizard, the managedBy attribute will not be set correctly and the wizard will generate this error: ERROR: [8810-117-28-8007202F] Unable to add group ACL to ….

Determines whether the Provisioning Wizard will enable the Exchange autoaccept feature upon provisioning of resources. The default SetResourceToAutoAccept=1 enables the feature. The alternative (0) leaves the feature disabled.

Tells the Data Migration Wizard whether to migrate an oversized message attachment using a method that modern Outlook (Outlook 2016 or later) or an OWA client can render correctly or to revert to an attachment type that legacy Outlook 2013 or earlier can render.

The default value 0 migrates attachments for modern Outlook and value 1 migrates attachments in the way that legacy Outlook supports.

When provisioning users into local AD, and ProvisionUsers=1, this parameter tells the Provisioning Wizard to replace each user's mail domain with the specified parameter value. For example:

... tells the wizard that a user whose target address would otherwise be UserXYZ@sitraka.com should instead be provisioned into AD as UserXYZ@boofah.com. The default value is null (no substitution occurs).

This value corresponds to a GUI element in the Notes Migration Manager: the Target Exchange server version field in the Exchange Server Configuration screen. Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

The parameter value specifies the migration destination, by one of these valid numeric keywords:

An auto-set parameter (see GUI-set and other “auto-set” parameters) that notes whether the Data Migration Wizard has detected CDOEXM, or PowerShell, or both, or neither, on the target (destination) Exchange server. The parameter value is a single-digit keyword representing one of four possible cases:

By default, MNE adds the test message "Quest access test message" to the Trash folder of the user target mailbox during migration to test the mailbox access.

To skip testing mailbox access and stop the test message being added to the target mailbox at migration, specify [Exchange] TestMailboxAccess=0.

When you are migrating user collections that have a large number of users that are already validated, you can use this parameter to skip the time-consuming validation of each mailbox and to proceed immediately with the migration.

To skip the MAPI Http Connectivity test for each mailbox in the user collection during the 'Verifying Exchange Account' step of the migration wizard, specify [Exchange] TestMailboxMapiConnectivity=0.

… tells the Data Migration Wizard to run the Update-AddressList cmdlet after mailbox-enabling a collection, to complete the AD provisioning of recipients who are only partially provisioned. The Update-AddressList cmdlet will run with its identity parameter set to "All Users" by default, or to some other identity value if set by the AddressListName parameter (also in this [Exchange] section). This parameter can be useful in migrations to Exchange 2010, when objects have been provisioned by tools such as Microsoft Identity Integration Server (MIIS) or custom provisioning tools that do not fully provision recipient objects. By default (0), the cmdlet will not run.

… tells the wizard to run the Update-EmailAddressPolicy cmdlet after mailbox-enabling a collection, to complete the AD provisioning of recipients who are only partially provisioned. The Update-EmailAddressPolicy cmdlet will run with its identity parameter set to Default Policy by default, or to some other identity value if set by the AddressPolicyName parameter (also in this [Exchange] section). This can be useful in migrations to Exchange 2010, when objects have been provisioned by tools such as Microsoft Identity Integration Server (MIIS) or custom provisioning tools that do not fully provision recipient objects. By default (0), the cmdlet will not run.

When migrating to on-premises Exchange or Microsoft 365 targets, MIME encoded HTML emails may not display correctly in the email client if there is a mismatch between the character encoding declared in the HEAD element of the HTML message and the character encoding declared in the MIME headers. When a mismatch occurs, the message displays as garbled text.

To correct this issue, enable the parameter by specifying the character set used by the HTML HEAD element that is causing a problem. For example:

UpdateHtmlWithMismatchedCharset=UTF-16

When the parameter is enabled, MNE checks for the character set in the HTML HEAD element and when found, the character set is replaced with the MIME header character set.

The parameter is disabled by default. Only enable the parameter if corrupted characters are observed in migrated messages.

NOTE: If errors occur during the parsing of the HTML, NME migrates the message with no modification.

UpdateHtmlWithMismatchedCharset=UTF-16

UpdateHtmlWithMismatchedCharset=US-ASCII

MIME encoded HTML emails often have the charset encoding declared in two places. The first is within the MIME headers and the second is within the HEAD element of the HTML message itself. With properly formatted emails, these two charset declarations are identical. Some HTML emails have been found where the charset declaration in the MIME headers and the charset declaration in the HTML message do not match. Typically in these cases, the HTML charset declaration is not in the HEAD element where it is expected, but instead it appears later in the document, possibly in the BODY element. While these emails may not be technically valid, they are still handled properly by most email clients.

A new behavior has been observed in Microsoft 365 where the Exchange server attempts to correct the discrepancy in the charset declarations by removing the HTML charset declaration that conflicts with the MIME header charset declaration, and inserting a new HTML charset declaration in the HEAD element that matches the charset of the MIME header. In these cases the charset declaration will no longer match the encoding of the HTML body and as a result, non-ASCII characters are corrupted in the rendering of the email message.

To correct this issue, enable the UpdateHtmlWithMissingCharset option. With this option enabled, MNE checks for the presence of a charset declaration in the HTML HEAD element during the migration process. If missing, NME inserts a charset declaration using the charset value from the MIME message header. While this charset declaration may not match the encoding of the message, it makes Microsoft 365 think that everything is proper, and prevents Microsoft 365 from removing the correct charset declaration that appears later in the document. The second charset declaration in the body overrides the newly inserted one that is declared in the HEAD element. As a result, the email message renders properly in the email client.

If any parsing errors occur during the parsing of the HTML, NME migrates the message with no modifications.

This option is off by default. This option adds some minimal overhead to the migration process. It should only be enabled if corrupted characters are observed in the migrated messages.

The issue has only been observed when migrating to Microsoft 365, but it could potentially be introduced in a later update to on-premises Exchange.

Enables the Migrator for Notes to Exchange’s Admin Account Pool features (see the chapter “Microsoft 365 Admin Account Pool utility” in the Migrator for Notes to Exchange Administration Guide).

NOTE: This parameter corresponds to the Exchange Settings check box Use admin account pool.

This parameter is used only when migrating using Outlook MAPI. Most migrations will use the MNE MAPI/HTTP library instead. For more information, see [Exchange] UseMneMapiHttpLib=<#> .

Specifies whether or not the Exchange Autodiscover service will be used to configure the MAPI profile created to connect to Exchange. When UseAutodiscoverCreateProfile is set to 0, the following parameters are used to manually configure the MAPI profile settings:

When UseAutodiscoverCreateProfile is set to 1, the parameters above are ignored and any MAPI profiles that are created by MNE are configured using Autodiscover. The parameters listed below can be used to customize the call to the Autodiscover service:

Note the following:

NOTE: This parameter corresponds to the Exchange Settings check box Automatically configure profile.

MNE no longer uses Outlook MAPI to write data to the target server mailbox. Quest has created its own library that implements Microsoft’s MAPI/HTTP protocol. This library has many advantages over Outlook MAPI and it is now used in almost all migration scenarios that target server mailboxes.

There are limited scenarios where the MNE MAPI/HTTP library is not used:

Use this parameter to force MNE to revert back to using Outlook MAPI to perform the migration. Quest strongly recommends that customers not do this unless directed by Quest support personnel.

The parameter to use the MNE MAPI/HTTP library is enabled by default so parameters that use Outlook MAPI are not used during migration. The parameters that are only used by Outlook MAPI are as follows:

Determines whether the MNE Directory Export Wizard and Notes Migration Manager will update target addresses for the Microsoft 365 domain (applies only when migrating to Microsoft 365). When migrating to Microsoft 365, the default UseO365Domain=1 tells the Directory Export Wizard to update target addresses with the new Microsoft 365 domain. Also, if you change the target type to Microsoft 365 (in the MNE Notes Migration Manager) and apply that change, the default UseO365Domain=1 tells Notes Migration Manager to regenerate the address translation table, to update target addresses with the new Microsoft 365 domain. To not update target addresses with the Microsoft 365 domain, disable this feature by setting UseO365Domain=0.

Occurs in: Data Migr. This is an internal scratch parameter (see Transient “scratch” parameters).

Determines whether the scope of Migrator for Notes to Exchange’s Data Migration Wizard will be expanded to the entire forest rather than limited to just the local domain. For example: ViewEntireForest=1 tells the wizard to expand its scope to include the entire forest. The feature is off (0) by default.

An expanded scope can be useful, for example, where Migrator for Notes to Exchange needs to run the set adserversettings ‑viewentireforest $true PowerShell cmdlet in a multi-domain forest, to enable other PowerShell commands for the same scope. (Note that the cmdlet must be run by Migrator for Notes to Exchange, not run independently.)

[Filter] section

This value corresponds to a GUI element in the Data Migration Wizard, the KB field in the Select Date and Size Filters screen, which specifies a size limit for attachments (only attachments that are smaller than the designated size will be migrated). The parameter value here is in bytes, although the value in the screen is entered in KB. (The default 20971520 bytes for an O365 target corresponds to a 20480 KB entry in the screen.) The wizard writes this value to the Task Parameters from the 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 only calendar data ... dated on or after field in the Select Date and Size Filters screen, which specifies the earliest items that the program will migrate (items that are timestamped on or after the designated date). 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.

Specifies the earliest items that the program will migrate (items that are timestamped on or after the designated date). When set to NONE, all mail and calendar items are migrated.

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 only messages ... dated on or after field in the Select Date and Size Filters screen, which specifies the earliest items that the program will migrate (items that are timestamped on or after the designated date). 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 only calendar data ... dated on or before field in the Select Date and Size Filters screen, which specifies the latest items that the program will migrate (items that are timestamped on or before the designated date). 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.

Specifies the latest items that the program will migrate (items that are timestamped on or before the designated date). When set to NONE, all mail and calendar items are migrated.

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 only messages ... dated on or before field in the Select Date and Size Filters screen, which specifies the latest items that the program will migrate (items that are timestamped on or before the designated date). 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.