[IncludeFoldersAndViews] section
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]. |
[Notes] section
The Migration Wizard includes a configuration dialog where the active mail types can be configured. However, it only includes check boxes for the first four types, allowing you to disable one or more of these types of active mail. To disable active mail processing of Missing Form Field messages, or to enable the processing of messages with dropdown sections, the ActiveMailTypes setting must be manually configured in the Default Global Settings.
Determines if the migration of orphaned messages will use the Date/Time filters defined in the Migrate Data Wizard, in addition to the MailAndCalQueryFilter parameter. Note that this parameter is ignored if the MigrateOrphanedDocs parameter is turned off (set to 0).
Permits the designation of alternate names for appointment forms to migrate. For example:
... tells the program to recognize "class2" as an additional design class (in addition to the default design class) for Archive NSF files. If the program finds an NSF file that does not match any of the program's default design classes for Archive or Mail files, the program will look at this parameter (and the comparable MailDesignClass parameter) to find an alternate design class, and thereby determine the file type. To designate more than one additional design class for Archive files, use the pipe character ( | ) to separate between each pair of class names, like this:
In this notesdtapp.ini file , the parameter may also be set to:
Determines whether the SSDM's logging and statistics for unmigrated items will include or exclude items that do not appear in the FailedMessageList skipped-items folder because they were intentionally skipped. (The FailedMessageList feature is described in separate entries for the WriteFailedMessageList... parameters, also in this [Notes] section.)
For example, the program will intentionally skip PAB Replicator messages or calendar items if these items have not been selected for migration, but they will not appear in the FailedMessageList skipped-items folder since they were deliberately excluded from the migration. This CountIntentionallySkippedItems parameter lets you choose whether MNE should still count these items in its skipped-items statistics, and report them in its logs.
By default (1), the log and statistics will include items that have been skipped but do not appear in the skipped-items folder. To disable logging and counting such items, set CountIntentionallySkippedItems=0. Note also:
|
• |
Any setting for this CountIntentionallySkippedItems parameter is ignored if the FailedMessageList feature is disabled. |
|
• |
A setting of CountIntentionallySkippedItems=0 will override [General] LogSkippedAppointmentResponses=1 (so the program will not log or count skipped appointment responses). |
... tells the program to use the original method instead.
Specifies the name of a Domino server that the SSDM will use to compose HTTP- or Notes-style DocLink URLs if it cannot find the server by its own lookup method (as specified by the DocLinksFastLookupOnly parameter, described below). The parameter value is a string specifying the name of the server. The specified server name must be the TCP/IP server name (e.g., bighat.itsfunny.com), and not a Domino server name (bighat/itsfunny).
If the designated lookup method fails to find the server, SSDM will use the server name specified by DocLinksDefaultServer or, if no DocLinksDefaultServer is specified (default is null), will migrate the item without the DocLink.
Determines the method the SSDM will use to look up the server for an HTTP- or Notes-style DocLink. By default (1), the SSDM will use only a new, faster method introduced in Migrator for Notes to Exchange version 4.5.0. Or you can revert to the earlier method by setting DocLinksFastLookupOnly=0. (Quest has not observed any case where the older method was more reliable than the faster new method.)
If neither method finds the server, the SSDM will use the server name specified by the DocLinksDefaultServer parameter (see above) or, if no DocLinksDefaultServer is specified, will migrate the item without the DocLink.
Determines if the Notes links uses a Domino Server CN name instead of a Domino Server NetAddress when [General] HTMLdoclinks=3, migrate DocLinks to Exchange as Notes links (the default). When DocLinksPreferCNForNotesURL is set to the default value (0), the Domino Server NetAddress is used.
|
• |
If [General] HTMLdoclinks=3 and [Notes] DocLinkPreferCNForNotesUrl=0, the Migrated DocLink = notes://MNE-AUTO-D901.prod.quest.corp/db/view/document |
|
• |
If [General] HTMLdoclinks=3 and [Notes] DocLinkPreferCNForNotesUrl=1, the Migrated DocLink = notes://MNE-AUTO-D901/db/view/document |
Determines (in conjunction with the parameter [Notes] MapDefaultAclToReviewer) how the wizard maps some Notes access levels to Exchange, for calendar and to-do items. Specifically, the No Access and the Depositor access levels are mapped as shown in the following table, for selected Read Public and Write Public Notes permissions.
|
Migrator for Notes to Exchange Parameter Settings |
|||
|
MapDefaultAclToReviewer=1 |
|||
|
MapDefaultAclToReviewer=0 or 1 |
|||
Determines whether the program will migrate both encrypted and non-encrypted mail (0), or migrate encrypted mail only (1). For example, EncryptedMailOnly=1 tells the program to migrate only encrypted mail. This feature is also an option in the Data Migration Wizard (same parameter name in the same section, but in the Global Defaults and Task Parameters).
Determines whether the SSDM should use a pre-Notes 7 version of the nxrtf2.dll file, which the program uses to convert Notes rich text to MS RTF. The nxrtf2.dll file that accompanies Notes 7 and later provides better RTF fidelity during data extraction, but appears to be incompatible with some environments where it can cause the Notes environment to crash. This parameter lets you force the SSDM to use the older version of nxrtf2.dll:
The feature is off (ForceOldNxRTFdll=0) by default, but is enabled by setting the parameter value to 1, as in the example above.
This parameter can be used to perform the following tasks.
|
• |
For a user that is valid on both Notes and Exchange, prevent permissions from being granted for that user in Exchange. Specifying the user in the IgnoreACLs parameter suppresses the migration of permissions. |
|
• |
To set the parameter, specify the ACL member. For example:
... tells the wizard to ignore ACL member entries of Administrator. You can specify two or more values by separating them with commas. There is no default value for this parameter, but the Setup program automatically enters the following values upon installation:
Specifies one or more particular forms that should be ignored (not migrated). For example:
... tells the program to not migrate H_PAGEUI forms.
This parameter can also be used to force the program to ignore forms that are ordinarily processed, by preceding the form name with an exclamation point (i.e., IgnoreForms=!FormName).
Permits the designation of alternate names for journal entry forms to migrate. For example:
Determines (in conjunction with the parameter [Notes] ElevateCalendarAuthorACLtoEditor) how the wizard maps some Notes access levels to Exchange, for calendar and to-do items. Specifically, the No Access and the Depositor access levels are mapped as shown in the following table, for selected Read Public and Write Public Notes permissions.
|
Migrator for Notes to Exchange Parameter Settings |
|||
|
MapDefaultAclToReviewer=1 |
|||
|
MapDefaultAclToReviewer=0 or 1 |
|||
... tells the program to recognize "class2" as an additional design class (in addition to the default design class) for Mail NSF files. If the program finds an NSF file that does not match any of the program's default design classes for Archive or Mail files, the program will look at this parameter (and the comparable ArchiveDesignClass parameter) to find an alternate design class, and thereby determine the file type. To designate more than one additional design class for Mail files, use the pipe character ( | ) to separate between each pair of class names, like this:
In this notesdtapp.ini file, the parameter may also be set to MailDesignClass=all to force all NSFs in the specified directory to be displayed in the list, regardless of design class or item count. The "all" option was added in ver 3.2.
Determines whether the program will mark as “Public” a non-mail message whose Notes $PublicAccess attribute is not set. For example:
... tells the program to mark a non-mail-type message as “Public” if its $PublicAccess attribute is not set. By default (MapPrivateAsPublic=0), the program will leave such messages marked as “Private.”
Permits the designation of alternate names for mail forms to migrate. For example:
Determines whether the SSDM will migrate responses to appointment/meeting requests (Accepted, Declined, etc.). For example: MigrateAppointmentResponses=1 tells the SSDM to migrate responses.
Tells the program whether to migrate replication conflicts. By default (MigrateConflictDocs=0), conflict documents will not be migrated. But: MigrateConflictDocs=1 tells the program to migrate conflict documents to the All Documents folder.
Tells the program whether to migrate "orphaned" documents that appear only in the Notes All Documents folder. Such orphaned documents are migrated by default, to an All Documents folder in Exchange, but:
... tells the program to not migrate those items.
Determines whether the program will migrate calendar resources. For example, to tell the SSDM to not migrate resources: MigrateReservationsAlways=0
If not all objects in the collection are classified as resources, but MigrateReservationsAlways=1, the SSDM presents a popup warning explaining that the calendars of non-resource objects may not migrate correctly and suggesting that MigrateReservationsAlways be disabled (set to 0) unless the user is certain that all objects in the collection are resources. (The popup offers the option of ignoring a MigrateReservationsAlways=1 setting.)
Specifies the location of the notes.ini file. This value is inferred from the operating environment and automatically written to the notesdtapp.ini file; Quest recommends you do not manually enter or change this value except at the direction of Quest Support.
Permits the designation of alternate names for appointment notice forms to migrate. For example:
Sets the name of the All Documents folder in Exchange, which receives orphaned documents from Notes' All Documents folder. The folder is named All Documents by default, but you can assign any other valid name. For example: OrphanedDocsFolder=Orphans
PABDesignClass=class2 tells the program to recognize "class2" as an additional design class (in addition to the default design class) for PAB NSF files. If the program finds an NSF file that does not match any of the program's default design classes for Archive, Mail or PAB files, the program will look at this parameter (and the comparable ArchiveDesignClass and MailDesignClass parameters) to find an alternate design class, and thereby determine the file type. To designate more than one additional design class for PAB files, use the pipe character ( | ) to separate between each pair of class names, like this: PABDesignClass=class2|class3|class4
Defines a list of address-book attributes, from which at least one must be present within a PAB for the PAB to be migrated. The <Attrib#> variables stand for the names of address-book attributes in the Notes/Domino source. Each pair of attribute names must be separated by a pipe character ( | ). For example:
... tells the program to migrate a PAB only if it contains at least one of the attributes ListName or LastName or CompanyName. This feature is also an option in the Data Migration Wizard (same parameter name in the same section, but in the Global Defaults and Task Parameters).
This value corresponds to a GUI element in the SSDM: the Password text box in the Specify Notes Login Information screen. The program writes this value to the Task Parameters based on an admin's GUI entry. The parameter value here is obfuscated, as a security precaution, and Quest recommends you do not manually enter or change this value except at the direction of Quest Support.
Determines whether the program will quote non-ASCII characters in Notes rich text to preserve them during conversion to Microsoft RTF by versions of nxrtf.dll older than 5.0.11. Pre-5.0.11 versions of nxrtf.dll convert non-ASCII characters to question marks, so this feature corrects that limitation to permit the migration of non-ASCII characters—for example, Chinese or Thai characters. This feature is on (1) by default, but can be disabled by: QuoteNonAsciiCharsInRTF=0. The parameter is ignored if the prevailing version of nxrtf.dll is 5.0.11 or higher. See also the UseAppNxrtfDLL parameter (also in this [Notes] section) for related information.
The default value supports English, French, German and Japanese.
The default value supports English, French, German and Japanese.
|
to|An|A| 宛先 |
The default value supports English, French, German and Japanese.
Setting the parameter to 0 is equivalent to setting:
This value corresponds to a GUI element in the MNE console: the Server text box in the Notes Server Configuration screen. The program writes this value to notesdtapp.ini from the GUI entry in NMM; Quest recommends you do not manually enter or change this value except at the direction of Quest Support.
… tells the SSDM to skip (not migrate) Notes tasks that are marked as complete. The feature is off (SkipCompletedTasks=0) by default.
If SkipInternetHeaders is set to On (1), none of the message internet headers are migrated.
Specifies one or more messages that the SSDM should skip when migrating data, typically used to bypass the rare message that contains some problematic element, such as corrupted data, that the program cannot process. When a program run is abandoned by a “bad” message, the run log reports the message ID (an arbitrary hex string generated by the program) near the end of the log, for example: notesID 0X00001FFA. An admin can exclude that message by this parameter setting:
|
• |
|
• |
|
• |
|
• |
($All) (only when orphaned messages are migrated as per the [Notes] MigrateOrphanedDocs setting) |
Setting StandardAndUserFoldersOnly to 0 allows both system and user folders/views to be migrated. Note that this requires configuring the [Filters] section with the itemized list of folders and views that should not be included in the migration.
Specifies the name of the Notes folder that contains Notes stationery. Example:
Permits the designation of alternate names for task forms to migrate. For example:
Permits the designation of alternate names for task notice forms to migrate. For example:
Determines whether the SSDM will (1) or will not (0) automatically replace the Microsoft generic serif, sans-serif and Courier fonts in RTF message bodies with, respectively, Times New Roman, Arial and Courier New fonts. For example: UpdateRtfFonts=0 tells the wizard to not make those replacements. The option is on (1) by default.
Determines whether the program will try to use a more recent compatible version of nxrtf.dll (if available) to convert Notes rich text to MS RTF. Pre-5.0.11 versions of nxrtf.dll convert non-ASCII characters to question marks, so this feature permits the migration of non-ASCII characters—for example, Chinese or Thai characters—by telling the program to use a later version of nxrtf.dll. This feature is on (1) by default, but can be disabled by UseAppNxrtfDLL=0
The alternate (more recent) version of nxrtf.dll must reside in the same directory as the SSDM program file, and its major version must be the same as the major version of nnotes.dll. You may find a 5.0.11 version of nxrtf.dll in the Notes program directory of a known 5.0.11 client installation.
If the program finds no newer version of nxrtf.dll that meets the conditions noted above, it will use the nxrtf.dll found in the PATH. If no 5.0.11 or later version of nxrtf.dll is available, see QuoteNonAsciiCharsInRTF (also in this [Notes] section) for an alternate solution to the non-ASCII characters conversion problem.
UseIMAPFlags=1 tells the program to check bit 0 of the $FolderRefFlags Notes attribute to determine whether messages are read or unread. The bit is set to 0 if an item is unread, or set to 1 if the item has been read.
Determines whether the Specify directory where Notes mail files are located GUI element will appear on the Select Notes Local Mail File Replica to Migrate screen. For example: UseMailFileOnly=1 tells the program to display the Specify directory... text box, and its associated label and Browse button. By default (UseMailFileOnly=0), these GUI elements will not appear in the screen.
Specifies the name of an Outlook folder to which all user-created Notes folders will be migrated (as subfolders). For example: UserFolderPrefix=MyFolders tells the program to create a folder named MyFolders in the Outlook root directory (at the same level as the Inbox), and copy all user-created Notes folders to the new MyFolders folder in Outlook. The default value is Folders. See also Custom folder mapping for more information about this UserFolderPrefix parameter, and how its value affects custom-folder mapping parameters in the language sections of Migrator for Notes to Exchange parameters.
This value corresponds to a GUI element in the MNE console: the User ID file text box in the Notes Server Configuration screen. The program writes this value to notesdtapp.ini from the GUI entry in NMM; Quest recommends you do not manually enter or change this value except at the direction of Quest Support.
For example: UserViewPrefix=MyViews tells the program to create a folder named MyViews in the Outlook root directory (at the same level as the Inbox), and copy all user-created Notes views to the new MyViews folder in Outlook. The default value is Views.
The ViewAndFolderFlagPattern value is used to identify those Notes design elements of the VIEW class that should be classified as Views or Folders. Only the design elements whose design flags match the specified pattern are migrated. All other design elements will be ignored. This prevents the migration of design elements that belong to the VIEW class, but are not in fact views or folders. For example this pattern prevents the migration of shared columns.
The specified pattern must follow the syntax specified by the Notes API under Design Flag Patterns. The specific flags and their meanings can be obtained from the Notes API in the file stdnames.h. This header file also includes a list of patterns for identifying specific types of design elements. The default pattern used above comes from the pattern DFLAGPAT_VIEWS_AND_FOLDERS in stdnames.h.
|
WriteFailedMessageListToThisMbxFolder=[null] |
The WriteFailedMessageListToThisMbxFolder parameter specifies a name for the folder to be added to the user's mailbox, to contain the unmigrated items. WriteFailedMessageListClass specifies one or more types of unmigrated items for the feature to capture; valid keyword values are: Errored, Skipped and Filtered. To specify more than one type, separate multiple keywords by the pipe ("|") character, as in this example:
WriteFailedMessageListClass=Errored|Skipped|Filtered
This example tells the SSDM to create copies of any Errored, Skipped and/or Filtered items and save them in a new folder named Unmigrated in the user's mailbox.
The feature is enabled by entering any value for the WriteFailedMessageListToThisMbxFolder parameter. (If that parameter is omitted or its value is left empty, the feature is disabled and the WriteFailedMessageListClass parameter is ignored.) The feature is disabled by default (WriteFailedMessageListToThisMbxFolder is omitted or its value is [null]), and by default WriteFailedMessageListClass=Errored (only).
[PAB] section
Determines whether a migated PAB will be designated as the user’s default PAB, if no default PAB is already designated for that user in Exchange. For example: MakeDefault=0 tells the program to not set the migrated PAB as the user's default.
Determines whether the destination directory of a migated PAB will be designated as the user’s default PAB directory, if no default PAB directory is already designated for that user in Exchange. For example: ShowFirst=0 tells the program to not set the migrated PAB directory as the user's default.
[Screens] section
|
• |
show: The screen appears in every run. |
|
• |
skip: The screen appears only if the information it ordinarily obtains from the user cannot be otherwise obtained or inferred. |
|
• |
silent: The screen never appears in any run. |
Chapter 4 of the Migrator for Notes to Exchange Scenarios Guide explains how these parameters relate to others to customize the SSDM.
Determines whether, or under what circumstances, the Select Date and Size Filters screen will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. For example: Filter=show
The default value “no-op” is a fourth valid value (for this Filter parameter only). The “no-op” setting is functionally equivalent to “silent,” but signifies that the parameter value is unassigned—in which case the screen will not appear in a program run.
Determines whether, or under what circumstances, the Migration Report screen (the "Finished" screen) will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. For example: Finished=skip
Determines whether, or under what circumstances, the Specify Notes Login Information screen will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. For example: Login=skip
Determines whether, or under what circumstances, the Specify Data for Migration screen will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. For example: MigrateWhat=skip
Determines whether, or under what circumstances, the Select Profile screen will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. For example: Profile=show
Determines whether, or under what circumstances, the Migrating Data screen (the "Progress" screen) will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. Since this screen does not collect any information, the skip and silent options are equivalent. For example: Progress=skip
Determines whether, or under what circumstances, the Specify Directory for Migrated Archive screen will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. For example: PstDir=skip
Determines whether, or under what circumstances, the Select Notes Address Books to Migrate screen will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. For example: SelectAddrBook=show
Determines whether, or under what circumstances, the Select Notes Archive Files to Migrate screen will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. For example: SelectArchive=show
Determines whether, or under what circumstances, the Select Notes Local Mail File Replica to Migrate screen will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. For example: SelectMailFile=show
Determines whether, or under what circumstances, the Selection Summary screen will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. Since this screen does not collect any information, the skip and silent options are equivalent. For example: Summary=skip
Determines whether, or under what circumstances, the Welcome screen will appear in program runs. See For all parameters... at the beginning of this [Screens] section for valid parameter values. Since this screen does not collect any information, the skip and silent options are equivalent. For example: Welcome=skip