Migrator for Notes to Exchange 4.17 - Program Parameters Reference Guide

[Filter] section

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 parameter specifies the earliest items that the program will migrate (items that are timestamped on or after the designated date). When set to NONE, all mail and calendar items are migrated.

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

This value corresponds to a GUI element in the 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 parameter specifies the latest items that the program will migrate (items that are timestamped on or before the designated date). When set to NONE, all mail and calendar items are migrated.

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

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

[Filters] section

Each line specifies a folder name. The specified folder is excluded from the migration. For example:

[Filters]

Filter0=Folder1

Filter1=Folder2

Folders can be included or excluded by setting [Filters], [FolderTreeFilters], and [IncludeFoldersAndViews]. The precedence order is [Filters] > [IncludeFoldersAndViews] > [FolderTreeFilters].

[FolderTreeFilters] section

Each line specifies a folder name. The specified folder and all sub folders are excluded from the migration. For example:

[FolderTreeFilters]

Filter0=Folder1\sub1

Filter1=Folder2\sub1

Folders can be included or excluded by setting [Filters], [FolderTreeFilters], and [IncludeFoldersAndViews]. The precedence order is [Filters] > [IncludeFoldersAndViews] > [FolderTreeFilters].

[General] section

... tells the program to not copy ACL information to Exchange during the migration. By default (ACLs=1) the program will copy ACL information and will set folder permissions in Exchange. New in version 4.10: The ACLs parameter now also determines whether PAB ACLs will be migrated. Prior to this enhancement, PAB ACLs were always migrated regardless of this ACLs=<#> setting.

These are all internal scratch parameters (see Transient “scratch” parameters).

Determines whether the corresponding migration option will be visible to the user on the Specify Data for Migration screen. The default AppDoesXxxx=1 makes the option visible, while AppDoesXxxx=0 makes the option invisible (unavailable to the user) on the screen and also:

Note that these parameters do not set the marked-vs-unmarked status of the corresponding check boxes, although check box status can be controlled by the MigrateXxxxxx parameters. Chapter 4 of the Migrator for Notes to Exchange Scenarios Guide explains how this parameter relates to others used to customize the SSDM.

Specifies the destination for migrated archives. Valid values are "PST" or "server".

If ArchiveDest=server, the ArchiveDestServerArchive parameter (documented separately below) determines whether archives will be migrated to users' server-mail mailboxes or personal-archive mailboxes.

This parameter determines whether archives will be migrated to users' server-mail mailboxes (0) or personal-archive mailboxes (1). For example:

… tells the wizard to migrate the user archives to the personal archive mailboxes. Note that this ArchiveDestServerArchive parameter is relevant only if ArchiveDest=server (as documented above).

If ArchiveDest=pst, this ArchiveDestServerArchive parameter is ignored.

These are both internal scratch parameters (see Transient “scratch” parameters).

Enables/disables date filtering, to limit the items migrated by date: no earlier than, no later than, or both. By default this feature is disabled — that is, the date-filtering options will not be presented to the user. Note: To use date filters with the SSDM, you may need to register the mscal.ocx file.

Specifies the path and filename of the text file (*.txt) that contains a customized message that the program should insert in place of any attachment that the program removes due to a size limitation. The program lets you specify a size limit for attachments in migrating messages, so the program removes any attachment that exceeds the limit and replaces it with an explanatory note in the message body. The program inserts a default explanatory note unless UseFilteredAttachmentMsg=1 (see below), in which case the program inserts the customized message in the text file specified here. If UseFilteredAttachmentMsg=0, the program ignores this AttachmentFilteredbySizeMsg parameter. For example:

... tells the program to insert the text contents of c:\temp\custom_msg.txt in place of the removed attachment whenever an attachment exceeds the size limit. This feature is also an option in the Data Migration Wizard (same parameter name in the same [General] section, but in the Global Defaults and Task Parameters).

Specifies the path and filename of the text file (*.txt) that contains a customized message that the program should insert in place of an attachment to a migrated encrypted message. When an encrypted message is migrated, the attachment is removed and replaced by an explanatory note. The program will insert a default explanatory note unless UseFilteredAttachmentMsg=1 (see below), in which case the program will insert the customized message drawn from the text file specified here. If UseFilteredAttachmentMsg=0, the program will ignore this AttachmentLostDueToEncryptionMsg parameter. For example:

