[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:
|
• |
masks the portions of the Welcome and Migration Report screens that pertain to the hidden option; and |
|
• |
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=pst, this ArchiveDestServerArchive parameter is ignored.
These are both internal scratch parameters (see Transient “scratch” parameters).
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).
Tells the program whether to compress its log file. A compressed log file saves disk space, and is viewable by Quest's Log Viewer utility, but is not a generic 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:
|
• |
1 (Default) – Use the Notes contact’s display name – Create the display name using the format specified by the contact’s View display name format setting in Notes. |
|
• |
2 – Create the display name as FirstName LastName. The middle name and name suffix are included, if present. |
|
• |
3 – Create the display name as LastName, FirstName. The middle name is included, if present. |
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.
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.).
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 Notes Migration Manager: 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:
|
• |
Same: Use the Display Name attribute of the address book entry. By default Migrator for Notes to Exchange migrates contacts using display names that match the display name of the contact in Notes, however the contact’s display format can be modified using the [General] ContactDisplayNameFormat parameter. |
|
• |
FirstLast: Create the File As using the first name and last name attributes separated by a space. The middle name and name suffix are included, if present. |
|
• |
LastFirst: Create the File As using the last name and first name attributes separated by a comma. The middle name is included, if present. |
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:
For an off-line migration, this parameter must be set to HTMLdoclinks=0.
... 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).
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 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 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
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.
… 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.
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 Notes Migration Manager: 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.
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.
|
Default: [Outlook default directory] |
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 Notes Migration Manager: 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.
… 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.
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).
Internal scratch parameter (see Transient “scratch” parameters).
[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 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.
… 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 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.
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.