Quest® Notes Migrator for Exchange

Version 4.2.0.94

Release Notes

January 2010

(Doc ID 015)

Welcome to Notes Migrator for Exchange

New in this Release

Resolved Issues

Known Issues

Upgrade and Compatibility

Other Recent Releases

Welcome to Notes Migrator for Exchange

Quest Software's Notes Migrator for Exchange is a set of software applications designed to facilitate a variety of migration strategies for organizations moving from a Lotus Domino server, with Lotus Notes clients, to an Exchange 2003, 2007 or 2010 environment with Outlook clients. Notes Migrator for Exchange can:

Extract user data from the Domino server to mailbox-enable user accounts in the Active Directory.
Migrate mail, appointments, tasks, personal address books, personal distribution lists, and archives from the Notes environment to the Exchange environment and Outlook Personal Folders (.pst) files.
Set and remove mail-forwarding rules between Notes and Exchange to assure correct mail routing throughout the transition period.

All the features of Notes Migrator for Exchange are contained within six primary components:

Notes Migration Manager: A central "console" application that coordinates most administrator-driven tasks and features. The Notes Migration Manager in turn contains an assortment of specialized subcomponent applications, called Wizards (listed separately below), that facilitate particular program features. In addition to its Wizards, the Notes Migration Manager helps you monitor and manage most of the information pertaining to a migration project: program defaults and server access credentials, the locations of Notes/Domino source data, exported data from the Domino directory, and ongoing migration statistics that track the status of a migration project.
Self-Service Desktop Migrator with Throttling: A separate application that end users can run (one user at a time) to migrate their own mail, PABs and archives. (An administrator may also run this Desktop Migrator on behalf of an end user, running under the user's credentials.) Administrators can now regulate end users' desktop migrations and avoid bottlenecks by scheduling various user collections to migrate during different migration windows, by date and time, and limiting the amount of users who can migrate at one time.
SSDM Throttling Utility: A utility that lets an administrator regulate end users' execution of the Self-Service Desktop Migrator (SSDM), to avoid processing bottlenecks that might otherwise occur if too many users tried to use the SSDM simultaneously.
Notes Migration Scheduling Application: A separate command-line application that executes scheduled tasks. The program checks the SQL Server database to see whether any tasks have been scheduled to run since the last check, and then executes any such tasks.
Migration Database Utility: A utility that prepares a set of data tables that in turn let the Data Migration Wizard read Notes mail files from two or more source servers in a single program run. Without this utility, the Wizard can read mail files from multiple paths, but only from a single Notes server.
Log File Viewer: Simplifies the viewing and interpretation of Quest program log files, which are generated by most Quest applications to document process errors and warnings.

The Wizards that can be launched from Notes Migration Manager:

NABs Discovery Wizard: Searches the Notes/Domino server to locate all Notes NABs (Name and Address Books). The Directory Export Wizard and Internet Domains Discovery Wizard will then extract critical directory information from the NABs, which in turn will be read by Quest provisioning, object-merging, and migration Wizards so they can perform their tasks.
Internet Domains Discovery Wizard: Extracts all Internet domains it can find within the Notes' NABs (Name and Address Books) found by the NABs Discovery Wizard. These domains will then be used to generate address aliases for all users, so that Exchange can recognize and correctly route mail sent to users' old addresses.
Directory Export Wizard: Gathers user information from the Domino server(s) to create SQL Server data tables that will provide critical input data to the Quest provisioning, object-merging, and migration Wizards.
Collection Wizard: Lets you define the member contents of user and group collections. The provisioning, migration, and other features are applied to collections of users and groups, and the Collection Wizard is what defines these collections. You can add members to a collection by selecting objects from the SQL Server database, or by importing the contents of a .tsv (tab-separated-values format) file, or both.
AD Groups Provisioning Wizard: Defines a task that will provision distribution groups (create group objects) within Active Directory from a designated group collection, and schedules the task to run at a particular time, or at a series of recurring times.
Notes Data Locator Wizard: Defines a task that will locate data files in the Notes source for a particular user collection, or gather statistics from previously located data stores, and schedule the task to run at a particular time or at a series of recurring times.
AD Object Merging Wizard: Consolidates duplicate objects in Active Directory by merging information from Exchange Contacts (generated by Microsoft's Exchange Connector for Notes) into corresponding users' AD accounts, and then deleting the Contacts, to create a single mail-enabled security object per user in AD.
Send PAB Replicator Wizard: Sends a special email form to users within a particular user collection, that lets them replicate all of their PABs (personal address books) to a centralized Notes server directory, where the Data Migration Wizard will be able to find them and migrate them.
Data Migration Wizard: Defines a task that can, for all users within a particular user collection:
• Mailbox-enable Exchange accounts.
• Migrate user data.
• Update mail-forwarding rules.
• Perform other related Notes and Exchange administrative functions.
Self-Service Desktop Migration Statistics Collection Wizard: Gathers migration statistics written by the Self-Service Desktop Migrator, and loads the data into the SQL Server database, to help you track the progress of the migration project.

New in this Release

This release contains the following new and enhanced features:

This release introduces no new features or feature enhancements.

For new and enhanced features in other recent releases, see Other Recent Releases

Resolved Issues

Issues addressed in this release:

CR #78672	The remote PowerShell session now connects to the Exchange server rather than the Global Catalog host when migrating to Exchange 2010.
CR #78704	When migrating to Exchange 2010, if a targetAddress value of a contact contains a space or underscore during object merge, the existing targetAddress value is now preserved on the resultant user object.

For resolved issues in other recent releases, see Other Recent Releases

Known Issues

The following issues are known to exist at the time of this release.

General

CR #49488	The Directory Export Wizard generates a duplicate record for a user if the user's mail file path has been changed by Quest's Migration Database Utility.
CR #57447	When migrating only iNotes contacts, the Notes Mail Files screen does not appear, so you cannot choose to migrate via the server or the file system. The program will run via file system if that's what you chose for your last migration, unless you go into the Task Parameters or INI file and change it.
CR #57381	Exchange does not let other applications (including Notes Migrator for Exchange) set the "owner" property of items migrated to resource mailboxes.
CR #59936	Microsoft PowerShell may mistakenly report program errors if it is running on a system with Exchange 2003 management tools but no Exchange 2007 management tools.
CR #75465	If migrating to Exchange 2010: The number of remote PowerShell sessions is 18 by default, so when mailbox-enabling user accounts, the number of concurrent processes should not exceed 10 (since sessions are not immediately completely closed when NME disengages them). However, the max number of PowerShell sessions may be configured to a larger value thus eliminating this problem.
CR #75388	If migrating to Exchange 2010: When merging contacts or mailbox-enabling in a migration to an Exchange 2010 environment configured for one forest and multiple domains, the Global Catalog and Domain Controller settings (on the Active Directory Configuration screen of the Notes Migration Manager) must be set to a server in the domain that contains the Active Directory user objects to be merged or mailbox-enabled.

Directory Export Wizard

CR #56474

When using the Microsoft Transporter for coexistence and setting mail forwarding from Notes to Exchange, any subsequent run of the Directory Export Wizard will generate these errors (one per user):

ERROR: [2448-147-22-00000000] Unable to import SMTP Address '[address]'

The error occurs because the mail forwarding requires a modified address format, with two @ symbols, in the Notes person document. The Data Migration Wizard sets that address when setting mail forwarding, so the Directory Export Wizard then correctly flags it as an invalid SMTP address. Such errors may safely be ignored, since they are irrelevant after mail forwarding has been set. But some of these errors may occasionally report invalid addresses that are invalid for some other reason, and in these cases the addresses should be corrected.

Off-Line Migration

CR #30886

When migrating off-line, the HTMLdoclinks program parameter, in the [General] section of the Data Migration Wizard's task parameters, must be set to 0 (zero). The HTMLdoclinks=0 setting tells the Wizard to migrate Notes doclinks as Notes-style doclinks, which can be opened in Exchange only if a Notes client is installed on the client workstation. By default (HTMLdoclinks=1), Notes doclinks would migrate to Exchange as HTML-style links, which can be opened in a web browser if the user is able to use iNotes, but that default setting will cause errors in an off-line migration.

Outlook

CR #58004

Outlook archiving is not applied to migrated messages within the age range set for auto-archiving, because Outlook determines message age by Last Modified time, which it updates to the migration date/time upon migration. Since all migrated messages become zero days old as soon as they are migrated, and Outlook won't let the Data Migration Wizard reset that property to its true pre-migration date/time, the Outlook archiving feature skips the messages until they have "re-aged" to the archive age (typically 30 days) following migration, at which time all of the migrated messages will be archived.

DocLinks

CR #51131

In Outlook XP and Outlook 2003, migrated DocLinks cannot be opened from the preview pane, but can be opened only from the opened messages that contain them. (In Outlook 2007, however, DocLinks can be opened from the preview pane.)

Other Known Issues

Most of the known limitations of any migration process are due to feature inconsistencies between the source and target environments. That is, features that are available in the Notes environment simply cannot be migrated to a target environment that does not offer the same or comparable features. Other limitations are due to feature incompatibilities, where similar features are available in both the source and target environments, but their implementations are so different that the migration may be impractical. In any case, most administrators regard these sorts of limitations as trivial or incidental to an overall migration project.

Appendix A of the Notes Migrator for Exchange User Guide provides a complete list of all such known limitations of the migration process as facilitated by the current version of Quest's Notes Migrator for Exchange.

Upgrade and Compatibility

There is no need to uninstall the previous version before installing the new version. The upgrade installation and setup will be fully automated, and will preserve any data already migrated by an earlier version, so that you may simply resume the migration process from wherever you left off with the previous version.

System Requirements

Notes Migrator for Exchange requires the installation and configuration of multiple components on various machines: the source Domino server, the destination Exchange server, the admin's migration workstation (sometimes two or more admin workstations), and end-user client desktops. The migration workstation in particular will host an unusual combination of tools, developed by different vendors, and the combination can cause compatability problems on some machines. Be sure to see the more detailed System Requirements in the NME User Guide or Quick-Start Guide for tips to get multiple applications from different vendors to cooperate when installed on a single admin workstation.

This list specifies the basic minimum hardware and software requirements for this release of Notes Migrator for Exchange:

On the Domino server:	Must be running Lotus Domino version 4.6.x, 5.x, 6.x, 7.x, 8.0.0, 8.0.1 or 8.0.2.
On the Exchange server:	Must be running Exchange 2010, 2007 (SP0, SP1 or SP2), or Exchange 2003.
On each administrator workstation (running the Notes Migrator for Exchange admin components):	Workstation OS must be: *For migration to Exchange 2003:* a 32-bit version of Windows 2000, Windows XP SP2 or higher, or Windows Server 2003 or 2003 R2. *For migration to Exchange 2007 or 2010:* a 32-bit version of Windows XP SP3, Windows Server 2003 or 2003 R2, Windows 7, Windows Vista, or Windows Server 2008. *Notes Migrator for Exchange does not support a 64-bit OS.* Workstation must be a separate machine from the Exchange server, but a member of the same domain as AD and Exchange, and must meet these minimum hardware requirements: 1+ GHz processor. 1GB memory. 20GB free disk space. Recommendations for improved performance, especially for high-volume migrations: 3+ GHz processor. 2GB memory. 1 Gbps NIC. 1 Gbps or faster network connections among all migration workstations and the Exchange and Domino servers. *Required for migration to Exchange 2010 (only):* Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0), available (at this writing) at this Microsoft link. *Required for migration to Exchange 2007 (only):* Exchange 2007 or E2007 SP1 Management Tools (32-bit version), which in turn requires: .Net Framework 2.0, Microsoft Management Console (MMC), and Windows PowerShell. The 32-bit version of Exchange 2007 Management Tools is available (at this writing) at this Microsoft link, and see also Microsoft's installation instructions. *Required for any Exchange 2003 administrative functions (only):* Windows Admin Tools (adminpak.msi). Exchange System Manager (version to match the installed version of Exchange). *Required for ALL destination Exchange versions:* Lotus Notes must be installed in single-user mode and configured. The Notes client version must be in the range 5.0.11 to 7.0.1 (inclusive), or 8.0.0, 8.0.1 or 8.0.2, and must be able to open all the NSF files that you want to migrate. The client version should therefore match or be higher than the Domino server version. Outlook 2002, 2003, or 2007 (2003 or 2007 recommended) must be installed. Outlook 2003 or 2007 is required to migrate multi-byte items or items from multiple character sets, or to migrate to pst files larger than 2 GB. The MAPI DLLs required to perform a migration must be those that are part of Outlook, not the downloadable Exchange 2007 "server" MAPI. Any antivirus software must be turned off prior to running the Quest admin applications, but may be restored after the program runs.
On the server hosting the SSDM Scheduling Utility web service:	ASP.net version 2.0 must be installed.
SQL Server:	Access to a Microsoft SQL Server is required. Microsoft SQL Server 2005 Express is optionally included with Notes Migrator for Exchange (included with one of the two setup kits available for download). Alternatively, the program can use an existing (installed) Microsoft SQL Server version 2000 or 2005.
On user desktops (if running the SSDM):	Must be running Microsoft Windows 2000; or Windows XP SP2 Professional Edition; or Windows 2003; or Windows Vista Business, Enterprise or Ultimate Editions. Must be running Outlook 2000 SP3, or Outlook 2002, 2003, or 2007. The MAPI DLLs required to perform a migration must be those that are part of Outlook, not the downloadable Exchange 2007 "server" MAPI. Must be running a Lotus Notes client: UNICODE support requires version 5.0.11, or 6.x, 7.0.0, 7.0.1, 7.0.2, 8.0.0, 8.0.1, or 8.0.2. For version 4.6 clients you must contact Quest Technical Support for an alternate application that supports version 4.6. Any antivirus software must be turned off prior to running the desktop migrator, but may be restored after the program run.
All machines:	Must have network access.
Required Accounts & Permissions:	Important: In addition to the environmental requirements specified here, NME features require the configuration of admin accounts for access to directory and user data in both Notes and Exchange. For the configuration requirements for these accounts, be sure to see the Network Security Considerations and Options topic of the System Requirements section in the NME User Guide or Quick-Start Guide.

Global Operations

This section contains information about installing and operating this product in non-English or non-ASCII configurations. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

The platforms and configurations supported in this release may use any time zone, character encoding, language, or locale configuration to operate this product. This product supports multi-locale operation and uses the Unicode character set internally to support simultaneous operation with multilingual data.

This product supports the migration of all mail, calendar data, and personal address books, regardless of the source language or character encoding, by converting the data from Notes' internal encoding to Unicode.

Getting Started

Contents of the Release Package

The Notes Migrator for Exchange (NME) zip-bundled distribution file contains the following component applications, accessories and documentation files:

Quest NME Setup Wizard (to install and configure the other components listed below)

Quest NME components:

Notes Migration Manager

Wizards launched from Notes Migration Manager:

• NABs Discovery Wizard
• Internet Domains Discovery Wizard
• Directory Export Wizard
• Collection Wizard
• AD Groups Provisioning Wizard

• Notes Data Locator Wizard
• AD Object Merging Wizard
• Send PAB Replicator Wizard
• Data Migration Wizard
• SSDM Statistics Collection Wizard

Self-Service Desktop Migrator (SSDM)
SSDM Throttling Utility
Notes Migration Scheduling Application
Migration Database Utility
Log File Viewer

Quest NME product documentation:

Release Notes: NME Release Notes.html

PDF-format documents:

• Quick-Start Guide: QStartGuide.pdf
• Notes Migrator for Exchange User Guide (for admins): NMEUserGuide.pdf
• Self-Service Desktop Migrator User Guide: SSDMUserGuide.pdf
• Program Parameters Reference: NME_Params_Ref.pdf

On-line Help systems (compiled HTML Help files):

• For the Notes Migration Manager: notesmigmgr.chm
• For the Wizards launched from Notes Migration Manager: one *.chm Help file for each Wizard
• For the Migration Database Utility: migdbutil.chm
• For the Self-Service Desktop Migrator: notesdtapp.chm
• For the SSDM Throttling Utility: schedulingadmin.chm
• For the Log Viewer: wlogview.chm

Installation Instructions

Refer to the Notes Migrator for Exchange Quick-Start Guide for installation instructions.

For More Information

Contacting Quest Software:

Email	info@quest.com
Mail	Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA
Web	http://www.quest.com

Refer to our Web site for regional and international office information.

Contact Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.

Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com/.

From SupportLink, you can do the following:

Quickly find thousands of solutions (Knowledgebase articles/documents).
Download patches and upgrades.
Seek help from a Support engineer.
Log and update your case, and check its status.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global%20Support%20Guide.pdf. This guide is available in English only.

Legal Notices

Copyright Notice

This document contains proprietary information protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

© 2010 Quest Software, Inc.
ALL RIGHTS RESERVED.

If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
Email: legal@quest.com

Trademark Notice

Quest, Quest Software, and the Quest Software logo are trademarks and registered trademarks of Quest Software, Inc., in the United States of America and other countries. Other trademarks and registered trademarks used in this document are property of their respective owners.

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

Third-Party Software Contribution

Notes Migrator for Exchange contains a third-party component, zlib version 1.2.3, whose author requires this attribution. The license may be found on our website at http://www.quest.com/legal/third-party-licenses.aspx.

Other Recent Releases

New & Enhanced Features and Issues Addressed in Version ...

4.2.0.75

4.1.9.15 ::::: 4.1.8.0 ::::: 4.1.7.8 : .5 : .3 ::::: 4.1.6.17 : .15 : .8 : .4

4.1.5.55 : .50 : .39 : .38 : .36 : .34 : .30 : .27 : .25 : .23 : .17

4.1.4.26 : .25 : .23 : .20 : .15 :::::: 4.1.3.14 :::::: 4.1.2.13 : .7

4.1.1.64 : .61 : .60 : .44 : .30 : .29 : .23 : .21 : .18 :::::: 4.1.0.12

4.0.0.35 : .34 : .31 : .24 : .18 : .13 : .6

Version 4.2.0.75

New and enhanced features in Version 4.2.0.75:

Exchange 2010 support: NME now supports migration to Exchange 2010. See the updated System Requirements below for the configurations (both the target server and the admin's workstation) necessary to migrate to Exchange 2010.

Resolved issues in Version 4.2.0.75:

CR #74607	The AD Groups Provisioning Wizard now verifies that each program-generated mailNickname contains no more than 20 characters, since longer strings can cause errors. The Wizard has always generated mailNicknames of 20 or fewer characters, but in previous versions the string could exceed the limit if a digit were appended to differentiate two names with the same root.
CR #75510	The Directory Export Wizard can now be configured to be more forgiving when it encounters a rare "Field is too large" error that can occur when querying certain unreadable NSF files. The error otherwise prevents the Wizard from retrieving data from the remaining Notes source documents, and the export fails. But a new program parameter now lets you change the method the Directory Export Wizard uses for NSF queries, which will preempt most of those rare query errors. The new parameter: [DirectoryExport] NoSummary=1 ... tells the Wizard to open all Notes object records one at a time, rather than opening all non-group object records at once to facilitate a continuous stream of data from all open records. This feature is off (NoSummary=0) by default, and Quest recommends you leave it off unless you have encountered the particular "Field is too large" error, since program performance is likely to suffer (perhaps dramatically) if the Wizard has to open and close many object records individually. In either case, the Wizard reports any such error in its log file, but if NoSummary=1 the Wizard will then ignore the error and resume reading the remaining source data.
CR #74638	The User Guide now notes this issue in the process instructions for a BPOS migration (Appendix C), and for the Data Migration Wizard (in chapter 6): When migrating to BPOS (only), the Data Migration Wizard reports an error if you Set mail domain (in the Specify Notes to Exchange Mail Forwarding screen), because it cannot find the target object in the local domain. But this error may be safely ignored (just click OK to resume the process) because the Wizard will set the mail domain anyway. The phenomenon has also been added to the Known Limitations for BPOS migrations (in Appendix C).
CR #74637	The User Guide now notes this issue in the process instructions for a BPOS migration (Appendix C), and for the Data Migration Wizard (in chapter 6): When migrating to BPOS (only), the Data Migration Wizard cannot Manage mail routing and Migrate users both within a single program run. To accomplish both functions, simply run the Wizard successively, first to Manage mail routing, and then again to Migrate users. The phenomenon has also been added to the Known Limitations for BPOS migrations (in Appendix C).
CR #74926 CR #74929 CR #74931 CR #74928	The following issues have been identified and documented in the Known Limitations appendix of the NME User Guide: CR #74926: Page breaks, sections, horizontal rules, and computed text within a message do not migrate. CR #74929: A Created object within a Notes message appears twice (duplicated) after migration to Outlook. CR #74931: Embedded elements within a message do not migrate. CR #74928: Image resources (inserted in a Notes message by Create\|Image Resource) do not migrate.

Version 4.1.9.15

New and enhanced features in Version 4.1.9.15:

The Data Migration Wizard and SSDM now support MIME messages with UUEncoded attachments.

Resolved issues in Version 4.1.9.15:

CR #74111	DocLinks and attachments now appear correctly ordered within migrated messages that contain them. Attachment icons now appear inline within the message body, and are no longer duplicated at the end of the message. The duplicate-attachment-icons issue remains documented in the User Guide of this release as a Known Limitation, but that item will be removed in the next release.
CR #71626	DocLinks converted to Notes Migrator for SharePoint (NMSP) links are now properly formatted.
CR #69905	The Data Migration Wizard no longer skips items when migrating a Resource Reservation database.
CR #63367	The Data Migration Wizard now saves the checkbox setting for Connect using Outlook Anywhwere (on the Select Destination Exchange Server screen) from each program run to appear as the default setting for the next run — provided the Exchange Server Configuration screen (in Notes Migration Manager) has not been set to Always use these values.
CR #49474	The Data Migration Wizard no longer appends an extraneous digit "1" to the user names of Active Directory user objects when mailbox-enabling a contact (if MBoxFromContact=1 in the [ActiveDirectory] section of Task Parameters).
CR #69699	The item *Notes resources cannot be reserved from Exchange Rollup 7 or 8* has been removed from the list of Known Limitations in Appendix A of the NME User Guide because, while true, it is a coexistence issue rather than a migration issue, and moreover is not a limitation of NME but rather of the Exchange server.
CR #68442	The PAB Replicator now copies only user-created address books to the central server, and no longer inadvertently copies users' local NAB replicas or other local public address books.
CR #65137	The Data Migration Wizard, when group provisioning, can now be set to wait after deleting a contact (to make way for a group) before creating a distribution group in AD. In previous releases, in environments experiencing AD replication delays, the Wizard sometimes appended a 1 to some AD fields as it created user objects and tried to stamp addresses. The new CreateGroupDelay= parameter, in the [ActiveDirectory] section of Global Defaults and Task Parameters, now lets you specify a number of seconds for the Wizard to wait. You may want to set this value to something in the range of 30 to 300 seconds if your environment experiences AD replication delays. If you experience no such delays, you may leave the parameter set to its default of 0 seconds (no delay).
CR #64607	The Data Migration Wizard and SSDM can now be configured to not ignore MIME data that has a boundary preceded by whitespace and/or null characters. The feature is enabled by a boolean program parameter in the [Notes] section of Task Parameters: [Notes] MimeIgnoreBoundaryWhitespace=[#] ... where [#] is a 1 or 0 to indicate whether the feature is enabled or disabled. A value of 1 tells the program to ignore any whitespace and null characters preceding the MIME data. The feature is off (0) by default.
CR #64311	The migration of the Stationery folder no longer adds parentheses to the folder name — e.g., "(Stationery)" — in Outlook.
CR #70046	A migrated scenario in which two dates of a recurring meeting series are chronologically crossed (so that the earlier of the two becomes the later) no longer leaves a missing meeting in the calendar, which in previous releases could cause Outlook to hang when displaying the calendar Today screen.
CR #70766	Messages, calendar items and tasks with Composite Data bodies are now always migrated with the body intact.
CR #73359	The Data Migration Wizard and SSDM can now migrate Contact attributes of TYPE_NUMBER (e.g., containing a phone number stored as a number).
CR #69316	The NME User Guide has been updated to document SMTP mail routing by smart hosts as the preferred method of SMTP email coexistence (preferred over the subdomains method). See the Email Routing Options topic in the Coexistence section of chapter 2, and step 4 of the Necessary Pre-Migration Preparations section of chapter 3.
CR #72763	The NME Program Parameters Reference has been updated to add the two new parameters: CreateGroupDelay= (see CR #65137 above), and MimeIgnoreBoundaryWhitespace= (see CR #64607 above).
CR #71502 CR #71969 CR #71970	Several Known Limitations (Appendix A of the User Guide) have been updated to qualify them, since testing has shown that they apply only to certain environments and circumstances.

Version 4.1.8.0

New and enhanced features in Version 4.1.8.0:

Notes client 8.0.1 and 8.0.2 support: NME now supports Notes client versions 8.0.1 and 8.0.2 on the administrator's migration workstation.

Version 4.1.7.8

Resolved issues in Version 4.1.7.8:

CR #69328	The RewriteRTF= parameter default has been changed to 0, to enable rich text, attachments, and images within table cells to migrate properly from a Notes client 7.x or higher. (The fix was documented as a Resolved Issue in release 4.1.7.3 for CR #65316, but until now required a manual change to the parameter value, whose previous default was 7.) The RewriteRTF= parameter is in the [Exchange] section of NME Global Defaults and Task Parameters.
CR #69082	The Data Migration Wizard now truncates a contact's mailNickname to 19 characters if it exceeds that length (and if MBoxFromContact=1), so that it can mailbox-enable the contact. Prior to this release, the Wizard could not mailbox-enable a contact if the contact's mailNickname exceeded 19 characters.
CR #68981	The AD Groups Provisioning Wizard now correctly migrates distribution lists (groups) whose names contain underscore characters. Prior to this release a group whose name contained an underscore would appear in AD with the underscore removed—e.g., distrib_list would appear in AD as distriblist. As a byproduct of this solution, certain other characters within group names (namely / \ [ ] : ; \| = , + * ? < > "), which previously were deleted, are now retained but converted to underscores. In prior releases, these other characters were first converted to underscores, and then were deleted as underscores. Now that the Wizard preserves underscores, these other characters are still converted, but then are retained within the group names as underscores.
CR #64932	A meeting originally proposed and accepted in Notes, but then migrated to Exchange, and then cancelled by a migrated Exchange user who was the Notes originator, is now correctly removed from other Notes users' calendars. Prior to this release the cancellation email would appear normal to Notes recipients, and would report that the meeting had been removed from the calendar when actually it had not. The cancellation had no effect on Notes invitees' calendars. This fix will work only for calendars that are migrated by this release (and later) of NME.
CR #69409	The Data Migration Wizard and SSDM now use the user-defined name for attachments (if available) rather than the Notes-defined attachment name.
CR #69358	This limitation has been identified and added to the Known Limitations appendix in the NME User Guide: Exchange users running under Exchange Rollup 7 or 8 cannot book resources in Notes.

Version 4.1.7.5

Resolved issues in Version 4.1.7.5:

CR #64798	Certain email attachments no longer lose their filenames upon migration, which prevented users in some environments and circumstances from opening them in a prior release.
CR #65714	Reminder alarms for migrated follow-ups are now generated at the correct times.
CR #68463	iNotes contacts with no last name now migrate correctly, when the [Notes] PABRequiredAttrs= parameter value (in Task Parameters) is set to: [Notes] PABRequiredAttrs=ListName\|LastName\|CompanyName\|FirstName
CR #68148	A particular type of S/MIME calendar appointment, with a MIME body section but no body, now migrates correctly without generating an exception.
CR #68929	The NME Parameters Reference has been updated to add this information to the MBoxFromContact= parameter (pg 19 of the current edition, Doc ID 156): If MBoxFromContact=1, any UserFilter= or ContactFilter= parameter that may have previously been defined in this [ActiveDirectory] section should be removed.

Version 4.1.7.3

Resolved issues in Version 4.1.7.3:

CR #67011	The Data Migration Wizard no longer generates reminders for some meetings/appointments, tasks and Follow Up messages that occurred in the past, so that reminders for these past items no longer mistakenly pop up when users log in.
CR #65316	Rich text, attachments, and images within table cells now migrate properly from a Notes client 7.x or higher. Important: This fix requires that you set a program parameter value in the [Exchange] section of Global Defaults and/or Task Parameters as follows: [Exchange] RewriteRTF=0 The default is RewriteRTF=7, which would cause embedded images to not migrate correctly.
CR #66160	Mailbox-enabling now works in a user-forest and resource-forest configuration set up with a two-way trust.
CR #65487	The Directory Export Wizard now exports groups correctly after membership changes, such as when members have been added, removed, and then added again.
CR #65747	The Data Migration Wizard now correctly migrates a particular appointment that had not been migrating in particular circumstances in the preceding release.
CR #65325	The Known Limitations appendix of the NME User Guide has been updated to remove the R6 qualifier from the item documenting the non-migration of contacts' briefcase folder contents. (The limitation unfortunately applies to all source versions, not just R6.)
CR #66349	Calendar appointment responses and updates that, in certain particular environments and circumstances, had not been migrating in a prior release, now migrate correctly.

Version 4.1.6.17

Resolved issues in Version 4.1.6.17:

CR #65258	The Directory Exporter now correctly imports SMTP addresses with double quotation marks.
CR #65488	The Notes Migration Manager console no longer displays ampersand characters as underscore characters in exported group names. (The value in the SQL Server database was correct, but NMM rendered it incorrectly in the displayed table.)
CR #65319	Code refinements in the Data Migration Wizard have eliminated a rare problem whereby some Personal Address Book contacts were migrated with incorrect email addresses.
CR #66098	The AD Groups Provisioning Wizard no longer appends extraneous digits to the names of groups provisioned in AD when the source (Notes) group names begin with the "#" symbol and are differentiated only by digits that occur between the "#" symbol and alpha characters that follow. For example, the Notes groups #123Group, #124Group and #125Group, which prior to this release would gave appeared in AD as #123Group, #124Group1 and #125Group2, now are provisioned under their correct original names.

Version 4.1.6.15

New features and feature enhancements in Version 4.1.6.15:

Debug logging for custom attributes — Debug logging now includes more detailed information about how NME processes custom attributes.
Room Resource capacity now migrates — The Data Migration Wizard now migrates the capacity of a Room Resource when it migrates the Resource into Exchange 2007.
SSDM supports Win 2000 — The Self-Service Desktop Migrator can now run on Windows 2000. The new Win 2000 support has been added to the System Requirements documentation.

Resolved issues in Version 4.1.6.15:

CR #65497	The Data Migration Wizard no longer generates errors when attempting to manually run scheduled migrations of PABs. In a prior release the Wizard generated a collection-not-found error, with a collection GUID of all zeros, which then precipitated other errors.
CR #63636	Domino user-created folders whose names match Outlook system folders now migrate to the Outlook root folder, with " 1" (space and digit 1) appended to the folder name, rather than to their corresponding Outlook system folders, as in prior releases. For example, Contacts migrates to Contacts 1, Sent Items migrates to Sent Items 1, etc.
CR #65232	The Data Migration Wizard now correctly migrates the Notes Trash folder to Exchange/Outlook.
CR #49197	The Data Migration Wizard now correctly migrates the Notes Junk Mail system folder to Exchange/Outlook.
CR #64550	The default value for the AlwaysUseOldExchDN= parameter (in the [ActiveDirectory] section of Global Defaults and Task Parameters) has been changed from 1 to 0. The parameter determines whether the legacyExchangeDN will be maintained through merging and mailbox-enabling, to support free/busy synchronization from Notes to Exchange through the Notes Connector. Since NME now stamps the X500 address as a proxy address (if we change it), the new default AlwaysUseOldExchDN=0 produces a less cryptic name than the GUID.

Version 4.1.6.8

New features and feature enhancements in Version 4.1.6.8:

AD Alias/Mailnickname can be retained or overwritten — The AD Object Merge Wizard can now be configured to keep the Alias/Mailnickname stamped onto an object in AD (when creating objects via the Microsoft Transporter), rather than replacing that value with a value from Notes when merging and mailbox-enabling. The behavior is controlled by a new boolean Global Default or Task Parameter:

[ActiveDirectory]
AlwaysUseOldAlias=[#]

Program Parameters Reference

Resolved issues in Version 4.1.6.8:

CR #64913 CR #64914	Code enhancements have eliminated occasional unhandled exceptions (CR #64913) and errors (#64914) that occurred when the Data Migration Wizard attempted mailbox-enabling in systems configured for a User Forest and a Resource Forest.
CR #64912	The Data Migration Wizard no longer requires a Domain Controller designation for the User Forest, when the system is configured for a User Forest and a Resource Forest, since all operations in the User Forest are limited to read-only searches.
CR #64684	The four status conditions that appear in the Monitor tab of the SSDM Scheduling Administration utility are now documented in the updated NME User Guide and in the schedulingadmin.chm Help file. The four status conditions are: Processing: Number of users currently running the SSDM. Waiting: Number of users waiting for an opening to start running the SSDM. Timed Out Waiting: Number of users whose SSDM was waiting for so long that it timed out. Cancelled Waiting: Number of users who were waiting for an opening to start processing, but clicked Cancel on the SSDM to stop waiting.

Version 4.1.6.4

Issues addressed in Version 4.1.6.4:

CR #62906	The Notes Migration Manager, Data Migration Wizard, AD Object Merge Wizard, and AD Groups Provisioning Wizard all now prompt for a separate GC and DC (in the Active Directory Information screen), to preempt occasional errors that occurred in earlier releases.
CR #63907	A meeting invitation originating from an Outlook user and sent to a Notes invitee now migrates properly when the invitee migrates to Exchange. And a meeting whose invitation originated in Outlook but was accepted by a Notes user, now appears as it should in the invitee's Outlook Calendar after the invitee migrates.
CR #64008	Reminder alarms for meetings/appointments now execute correctly after migration.
CR #60843	The coexistence information, in chapter 2 of the NME User Guide, has been updated to include Quest's new Coexistence Manager for Notes product as a good option in Calendar coexistence strategies, and to correct some outdated information.
CR #64273	A new Appendix C has been added to the NME User Guide, to document the procedure for using NME to migrate from Notes to Microsoft's Business Productivity Online Suite (BPOS)—the array of email and related collaboration-software services provided by Microsoft-hosted Exchange, Active Directory, SharePoint, and other servers.
CR #63390	The NME Program Parameters Reference has been updated to include new parameters that have been added to various Wizards and applications in recent releases.

Version 4.1.5.55

New features and feature enhancements in Version 4.1.5.55:

UI controls to configure Exchange Proxy Settings: The Notes Migration Manager and Data Migration Wizard now provide convenient UI controls to configure Exchange Proxy Settings, which let the Data Migration Wizard use Remote Procedure Calls (RPC) within HTTP packets to communicate with the target Exchange server. These features were added in release 4.1.4.15, but were previously configurable only by program parameters in the Global Defaults and Task Parameters. The RPC protocol may improve data throughput on a slower network, especially when migrating to Exchange 2007.

Admin control of remigrations by message features: A new program parameter lets an admin control which messages to remigrate, depending on the features of each message:

[General]
MsgRequireAnyFeature=<#>

0: Migrate all items (default).
1: Migrate only items with embedded OLE objects.
2: Migrate only items with inline MIME attachments.
4: Migrate only items with Notes RTF bodies with bitmaps.
7: Migrate only items with one or more of the features listed above.

Issues addressed in Version 4.1.5.55:

CR #62150	The Data Migration Wizard now correctly migrates embedded OLE objects and inline MIME attachments.
CR #62455	The Notes Migration Scheduling Application no longer genererates an "Invalid URI" error when run after an initial NME installation.
CR #62573	RPC proxy settings now work correctly when communicating with the Exchange server other than via straight RPC.

Version 4.1.5.50

New features and feature enhancements in Version 4.1.5.50:

SSDM Throttle feature enhancements: The Throttling features of the Self-Service Desktop Migrator (SSDM) have been enhanced as follows:
- The SSDM will now display more appropriate notification messages when a user tries to run the SSDM within the migration window date range for his/her collection, but before or after the permitted time-of-day range.
- The SSDM Throttling Utility lets an admin customize the text of the new before/after time-of-day notification messages (the same as an admin can customize the text of notification messages for other run restrictions).
- The SSDM Throttling Utility contains a new tabbed panel, labeled Monitor, which lets an admin monitor the current status of SSDM usage, by numbers of users: Processing (currently), Waiting, Timed Out Waiting, and Cancelled Waiting.
These new features are all documented in the updated NME User Guide and schedulingadmin.chm Help file that accompany this release.
Admin control of SSDM Finished screen display: A new boolean program parameter in the [General] section of the notesdtapp.ini file lets an admin control whether the SSDM Finished screen will display the app's statistics, and the View Errors button. For example:

[General]
ReportErrors=0

... tells the SSDM to not report its error, warning, filtered and skipped counts on the Finished screen, and to not offer the View Errors button. By default (ReportErrors=1) the Wizard will show all of these elements.
Admin control over Directory Export skipping group member info: A new boolean program parameter, in the [DirectoryExport] section of Task Parameters and/or Global Defaults, lets an admin control whether the Directory Export Wizard will export or skip group member information:

[DirectoryExport]
SkipGroupMembers=<#>

The default is 0, meaning that the Wizard will not skip (will export) group member information.
Directory Export captures User Name proxy address: The Directory Export Wizard now captures the proxy address from the User Name field in the Notes person document.
Admin control of Directory Export extraction of Internet aliases for TargetAliases: A new boolean program parameter in Task Parameters and/or Global Defaults lets an admin control whether the Directory Export Wizard will extract users' Internet aliases from the Domino server and insert them into the TargetAliases column of the exported data tables. For example, the default setting:

[DirectoryExport]
GenerateAliases=1

... enables this feature. The alternative (GenerateAliases=0) disables this feature—tells the Directory Export Wizard to generate only a TargetAddress (the primary SMTP address), but no TargetAliases (secondary SMTP addresses). If the TargetAliases column is populated (either by GenerateAliases=1 or manually), the Data Migration Wizard will load the aliases into Active Directory as it mailbox-enables Exchange accounts.
Admin control of Notes JournalEntry and CleanSheet item migration: A new program parameter, in the [Notes] section of Task Parameters or Global Defaults, lets an admin choose whether Notes JournalEntry and CleanSheet items should be migrated to Exchange as Activities (default) or StickyNotes. For example:

[Notes]
JournalEntryMessageType=StickyNote // or =Activity (default)
Admin control of mail file path in Migration DB Util: The Migration Database Utility component of NME now lets an admin change the path to a mail file, in addition to changing the server. In prior releases, for a mail file server/domain!!mail\sample.nsf, the utility could change the server/domain portion only, but now it can change the folder name mail.

Issues addressed in Version 4.1.5.50:

General

CR #59119	The Data Migration Wizard now propagates public delegates to Active Directory only when it will also migrate server mail to the Exchange mailbox. This change eliminates the seemingly irrelevant appearance of the Active Directory Information screen when migrating server mail to a pst file.
CR #52933	The Data Migration Wizard now correctly sets the text encoding on large HTML message bodies, so non-ASCII characters display correctly.
CR #57752	HTML message bodies now migrate correctly, not empty as sometimes occurred in particular circumstances in prior releases.
CR #61054	The Data Migration Wizard now migrates Notes journal items with date/time stamps set to their Notes DiaryDate fields, rather than to the system date/time as in prior releases.

Directory Exporter

CR #60699

Process refinements in the Directory Export Wizard have eliminated the rare cases where, when a user and contact share the same source and/or target address, the contact's address prevailed in the exported data. These changes also ensure that subsequent runs of the Directory Export Wizard will not create duplicate objects or enable new addresses, and assure the consistency of the address translation table, and also resolve several other less common addressing issues.

CR #60700

A subsequent run of the Directory Export Wizard no longer generates duplicate records for a single user or contact when Domino admin is used to edit the Notes person document to change the Internet address to the SMTP address of a contact.

Version 4.1.5.39

New features and feature enhancements in Version 4.1.5.39:

New Collection Import/Export Features: The Migration Database Utility now offers features that let you save all defined collections to TSV files, and import them back into the SQL server database, to spare you the time and trouble of having to manually recreate collections in the event the SQL database is deleted and reloaded by another directory export. It is rare but possible that data corruption or incongruities in the SQL database may make it easier to simply delete the database contents and re-export data from the Notes/Domino source, although in that case it would be tedious for many admins to have to manually recreate collections. This new feature therefore lets you export all defined collections to TSV files (all at once), and then import them all back into the database after it has been reloaded. Prior to this feature, collections could be exported and imported from the Notes Migration Manager, but only one collection at a time.
Optional migration of responses to appointment/meeting requests: A new program parameter lets an admin control whether the migration application will migrate responses to appointment/meeting requests (i.e., Accepted, Declined, etc.). The new MigrateAppointmentResponses= boolean parameter can be set in the [Notes] section of Global Defaults or Task Parameters (for the Data Migration Wizard) and/or in notesdtapp.ini (for the SSDM):

[Notes]
MigrateAppointmentResponses=1

// default = 0 (responses will not migrate)

... tells the application to migrate responses.
Greater admin control over setting Notes person document attribute values: A new checkbox on the Data Migration Wizard's Notes Administrative Operations screen lets you tell the Wizard whether to Set Person Document Attributes by referring to the pertinent parameter settings in the [PersonDocCustom] section of the Task Parameters. If the checkbox is marked, the Wizard will assign attribute values as defined in the Task Parameters (documented in the NME Program Parameters Reference). If the checkbox is unmarked, the Wizard will ignore the [PersonDocCustom] section of the Task Parameters.

AD Object Merge maps additional NME fields to LDAP attributes: The AD Object Merge Wizard, when ProvisionUsers=1 (to create a new mail-enabled object when none is found to correspond to a collection user), now maps additional NME fields to LDAP attributes:

Description
Middle (to middleName)
Generation (to generationQualifier)
Title
Company

Department
EmployeeID
StreetAddress
City (to l)

StateOrProvince (to st)
PostalCode
Country (to co)
OfficeNumber (to physicalDeliveryOfficeName)

Expanded control of forms migration: The XxxxForms= program parameters (AppointmentForms=, MemoForms=, etc.), which permit the designation of alternate names for forms to migrate, now support values ending with an asterisk (*) for simple wildcard matching.
New program parameter to specify forms to ignore: A new program parameter lets an admin specify particular forms for the Data Migration Wizard or SSDM to ignore (not migrate, and not report the non-migration in the log). The IgnoreForms= parameter can be set in the [Notes] section of Global Defaults or Task Parameters (for the Data Migration Wizard) and/or in notesdtapp.ini (for the SSDM). For example:
[Notes]
IgnoreForms=H_PAGEUI

// default = H_PAGEUI

... tells the program to not migrate H_PAGEUI forms, and not report it in the log.
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).

Issues addressed in Version 4.1.5.39:

CR #59010

Multiple migration workstations running in parallel no longer encounter a locked addresstranslation.bin file. The migration application now makes and works from temporary working copies of the file, so other program components on other workstations can access the file.

CR #28987

The Notes Migration Manager no longer generates an error when you edit a collection with Advanced Settings enabled (on the View menu).

CR #54784

In chapter 3 of the User Guide, in the Migration Per Desktop section, under Command-Line Switches for Running the Desktop Migrator in Silent Mode: The definition of the /notesid <UserID> switch was incorrect, and has now been corrected to:

/notesid : The full path and file name of the user's Notes UserID.

And the accompanying command-line example has been corrected to:

notesdtapp /silent /notesid "c:\Documents and Settings\JDoe\Local Settings\Application Data\Lotus\Notes\Data\jdoe.id" /notespass password ....

CR #60715

To improve readability and usability, the Data Migration Wizard now substitutes an ellipsis ("...") for long character strings that occur in interior elements of the Mailbox Database field in the Specify Exchange Mailbox Info screen.

Version 4.1.5.38

New features and feature enhancements in Version 4.1.5.38:

New AD Object Merge parameters set AD userAccountControl attribute: Two new program parameters for the AD Object Merge Wizard now let you tell the Wizard to set the userAccountControl attribute value in Active Directory:

[ActiveDirectory]
SetUserAccountControl=<#>
UserAccountControl=<###>

// default = 0
// default = 512 (NORMAL_ACCOUNT)
- SetUserAccountControl= is a boolean parameter that tells the Wizard whether to set the value.
- If SetUserAccountControl=1, the UserAccountControl= parameter then sets the value with an integer.
- If SetUserAccountControl=0, the UserAccountControl= parameter is ignored.

Issues addressed in Version 4.1.5.38:

CR #59216	The Directory Export Wizard no longer ignores group members when a whitespace immediately precedes a group member. All group members are now exported, regardless of any whitespace.
CR #60062	The AD Object Merge Wizard, when ProvisionUsers=1 (to create a new mail-enabled object when none is found to correspond to a collection user), now correctly creates objects with first and last names, rather than just display names.

Version 4.1.5.36

Issues addressed in Version 4.1.5.36:

CR #59174	Subsequent runs of the Directory Exporter now correctly update the server and file name in the mail file value stored in the SQL database, and do not create a second mail file entry.
CR #59935	Code refinements have eliminated errors that could occur when the Migration Console and Data Migration Wizard attempt to validate the Exchange Administrator username and password while the RPCUseAdminMapiProfile=1 configuration setting is enabled.
CR #60017	The Data Migration Wizard now more reliably migrates recurring appointments with custom recurrence rules. Code refinements have eliminated the error that could occur when the date of an appointment within a series had been modified.
CR #60086	The User Guide has been updated to note that, when configuring ASP.net for use with the SSDM Throttling features, the entry for the User name field, under Identity settings on the Application tab of the ASP.net Configuration Settings, must take the form domain\username. (This change occurs in the second bullet point under step 7 of the installation/configuration procedure documented for How Do I Regulate Use of the SSDM to Avoid Processing Bottlenecks?, in chapter 4.)
CR #60063	The SMTPForwardingAddress=<#> program parameter (in the [Notes] section) has been added to the updated Program Parameters Reference that accompanies this release. It had been inadvertently omitted from the Reference in the previous release.

Version 4.1.5.34

New features in Version 4.1.5.34:

Support for mapping Notes person doc settings: An admin may now map Notes person document settings in the Data Migration Wizard, to define particular person doc fields to the Wizard and then assign values to the fields in Notes. These features are facilitated by a new set of program parameters, in a new [PersonDocCustom] section of Task Parameters and Global Defaults, and are fully documented in the updated Program Parameters Reference.
Optional migration of exceptions to recurring appointments that occur outside a date filter: A new program parameter lets an admin choose whether the Data Migration Wizard or SSDM should 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. The optional boolean parameter, SkipOutOfRangeExceptions=<#>, is defined in the [General] section of Global Defaults or Task Parameters for the Data Migration Wizard, or in notesdtapp.ini for the SSDM. 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:

SkipOutOfRangeExceptions=1

... 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.
Optional migration of recurring appointments when part of the series occurs outside a date filter: A new program parameter lets an admin choose whether the Data Migration Wizard or SSDM should migrate all instances of a recurring appointment or task when the first instance occurs prior to the range of a defined date filter, but the last instance occurs within or after the date filter range. The optional boolean parameter, MigrateRecurringBeforeRange=<#>, is defined in the [General] section of Global Defaults or Task Parameters for the Data Migration Wizard, or in notesdtapp.ini for the SSDM.
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 had been defined to run three weeks beginning October 1 (so appointments occur on October 1, 8 and 15), then:

MigrateRecurringBeforeRange=1
... 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 tell the Wizard 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.
Control of identity parameter for the Update-AddressList cmdlet: An admin can now specify the name of the identity parameter for the Update-AddressList cmdlet, which the Data Migration Wizard runs after mailbox-enabling a collection if [Exchange] RunUpdateAddressList=1. The name can be specified by a new AddressListName=<NameOfList> parameter in the [Exchange] section of Global Defaults or Task Parameters. If unspecified, the value defaults to "All Users."
Control of identity parameter for the Update-EmailAddressPolicy cmdlet: An admin can now specify the name of the identity parameter for the Update-EmailAddressPolicy cmdlet, which the Data Migration Wizard runs after mailbox-enabling a collection if [Exchange] RunUpdateEmailAddressPolicy=1. The name can be specified by a new AddressPolicyName=<NameOfPolicy> parameter in the [Exchange] section of Global Defaults or Task Parameters. If unspecified, the value defaults to "Default Policy."
New option for composing Domino forwarding addresses and AD proxyAddresses: A new program parameter, in the [Notes] section of Global Defaults or Task Parameters, lets an admin tell the Data Migration Wizard, in mail routing, to omit the second "@XXXX" element from the Domino forwarding address and AD proxyAddress values:

If SMTPForwardingAddress=0
If SMTPForwardingAddress=1

user@smtp.domain.com@DOMINODOMAIN
smtp:user@smtp.domain.com@DOMINODOMAIN
user@smtp.domain.com
smtp:user@smtp.domain.com

This parameter may be useful when Transporter is used for co-existence and new mail goes to Exchange, if users in a single collection being migrated with mail routing are in two different Domino domains. This parameter could then be used to not include the same domain for every user, when it is incorrect for some users. Other adjustments may be needed outside of Notes Migrator for Exchange features to make free/busy or mail coexistence work.
Even with SMTPForwardingAddress=1, the admin must still enter some value for the Domino domain on the Set Notes Forwarding screen, to enable the Next button—although the value entered will not be used in the migration.
AD Object Merging Wizard asks how to find Contacts: The AD Object Merging Wizard now asks an admin, on its Choose your method for finding objects screen, to specify How contacts were loaded into Active Directory. That entry in turn determines which of two methods the Wizard will use to find a Contact when merging: by the SMTP address, or the default method of finding a Contact by its Notes source address. The new field is now documented in the updated User Guide and Help file, and the entry for the corresponding program parameter, MergeFindbySMTP=, has also been updated in the Program Parameters Reference.
Control of managedBy attribute in AD Groups Provisioning: The AD Groups Provisioning Wizard now lets an admin specify whether the Wizard will set the managedBy attribute to the DN of the owner in the user forest or resource forest—for environments configured for a resource and user forest. The option is enabled or disabled by a new boolean program parameter, SetManagedByToUserForest=<#>, in the [Exchange] section of Task Parameters and Global Defaults. The new parameter is fully documented in the updated Program Parameters Reference.

Issues addressed in Version 4.1.5.34:

CR #59017	The User Guide and Data Migration Wizard Help file now explicitly warn against selecting the Transporter for mail coexistence if the Transporter will not also be used for calendar free/busy coexistence. (These selections are made on the Wizard's "Specify Mail Routing Options" screen.) Designating the Transporter for mail routing will process user objects in a way that requires also using the Transporter for calendar coexistence. If you select the Transporter for mail coexistence, the Wizard automatically pre-selects the Transporter as the method for calendar coexistence. If you really want to use the Transporter for mail coexistence but not for calendar coexistence, you may set mail coexistence to Microsoft Notes Connector, but still use the Transporter for that function.
CR #58833	The Data Migration Wizard now correctly generates proxy addresses for Notes-to-Exchange mail routing when using Microsoft Transporter.
CR #54024	An admin can now specify the name of the identity parameter for the Update-AddressList cmdlet, which the Data Migration Wizard runs after mailbox-enabling a collection if [Exchange] RunUpdateAddressList=1. The name can be specified by a new AddressListName=<NameOfList> parameter in the [Exchange] section of Global Defaults or Task Parameters. If unspecified, the value defaults to "All Users."
CR #54026	An admin can now specify the name of the identity parameter for the Update-EmailAddressPolicy cmdlet, which the Data Migration Wizard runs after mailbox-enabling a collection if [Exchange] RunUpdateEmailAddressPolicy=1. The name can be specified by a new AddressPolicyName=<NameOfPolicy> parameter in the [Exchange] section of Global Defaults or Task Parameters. If unspecified, the value defaults to "Default Policy."
CR #57502	The names of meeting originators now appear as they should in migrated meeting records for resources.
CR #56802	In the Data Migration Wizard, the screen that asks you to specify "How were accounts loaded into Active Directory" now accommodates the Microsoft Transporter as a selectable option (in addition to the Microsoft Connector and "Other" methods).
CR #58652	A drop-down list box in the AD Object Merge Wizard, which had mistakenly permitted editing of the selected item, has been fixed to permit only selection of an item from the list.
CR #58986	The User Guide procedure for offline migration (in chapter 4) has been expanded to include the steps necessary to set each user's mailFilePath value—by exporting user data to a TSV file, entering the mailFilePath data, and then importing the updated TSV data back into the SQL server database.
CR #59003	A typo in the Program Parameters Reference entry for the Filter[#]= parameter (in the [Filters] section) has been corrected.
CR #59004	The Program Parameters Reference entry for the WatchdogMinutes= parameter (in the [General] section) now explains: A value of 0 tells the Wizard to wait indefinitely (forever) for activity, rather than reporting a fatal error has occurred after some period of time.
CR #58501	The [ErrorsToIgnore] section of program parameters, in Global Defaults and Task Parameters and in the notesdtapp.ini file, now works as documented in the Program Parameters Reference. These parameters let the admin specify one or more particular runtime errors and/or warnings that a Wizard or program should ignore when documenting its activities and outcomes in its log file.
CR #57233	The User Guide and Notes Migration Manager Help file have been updated to make more clear: The User name field, under User Forest Credentials on the AD Configuration screen, must be the SAM Account name, not the UPN.

Version 4.1.5.30

Issues addressed in Version 4.1.5.30:

CR #56813

The AD Groups Provisioning Wizard now supports a new program parameter that tells the wizard which AD group objects to consider when merging AD objects with Notes objects (by matching AD attribute values with Notes attribute values in corresponding objects). This new GroupsSearchFilter=<expression> parameter, in the [ActiveDirectory] section of Global Defaults and/or Task Parameters, defines a subexpression of a customized AD search query. This feature is useful in cases where two or more objects may carry the same value for the AD attribute designated in the app run, but the objects can be differentiated by some other attribute. The <expression> value must be formatted as an AD query subexpression, including opening and closing parentheses, as in:

[ActiveDirectory]
GroupsSearchFilter=(objectClass=group)

The above example tells the program to consider only an object whose objectClass parameter value is "group." Conversely, the set to be considered may be defined by exclusion, as in:

GroupsSearchFilter=(!(objectClass=user))

... to tell the Wizard to disregard any object whose objectClass parameter value is "user," but to consider all others.

CR #54756

To improve readability and usability, the Data Migration Wizard now substitutes an ellipsis ("...") for long character strings that occur in interior elements of the Server field in the Specify Exchange Mailbox Info screen.

CR #37513

The AD Groups Provisioning Wizard now supports creation of universal security groups in either Exchange 2003 or Exchange 2007. In the Choose your method for finding objects screen, if Group Scope is set to Universal, the Security option for Group Type is now enabled as a valid choice.

CR #48675

The mail-enabling feature of the Data Migration Wizard now works properly when selecting from multiple storage groups with mail stores that have the same name, when migrating to Exchange 2007.

CR #49396

Error traps for program errors associated with PowerShell now capture the entire PowerShell command for the event log, to help support staff reproduce, diagnose and troubleshoot the problem.

CR #55754

Appointments in a reservation database now migrate correctly, as calendar items.

Version 4.1.5.27

Feature enhancement in Version 4.1.5.27:

CR #56724

Recurring daily migration window option in SSDM Throttle: The SSDM Throttling utility now permits the definition of migration windows that recur at the same time each day, for a range of dates. For example, a collection's members may be set to migrate from 08-25-2008 through 08-29-2008, and only between 4pm and 6pm on those dates.
The Migration Time Window fields for From and To still define the starting and ending dates and times of the broader range, but a new checkbox — Only allow migrations between: — lets you optionally set a "sub-range" that further limits migrations to only the hours specified in the accompanying time fields. If the checkbox is marked, the SSDM will run for a user in that collection only between the specified hours within the broader date/time range. If the checkbox is not marked, then users may migrate at any time within the broader date/time range.

Version 4.1.5.25

New feature in Version 4.1.5.25:

Expanded coexistence features with Microsoft Transporter — The Data Migration Wizard now supports simplified coexistence options for SMTP mail routing and calendar free/busy with Microsoft Transporter, for sites migrating to Exchange 2007. Wizard features now take better advantage of Transporter capabilities to simplify coexistence schemes for mail routing, directory synchronizations, and calendar free/busy synchronizations and lookups. While the Transporter does not facilitate the actual flow of mail for mail routing, its setup features for free/busy and dirsynch coexistence can configure Notes person documents and AD object records for a mail coexistence facilitated by SMTP addressing.
These features are fully documented in the updated NME User Guide (Doc ID 188) that accompanies this release. See the Coexistence Options section of Chapter 2 for updated general information about coexistence options. The field notes and application notes in the Data Migration Wizard section of Chapter 6, and in the Wizard's Help system, have been updated to document the new and modified fields within the Wizard.

Version 4.1.5.23

New feature in Version 4.1.5.23:

IncludeServerMailFile=<#> Parameter — A new program parameter in the notesdtapp.ini file lets an admin control whether the SSDM program will attempt to connect to the Notes server to display the server mail file within the list of available mail files. For example:

[General]
IncludeServerMailFile=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.

Version 4.1.5.17

New feature in Version 4.1.5.17:

SSDM Throttling Features — An administrator can now regulate end users' execution of the Self-Service Desktop Migrator (SSDM), to avoid processing bottlenecks that might otherwise occur if too many users tried to use the SSDM simultaneously. A new SSDM Throttling Utility lets an admin define different migration "windows," by date and time, for different user collections to be migrated, and the SSDM automatically checks to see if the current user is running the program within his/her scheduled window. The SSDM Throttling Utility also lets an admin set a concurrency limit for each collection, so no more than a set number of users will be allowed to run the SSDM at the same time. The SSDM Throttling Utility is fully documented in the updated NME User Guide that accompanies this release; see chapter 4 ("How Do I...?") for details.

Version 4.1.4.26

Issues addressed in Version 4.1.4.26:

CR #53953

Extraneous characters no longer added to some empty message bodies: The migration of a message with no body, as when a blank message is sent to deliver an attachment, no longer introduces extraneous characters from the MIME encoding to the message body.

Version 4.1.4.25

New features in Version 4.1.4.25:

Font replacement option in RTF-format messages — The Data Migration Wizard and SSDM can now 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. The option is controlled by the new UpdateRtfFonts=<#> boolean program parameter in the [Notes] section of Global Defaults and Task Parameters (for the Wizard), and/or in notesdtapp.ini (for the SSDM):

[Notes]
UpdateRtfFonts=1
The parameter value is a 0 or 1, where 1 enables the font replacements and 0 (default) disables the feature.

Version 4.1.4.23

New features in Version 4.1.4.23:

New FreeBusyDays= parameter — Notes Migrator for Exchange now lets you define a time period, in days, for which the program will tell Outlook to calculate users' free-busy data upon migration of each user's calendar items. In previous releases this value was undefined and unlimited, and as such could cause performance issues when the program calculated free-busy data far into the future.
This new feature is available for both the Data Migration Wizard and the desktop migrator (SSDM), and is set by the new FreeBusyDays=<#> parameter in the [Exchange] section of Global Defaults and Task Parameters (for the Wizard), and/or in notesdtapp.ini (for the SSDM):

[Exchange]
FreeBusyDays=91
The parameter value is an integer that specifies the number of days into the future that you want the program to check free-busy data. The defined period begins at the current system time minus 24 hours, and continues through a number of days equal to the parameter value plus 1. In the above example, FreeBusyDays=91 tells Notes Migrator to calculate only 91 days ahead when looking for calendar conflicts upon migration. If unspecified, the value defaults to 62 days.

Issues Addressed in Version 4.1.4.23:

CR #51410	Recurring meetings in Notes that have non-standard recurrence patterns now migrate according to Notes rules: Recurring meetings that occur twice or more per week now migrate into Exchange as meetings with recurrence rules. Previously, these meetings migrated as single occurrences.
CR #38622	Migration of multiple email addresses per contact in Personal Address Books, for Notes 6 and higher: Up to three email addresses per contact are now supported.

Version 4.1.4.20

Issues Addressed in Version 4.1.4.20:

CR #48943	Contact legacyExchangeDN preserved during group provisioning: The AD Groups Provisioning Wizard now preserves a Contact's legacyExchangeDN as an X.500 proxyAddress when provisioning the group in AD.
CR #35892	Replication conflict documents ignored: The Directory Export Wizard can now correctly handle replication conflict documents that occur within a source NAB, by ignoring them. Prior to this release, the Wizard exported a conflict document and its corresponding original as separate objects with the same SMTP address.
CR #43611	Extension Attributes retained: The Data Migration Wizard now properly retains Extension Attributes in Active Directory when mailbox-enabling accounts.
CR #51014	Composite HTML message bodies now migrate: The Data Migration Wizard now correctly migrates certain composite HTML message bodies that had previously been migrated to Notes.

Version 4.1.4.15

New features in Version 4.1.4.15:

RPC over HTTP protocol now available — The Data Migration Wizard can now use Remote Procedure Calls (RPC) within HTTP packets to communicate with the target Exchange Server. The RPC protocol may improve data throughput on a slower network, especially when migrating to Exchange 2007. This feature is enabled or disabled by the RPCUseHTTP= parameter, in the [Exchange] section of Global Defaults or Task Parameters. Other parameters in the [Exchange] section control various settings associated with the RPC protocol. (See the updated Program Parameters Reference for more details. All of the associated parameters are in the [Exchange] section, with parameter names beginning with "RPC.")
"Friendlier" support for DocLinks migration options — The Data Migration Wizard now contains a new screen for an admin to specify how to migrate Notes DocLinks. Prior to this release, the choice of DocLinks destination format was controlled only by a program parameter in the Global Defaults, Task Parameters, and notesdtapp.ini file — as documented for release 4.1.3.14 (see "Proposion Portal support in migrated DocLinks"). But the Data Migration Wizard now contains a new screen, Specify How To Migrate Notes DocLinks, that lets you set and configure your choice during the program run. The new screen is documented in the NME User Guide and Help system that accompany this release.
Domino 8.0 Support — Notes Migrator for Exchange now supports Notes Domino version 8.0 as a source server.
Notes 8.0 Support — Notes Migrator for Exchange now supports Lotus Notes version 8.0 on the administrator's migration workstation, and on the desktops of users who will run the Self-Service Desktop Migrator.
Support for Exchange 2007 SP1 and its Management Tools — Notes Migrator for Exchange now supports Exchange 2007 SP1 and its Management Tools on the administrator's migration workstation.

Issues Addressed in Version 4.1.4.15:

CR #42919	Contact Birth Year errors resolved: Code refinements have eliminated the occasional errors that occurred in migrated Birth Years when migrating Contacts. The migration process had erroneously migrated some Birth Years as "1970" regardless of the actual Birth Year in the Notes source.
CR #45659	SSDM MAPI credentials prompt error resolved: The SSDM's prompt for MAPI credentials now correctly accepts and processes all valid credentials.
CR #50564	Split-PDL reminders in Outlook Cached mode eliminated: Outlook no longer repeatedly reminds users of their split migrated PDLs upon every log-in. (A large PDL that exceeds Outlook's limit is automatically split by NME into two or more PDLs upon migration to Outlook PST. In prior NME releases, when Outlook was running in Cached mode, it reminded the user of any such split PDLs every time the user logged in. The reminders could be dismissed, but their repetition was annoying.)
CR #49891	Documentation elaboration for mail-in databases: The Notes Migrator for Exchange User Guide has been updated to include an elaborated explanation of how NME migrates Notes' mail-in databases. See new sections in chapter 2 (Strategic Planning Issues) and chapter 4 (How Do I...?).
CR #49892	Documentation elaboration for resource migration: The Notes Migrator for Exchange User Guide has been updated to include an elaborated explanation of how NME migrates Notes resources. See updated "Strategies for Migrating Resources" in chapter 2, and a new section to chapter 4 (How Do I...?).

Version 4.1.3.14

Updates to existing features in Version 4.1.3.14:

Pre-/Post-Migration Emails to End Users - The Data Migration Wizard now lets you send personalized ("mail-merge") emails to users before or after they are migrated. Such notifications let you announce an upcoming migration, explain the implications to end users, and tell them what they can expect and what will be expected of them. See How Do I Send Pre- or Post-Migration Notification Emails to End Users? in chapter 4 of the updated User Guide for instructions to send pre- or post-migration emails to end users.
Proposion Portal support in migrated DocLinks - The Data Migration Wizard and SSDM (desktop migrator) now support migration of Notes DocLinks to links in the Proposion Portal format. The existing HTMLdoclinks program parameter now supports the Proposion-format option in addition to the Notes-format and HTML-format options previously available.

[General]
HTMLdoclinks=2
... tells the Wizard to migrate DocLinks in the Proposion format. The options for Notes format (0) and HTML format (1) remain the same.
When HTMLdoclinks=2, you must also specify the name of the SharePoint server that contains the documents to which the Proposion links point:

[General]
SharePointServerName=<SharePointServerName>

Issues Addressed in Version 4.1.3.14:

CR #41736

SSDM login problem for Outlook 2007 on Vista-Japanese: Repeated prompts for login credentials upon SSDM login to Outlook 2007 on Vista-Japanese appear related to the Windows Firewall. When the firewall prompts you to Allow or Cancel the SSDM's access attempt, choose Allow to dismiss the prompt and Outlook will thereafter accept the login credentials.

Version 4.1.2.13

Issues Addressed in Version 4.1.2.13:

CR #36199

New parameter prevents incorrect aliases during mailbox-enabling: A new program parameter lets you control the time interval between two subfunctions of the Data Migration Wizard's mailbox-enabling process, which might otherwise cause PowerShell to generate incorrect aliases where Active Directory accounts are replicated among multiple servers. The Wizard disables mail for an account before it creates the mailbox, but the mail-enabled account can appear to still exist for a few seconds on any servers where the account is replicated. When PowerShell sees a not-yet-disabled account on the other server, it mistakenly treats the new mailbox as a duplicate, appending the digit "1" to the alias to differentiate it from the other account.
If your AD accounts are replicated on multiple servers, and you experience this "Alias1" problem when enabling mailboxes, use the CreateMailboxDelay parameter (in the [Active Directory] section), to force a delay between the mail-disabling function and the mailbox creation, to allow enough time for other servers to catch up and disable their replicated accounts. The parameter value defines a delay in seconds, in a valid range from 0 to 30000, and defaults to 0. For example:

[ActiveDirectory]
CreateMailboxDelay=15

... tells the Wizard to wait 15 seconds after mail-disabling an account before creating the associated mailbox. Quest in-house testing suggests the resolution of this problem may require a delay as long as 33 seconds, but often much shorter. Experiment with shorter values to determine the delay required in your own environment.

Version 4.1.2.7

Updates to existing features in Version 4.1.2.7:

Microsoft Vista support for desktop migrator - The Self-Service Desktop Migrator can now run on user workstations running the Microsoft Vista operating system.
Migration Database Utility - This new utility loads data-location information into the SQL Server database, so that the Data Migration Wizard can migrate mail files from two or more source servers. Without this utility, the Wizard can read mail files from multiple paths, but only from a single Notes server.

Issues Addressed in Version 4.1.2.7:

CR #30720	Erroneous SQLCMD error notations eliminated: Code refinements have eliminated erroneous SQLCMD errors that occurred upon running the Data Migration Wizard if SQLCMD was not specified in the Path. This refinement adds SQLCMD to the Path statement if it was not already included.
CR #36361	"Unable to enable object" errors eliminated: Code refinements have eliminated "Unable to enable object" errors that occurred during runs of the AD Groups Provisioning Wizard when the Wizard used certain external methods to create external contacts. The process inadvertently introduced an invalid SMTP address, but the code refinements now correct the address to preempt the error.
CR #38471	All migrated recurring appointments now work in Outlook 2007: Code refinements have corrected a processing error that left some recurring appointments invisible and/or inaccessible in Outlook 2007 when they were set to occur in the last week of a month. A processing value for this circumstance that worked correctly in Outlook 2003 is not recognized in Outlook 2007, so the appointments did not appear in the Outlook 2007 calendar, and could not be opened when viewed "by Category." The refinement in this release uses a different value to signify the last week of a month.
CR #40123	*Directory Export Unable to import Objects* errors eliminated:** Code refinements have eliminated the Unable to import Objects errors that occurred when the Directory Export Wizard was loading data into the SQL Server database.
CR #40282	SSDM conflict with desktop-search apps resolved: Code refinements have resolved compatability issues between the SSDM and desktop-search applications, which had caused some PST filenames to be corrupted. The System Requirements prohibition against desktop-search apps (added in ver 4.1.1.60 — see below, CR #40283) has been removed.
CR #40331	User Collections features in Notes Migration Manager now appear in proper sequence: The navigation sidebar in the Notes Migration Manager now shows the User Collections features in a sequence where the Send PAB Replicator screen correctly precedes the Locate Notes Data Stores screen. In most cases the Send PAB Replicator feature would be used before Locate Notes Data Stores, but in previous versions the two appeared in reverse order in the navigation sidebar.
CR #41442	*Best reply option for Keep blocking* vs. Unblock Security Alert from Windows Firewall: When a user runs an SSDM migration on a workstation with the Microsoft Vista operating system, Windows Firewall may post a Security Alert that offers a choice between Keep blocking and Unblock. The alert, and the user's reply to it, are irrelevant to the migration process. The Unblock option would prompt the user for administrator credentials, so the Keep blocking** option is the easiest way to dismiss the alert. This information has now been added to the SSDM User Guide (page 21 in Doc ID 256).

Version 4.1.1.64

Issues Addressed in Version 4.1.1.64:

CR #41019	NSD error resolved: Code enhancements have resolved an NSD error that occurred only when migrating calendar data within a particular NSF file for a particular migrating organization.
CR #41115	Erroneous Warning eliminated: Code refinements have eliminated an erroneous program Warning: "Unexpected NULL passed for parameter."
CR #41116	Erroneous "out of memory" error message on Domino server console eliminated: Code refinements have eliminated an erroneous "out of memory" error message that appeared on the Domino server console after a valid syntax error occurred due to corrupted data in the Notes source. The original valid error message will still appear, but the "out of memory" message is now eliminated.
CR #25974 & #40639	Offline migration process documented: The NME User Guide has been updated to document the process for offline migration. See in chapter 4: "How Do I Perform an Offline Migration?"
CR #36092	Personalized ("mail-merge") notification email templates documented: The NME User Guide has been updated to document the creation and editing of "merge" template files used by the Data Migration Manager to generate personalized notification emails to end users upon their migration (the "You've been migrated!" and "Welcome to Exchange!" emails). See in chapter 4: "How Do I Create or Edit a Template for Personalized User-Notification Emails?"
CR #36116	"Create Collection" button documented: The NME User Guide and Notes Migration Manager Help file now document the "Create Collection" button that appears on the Manage Users screen of Notes Migration Manager.

Version 4.1.1.61

Issues Addressed in Version 4.1.1.61:

CR #40619

Merging, mailbox-enabling and provisioning groups when a single forest contains domains with different top-level domain names: The base DN in an ADSI search had previously been too specific for GCs that contain objects due to transitive trust, but the admin now has the option of not specifying a base DN at all.

Version 4.1.1.60

Issues Addressed in Version 4.1.1.60:

CR #35677	Replies to migrated meeting invitations in Outlook 2007 now enabled: Code enhancements have now enabled the reply options to a migrated meeting invitation in Outlook 2007. This was not an issue for Outlook 2003, which processes meeting invitations differently from Outlook 2007.
CR #36488	"Constraint violation" errors resolved: A code enhancement has resolved the constraint-violation errors that occurred when attempting group provisioning on a domain with Windows 2000 domain controllers.
CR #37639	AD group provisioning errors resolved: A code enhancement has resolved group provisioning errors that previously occurred when the last character in a truncated samaccountname string happened to be an invalid samaccountname character.
CR #40283	SSDM conflict with antivirus and desktop-search apps documented: The NME User Guide and SSDM User Guide have been updated to note that some SSDM functions are incompatible with antivirus and desktop-search applications, and to document how to repair corrupted PST file names that may result if desktop-search apps are not disabled prior to running the SSDM. System Requirements in the Quick-Start Guide, NME User Guide, and Release Notes have been updated to note that such apps should be disabled prior to running the SSDM.

Version 4.1.1.44

Issues Addressed in Version 4.1.1.44:

CR #32600	Improved processing of source data: Code refinements now improve the NME components' processing of particular character strings in source data.
CR #33522	Calendar items migration is faster: Code refinements have eliminated the long processing delays that sometimes occurred when migrating certain types of Calendar data.
CR #33945	"You have been migrated" messages: End users' "You have been migrated" messages (generated by the Data Migration Wizard) now appear in Notes as they should.
CR #34356	Previously unreported object-merge errors are now reported: A particular type of mail-enabling error in the AD Object Merging Wizard, which previously was not reported in the program log, is now correctly noted as an error in the log file.
CR #34722	Directory Export Wizard re-run errors resolved: Code refinements have eliminated errors that occurred when a subsequent run of the Directory Export Wizard attempted to load changed or new attributes.
CR #35685	Directory Export Wizard group export errors resolved: Code refinements have eliminated a particular type of error in the Directory Export Wizard, which occurred when attempting to export groups data.
CR #35896	PowerShell calls to create linked mailboxes: Notes Migrator for Exchange now calls PowerShell commands to support linked mailboxes in the Exchange 2007/AD environment.
CR #36023	"Could not load patch SQL file" error resolved: The SQL script called by the Setup utility now correctly sets the product version number, which eliminates the error.

Version 4.1.1.30

Updates to existing features in ver 4.1.1.30:

Support for Notes Custom Attributes - The Directory Export Wizard can now export Notes custom attributes, so the Collection Wizard can use the attributes as a basis for member selection to various collections. The CustomAttr[#] program parameter(s), in the [Notes] section of Global Defaults, let you define which of Notes' custom attributes you want the Directory Export Wizard to capture:

[Notes]
CustomAttr1=Name_of_a_Notes_Attrib
CustomAttr2=Name_of_Another_Notes_Attrib
CustomAttr3=Name_of_Some_Other_Notes_Attrib
CustomAttr4=Name_of_Yet_Another_Notes_Attrib
You may define as many as ten attributes to capture, CustomAttr1 through CustomAttr10. The Directory Export Wizard will then export the data values associated with the defined attributes, and save them in the exported data table in the SQL Server database, so the information will be available to the Collection Wizard. Note that these CustomAttr[#] parameters must be defined in the Global Defaults — not (only) in the Directory Export Wizard's task parameters.
In the Collection Wizard, any such defined custom attribute may be designated as a basis for member selection for a particular collection. For example, you might create a collection by selecting only members whose Attrib_4 value equals "XYZ." In the Add Members screen, the defined custom attributes will appear in the Attribute drop-down list box as additional selectable options.

Issues Addressed in Version 4.1.1.30:

CR #31204

Directory Export of empty source field in group member record: The Directory Export Wizard will now uneventfully process a Notes group member when the source record contains an empty field. That condition in earlier releases introduced performance issues that are now resolved by this code enhancement.

Version 4.1.1.29

Issues Addressed in Version 4.1.1.29:

CR #26064	"Welcome to Exchange" message: The "Welcome to Exchange" message, which sometimes did not display properly in some Outlook 2007 and Outlook Web Access clients, now appears as it should.
CR #26083	SSDM in Silent mode with command-line flags: The SSDM now runs correctly in Silent mode when executed with command-line flags.
CR #28550	Data Migration Wizard and SSDM resiliency: The Data Migration Wizard and SSDM have been refined to better handle a particular rare circumstance in a customer's NSF file.
CR #29506	AD Object Merge Wizard timing issue: A task-execution timing issue in the AD Object Merge Wizard that had caused program failures has now been resolved. Two timing controls have been added to the code, as program parameters in the [ActiveDirectory] section of Global Defaults and Task Parameters: MailEnableAttempts=[#] Determines the maximum number of times the AD Object Merge Wizard will attempt to mail-enable an object in AD before giving up and logging a failure error. The default is 3, but the parameter will accept any value in the range 1 to 1000, inclusive. MailEnableRetryWaitSeconds=[##] Determines the number of seconds the AD Object Merge Wizard will wait between attempts to mail-enable an object in AD. The default is 30, but the parameter will accept any value in the range 1 to 30000 (30000 seconds = 500 minutes), inclusive.
CR #30612	Migration without a Domino server for users with file-system PABs: The Data Migration Wizard can now migrate users whose PABs are all in the file system, when there is no Domino server.
CR #30830	Document support for Notes client 7.0.0 and 7.0.1: The System Requirements in the Notes Migrator for Exchange Quick-Start Guide and User Guide, and in these Release Notes, now specify support for Notes client versions 7.0.0 and 7.0.1. Earlier releases mistakenly cited support for version "7.x," which Quest cannot logically certify since it cannot yet test the versions beyond 7.0.1 that have not yet been released.

Version 4.1.1.23

Issues Addressed in Version 4.1.1.23:

CR #27656

Migration of embedded MIME images: Embedded MIME images now migrate properly.

Version 4.1.1.21

Issues Addressed in Version 4.1.1.21:

CR #24780

Elimination of Outlook Calendar duplicates: Calendar parent objects for meetings in the Notes source no longer migrate as meetings themselves, which had caused some inadvertent meeting duplicates in Outlook.

Version 4.1.1.18

Updates to existing features in ver 4.1.1.18:

Migration of calendar and task folder ACLs, and of delegation rights ("send of behalf of") - The Data Migration Wizard and Self-Service Desktop Migrator both now migrate calendar and task folder ACLs, and the Data Migration Wizard can also migrate Notes' "send on behalf of" delegation rights. Migration of delegation rights is enabled by default, but can be disabled by publicDelegates=0 in the [General] section of the Global Defaults or Task Parameters.
Support for MS Daylight Savings Time patch - Notes Migrator for Exchange now correctly migrates items, including recurring Calendar events, regardless of whether the Microsoft 2007 Daylight Savings Time (DST) patch has been installed on the admin's migration workstation.
Important Note: Even with this new support for the DST patch, an admin should run a correction script from Lotus to correct appointment times in the source before migrating any data with Notes Migrator for Exchange. The Lotus script should be run on the Domino server, on every source mail file in the organization, to fix the appointment times on recurring calendar items affected by the DST change: appointments that fall between March 11 and 31, 2007, and those that fall between October 28 and November 3, 2007. If the Lotus script is not run before the migration, the migrated items will appear an hour later than originally scheduled, even though the items will display the correct timezone (with "-old" appended) due to the NME 4.1.1 enhancement.
Support for Outlook 2007 - All Wizards and other component applications of Notes Migrator for Exchange now support Outlook 2007.

Issues Addressed in Version 4.1.1.18:

CR #22474	Directory Export generation of aliases for manually entered domains: The Directory Export Wizard now generates TargetAliases (into the SQL Server database table) for domains that are manually added to the Domains table in the Discover Notes Info Configuration screen of Notes Migration Manager.
CR #22480	Migration of duplicate PABs and archives from SSDM eliminated: The Data Migration Wizard no longer attempts to migrate PABs and archives that have already been migrated by the Self-Service Desktop Migrator. The SSDM Statistics Collection Wizard still adds PABs and archives migrated by the SSDM to the Locate Notes Data Stores form, as before, but in prior releases the Data Migration Wizard attempted to migrate the duplicates.
CR #22481	Preservation of keyfilename value in notes.ini after launch of SSDM: In the last release, the Self-Service Desktop Migrator would overwrite the keyfilename value (which corresponds to the Notes User ID file name), but that value is now preserved.
CR #22482	Provisioning larger numbers of groups: The AD Groups Provisioning Wizard can now provision larger numbers of groups.
CR #22485	Group provisioning issues in Exchange 2007 resolved: In some network configurations, groups that had been provisioned into AD for an Exchange 2007 target environment were not mail-enabled as they should have been. This problem is now fixed.
CR #22834	MboxFromContact program parameter restored: This parameter in the [Active Directory] section of Global Defaults and Task Parameters had been inadvertently disabled in the preceding version, but is now restored. MboxFromContact tells the Data Migration Wizard whether to convert a contact into a mailbox when mailbox enabling. This feature is off (0) by default, since in a typical scenario no contacts should remain after the AD Object Merging Wizard has run (to merge contacts into existing AD objects). The parameter permits the enabling of the feature by MBoxFromContact=1, for some rare circumstances where the option is preferrable.

Version 4.1.0.12

New features in ver 4.1.0.12:

Exchange 2007 support - Notes Migrator for Exchange now supports migration to Exchange 2007, and mailbox creation with PowerShell for Exchange 2007 servers.
Notes 7 support - Notes Migrator for Exchange now supports migration from Notes version 7.
Mail-merge user-notification emails - The Data Migration Wizard can now generate mail-merge emails to end users, to notify them (in their Notes mailboxes) that they've been migrated, and/or to welcome them to Exchange and Outlook (in their new Outlook mailboxes). The features let you customize the Subject and From fields, and designate a suitable template for the message body.
Preservation of Notes ACLs - NSF database ACLs are now mapped to each Exchange folder. Any ACLs that are set for the migrated NSF are applied to all the folders in the Exchange mailbox.
Preservation of Notes follow-up flags - The migration process now preserves, in Outlook, any follow-up flags in the Notes source.
Multiple-user selection in Notes Migration Manager - The Manage Users and Manage Groups screens now let you define a new collection by selecting multiple members for inclusion from the Collection members table. To define a multi-member collection: Press and hold the Ctrl key while clicking on each additional member you want to add, and then click Create Collection.
New Program Parameters documentation - The Program Parameters Reference, previously available only by separate download, is now included in the primary product kit and installed with the other PDF-format documentation.
Log files now document system information - Notes Migrator for Exchange applications now log system information at the top of each log file, as appropriate (per application): versions of the Outlook and Notes clients installed on the migration workstation, versions of the Domino and Exchange servers, and versions of the Notes clients. This feature will help Quest Support staff recreate a problem, to analyze and solve it.
Term licenses - Notes Migrator for Exchange now supports limited-term, fully-functional licenses ("term licenses"), in addition to demo (trial) licenses and perpetual fully-functional licenses.

Updates to existing features in ver 4.1.0.12:

Wizard "memory" - All of the Wizards now "remember" program settings, and recall them from one run to the next on any given workstation.
Enhanced mail-forwarding controls - Mail-fowarding features that were previously controlled only by program parameters are now more easily configured from the Data Migration Wizard's primary user interface. The associated options have also been expanded and reorganized for greater admin control over these features.
Enhanced "silent mode" for Self-Service Desktop Migrator - The Self-Service Desktop Migrator now permits greater admin control over which screens and which fields will appear to the user in the GUI, and the values that will prevail for fields that are hidden from the user. These program customizations are accomplished by a set of program parameters, documented in Chapter 4 of the Notes Migrator for Exchange User Guide.
Differentiation of Notes mail-in databases - The Directory Export Wizard now recognizes mail-in databases as distinct from other (user) mailboxes, and identifies them as such in Notes Migration Manager, in the Object Type column of the Objects found table.
Improved data-table rendering in Notes Migration Manager screens - Improvements in the fundamental table-rendering functions of Notes Migration Manager help the program resize all of its data tables better, load data contents quicker, and handle very large collections more efficiently than in previous releases.
New Remove NAB button in the Find NABs screen - A Remove NAB button has been added to the Find NABs screen in Notes Migration Manager, so an admin can remove a NAB from the displayed list of NAB data sources. The new button lets an admin exclude a particular NAB from consideration as a source of information used by other Quest programs to provision Active Directory, identify users and other objects for migration, and facilitate accurate mail-forwarding for the duration of the migration.
Improved data management in SQL Server database - The widths of several fields have been expanded to better accommodate longer data values, and the code has been amended to better handle any field overruns that may still occur. An overrun no longer interrupts a program run, but is now simply reported as program Warnings in the log file.
Restored migration summary statistics in log file - The Data Migration Wizard now reports a summary of its migration statistics at the end of its program log file, as the corresponding batch-migration application did prior to version 4.0.
Recognition of Notes DJXMail template - The Data Migration Wizard now recognizes and migrates the DJXMail template, popular in Japan, as a standard mail template.

Issues Addressed in Version 4.1.0.12:

Data Migration Wizard now finds Sent and Draft items (resolves CaseID 476493-1): The Data Migration Wizard and Self-Service Desktop Migrator now recheck the Sent and Drafts views of the Notes source, by an alternate method, if their first method finds no Sent or Drafts items. This solves a problem that occurred in some configurations where the applications appeared to not "see" items in the Sent and Drafts views, and therefore did not migrate them.
Data Locator Wizard now correctly locates on second run via MailFilePath (resolves CaseID 478078-1): A coding error in the Data Locator Wizard has been corrected to eliminate a rare problem whereby the Wizard failed to re-import a local NSF file when the Wizard was run a second time using the MailFilePath method to locate the file.

Version 4.0.0.35

Improved handling of calendar items (resolves Case ID 468360): The Data Migration Wizard now correctly migrates certain types of calendar items so that they can be opened in Outlook.
Tagging of migrated PAB entries with Notes source folder category is now optional (resolves Case ID 471049): A new program parameter has been defined in the [PAB] section of Global Defaults and Task Parameters, to make the tagging optional.

[PAB]
SourceFolderCategory=1
... tells the Data Migration Wizard to tag migrated PAB entries with the Notes source folder category, as it always did in prior releases. By default (0) the Wizard will not tag migrated PAB entries.
Timezone differentials in QSCHED functions at some European sites are now resolved (resolves Case ID 486011): The QSCHED application now runs tasks in local time, the same as they were scheduled.

Version 4.0.0.34

Removing forwarding when not migrating data no longer generates errors: Exchange-to-Notes mail-forwarding rules can now be removed in an independent run of the Data Migration Wizard (without migrating data), without generating any errors to the log as in prior releases.
Data Migration Wizard now falls back to a more generic language resource to name Outlook folders if it cannot find the folder names for a more specific language variant (resolves Case ID 470682): The Global Defaults, Task Parameters, and notesdtapp.ini file contain sections that specify migrated Outlook folder names, per language, and the Data Migration Wizard refers to those resources when naming new Outlook folders. But if the specified locale is associated with a particular variant of a language--for example, French as spoken in France vs. Canada vs. Belgium, etc.--and the Wizard can't find a section for that variant, then it will instead consult a section for a more generic level of the language. In Quebec, for example, if the Wizard can't find a section for [FRC] (Canadian French), it will instead use the folder names specified in [FR] (generic French). In previous releases, the Wizard would default to English-language folder names if it couldn't find a section for a particular language variant.
Alternatively, an administrator could create a new section in the Global Defaults and/or notesdtapp.ini for the particular language variant associated with his or her locale. The three-letter section name must conform to the TLA (three-letter acronym) defined by Microsoft: http://www.microsoft.com/globaldev/reference/winxp/langtla.mspx.
Data Migration Wizard no longer provisions disabled aliases: The Wizard now provisions into AD only the aliases that are enabled in the SQL Server database. Any aliases marked in the database as disabled will not be provisioned.

Version 4.0.0.31

Data Migration Wizard now correctly migrates calendar update items that have not yet been accepted or declined: In previous releases, such update items were lost for any recipient who had not accepted or declined the update prior to migration.
Admin can now optionally suppress displays of item-count estimates on Self-Service Desktop Migrator Progress screen (resolves Case ID 465117): Two new program parameters in the [General] section of notesdtapp.ini let you suppress the display of estimated item counts:

reportMofN=0
... tells the Wizard to display "Processed M item(s)" instead of "Processed M of N item(s)."

reportPct=0
... tells the Wizard to not update the title, and to suppress the percent value in the progress bar.
The defaults for these parameters (1 in both cases) tell the Wizard to show the full "Processed M of N item(s)," update the title, and show the percent value in the progress bar.
Data Migration Wizard now supports mapping a single Notes attribute to multiple MAPI attributes. (resolves Case ID 468451).
Documentation Updates: All product documentation, both the printable PDF guides and the on-line Help systems, have been updated to address feedback from customers and Quest support staff. The updates include new material to elaborate on certain topics, clarifications and sidebar notes where appropriate, refinements to the System Requirements, and corrections of a few typographical errors.

Version 4.0.0.27

Self-Service Desktop Migrator now supports migration of non-ASCII characters from pre-5.0.11 versions of Notes client: When converting Notes rich text to MS RTF, pre-5.0.11 versions of nxrtf.dll convert non-ASCII characters to question marks. These two new features permit the migration of non-ASCII characters--for example, Chinese or Thai characters--by two different methods. One feature tells the program to use a later version of nxrtf.dll, if available. If a later version of nxrtf.dll is not available, the other feature can manually correct the conversion limitation of a pre-5.0.11 nxrtf.dll. Both features are controlled by program parameters in the [Notes] section of notesdtapp.ini:
- UseAppNxrtfDLL=<#>: Binary parameter (0 or 1), 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. This feature permits the migration of non-ASCII 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 Self-Service Desktop Migrator 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 (for example, c:\lotus\notes\) 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 below for an alternate solution to the problem.
- QuoteNonAsciiCharsInRTF=<#>: Binary parameter (0 or 1), 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. 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.
Data Migration Wizard now supports journal migration from Notes R6.5.5: An internal code refinement in the Data Migration Wizard now permits the migration of journals from a Notes R6.5.5 client.
Data Migration Wizard now supports up to 64K of aliases when creating a mailbox: The added capacity lets the program conceivably add more than 2,000 to 3,000 aliases per mailbox.
Notes Data Locator Wizard now supports rediscovery of a mail file with a quota that has changed since the Wizard first discovered the file: In previous releases the Wizard would generate an error when the quota of a previously located mail file was changed, and then the Wizard was run again to locate the file again.
RTF content handling improved in Self-Service Desktop Migrator: This internal code enhancement corrects a problem that occurred in previous releases, in which the Desktop Migrator misinterpreted certain conditions within RTF content to mistakenly truncate a message body.
All documentation has been updated: All three PDF documents and all on-line Help systems have been updated with elaborations, additions, and corrections to accommodate recent feature additions and enhancements, recent changes to system requirements, and recent documentation feedback from engineers and support staff.

Version 4.0.0.24

Data Migration Wizard and Self-Service Desktop Migrator now support migration of images (resolves Case ID 453745): A new program parameter has been added for both batch migrations and per-desktop migrations (in the [Exchange] section of Global Defaults, Task Parameters, and notesdtapp.ini) that now permits the selective enabling/disabling of Microsoft's RTF conversion, which strips embedded images from migrated mail, appointments, and tasks.
The RewriteRTF parameter value is a single digit, 0-7 (default 7), that specifies which (if any) of migrating mail, appointment, and task items the Wizard should pass through Microsoft's rich-text converter. The Microsoft RTF conversion in many cases will refine the exported compound document format from Notes' own converter, but can now be disabled if the preservation of embedded images is more important than the format refinement. However, not processing the RTF will result in Calendar/Tasks not synchronizing with Windows Mobile 2005 devices. The parameter value must be a single digit in the range 0 to 7, to indicate which item types should be processed by Microsoft's RTF conversion:

0: None
1: Mail Only
2: Appts Only
3: Mail + Appts
4: Tasks Only
5: Mail + Tasks
6: Appts + Tasks
7: Mail + Appts + Tasks
Directory Export Wizard now supports export from NSF files larger than 2 GB: A database creation script associated with the Directory Export Wizard has been enhanced to permit correct statistics gathering from NSF files larger than 2.0 GB.
Data Migration Wizard now permits migration of certain NSF files (resolves Case ID 453449): A code refinement now eliminates errors that previously caused fatal application errors for certain NSF files.
Data Migration Wizard now migrates certain DocLinks (resolves Case ID 457836): The DocLinks buffer associated with migrating Notes DocLinks has been amended to permit the uneventful migration of NSF files containing DocLinks.
Data Migration Wizard and Self-Service Desktop Migrator now both support migration of Journals: A code refinement in the Data Migration Wizard now permits migration of Journals, as the Desktop Migrator has in previous releases.
Obfuscated passwords: All passwords that are written to log files and program parameters are now obfuscated.
Directory Export Wizard performance enhancements: The Directory Export Wizard now uses enhanced importing and query methods to import data stores and data store owners, which dramatically improve program performance when running the Wizard after an earlier run has already loaded some data into the SQL Server database.
Elimination of excessive trivial warnings: An internal code method that previously generated excessive (but trivial) warning messages during the reformatting of MS RTF message bodies, and left excessive temp files in the %temp% directory, has been improved. The warnings and excessive temp files no longer occur.

Version 4.0.0.18

Support for Notes systems with no global domain document: The Directory Export Wizard can now be run for a Notes system with no global domain document.
Context sensitivity for on-line Helps: The on-line Help systems for all product Wizards and other applications are now context-sensitive, to display the pertinent Help topic relative to the current display when a user call for the Help.
Support for the multi-user install configuration: The Self-Service Desktop Migrator now supports the multi-user install configuration. To enable this support, edit the notesinipath parameter in the [Notes] section of notesdtapp.ini. For example:

[Notes]
notesinipath=h:\notesclient\notes.ini
Exported data now includes Notes Short Name: The Notes Directory Exporter now captures the Notes Short Name and loads its values into the UserId column of the SQL Server database. The Notes Short Name is often a useful value to use when matching objects in the AD Object Merge Wizard.
Erroneous attachment timestamps: The Data Migration Wizard can now process attachments with erroneous 31st-century timestamps (erroneously assigned in Notes environment) without crashing.

Version 4.0.0.13

Free/Busy synchronization from Notes to Exchange through Notes Connector: The legacyExchangeDN can now be maintained through merging and mailbox-enabling, to support free/busy synchronization from Notes to Exchange through the Notes Connector. To remove the free-busy properties to stop Exchange from looking in Notes for users' free-busy information, you must select Remove Forwarding in the Exchange Administrative Operations. This also removes the free/busy forwarding, and is required even if mail-forwarding is not set. If you need free/busy synchronization through the Connector, set the following configuration setting:

[ActiveDirectory]
AlwaysUseOldExchDn=1
The default value for this parameter is 0, which is appropriate for sites that do not require free/busy synchronization through the Connector.
More options for gathering Notes PABs onto central server: The PAB Replicator Wizard now offers a choice of three forms to send to users to automate their copying PABs to a centralized location:
- PabReplicator.CopyToServer: Copies PABs to the specified Domino server directory; does not use mail file. (This is the same form that shipped with the initial release of 4.0.)
- PabReplicator.CopyOrSyncToMailFile: Copies PAB entries to mail file, or performs iNotes sync if available. Works with iNotes and non-iNotes mail files.
- PabReplicator.SyncToMailFile: Performs iNotes sync; works only with iNotes mail files.
The AD Object Merge Wizard is now compatible with SQL Server 2000.
Support for Blackberry Devices: The data-migration process has been enhanced so that migrated calendar data will now synchronize with Blackberry devices.

Version 4.0.0.6 (Initial 4.0 Release)

Project-Based User Interface: The interface to Notes Migrator for Exchange has changed. All components that are run from the migration workstation are now launched from a single console, called the Notes Migration Manager. The Notes Migration Manager is organized to lead you through your migration tasks, providing easy access to all the information and tools you need to get the job done.
The "Project View" of Notes Migration Manager provides a high-level view of the status of your migration project, showing you at a glance how many users have migrated, your overall data migration rates, and more. Other forms let you set default settings for reuse from component to component, and from one migration run to another. The Notes Migration Manager is also the platform for launching the various Wizards that perform the critical discovery, provisioning and migration tasks. Other forms let you monitor recent runs, schedule tasks, and view reports and logs.
Reporting: Notes Migrator for Exchange now generates a number of reports to make your pre-migration planning easier, and to keep you on top of your ongoing migration. After you run through the data gathering steps, you can review reports that describe your Notes environment: what Notes servers you have, what domains you are using, what users and resources and groups you have, where they reside, and how much data they have to migrate. These reports can help you plan both your migration strategy and your storage needs on the Exchange side. As your migration progresses, other reports summarize who and what have been migrated, which Notes data stores have been migrated, and what groups have been provisioned to Active Directory.
Task Scheduling: Notes Migrator for Exchange now includes the ability to schedule migration operations that you want to run periodically, or at a later time. This lets you develop a periodic schedule of Notes directory exports followed by group provisioning runs, for example, to keep your Notes and Exchange distribution lists synchronized. It also lets you configure a data migration run during your work day, but schedule it to run after hours when network and server loads are low.
Central Database Shared by Migration Workstations: A central database, stored on a Microsoft SQL Server, is now used for the primary storage of all migration data. Notes Migrator for Exchange version 4.0 requires access to a Microsoft SQL server. You may use your existing SQL Server 2005 or 2000, or install a new SQL server. Microsoft SQL Server 2005 Express is bundled with the full installation kit for Notes Migrator for Exchange. To use a preexisting SQL Server, you must have the SQL Native client installed on each migration workstation.
Collections: To provide flexibility, the mailboxes to be migrated and the groups to be provisioned are grouped into collections. When migration tasks are performed on many users or groups, a collection is used to define the set of users or groups. These collections are stored in the central database, and replace the UsersToMigrate.TSV and GroupsToProvision.TXT files that were used in earlier versions of Notes Migrator for Exchange. Collections are defined with the Collection Wizard, which can either import a list from a TSV file or generate a collection based on SQL queries into the central database.
Licensing: Notes Migrator for Exchange now requires an activation key when you purchase the product or arrange for an evaluation trial. You will not be able to migrate more users than you are licensed to migrate, although any user who has already been counted against the license limit may be re-migrated any number of times.
Enhancements to existing Notes Migrator for Exchange features:
- Log Viewer features:
  - You can now optionally avoid contacting the Internet when using the Log Viewer at sites that do not have Internet access. This will provide a performance enhancement for sites that are blocked from the Internet.
  - The Log Viewer now provides more detailed reports, an ordered listing of errors, with user list and the solution details from the solution website.
- Group provisioning enhancements:
  - Collections of groups may now be provisioned to the Active Directory container of your choice.
  - You may now use the provisioning GUI to choose the type and scope of AD group to create when provisioning groups in Active Directory
- Resources can now automatically be assigned the MAPI parameters that make the resource mailboxes act as Exchange resources during migration.

If SMTPForwardingAddress=0	If SMTPForwardingAddress=1
user@smtp.domain.com@DOMINODOMAIN smtp:user@smtp.domain.com@DOMINODOMAIN	user@smtp.domain.com smtp:user@smtp.domain.com