... tells the program to insert the contents of c:\temp\custom_msg.txt in place of the removed attachment in each migrated encrypted message. 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).

Specifies the path and filename of the text file (*.txt) that contains a customized message that the program should insert in place of the encrypted body of a migrated encrypted message. When an encrypted message is migrated, the encrypted message text is removed from the message body, but is replaced by an explanatory note. The program will insert a default message unless UseFilteredBodyMsg=1 (see below), in which case the program will insert the customized message drawn from the text file specified here. If UseFilteredBodyMsg=0, the program will ignore this BodyLostDueToEncryptionMsg parameter. For example:

... tells the program to insert the contents of c:\temp\custom_message.txt in place of the removed message body in each migrated encrypted message. 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).

When set, the program compresses log files. A compressed log file saves disk space, but is not a text file that can be viewed in Notepad or Word. This is a binary parameter; the only valid values are 0 (off) or 1 (on). For example: CompressLogFile=1 tells the program to compress the file.

Determines how contacts are displayed in Outlook. The options for this setting are:

Determines how the user’s Contacts folder will be named. For example: ContactsName=MyContacts tells the program to name the Contacts folder “MyContacts.”

Identifies the root of the source subtree the program will scan to find archive .nsf files for migration. For example: CurArchiveDir=c:\notes\data\archive tells the program to look for archive .nsf files in c:\lotus\notes\data\archive, and in all subfolders thereunder. Environment variables may be included in the path.

Identifies the root of the source subtree the program will scan to find mail .nsf files for migration. For example: CurArchiveDir=c:\lotus\notes\data\mail tells the program to look for mail .nsf files in c:\lotus\notes\data\mail, and in all subfolders thereunder.

This parameter supports the Domino feature that allows you to schedule messages to be sent on a specific date and time. After migration, Exchange or Exchange Online will not send the deferred messages.

Specifies the earliest date that deferred emails (sent items that are timestamped on or after that date) will be written to a log file (named XXX-DeferredEmails.tsv) located in the SSDM log folder. If the parameter is not set, only deferred messages that have a date after NOW are written to the log file. If you plan to shut down the Domino server on a specific day after the migration, it is recommended that you set the parameter to be on or before that day. This provides you with a list of deferred emails that were not delivered by Domino.

Specifies if the program caches and writes out 128 DEBUG log lines before a WARNING or ERROR when LogLevel is less than or equal to 2. When LogLevel equals 3, the debug log is always written out.

When set to the default value (0), the debug pool is enabled and the program caches up to 128 DEBUG log lines. The program writes out the previous 128 DEBUG log lines when it meets a WARNING or ERROR.

Set DisableDebugPool=1 if you don't want the previous DEBUG log to be written out before a WARNING or ERROR when LogLevel is less than or equal to 2.

By default, the SSDM interface and help are displayed in the language specified in the operating system settings (language and locale). You can use the DisplayLanguage parameter to specify a language.

The <LanguageCode> specified must be either the two letter code defined by ISO 639-1 or the three letter code defined by ISO 639-2. For example, the two letter code for French is fr and the three letter code is fra.

If an unsupported language is specified:

Currently, SSDM supports English and French.

Tells the SSDM to migrate encrypted Notes messages to a separate PST file in Outlook, no matter how many source.nsf files are selected for the migration, and specifies the full filename and extension for the target PST file. In any subsequent SSDM runs, the program will preserve the earlier PST files and automatically append a digit to the designated filename to differentiate it from previously migrated PSTs (filename.pst, filename_1.pst, filename_2.pst, etc.).

The default is [null], which effectively disables the feature so that encrypted messages are sent to the same PST files as all other (unencrypted) migrated items.

Note that this feature is enabled only when all migrated items are directed to PSTs by:

If any of those item types is directed to a non-PST destination, the EncryptedPstFileName parameter is ignored.

This value corresponds to a GUI element in the MNE console: the End-User statistics directory text box in the Gather End-User Statistics 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.

This value corresponds to a GUI element in the Data Migration Wizard, the Set contact ‘File as’ to drop-down listbox in the Specify Data for Migration 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.

The FileAsFormat parameter determines the format of the contact’s File As attribute in Exchange. The File As attribute is used by Outlook to alphabetize your contacts. The options for this setting are:

Identifies the source (Notes) location and filename of an address book to be migrated. The program ordinarily prompts the user for this information during a program run, but the information must be specified in advance by this parameter if the program will run in silent mode.

