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:
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.
Determines which of two methods the Directory Export Wizard will use 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 the default method (NoSummary=0), the error would prevent the wizard from retrieving data from the remaining Notes source documents, and the export would fail. But:
... tells the wizard to open 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 any such error in its log file, but if NoSummary=1 the wizard will then ignore the error and resume reading the remaining source data.
… tells the wizard to enable the feature, to suppress Domino catalog lookups. The default (SkipCatalogSearch=0) leaves this option disabled.
… tells the wizard to skip (not export) group member information.
AD Grps, Prov, Dir Exp, Data Loc, NABs Disc, Doms Disc, Data Migr, PAB Replic |
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:
• |
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.
In the past, it has been observed that there can be a significant delay between granting Full Access permission and Office 365 allowing the account to access the mailbox. In MNE version 4.15.0, the PowerShell cmdlets Add-MNEMailboxAdminPermission and Remove-MNEMailboxAdminPermission were added which can be used to grant Full Access permission ahead of the migration (and revoke it after the migration). This is currently the recommended method of granting permission to the admin account for the migration. If using the PowerShell cmdlets to grant access, disable the built in mechanism by setting AddFullAccessPermission=0.
By default (AddOnlineMeetingUrlScheme=0), Migrator for Notes to Exchange prepends nothing to the URL.
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.
Associated with Migrator for Notes to Exchange’s Admin Account Pool features (see the chapter “Office 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 “Office 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 Office 365 Admin Account Pool utility creates the group and assigns the following roles to the group:
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 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 Administrator SMTP address 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.
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.
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.
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, then the setting defaults to 0.
… tells the wizard to migrate such information. The feature can be disabled by AllowHTMLCalendarBodies=0.
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 admin’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 checkbox 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 AD 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.
... and also, in the [General] section:
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:
• |
Outlook 2010: MNE does not support the MAPI/HTTP protocol when migrating with Outlook 2010. The MAPI/HTTP protocol will never be selected when migrating to on-premise Exchange servers. MNE does not support migrating to O365 with Outlook 2010. |
• |
Outlook 2013: The AutodiscoverDisableMapiHttp parameter can be used to prevent the MAPI/HTTP protocol from being selected when the MAPI profile is being created. |
• |
Outlook 2016 and Outlook 2019: The protocol used by Outlook is selected by MAPI when the MAPI connection is opened, however the protocol selected can be influenced through a registry setting (see the notes below). |
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. |
|
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 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 Office 365.
The Exchange Autodiscover service can return two sets of URLs in its query responses:
• |
Set AutodiscoverPreferInternalUrl=0 to prefer external URLs. |
• |
Set AutodiscoverPreferInternalUrl=1 to prefer internal URLs. |
This parameter is used when migrating with the MNE MAPI/HTTP library or with Outlook MAPI.
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 Office 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 Office 365 Environment is chosen from the list of URLs in the [AzureADAuthorizationEndPointUris] section.
The parameter value is a keyword that must be one of these single digits:
This value corresponds to a GUI element in the Data Migration Wizard: the Mailbox-enable ... accounts checkbox 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 Office 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=<#> .
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).
This value corresponds to a GUI element in the Data Migration Wizard: the Remove mail Forwarding address checkbox 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 checkbox 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 admin’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:
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 admin’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:
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 checkbox 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 checkbox). To disable the Exchange feature (unmark the Exchange checkbox), 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 Office 365 scenario (O365 provisioned by a local proprietary AD) when mailbox-enabling the remote mailboxes (on O365). The feature can be enabled by EnableRemoteMailboxArchive=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 option of extracting images from Notes messages and replacing them with OLE Device Independent Bitmap object attachments. This option makes images renderable in both OWA and the Office web client, and also improves image compression by a factor of two. The feature is enabled by default (1), or set ExtractEmbeddedImages=0 to disable it.
If the OLE Device Independent Bitmap uses significantly more storage than the original source image, you may be able to reduce the storage requirements by using the parameter MaxExtractedImageArea.
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.
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:
• |
TargetAddress (default): The left-hand side (LHS) of the TargetAddress column in the data table becomes the LHS of the forwarding address, to which the wizard appends the Forwarding Domain specified in the user interface during the program run. |
• |
SourceAddress: The SourceAddress column in the data table becomes the left-hand side (LHS) of the forwarding address, to which the wizard appends the Forwarding Domain specified in the user interface during the program run. |
• |
ForwardingAddress: The ForwardingAddress column in the data table becomes the forwarding address. |
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 Office 365 User domain drop-down list, used to specify the Office 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 Office 365 for the admin credentials entered elsewhere on the same screen. The Office 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 Office 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.
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=<#> .
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. |
The value specified by the [Exchange] 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=<#> .
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 execute 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=<#> .
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:
• |
[Exchange] UseAdminAcctPool: When the use of an Admin Account Pool is enabled, the use of a shared MAPI profile is disabled, regardless of the MapiUseSharedProfile setting. |
• |
[Exchange] MapiAdminProfile: If a manually created MAPI profile is specified, no dynamic MAPI profiles are created. The manually created profile is always be used. |
This setting is applied when [Exchange] ExtractEmbeddedImages is enabled.
To mitigate the impact to the target mailbox size of emails that contain large embedded images, the MaxExtractedImageArea setting can be used to specify the maximum allowable image area, in pixels, of the generated BMP image. During the conversion, if the limit would be exceeded, the embedded image is removed from the body of the email and it is replaced with the original image from the Notes source stored to the migrated message as a standard file attachment.
For example, to specify that all images lager than 640 x 480 (307200) pixels should be removed from the email body and migrated as file attachments, set MaxExtractedImageArea=307200.
When MaxExtractedImageArea=0, the image is migrated to Exchange with no size limit applied.
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 aborted.
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 then 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 then 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.
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.
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.
This value corresponds to a GUI element in the Data Migration Wizard: the Do not connect to an Exchange server checkbox 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 a single Office 365 account SKU that the Data Migration Wizard should use when licensing end users for O365. 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 Office 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.
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 Office 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.
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 MNE logs onto an Office 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.
Identifies the URL of the Office 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 Office 365 Environment is selected from the list of URLs in the [MsOnlinePSConnectionUris] section.
Specifies the Usage Location required by Microsoft for Office 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, then 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 then 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 wizard to delete the Exchange copy of the item and then 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:
Corresponds to a GUI element in the Data Migration Wizard: the Reset Office 365 Passwords check box on the wizard's Operations screen. The checkbox and parameter value determine whether, when mailbox-enabling users in Office 365, the wizard will automatically generate random Office 365 passwords, assign them to users' Office 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.
4: Tasks Only |
• |
None (0): Don’t migrate any permissions to the Root folder. Users can only open specific well-known folders in mailboxes to which they have access using the Outlook Open User’s Folder feature. |
• |
Set Folder Visibility Only (1): Users who have access to any kind of content within the Notes mail file are granted Folder Visibility rights on the root folder in the target mailbox. This allows users to browse the folder structure of the root folder. However, the users can only access the content of the child folders to which they’ve been granted access. The downside of this approach is that any folders that are created directly under the root folder after the migration inherit the permissions of the root folder. This could lead to some users having limited access to some of the content within the mailbox. For example, a user who should have access to email content would be able to access the mail folders that were created during migration, but would not have access to the content of mail folders that were created after the migration. Conversely, users that have access to calendar/task/contact data only in the source mail file can view the folder structure of these newly created mail folders. However, they cannot view the content of these new mail folders. |
• |
Mail Folder Permission Only (2): MNE configures the permission on the root folder to match all other mail folders (such as the Inbox). The advantage of this approach is that users who have access to email have all of the access that they need in the target mailbox on folders that are created during the migration and also on folders that are created directly under the root folder after the migration (since those folders inherit their permissions from the root folder). The one disadvantage is that users who only have access to calendar/task/contact data can only access that data using Outlook’s Open User’s Folder feature. They cannot browse the mailbox content from the root folder. |
• |
Combined Permissions (3): MNE combines the behavior of the previous two settings. Users who have access to mail content are granted equivalent access to the root folder. Users who have access to calendar/task/contact data are granted Folder Visibility permissions on the root folder. There are numerous benefits to this approach. All users who have access to any kind of content can browse the folders of the target mailbox from the root of the mailbox. Users with access to mail content are assured to have access to folders created during the migration and those that are created directly under the root folder after the migration. The one minor downside of this approach is that because folders that are created directly under the root folder after the migration inherit the permission of the root folder, users who have access to calendar/task/contact data are only granted Folder Visibility permissions on those folders. This does not grant these users access to the content within these folders. However, they can view the folder structure under these folders, granting them slightly more access than intended. |
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 Office 365 (when migrating to Office 365). Use this setting, paired with the RPCUseAdminMapiProfile parameter (also documented separately below), when migrating to Office 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 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 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 Office 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… checkbox) 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 then 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 checkbox, 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:
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 checkbox) 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… checkbox) 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 then 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 checkbox) 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.
The feature is enabled/disabled, and the server name is set, by:
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 (SetManagedByToUserForest=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:
|
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.
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:
… 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 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.
UpdateHtmlWithMismatchedCharset=UTF-16
UpdateHtmlWithMismatchedCharset=UTF-16
UpdateHtmlWithMismatchedCharset=US-ASCII
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 Office 365 think that everything is proper, and prevents Office 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.
Enables the Migrator for Notes to Exchange’s Admin Account Pool features (see the chapter “Office 365 Admin Account Pool utility” in the Migrator for Notes to Exchange Administration Guide).
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:
• |
The UseAutodiscoverCreateProfile parameter is only configurable when migrating to an on-premises target with Outlook 2010 or 2013. |
NOTE: This parameter corresponds to the Exchange Settings check box Automatically configure profile. |
There are limited scenarios where the MNE MAPI/HTTP library is not used:
Determines whether Migrator for Notes to Exchange's Directory Export Wizard and Notes Migration Manager will update target addresses for the Office 365 domain (applies only when migrating to O65). When migrating to Office 365, the default UseO365Domain=1 tells the Directory Export Wizard to update target addresses with the new Office 365 domain. Also, if you change the target type to Office 365 (in Migrator for Notes to Exchange's Notes Migration Manager) and then Apply that change, the default UseO365Domain=1 tells Notes Migration Manager to regenerate the address translation table, to update target addresses with the new O365 domain. To not update target addresses with the O365 domain, disable this feature by setting UseO365Domain=0.
Occurs in: Data Migr. This is an internal scratch parameter (see Transient “scratch” parameters).
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.)
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.
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.
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.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy