Chat now with support
与支持团队交流

Migrator for Notes to Exchange 4.16 - Program Parameters Reference Guide

About the Migrator for Notes to Exchange documentation Introduction Parameters for Admin Components Parameters for the Self-Service Desktop Migrator (SSDM)

[Notes] section

Type:

Default:

 

New in:

integer

31

 

4.11

When Active Mail Processing is enabled, this parameter determines what type of Active Mail should be processed. This parameter is implemented as a set of bit flags where each bit corresponds with a specific type of active mail to be processed. The following bit values are supported:

The default value for this parameter is 31, meaning that when Active Mail Processing is enabled, MNE will process all types of active mail except for dropdown sections.

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.

For example, to configure MNE to process all types of active mail, add the following setting to the default global settings:

Type:

Default:

 

New in:

boolean

1

 

4.13.1

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

When this parameter is turned on (set to 1), orphaned messages are treated the same as regular messages in how the various filters are applied.

Type:

Default:

 

New in:

string

[none]

 

3.1.0

Permits the designation of alternate names for appointment forms to migrate. For example:

You may enter a value ending with an asterisk (*) for simple wildcard matching. You may also specify one or more form names; the first listed name is the default. To define more than one, use a pipe character ( | ) to separate each pair:

Forms are used to classify message type. The precedence order is:
JournalEntryForms > MemoForms > AppointmentForms | NoticeForms | TaskForms | TaskNoticeForms | ReservationForms

For example, if a message matches with both MemoForms and AppointmentForms, it is classified as mail, not as an appointment.

Type: string

Default: [none]

Expanded in ver 3.2

... 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 (but not for the Data Migration Wizard), the parameter may also be set to:

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

Type: boolean

Default: 1

New in ver 4.12.1

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] LogSkippedAppointment­Responses=1 (so the program will not log or count skipped appointment responses).

Type: boolean

Default: 1

 

Controls whether the SSDM will use a newer processing method to improve performance when migrating with a date filter, or use the older original method. The program default (1) is to use the newer method, but:

... tells the program to use the original method instead.

Type: string

Default: [null]

 

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.

Type: boolean

Default: 1

 

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.

Type: integer

Default: 80

 

Specifies which port to insert into a DocLink URL upon migration of a DocLink. If unspecified, the SSDM will use port 80.

Type:

Default:

 

New in:

boolean

0

 

4.15.1

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.

For example, if the Domino server is configured as follows:
Domino Server CN name = MNE-AUTO-D901
Domino Server NetAddress = MNE-AUTO-D901.prod.quest.corp

If [General] HTMLdoclinks=3 and [Notes] DocLinkPreferCNForNotesUrl=0,
then the Migrated DocLink = notes://MNE-AUTO-D901.prod.quest.corp/db/view/document
If [General] HTMLdoclinks=3 and [Notes] DocLinkPreferCNForNotesUrl=1,
then the Migrated DocLink = notes://MNE-AUTO-D901/db/view/document

Type:

Default:

 

New in:

boolean

0

 

4.7

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.

Read Public

Write Public

Migrator for Notes to Exchange Parameter Settings
(defaults are shown here in red)

Exchange
Calendar / ToDo
Access Rights

No

[ — — — — — — — — any combination — — — — — — — — ]

No Access

Yes

No

MapDefaultAclToReviewer=0
ElevateCalendarAuthorACLtoEditor=0

No Access

MapDefaultAclToReviewer=0
ElevateCalendarAuthorACLtoEditor=1

Reviewer

MapDefaultAclToReviewer=1
ElevateCalendarAuthorACLtoEditor=0
or 1

Reviewer

Yes

MapDefaultAclToReviewer=0
ElevateCalendarAuthorACLtoEditor=0

No Access

MapDefaultAclToReviewer=0 or 1
ElevateCalendarAuthorACLtoEditor=1

Editor

MapDefaultAclToReviewer=1
ElevateCalendarAuthorACLtoEditor=0

Author

Type: boolean

Default: 0

New in ver 3.2.0

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

Type: boolean

Default: 0 (off)

New in ver 4.11