You may define one or more address books to be migrated. The digit(s) appended to a ForceAddrBook<#> key name differentiate one parameter from another. Multiple ForceAddrBook<#> parameters need not appear in numerical order, but must begin with 0 and must fill a numeric sequence. For example:

The number of ForceAddrBook<#> parameters must be specified by ForceAddrBooks parameter, also in this [General] section and described separately below.

Defines the number of ForceAddrBook<#> parameters (see above) that the program will process. For example:

Tells the SSDM to migrate Notes DocLinks to Exchange in a particular link format. For example:

... tells the wizard to migrate DocLinks to Exchange as HTML-style links. Valid parameter values are:

For an off-line migration, this parameter must be set to HTMLdoclinks=0.

Determines whether the program will attempt to connect to the Notes server to display the server mail file within the list of available mail files. For example:

... tells the program to not connect to the Notes server, but to offer only local mail file replicas. By default (IncludeServerMailFile=1), the program will attempt to connect to the Notes server and will display a list of any local mail file replicas and the server mail file that it finds.

Internal scratch parameter (see Transient “scratch” parameters).

Specifies which set of folder names should be used when assigning folder names to Outlook PST and personal archive folders. The wizard's Task Parameters may contain several sets of PST and personal archive folder names for different locales, differentiated by different [SECTIONNAME]s for the different locales. This parameter simply specifies the name of the locale section that contains the locale-specific PST and personal archive folder names you want the wizard to use for this purpose:

The default is null, in which case the wizard uses the section associated with the system locale (of the computer running the wizard). But if (for example) LanguageCode=DE, the wizard will use the PST and personal archive folder names defined in the [DE] section of the Task Parameters. Note that there must exist a language section in the Global Defaults to support the SECTIONNAME you specify.

Tells the program where to write its log file. The parameter can specify either a UNC shared directory or a local drive. For example:

... tells the program to write its log file to the \\server\share\ folder. By default, if the parameter is unspecified in the INI file, the program will write its log file as notesdtapp.wlog to whatever path is associated with the %temp% environment variable. If some other path is specified by this parameter, the filename will be: COMPUTERNAME-yyyymmdd-hhmmss.wlog

Specifies how much detail the program will include in its run logs. The default value 2 is suitable for most routine production runs. If you need to diagnose a problem, set the value to 3 (verbose): LogLevel=3

Specifies the number of folders to cache before flushing the cache. Exchange limits the number of objects that can be open at one time. The limit for folders is 500, so if a user has more than 500 folders, the default setting of MaxFolderCache=450 tells the SSDM to flush the cache at 450, so that all folders will migrate.

Valid values are 0 ≤ x ≤ max, where the maximum value is one less than the max folder count that is configured on your Exchange server in the registry settings. See this Microsoft article.

If this cache flush feature is turned off (by MaxFolderCache=0, so that the cache is unlimited), and a user has more than 500 folders, the folders will not be created, and the SSDM will note an error in the log.

Specifies the maximum size (in MBs) of large PSTs (Outlook 2003 or later Unicode PST files), beyond which the SSDM will split the file into two or more files. This parameter is ignored for users running Outlook 2002 or earlier. Valid values are 0 ≤ x ≤ 51200 for Outlook 2010, or 0 ≤ x ≤ 20480 for earlier Outlook versions. (Pre-2010 versions of Outlook cannot open a file larger than 20 MB.) For example: MaxLargePstSize=40960

Specifies the maximum size (in MBs) of PSTs (for Outlook 2002 and earlier PST files), beyond which the SSDM will split the file into two or more files. Valid values are 0 ≤ x ≤ 2048.

The name of the single folder to which the SSDM will merge all migrated address books, if you want to migrate them to a folder other than the default Contacts folder. For example: MergeAddressBookFolder=AllContacts. This parameter is ignored if MergeAddressBooks=0.

... tells the program to merge all migrated address books into the single Contacts folder, or into a single folder as named by the MergeAddressBookFolder parameter (see above). If using the option MergeAddressBooks=0, the program will migrate different address books to different folders, one folder per address book.

For each parameter, a setting of 1 tells the program to migrate the item type (Archives, PABs or ServerMail) if the Specify Data for Migration screen does not appear, or sets the associated check box in that screen to be marked by default. For example: MigrateArchives=1 tells the SSDM to migrate archives if the Specify Data for Migration screen does not appear, or sets the Migrate archive check box in that screen to be marked by default.

