Determines whether HTML information in the Description field of calendar appointments and tasks will migrate. The default:
… tells the SSDM to migrate such information. The feature can be disabled by AllowHTMLCalendarBodies=0.
Tells the SSDM 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 the type-ahead feature easier to use, can be enabled by
... and also, in the [General] section:
The parameter value is a keyword that must be one of these single digits:
When this option is enabled, the following parameters must also be configured:
NOTE: These parameters are configured by the MNE Migration Console on the Exchange Server page when the Apply button is clicked. |
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.
Specifies a comma delimited list of MAPI error codes for the MAPI Retry feature. MAPI Retry is a feature of MNE that attempts to recover from intermittent or brief network connectivity issues. The errors that are included in this list are errors that are typically returned from MAPI API functions when network connection issues do occur. If MNE encounters one of the MAPI errors listed in the MAPIErrorsToRetry setting, it will attempt to recover using the algorithm described below.
1 |
If a MAPI call fails with one of the errors listed in the MAPIErrorsToRetry list, the API call is made again after pausing for the number of seconds specified by MessageRetryWait. MNE keeps retrying for a maximum of MAPIRetryCount times. |
3 |
If the attempt to open a new MAPI session fails, MNE waits for the number of second specified by MessageRetryWait and tries opening a new session again. MNE keeps trying to reconnect for a maximum of MaxSessionReconnectCount times. |
6 |
MNE attempts to migrate each object using the algorithm above up to a maximum of MessageRetryCount times. If MNE reaches the MessageRetryCount limit, it assumes that there is something wrong with the object itself and it proceeds to the next object to be migrated. |
The full list of parameters used to customize the MAPI Retry feature is below.
The value specified by the [Exchange] MessageRetryCount parameter |
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 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.
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.
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.
Determines whether the SSDM 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), the SSDM migrates FYI attendees of a Notes meeting to the bcc field in Exchange. You can disable the feature (0) to make the SSDM migrate FYI attendees to the cc field.
Identifies the Office 365 URL that provides Modern Authentication services. This setting is updated by the Migration Console when the Apply button is pressed on the Exchange Server page. The URL associated with the selected Office 365 Environment is chosen from the list of URL’s in the [MsOnlineAuthorityUrls] section.
Identifies the Office 365 tenant ID in Modern Authentication requests that are sent to Office 365. This setting is updated by the Migration Console when the Apply button is pressed on the Exchange Server page.
For example:
O365Tenant=consoso.onmicrosoft.com
Identifies the base URL for the Office 365 tenant’s mail API’s, such as O365 REST API and EWS. This setting is updated by the Migration Console when the Apply button is pressed on the Exchange Server page. The URL associated with the selected Office 365 Environment is chosen from the list of URL’s in the [OutlookRestApiUrls] section.
... tells the SSDM 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:
4: Tasks Only |
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 actual 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.
This value specifies the max size limit for attachments—that is, the program will migrate only attachments that are smaller than the size designated here, in KB. For example: AttachSize=8000 tells the program to not migrate attachments larger than 8000 KB.
This value corresponds to a GUI element in the SSDM: 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 (will migrate only items that are timestamped on or after the designated date). The SSDM writes this value to the Task Parameters from the user'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 SSDM: 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 (will migrate only items that are timestamped on or after the designated date). The SSDM writes this value to the Task Parameters from the user'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 SSDM: 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 (will migrate only items that are timestamped on or before the designated date). The SSDM writes this value to the Task Parameters from the user'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 SSDM: 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 (will migrate only items that are timestamped on or before the designated date). The SSDM writes this value to the Task Parameters from the user's GUI entry; Quest recommends you do not manually enter or change this value except at the direction of Quest Support.
Each line specifies a folder name. The specified folder is excluded from the migration. For example:
Folders can be included or excluded by setting [Filters], [FolderTreeFilters], and [IncludeFoldersAndViews]. The precedence order is [Filters] > [IncludeFoldersAndViews] > [FolderTreeFilters].
• |
If a folder is named in both the [Filters] section and the [IncludeFoldersAndViews] section, the [Filters] section takes precedence and the folder or view is not migrated. |
• |
If a folder is named in both the [IncludeFoldersAndViews] and the [FolderTreeFilters], the [IncludeFoldersAndViews] sections take precedence and the folder or view is migrated. Since the [FolderTreeFilters] section impacts the sub folders, the sub folders are still excluded if they are not named in the [IncludeFoldersAndViews]. |
Folders can be included or excluded by setting [Filters], [FolderTreeFilters], and [IncludeFoldersAndViews]. The precedence order is [Filters] > [IncludeFoldersAndViews] > [FolderTreeFilters].
• |
If a folder is named in both the [Filters] section and the [IncludeFoldersAndViews] section, the [Filters] section takes precedence and the folder or view is not migrated. |
• |
If a folder is named in both the [IncludeFoldersAndViews] and the [FolderTreeFilters], the [IncludeFoldersAndViews] sections take precedence and the folder or view is migrated. Since the [FolderTreeFilters] section impacts the sub folders, the sub folders are still excluded if they are not named in the [IncludeFoldersAndViews]. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center