Determines whether the SSDM will (1) or will not (0) use an alternate processing method to improve handling of certain foreign characters when migrating from Notes 7. The feature offers improved fidelity when migrating from some Notes 7 sources, but should be left disabled (default) unless you are experiencing garbled text with extraneous question marks in migrated Notes 7 messages containing foreign characters.

Type: boolean

Default: 0

 

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.

Type: string

Default: [none]

New in ver 4.1

The Data Migration Wizard seeks to validate ACL entries by matching each with a corresponding ACL entry in Exchange. Use this parameter to specify one or more ACL member entries that the Data Migration Wizard should ignore.

This parameter can be used to perform the following tasks.

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:

Type: string

Default: H_PAGEUI

New in ver 4.1.5

Specifies one or more particular forms for the Data Migration Wizard to ignore (not migrate). 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).

Type:

Default:

 

New in:

keyword

Activity

 

4.1.5

Permits the designation of alternate names for journal entry forms to migrate. For example:

You may enter a value ending with an asterisk (*) for simple wildcard matching. You may also specify one or more form names; the first listed name is the default. To define more than one, use a pipe character ( | ) to separate each pair:

Forms are used to classify message type. The precedence order is:
JournalEntryForms > MemoForms > AppointmentForms | NoticeForms | TaskForms | TaskNoticeForms | ReservationForms

For example, if a message matches with both MemoForms and AppointmentForms, it is classified as mail, not as an appointment.

Type:

Default:

 

New in:

boolean

1

 

4.5.4

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.

Read Public

Write Public

Migrator for Notes to Exchange Parameter Settings
(defaults are shown here in red)

Exchange
Calendar / ToDo
Access Rights

No

[ — — — — — — — — any combination — — — — — — — — ]

No Access

Yes

No

MapDefaultAclToReviewer=0
ElevateCalendarAuthorACLtoEditor=0

No Access

MapDefaultAclToReviewer=0
ElevateCalendarAuthorACLtoEditor=1

Reviewer

MapDefaultAclToReviewer=1
ElevateCalendarAuthorACLtoEditor=0
or 1

Reviewer

Yes

MapDefaultAclToReviewer=0
ElevateCalendarAuthorACLtoEditor=0

No Access

MapDefaultAclToReviewer=0 or 1
ElevateCalendarAuthorACLtoEditor=1

Editor

MapDefaultAclToReviewer=1
ElevateCalendarAuthorACLtoEditor=0

Author

Type: string

Default: [none]

Expanded in ver 3.2

... 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 (but not for the Data Migration Wizard), 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.

Type: boolean

Default: 0

 

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

Type:

Default:

 

New in:

string

[none]

 

3.1.0

Permits the designation of alternate names for mail forms to migrate. For example:

You may enter a value ending with an asterisk (*) for simple wildcard matching. You may also specify one or more form names; the first listed name is the default. To define more than one, use a pipe character ( | ) to separate each pair:

Forms are used to classify message type. The precedence order is:
JournalEntryForms > MemoForms > AppointmentForms | NoticeForms | TaskForms | TaskNoticeForms | ReservationForms

For example, if a message matches with both MemoForms and AppointmentForms, it is classified as mail, not as an appointment.

Type: boolean

Default: 0

New in ver 4.1.5

Determines whether the SSDM will migrate responses to appointment/meeting requests (Accepted, Declined, etc.). For example: MigrateAppointmentResponses=1 tells the SSDM to migrate responses.

Type: boolean

Default: 0

New in ver 3.1.0

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.

Type: boolean

Default: 1

 

... tells the program to not migrate empty folders. By default, the program will migrate all folders regardless of whether they contain any items.

Type: boolean

Default: 1

 

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.

Type: boolean

Default: 1

 

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

Type: boolean

Default: 0

New in ver 4.1.9

Determines whether the program will be configured to not ignore MIME data that is preceded by a boundary of whitespace and/or null characters. Example:

... tells the program to not ignore MIME data that is preceded by a boundary of whitespace and/or null characters. The feature is off (0) by default.

Type: string

Default: [inferred from operating environment]

 

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.

Type:

Default:

 

New in:

string

[none]

 

3.1.0

