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]. |
... tells the wizard to not manipulate ACLs in any way during the migration. By default (ACLs=1) the wizard 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.
Tells the Data Migration Wizard whether to migrate Notes server-based AutoForwarding rules to comparable forwarding rules in Exchange, when the rules contain Notes-style addresses instead of SMTP addresses. For example: AllowForwardtoNotesConnector=0 tells the wizard to not migrate rules with Notes-style addresses. This parameter is ignored if MigForwarding=0 (see below).
Specifies the destination for migrated archives. Valid values are "PST" or "server."
If ArchiveDest=server, then the ArchiveDestServerArchive parameter (documented separately below) determines whether archives will be migrated to users' server-mail mailboxes or personal-archive mailboxes.
… tells the wizard to migrate users' archives to their 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.
Determines whether the Select Destinations for Migrated Data screen, in the Data Migration Wizard, will display (1) or hide (0) the Archives drop-down list box. By default (1), the item does appear in the screen, but AskArchiveDest=0 tells the wizard to not show the Archives field in the screen.
Determines whether the Select Destinations for Migrated Data screen, in the Data Migration Wizard, will display (1) or hide (0) the Address books drop-down list box. By default (1), the item does appear in the screen, but:
... tells the wizard to not show the Address books field in the screen.
Determines whether the Select Destinations for Migrated Data screen, in the Data Migration Wizard, will display (1) or hide (0) the Server-based data drop-down list box. By default (1), the item does appear in the screen, but:
... tells the wizard to not show the Server-based data field in the screen.
Occurs in: Data Migr. This is an internal scratch parameter (see Transient “scratch” parameters). The Wizard notes whether a compiled AddressTranslation.bin file has ever been generated (1=yes, 0=no), and writes the value to this parameter.
Specifies the path and filename of the text file (*.txt) that contains a customized message that the Data Migration Wizard should insert in place of any attachment that the wizard removes due to a size limitation. The Wizard lets you specify a size limit for attachments in migrating messages, so the wizard will remove any attachment that exceeds the limit and replace it wih an explanatory note in the message body. The Wizard will insert a default explanatory note unless UseFilteredAttachmentMsg=1 (see below), in which case the wizard will insert the customized message drawn from the text file specified here. If UseFilteredAttachmentMsg=0, the wizard will ignore this AttachmentFilteredbySizeMsg parameter. For example:
... tells the wizard to insert the 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 SSDM (same parameter, but in notesdtapp.ini).
Specifies the path and filename of the text file (*.txt) that contains a customized message that the Data Migration Wizard 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 Wizard will insert a default explanatory note unless UseFilteredAttachmentMsg=1 (see below), in which case the wizard will insert the customized message drawn from the text file specified here. If UseFilteredAttachmentMsg=0, the wizard will ignore this AttachmentLostDueToEncryptionMsg parameter. For example:
... tells the wizard 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 SSDM (same parameter, but in notesdtapp.ini).
Specifies the path and filename of the text file (*.txt) that contains a customized message that the Data Migration Wizard 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 Wizard will insert a default message unless UseFilteredBodyMsg=1 (see below), in which case the wizard will insert the customized message drawn from the text file specified here. If UseFilteredBodyMsg=0, the wizard will ignore this BodyLostDueToEncryptionMsg parameter. For example:
... tells the wizard to insert the contents of c:\temp\custom_msg.txt in place of the removed message body in each migrated encrypted message. This feature is also an option in the SSDM (same parameter, but in notesdtapp.ini).
This value corresponds to a GUI element in the Notes Migration Manager: the Directory for central log and status files text box (under End-user tool settings) in the Shared Directories Configuration screen. The program 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.
This value corresponds to a GUI element in the Notes Migration Manager: the Log level radio buttons for End-user tool settings in the Shared Directories Configuration screen. The value specifies how much detail the program will include in its run logs. Valid values are single digits, 0 ≤ x ≤ 3. The default value 1 is suitable for most routine production runs. If you need to diagnose a problem, set the value to 3 (verbose). The GUI offfers two radio-button options that correspond to these numeric parameter values:
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 users’ primary Contacts folders are named. For example:
... tells the wizard to name each user’s primary Contacts folder “MyContacts.”
This value corresponds to a GUI element in the Data Migration Wizard: the Manage mail routing checkbox in the Operations 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.
This value corresponds to a GUI element in the Data Migration Wizard: the Notes administrative functions checkbox in the Operations 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.
Occurs in: Data Migr. This is an internal scratch parameter (see Transient “scratch” parameters).
This value corresponds to a GUI element in the Notes Migration Manager: the Common application directory text box (under Common tool settings) in the Shared Directories Configuration screen. The program 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.
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 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.
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. |
Note that this ForwardingMethod parameter replaces the previous UseHiddenADContact boolean parameter, which is deprecated as of version 4.5.
For an off-line migration, this parameter must be set to HTMLdoclinks=0.
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, the program writes 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. Valid values are single digits, 0 ≤ x ≤ 3. 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
Determines whether the Data Migration Wizard's log entries and stats counts for unmigrated items will (1) or will not (0) include appointment responses that were skipped by configuration—by setting [Notes] MigrateAppointmentResponses=0. (See the entry for MigrateAppointmentResponses=<#>, in the [Notes] section below, for more information about this other option.)
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 will tell the Data Migration Wizard to flush the cache at 450, so 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 defined by these Microsoft articles:
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 wizard will note an error in the log.
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. (Note that pre-2010 versions of Outlook cannot open a file larger than 20 MB.)
This parameter is ignored if MergeAddressBooks=0.
MergeAddressBooks=1 tells the wizard to merge all migrated address books into the single Contacts folder, or into a single folder as named by the MergeAddressBookFolder parameter (see above). When MergeAddressBooks=0, the program will migrate different address books to different folders, one folder per address book.
... disables the migration of server-based forwarding rules. By default (MigForwarding=1) the wizard will migrate Notes forwarding rules. If the Notes forwarding address is a Notes-style address, the address will be added in Exchange as a Notes address only if AllowForwardtoNotesConnector=1.
This value corresponds to a GUI element in the Data Migration Wizard: the Migrate users checkbox in the Operations 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.
This value corresponds to a GUI element in the Data Migration Wizard: the Migrate archives checkbox 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.
This value corresponds to a GUI element in the Data Migration Wizard: the Migrate personal address books checkbox 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.
MigrateRecentContacts=1 tells the wizard/SSDM to migrate the PABs' Recent Contacts list to the folder specified by the RecentContactsFolder parameter.
… would tell the wizard 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), then MigrateRecurringBeforeRange=1 would 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.
This value corresponds to a GUI element in the Data Migration Wizard: the Migrate mail data checkbox 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.
For example: MsgRequireAnyFeature=2 tells the wizard to migrate only messages with inline MIME attachments.
If PABDest=server, then the PABDestServerArchive parameter (documented separately below) determines whether PABs will be migrated to users' server-mail mailboxes or personal-archive mailboxes.
For an Exchange 2010 or Office 365 target (only), and when migrating to users' Exchange server (only), 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 corresponds to a GUI element in the Notes Migration Manager: the Post user logs to the central directory checkbox in the Shared Directories Configuration screen. The program writes the value from an admin's GUI entry to the NMM Task Parameters, and also (the same value) to a corresponding PostLogs parameter and a SendStatus parameter in the [General] section of the notesdtapp.ini file (for the SSDM). (For more information, see the PostLogs and SendStatus parameters in the notesdtapp.ini pages of this Reference.) Quest recommends you do not manually enter or change this value except at the direction of Quest Support.
These several parameters together configure Migrator for Notes to Exchange proxy settings, to better facilitate connections to Office 365 and other hosted platforms when using a proxy server to connect to the Internet. These parameters pertain only to PowerShell operations, and also require that MAPI proxy access be configured through Windows’ Internet Options dialog box. This Quest KnowledgeBase article explains how to configure a proxy server in Windows that will allow Migrator for Notes to Exchange to connect to Office 365.
ProxyAccessType can be set to any of these values:
• |
ProxyAuthMechanismType can be set to any of these values:
ProxyUserName must also be specified for some types of authentication.
~ProxyPassword must also be specified for some types of authentication.
Occurs in: Data Migr. This is an internal scratch parameter (see Transient “scratch” parameters).
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 Migrator for Notes to Exchange's scheduling application (Qsched.exe) will reset recurring work items back to a "ready" state upon launch. Before this parameter was introduced, the reset was automatically applied and sometimes caused users to migrate multiple times. The default (ResetMigAppWorkItems=0) does not reset work items to a "ready" state for recurring tasks. To enable the feature (the behavior in earlier releases), set ResetMigAppWorkItems=1. Quest recommends this feature always be disabled (0) if you are attempting a balanced migration across multiple machines.
Deprecated in: | ||||
Determines whether Migrator for Notes to Exchange's scheduling application (QSched.exe) will run as a service, which in turn loads the MAPI subsystem in a "running as service" context, so MAPI will not try to display a log-in prompt to the user. For example, RunAsService=1 tells QSched to run as a service. By default (0), QSched will not run as a service—as in prior Migrator for Notes to Exchange releases.
Due to changes in the scheduling service, this parameter is deprecated in version 4.9.0 and higher.
Sets the destination for migrated server mail. Valid values are "PST" or "server." For example:
If ServerMailDest=server, then the ServerMailDestServerArchive parameter (documented separately below) determines whether server mail will be migrated to users' server-mail mailboxes or personal-archive mailboxes.
For Exchange 2010 (only), and when migrating to users' Exchange server (only), 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.
Specifies the name of the SharePoint server where the Proposion-linked documents reside, if HTMLdoclinks=2 (in this same [General] section). For example:
Determines whether the Data Migration Wizard will (1) or will not (0) display an optional set of fields, on its Select Notes Administrative Operations screen, that let the admin set the domain values for the source mail domain, calendar domain, and mail system. For example:
... tells the wizard to display the fields. When ShowSetMailDomain=1, these other parameters (in the [Notes] section of these parameter settings) may be used to set the default values for the corresponding fields:
… 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, then the wizard will skip 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), then the wizard would migrate the instance as changed, for October 2.
This value, automatically generated from values in the SQL Server Configuration screen of Notes Migration Manager, is used by the Data Migration Wizard to access necessary licensing information during the migration process. Quest recommends you do not manually enter or change this value except at the direction of Quest Support.
This value, representing the number of simultaneous processes the program will use to perform migrations, corresponds to a GUI element in the Data Migration Wizard: the Number of migration threads field in the Specify Migration Run Information 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 the value except at the direction of Quest Support.
Determines whether the Data Migration Wizard will insert a default message (0) or a customized message (1) to replace an attachment that the wizard has removed from a migrating message because it is encrypted or because the attachment exceeds a size limit. The Wizard removes such an attachment from a migrating 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 wizard to insert the customized message. This feature is also an option in the SSDM (same parameter, but in notesdtapp.ini).
Determines whether the Data Migration Wizard will insert a default message or a customized message to replace the encrypted body of a migrated encrypted message. The Wizard 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:
... tells the wizard to insert the customized message. This feature is also an option in the SSDM (same parameter, but in notesdtapp.ini).
Occurs in: Data Migr. This is an internal scratch parameter (see Transient “scratch” parameters).
Migration to hosted platforms often generates more process timeouts than migration to a local server, particularly when migrating quantities of large messages (usually due to large attachments). We therefore recommend the default watchdogminutes=180 for connections to Office 365, to make the migration program "forgiving." A substantially lower setting of, say, watchdogminutes=30 might be better suited to migration to a local server, where shorter and higher-quality transmission paths make timeouts less common.
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]. |
This section contains a list of URLs for each of the Office 365 clouds that are supported by MNE. These values are used by the Migration Console’s Exchange Server page to set the [Exchange] O365AuthenticationUrl setting in the SSDM’s NotesDTApp.ini file.
The values in this section should only be modified at the direction of Quest support.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center