A value of 0 tells the program to not migrate the item type (Archives, PABs or ServerMail), or sets the associated check box to be unmarked by default. A MigrateXxxxx parameter is ignored if its associated AppDoesXxxx=0. The most common use of these parameters is to provide the necessary entry values when the program is configured to hide the Specify Data screen. Chapter 4 of the Migrator for Notes to Exchange Scenarios Guide explains how these parameters relate to others used to customize the SSDM.

MigrateRecentContacts=1 tells the wizard/SSDM to migrate the PABs' Recent Contacts list to the folder specified by the RecentContactsFolder parameter.

Determines whether the program will (1) or will not (0) migrate all instances of a recurring appointment or task when the first instance occurs prior to the range of a specified date filter (if any has been defined), but the last instance occurs within or after the date filter range. For example, if a date filter had been defined to migrate only mail and calendar items from October 10 through 25, and a recurring weekly appointment or task has been defined to run three weeks beginning October 1 (so appointments occur on October 1, 8 and 15), then:

… would tell the program to migrate all three instances of the series. Likewise, if the same October 10-25 date filter were defined, and a recurring weekly appointment spanned five weeks beginning October 1 (for instances on October 1, 8, 15, 22 and 29), MigrateRecurringBeforeRange=1 would tell the program to migrate all five instances.

If MigrateRecurringBeforeRange=0, none of the instances of a recurring appointment or task are migrated if the first instance of the series occurs prior to the range of a defined date filter.

When set to (1), the MNE console navigation drawer displays the option Upgrade Templates. When selected, MNE upgrades all the full templates in the database to differential templates. Differential templates pick up changes made to the Global Default settings.

After the templates have been upgraded, the parameter is set to (0). You should not configure this parameter directly, it is set by program.

The destination for migrated Personal Address Books data. Valid values are "PST" or "server". For example:

If PABDest=server, the PABDestServerArchive parameter (documented separately below) determines whether PABs will be migrated to users' server-mail mailboxes or personal-archive mailboxes.

This parameter determines whether PABs will be migrated to users' server-mail mailboxes (0) or personal-archive mailboxes (1). For example: PABDestServerArchive=1 tells the wizard to migrate users' PABs to their personal-archive mailboxes. Note that this PABDestServerArchive parameter is relevant only if PABDest=server (as documented above). If PABDest=pst, this PABDestServerArchive parameter is ignored.

This value is derived from a GUI element in the MNE console: the Post user logs to the central directory check box in the Shared Directories Configuration screen. The NMM program writes the value to this PostLogs parameter, in addition to a corresponding PostLogs parameter in its own NMM Task Parameters. Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

The parameter value here determines whether the SSDM will copy its log files from the users’ local temp directories to the centralized directory specified in the NMM. The option is on by default (PostLogs=1). The alternative, PostLogs=0, tells the Desktop Migrator to write its log files only to individual users' local temp directories, and not copy them to the centralized directory.

When set to (1), MNE prompts the user to upgrades all the full templates in the database to differential templates when the MNE console is launched. Differential templates pick up changes made to the Global Default settings.

After the templates have been upgraded or the customer selects “Don’t ask me again”, the parameter is set to (0). You should not configure this parameter directly, it is set by program.

Specifies the name of the folder to which the PAB’s Recent Contacts list will be migrated. This parameter is ignored if MigrateRecentContacts=0.

Determines whether the SSDM Finished screen will display the app's statistics, and the View Errors button. For example: ReportErrors=0 tells the SSDM to not report its counts of errors, warnings, filters and skips on the Finished screen, and to not offer the View Errors button.

Determines whether the SSDM will display the total number of items to be processed in the item count on its Progress screen. For example: reportMofN=0 tells the program to display "Processed M item(s)" instead of the default (1) "Processed M of N item(s)."

Determines whether the SSDM will display item-count estimates in the title and progress bar on its Progress screen. For example: reportPct=0 tells the program to not update the title, and to suppress the percent value in the progress bar.

These parameters correspond to a GUI element in the SSDM: the Select address books... check box(es) in the Select Notes Address Books to Migrate screen. Each SelectedAddrBook<#> parameter specifies the path and filename of an address book to be migrated. The program writes these values to the notesdtapp.ini file from an admin's GUI selection(s); Quest recommends you do not enter or change these parameter values except at the explicit direction of Quest Support staff.