Permits the designation of alternate names for appointment notice forms to migrate. For example:

You may enter a value ending with an asterisk (*) for simple wildcard matching. You may also specify one or more form names; the first listed name is the default. To define more than one, use a pipe character ( | ) to separate each pair:

Forms are used to classify message type. The precedence order is:
JournalEntryForms > MemoForms > AppointmentForms | NoticeForms | TaskForms | TaskNoticeForms | ReservationForms

For example, if a message matches with both MemoForms and AppointmentForms, it is classified as mail, not as an appointment.

Type: string

Default: [none]

New in ver 3.0.0

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

Type: string

Default: [none]

 

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

Type: string

Default: [none]

New in ver 3.1.0

Tells the program whether and how to migrate personal address book (PAB) form types that are not of the standard "Group" form type. For example, to migrate PAB Group form type "Business Card," you would enter:

By default (if this parameter is omitted) the program will not migrate PAB form types that are not of the standard form type.

Type: string

Default: [none]

New in ver 3.1.0

Tells the program whether and how to migrate personal address book (PAB) form types that are not of the standard "Person" form type. For example, to migrate PAB Person form type "Business Card," you would enter:

By default (if this parameter is omitted) the program will not migrate PAB form types that are not of the standard form type.

Type: string

Default: [none]

New in ver 3.2.0

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

Type: string

Default: [GUI entry]

 

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.

Type: boolean

Default: 1

New in ver 4.0.0

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.

Type:

Default:

 

New in:

string

[none]

 

3.1.0

Permits the designation of alternate names for appointment or resource reservation forms to migrate. For example:

You may enter a value ending with an asterisk (*) for simple wildcard matching. You may also specify one or more form names; the first listed name is the default. To define more than one, use a pipe character ( | ) to separate each pair:

Forms are used to classify message type. The precedence order is:
JournalEntryForms > MemoForms > AppointmentForms | NoticeForms | TaskForms | TaskNoticeForms | ReservationForms

For example, if a message matches with both MemoForms and AppointmentForms, it is classified as mail, not as an appointment.

Type:

Default:

 

New in:

boolean

1

 

3.2

When set to the default value (1), MNE scans Notes files for document links in the RTF message body and rewrites the links as HTML-style links. To disable the parameter, set the value to 0.

Setting the parameter to 0 is equivalent to setting:

Type: string

Default: [GUI entry]

 

This value corresponds to a GUI element in the Notes Migration Manager: 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.

Type: boolean

Default: 0

New in ver 4.5

Determines whether the SSDM will skip or migrate tasks that are complete in the Notes source. For example:

… tells the SSDM to skip (not migrate) Notes tasks that are marked as complete. The feature is off (SkipCompletedTasks=0) by default.

Type:

Default:

 

New in:

boolean

0

 

4.13.0.78

Determines if message internet headers are migrated. By default, message internet headers are not skipped. When internet headers are migrated, all internet header information and the header is migrated.

If SkipInternetHeaders is set to On (1), then none of the message internet headers are migrated.

Type: string

Default: [none]

New in ver 4.1

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 aborted 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 then simply exclude that message by this parameter setting:

... so the program will ignore that message the next time it runs. In the event a single program run should encounter two or more problematic messages, you can use this parameter to specify multiple message IDs separated by commas.

Type:

Default:

 

New in:

boolean

1

 

4.15

When this option is enabled, folders and views whose names are surrounded by brackets are flagged as system objects. System views and folders (with the exception of a specific set of standard system views and folders) will not be migrated. With this option enabled, a typical migration will include the following views and folders:

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.

Type: string

Default: [none]

 

Specifies the name of the Notes folder that contains Notes stationery. Example:

Usually the program can automatically determine the source location of Notes stationery, but in some cases the folder must be explicitly specified by this parameter.

Type: string

Default: [none]

 

Specifies one or more custom-designed Notes stationery forms to migrate. The parameter value consists of a form filename, which may end with an asterisk (*) for simple wildcard matching. You may specify multiple filenames by using a pipe character ( | ) to separate each pair. For example:
StationeryForms=filename1 | filename2 | filename3

Type:

Default:

 

New in:

string

[none]

 

