Quest® Notes Migrator for Exchange

Version 4.1.5.17

Release Notes

June 2008

(Doc ID 171)

 


Contents

Welcome to Notes Migrator for Exchange

New in this Release

Resolved Issues and Enhancements

Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

For More Information


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 or 2007 environment with Outlook clients. Notes Migrator for Exchange can:

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

The Wizards that can be launched from Notes Migration Manager:

 


New in this Release

New features in Version 4.1.5.17:

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

 


Resolved Issues and Enhancements

Issues addressed in Version 4.1.5.17:

None in this release.
For resolved issues and enhancements 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.

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.

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 incompatabilities, 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 administators 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.

Important Notes:

 


System Requirements

Notes Migrator for Exchange requires the installation and configuration of several 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. In addition to the Quest components, a migration requires the installation and proper configuration of other, non-Quest applications including the Domino and Exchange servers, Active Directory, and the Notes and Outlook clients. The full installation and configuration requirements are therefore more detailed than the requirements summary provided here. See the Notes Migrator for Exchange Quick-Start Guide for complete System Requirements, including tips for how 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 Notes Migrator for Exchange version 4.1.0.0:

On the Domino server:
  • Must be running Lotus Domino version 4.6.x, 5.x, 6.x, 7.x, or 8.x.
On the Exchange server:
  • Must be running Exchange 2007, Exchange 2007 SP1, or Exchange 2003.
On each administrator workstation (running the Notes Migrator for Exchange admin components):
  • Workstation OS must be Windows XP (32 bit) SP2 or higher, or Windows 2003 Server (32 bit) SP1 or higher. 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 meeting 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 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).
  • 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, 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 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 Self-Service Desktop Migrator):
  • Must be running Microsoft Windows 2000 SP4; or Windows XP SP2 Professional Edition; or Windows Vista Business, Enterprise or Ultimate Editions.
  • Must be running Outlook 2000, 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, or 8.0.0. 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.

 


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) version 4.1.0.0 zip-bundled distribution file contains the following component applications, accessories and documentation files:

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:

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.

 


Copyright & Trademark Notices

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.

 

© 2008 Quest Software, Inc. ALL RIGHTS RESERVED.

 

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT 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.

 

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

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.

 




Other Recent Releases

New & Updated Features and Issues Addressed in Version ...
 •  4.1.4.26  •  4.1.4.25  •  4.1.4.23  •  4.1.4.20  •  4.1.4.15
 •  4.1.3.14  •  4.1.2.13  •  4.1.2.7  •  4.1.1.64  •  4.1.1.61  •  4.1.1.60
 •  4.1.1.44  •  4.1.1.30  •  4.1.1.29  •  4.1.1.23  •  4.1.1.21  •  4.1.1.18  •  4.1.0.12 (initial 4.1 release)
 •  4.0.0.35  •  4.0.0.34  •  4.0.0.31  •  4.0.0.24  •  4.0.0.18  •  4.0.0.13  •  4.0.0.6 (initial 4.0 release)

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:


Version 4.1.4.23

New features in Version 4.1.4.23:

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:

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:

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:

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:

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:

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:

Updates to existing features in ver 4.1.0.12:

Issues Addressed in Version 4.1.0.12:


Version 4.0.0.35


Version 4.0.0.34


Version 4.0.0.31


Version 4.0.0.27


Version 4.0.0.24


Version 4.0.0.18


Version 4.0.0.13


Version 4.0.0.6 (Initial 4.0 Release)