The digit(s) appended to a SelectedAddrBook<#> key name differentiate one parameter from another. Multiple SelectedAddrBook<#> parameters need not appear in numerical order, and need not form an uninterrupted numeric sequence. But the program will read only SelectedAddrBook<#> parameters whose differentiating digits are less than a value specified by a TotalSelAddrBooks parameter in the same [General] section. See the TotalSelAddrBooks parameter below for more information. For example:

Each SelectedArchive<#> parameter specifies the path and filename of an archive to be migrated. These parameters are ignored if the SSDM displays its Select Notes Archive Files to Migrate screen, in which case the user's GUI entries determine the program behavior. (That screen will not appear if SelectArchive=silent. If SelectArchive=skip, the SSDM will display the screen only if no SelectedArchive<#> parameter is specified in the Task Parameters.)

The digit(s) appended to a SelectedArchive<#> key name differentiate one parameter from another. Multiple SelectedArchive<#> parameters need not appear in numerical order, and need not form an uninterrupted numeric sequence. But the program will read only SelectedArchive<#> parameters whose differentiating digits are less than a value specified by a TotalSelArchives parameter in the first line of the same section. See the TotalSelArchives parameter below for more information. For example:

If MNE finds more than one mailbox in the selected Outlook profile, MNE displays a Select Mailbox screen to prompt the user to designate the target mailbox. The SSDM can be configured to skip the Select Mailbox screen, but in that case (and if more than one mailbox is associated with the selected Outlook profile) the program must be able to determine the correct mailbox to use. Use this parameter to specify the user’s target mailbox. For example:

Specifying the target mailbox in the INI file will be useful only if:

The SSDM does not need this MailboxName value if one and only one mailbox will be found in the user’s Outlook profile.

This value corresponds to a GUI element in the SSDM: the Select mail file... check box(es) in the Select Notes Local Mail File Replica to Migrate screen. The program writes this value to the notesdtapp.ini file from an admin's GUI entry; Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

The parameter value consists of a filename designated in the GUI by its marked check box. For example: SelectedMailFile=filename.nsf

If more than one check box is marked in the screen, only the last filename marked in the list will appear as the value of this parameter. The file resides in the path designated in the Specify directory... text box on the same screen.

Specifies the Outlook profile to which the program will migrate data. For example: SelectedProfile=Joel Brennen

The program will need this SelectedProfile parameter only if more than one eligible profile will be found on any user’s workstation. Chapter 4 of the Migrator for Notes to Exchange Scenarios Guide explains how this parameter relates to others used to customize the SSDM.

Specifies the destination folder (path) for the user’s migrated archive. The <path> is specified as a full UNC or mapped-drive path (without filename) relative to the user’s computer. For example:

Environment variables may be included in the path.

The default is the Outlook Default Directory, which the program can determine from its operating environment. This parameter is therefore necessary only if you want users’ migrated archives to go somewhere other than the Default Directory. Chapter 4 of the Migrator for Notes to Exchange Scenarios Guide explains how this parameter relates to others used to customize the SSDM.

This value is derived from a GUI element in the MNE console: the Post user logs to the central directory check box in the Shared Directories Configuration screen. The NMM program writes the value to this SendStatus parameter, in addition to the PostLogs parameter in its own NMM Task Parameters, and another PostLogs parameter in this same [General] section of notesdtapp.ini. Quest recommends you do not manually enter or change this value except at the direction of Quest Support.

The parameter value tells the Desktop Migrator whether to write a statistics file (a separate stats file per program run) in the centralized directory specified for log files in the NMM. The option is on by default (SendStatus=1), but SendStatus=0 tells the program to not write any stats files.

Sets the destination for migrated server mail. Valid values are "PST" or "server". For example:

If ServerMailDest=server, the ServerMailDestServerArchive parameter (documented separately below) determines whether server mail will be migrated to users' server-mail mailboxes or personal-archive mailboxes.

This parameter determines whether server mail will be migrated to the users' server-mail mailboxes (0) or personal-archive mailboxes (1). For example: ServerMailDestServerArchive=1 tells the wizard to migrate users' server mail to their personal-archive mailboxes.

Note that this ServerMailDestServerArchive parameter is relevant only if ServerMailDest=server (as documented above). If ServerMailDest=pst, this ServerMailDestServerArchive parameter is ignored.