3.1.0

Permits the designation of alternate names for task forms to migrate. For example:

You may enter a value ending with an asterisk (*) for simple wildcard matching. You may also specify one or more form names; the first listed name is the default. To define more than one, use a pipe character ( | ) to separate each pair:

Forms are used to classify message type. The precedence order is:
JournalEntryForms > MemoForms > AppointmentForms | NoticeForms | TaskForms | TaskNoticeForms | ReservationForms

For example, if a message matches with both MemoForms and AppointmentForms, it is classified as mail, not as an appointment.

Type:

Default:

 

New in:

string

[none]

 

3.1.0

Permits the designation of alternate names for task notice forms to migrate. For example:

You may enter a value ending with an asterisk (*) for simple wildcard matching. You may also specify one or more form names; the first listed name is the default. To define more than one, use a pipe character ( | ) to separate each pair:

Forms are used to classify message type. The precedence order is:
JournalEntryForms > MemoForms > AppointmentForms | NoticeForms | TaskForms | TaskNoticeForms | ReservationForms

For example, if a message matches with both MemoForms and AppointmentForms, it is classified as mail, not as an appointment.

Type: boolean

Default: 1

New in ver 4.1.4

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.

Type: boolean

Default: 1

New in ver 4.0.0

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.

Type: boolean

Default: 0

 

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.

Type:

Default:

 

New In:

boolean

1

 

4.12

Specifies the method the Data Migration Wizard will use to process a complex recurring meeting series where the series parent is difficult to identify. For example:

... tells the wizard to apply an alternate method that is better suited to such complex series. By default (1) MNE uses the previous method, which is better suited to environments migrating no (or few) such series.

Type: boolean

Default: 0

 

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.

Type: string

Default: Folders

New in ver 4.1

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 Data Migration Wizard to create a folder named MyFolders in the Outlook root directory (at the same level as the Inbox), and then 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.

Type: string

Default: [null]

 

This value corresponds to a GUI element in the Notes Migration Manager: 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.

Type:

Default:

 

New in:

string

Views

 

4.15

Specifies the name of an Outlook folder where all user-created Notes views are migrated to (as subfolders).

For example: UserViewPrefix=MyViews tells the Data Migration Wizard to create a folder named MyViews in the Outlook root directory (at the same level as the Inbox), and then copy all user-created Notes views to the new MyViews folder in Outlook. The default value is Views.

Type:

Default:

 

New in

string

-G40^n

 

4.15

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.

This parameter is considered an extremely advanced setting, and should only be modified at the direction of Quest Support.

Types: string and keyword(s)

Defaults:

WriteFailedMessageListToThisMbxFolder=[null]
WriteFailedMessageListClass=Errored

New in 4.12.1

This pair of parameters together let you configure the SSDM to generate a folder of messages and calendar items that are not migrated to the target. These items will be referenced as doclinks in a new folder in the user's Notes mailbox. The feature is enabled/disabled and configured by:

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:

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

Type: boolean

Default: 1

 

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.

Type: boolean

Default: 1

 

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

These are all "multiple-choice" parameters. For any of the parameters in this [Screens] section, the three valid values are:

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.

Type: keyword

Default: no-op

 

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.

Type: keyword

Default: show

 

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

Type: keyword

Default: show

 

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

Type: keyword

Default: show

 

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

Type: keyword

Default: 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

Type: keyword

Default: 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

Type: keyword

Default: show

 

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

Type: keyword

Default: 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

Type: keyword

Default: skip

 

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

Type: keyword

Default: skip

 

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

Type: keyword

Default: 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

Type: keyword

Default: show

 

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

[ServerData] section

Type: boolean

Default: 1

 

Determines whether the program will migrate server calendar data. For example: MigrateCalData=0 tells the program to not migrate server calendar data. By default (MigrateCalData=1), the program will migrate server calendar data.

Type: boolean

Default: 1

New in ver 3.2

Determines whether the SSDM should attempt to migrate the encrypted portions of encrypted messages in the source server mail. This feature can also be applied to encrypted messages in the source archives, by this same parameter name in the [ArchiveData] section of notesdtapp.ini. The feature is also available for the Data Migration Wizard (same parameters in the same sections, but in Migrator for Notes to Exchange's Global Defaults and Task Parameters), but in the wizard the default is 0.

The SSDM can migrate the encrypted portion of an encrypted message if it has the access credentials of the user who is authorized to decrypt the encrypted portion. This is the typical case for most organizations who use the SSDM, where individual users run the SSDM under their own login credentials, to migrate their own data. But in the rare case where the access credentials for a user's encrypted data are different from the credentials of whoever is running the program, this parameter lets you control how the SSDM should handle encrypted data. If the program attempts to migrate an encrypted message but lacks the necessary credentials, it can migrate the unencrypted portions, skip the encrypted portions, and insert text notices to explain that the encrypted portions could not be migrated.

On the other hand: MigrateEncryptedMessages=0 tells the SSDM to not even attempt migrating the encrypted portions, but to just migrate the unencrypted portions and insert the notice text. If MigrateEncryptedMessages=1, the program will attempt to migrate the encrypted portions, and will succeed or fail depending on whether the account running the SSDM has the necessary credentials. If it fails, the SSDM will migrate the message, skip the unencrypted portion and insert the notice—the same outcome as for MigrateEncryptedMessages=0.

A related Migrator for Notes to Exchange parameter lets you tell the SSDM to skip an entire message (both encrypted and unencrypted portions) if the program is already configured to skip the encrypted portion (only) by MigrateEncryptedMessages=0. See SkipEntireEncryptedMessage in this same [ServerData] section for more information.

Type: boolean

Default: [GUI entry]

 

This value corresponds to a GUI element in the SSDM: the Migrate local mail file replica checkbox of the Specify Data for Migration screen. The SSDM writes this value to notesdtapp.ini from a user's GUI entry; Quest recommends you do not manually enter or change this value except at the explicit direction of Quest Support staff.

Type: boolean

Default: 1

New in ver 4.2.1

Determines whether the program will migrate server task data. For example: MigrateTaskData=0 tells the program to not migrate server tasks. By default (MigrateTaskData=1), the program will migrate server tasks.

Type: boolean

Default: 0

 

... tells the program to migrate the server trash folder if the Specify Data for Migration screen does not appear, or sets the associated checkbox in that screen to be marked by default. A value of 0 tells the program to not migrate the server trash folder, or sets the associated checkbox to be unmarked by default. The most common use of this parameter is to provide the necessary entry value when the program is configured to hide the Specify Data screen. Chapter 4 of the Migrator for Notes to Exchange Scenarios Guide explains how this parameter relates to others used to customize the SSDM.

Type: keyword

Default: 0 (but the SSDM initializes the value to 1)

 

Determines whether and how the SSDM will migrate archive items that occur within Notes views. For example: MigrateViews=1 tells the program to migrate items only from the first view in which they are found. Valid parameter values are:

Note that the program will initialize this parameter to 1 if it is omitted from notesdtapp.ini, even though technically the program default is 0. You must explicitly include the parameter in notesdtapp.ini if you want the SSDM to run with MigrateViews=0 or MigrateViews=2.

Type: boolean

Default: 0

 

Determines whether the program will migrate out-of-office messages. For example: OOF=1 tells the program to migrate out-of-office messages. By default (OOF=0), the program will not migrate out-of-office messages

 

NOTE: Migration of out-of-office messages (OOF=1) is not supported if the migration target is set to Personal folder (.pst).

Type: boolean

Default: 0

New in ver 4.6

Determines whether the SSDM will skip entire encrypted messages (skip both encrypted and unencrypted portions) in the source server data if the SSDM is already configured to skip the encrypted portions by MigrateEncryptedMessages=0 (also in this [ServerData] section).

… tells the program to skip any encrypted messages in their entirety if MigrateEncryptedMessages=0. This SkipEntireEncryptedMessage parameter is irrelevant and ignored if MigrateEncryptedMessages=1.

For more information about how encrypted messages are migrated, and how this SkipEntireEncryptedMessage parameter helps control how the SSDM processes encrypted messages, see the parameter notes for MigrateEncryptedMessages earlier in this [ServerData] section.

相关文档