Internal scratch parameter (see Transient “scratch” parameters).

Specifies the name of the SharePoint server where the Proposion-linked documents reside, if HTMLdoclinks=2 (in this same [General] section). For example: SharePointServerName=Banff

Determines whether the SSDM will show or hide the Error Log Report button on the last SSDM end-user screen. The button is enabled (1) by default. Disabling the button may be useful in some environments where accessing a large log file might cause a user desktop to hang.

Determines whether the SSDM will (0) or will not (1) migrate an exception to a recurring appointment or task when the original or rescheduled start time falls outside the range of a defined date filter (if any). This parameter does not control whether such an instance would be migrated at all, but only whether the instance would be migrated as originally scheduled, or as it was changed. If, for example:

… and one instance of a recurring series was originally scheduled for October 1 but had been changed to October 2, and if that instance occurs outside a defined date filter range, the SSDM skips the exception—i.e., will migrate the instance at its original October 1 time rather than as changed, to October 2. If SkipOutOfRangeExceptions=0 (default), the SSDM would migrate the instance as changed, for October 2.

Specifies the path and filename of the SMTP Translation Table: a data file generated by the Directory Export Wizard and used by other Quest applications and wizards to convert addresses in messages, address books, and contacts to the appropriate Internet (SMTP) address for each user. The Directory Export Wizard writes this value to the Task Parameters automatically; Quest recommends you do not enter or change this value except at the explicit direction of Quest Support.

Internal scratch parameter (see Transient “scratch” parameters).

A limit to the number of SelectedAddrBook<#> parameters (see above) that the SSDM will process in this section. The program will read only SelectedAddrBook<#> parameters whose differentiating digits are less than the parameter value specified here. For example, if:

... the program will migrate all the address books except SelectedAddrBook4 and SelectedAddrBook5, since TotalSelAddrBooks=4, and neither 4 nor 5 is less than 4. If unspecified, the TotalSelAddrBooks parameter defaults to 0. If specified, the parameter must occur as the first line of the section, as shown above.

A limit to the number of SelectedArchive<#> parameters (see above) that the program will process in this section. The program will read only SelectedArchive<#> parameters whose differentiating digits are less than the TotalSelArchives value specified here. For example, if:

... the program will read all the parameters except SelectedArchive3 and SelectedArchive4, since TotalSelArchives=3, and neither 3 nor 4 is less than 3.

If unspecified, the TotalSelArchives parameter defaults to 0. If specified, the parameter must occur as the first line of the section, as shown above.

The number of mail files to be migrated. This value is derived from an administrator’s selection for the Select mail file... check box(es) in the Select Notes Local Mail File Replica to Migrate screen. Since the program does not permit the migration of more than one mail file per program run, this parameter is always set to:

Internal scratch parameter (see Transient “scratch” parameters).

Determines whether the program will insert a default message (0) or a customized message (1) to replace an attachment that the program removes from a migrating message because it is encrypted or because the attachment exceeds a size limit. The program removes such an attachment from a message, and replaces it with an explanatory note. The explanatory note can be either a default explanation, or some customized message from a text file specified by a separate parameter (either AttachmentLostDueToEncryptionMsg or AttachmentFilteredbySizeMsg, as described above).

For example: UseFilteredAttachmentMsg=1 tells the program to insert the customized message. This feature is also an option in the Data Migration Wizard (same parameter name in same section, but in the Global Defaults and Task Parameters).

Determines whether the program will insert a default message or a customized message to replace the encrypted body of a migrated encrypted message. The program removes the message body from every encrypted message it migrates, and replaces it with an explanatory note. The explanatory note can be either the default ("An encrypted bodypart was discarded"), or some customized message from a text file specified by the separate BodyLostDueToEncryptionMsg parameter (see above).

For example: UseFilteredBodyMsg=1 tells the program to insert the customized message. This feature is also an option in the Data Migration Wizard (same parameter name in same section, but in Global Defaults and Task Parameters).

... forces the program to not use large PSTs, whereas by default (1) the program will use large PSTs if possible. Note: A setting of 1 will not force Unicode PSTs if Outlook 2003 or later is not installed. The program cannot create PSTs without the proper MAPI components (from Outlook 2003 or later) in place.

Internal scratch parameter (see Transient “scratch” parameters).

Determines whether the SSDM will migrate all data into a single pst file per user (0), or to multiple psts (1, the default).