See the "Legal Notice" section later in this document for important information.

Welcome to the Microsoft Transporter Suite for Lotus Domino. In addition to the information in this document, please see the Transporter Help file (MTHelp.chm) for troubleshooting information and other details. This document contains the following sections:

Before You Begin

You must perform the following tasks before running the Transporter Suite:

  • On the Exchange Client Access server, enable Exchange impersonation for the account that will be migrating mail. Impersonation allows the account to temporarily authenticate as another user in order to add information to that user's mailbox. Use the following Windows PowerShell command to enable impersonation:

    Add-ADPermission -Identity (get-exchangeserver).DistinguishedName -User (Get-User -Identity [UserName] | select-object).identity -extendedRight ms-Exch-EPI-Impersonation 

Prerequisite Downloads

Prerequisites

This section lists the supported prerequisites for installing and running the various components of the Transporter suite. See MtHelp.chm for additional details about the minimum account rights to perform these tasks.

Setup Prerequisites

Operating system Lotus Notes Lotus Domino Other

32-bit or 64-bit Microsoft Windows XP with latest updates

or

32-bit or 64-bit Windows Server 2003 with latest updates

Lotus Notes 6.x or 7.x installed on server or workstation(s) where Transporter is installed

Lotus Domino 6.x or 7.x for interoperability

Lotus Domino 5.x, 6.x or 7.x for migration

Exchange Management Console

or

Microsoft Management Console 3.0

Windows PowerShell 1.0

Directory Connector Prerequisites

In addition to the Setup prerequisites:

  • Microsoft Exchange Server 2007 Hub Transport and/or Mailbox server roles are supported

Free/Busy Connector Prerequisites

In addition to the Setup prerequisites:

  • Microsoft Exchange Server 2007 Hub Transport and/or Mailbox server roles are supported

  • Exchange MAPI client

User Migration Prerequisites

In addition to the Setup prerequisites:

  • Exchange Management Console

Mail Migration Prerequisites

In addition to the Setup prerequisites:

  • Exchange Management Console

Application Migration Prerequisites

In addition to the Setup prerequisites:

  • Microsoft Windows SharePoint Services 3.0

or

  • Microsoft Office SharePoint Server 2007

Known Issues

Known issues are documented in the Troubleshooting topic in the MTHelp.chm file. Additional issues found in this release of the Microsoft Transporter Suite for Lotus Domino are described in the following sections:

  • Setup

  • Calendar Interoperability

  • SMTP Mail Routing

  • Mailbox Migration

  • Application Migration

Setup

  • Upgrade from previous (beta) versions of Microsoft Transporter is not supported. Uninstall the old version using Microsoft Windows Add/Remove Programs before installing Microsoft Transporter.

  • If you want to uninstall and reinstall Transporter with the same configuration information, back up the configuration files in the \Microsoft Transporter\Microsoft Transporter Tools\Config folder prior to uninstalling Transporter.

Calendar Interoperability

  • Free/busy lookups don't work against Lotus Domino servers started as an application. To resolve this issue, start the Lotus Domino server as a Windows Service.

  • Meeting invitations sent from Lotus Notes 6.5.5 or greater display correctly in Microsoft Office Outlook, but the invitations include an iCal attachment. This attachment can be ignored.

  • Meeting invitations sent from Outlook lose attachments when routed to Lotus Notes.

  • Recurring meetings between Outlook and Lotus Notes users cannot be updated because the systems process recurring meetings differently. To update recurring meetings, cancel the original meeting and then create a new meeting.

  • Meeting requests with Rich Text created by Lotus Notes users are displayed as plain text by Outlook.

  • Meeting counter proposals/propose new time between Outlook and Lotus Notes users do not work. Lotus Notes users receive a tentative acceptance rather than a counter proposal.

  • A meeting with custom recurrence sent from a Lotus Notes user to an Outlook user is displayed as an e-mail message in Outlook.

  • If there is no Free/Busy public folder, the following error occurs: "Cannot find Exchange Server error when trying to create new Free/Busy Connector." This error prevents the Free/Busy Connector from being created. Create a Free/Busy public folder, and then create the Free/Busy Connector.

  • If Transporter is installed on a server that is running Exchange Server 2007 with the Mailbox and the Client Access server roles, Free/Busy lookups won't work until Publicvdir SSL is disabled. To disable Publicvdir SSL, right-click My Computer, select Manage and then click Internet Information Services (IIS) Manager. Navigate to Web Sites/Default Web Site/Public, and then open the Properties dialog box. Click the Directory Security tab, and then click Secure Communications Edit. Clear the Require secure channel (SSL) option, and then click OK. Restart IIS by typing iisreset at the command prompt for this change to take effect.

  • When a Lotus Notes 7.0.2 user creates a meeting and lists Outlook users, Notes does not always send the meeting to the first Outlook person. Remove this user's name and add the user again to resolve this issue.

SMTP Mail Routing

  • Lotus Domino 5 is not supported for SMTP mail routing because it does not support native MIME or iCal. Implement mail routing between Lotus Domino 5 and Exchange 2007 by using the Microsoft Exchange Server 2003 Connector for Lotus Notes on an Exchange Server 2003 server.

  • Embedded pictures sent from Outlook to Lotus Notes are not displayed because Lotus Notes does not support the default Outlook file format (.png).

Mailbox Migration

  • Read/Unread marks only migrate if the Notes user ID file on the computer performing the migration has Manager Access Control List (ACL) rights to the user's mail database.

  • If Transporter returns the error "Could not retrieve E12 Web Services URL", use the -ClientAccessServer parameter in the Move-DominoMailbox cmdlet to identify the Client Access server running Web Services.

  • When migrating recurring meetings, the last instance of the meeting is not migrated. Apply the Exchange Server 2007 QFE to prevent this problem.

Application Migration

  • Last-accessed information is disabled in Lotus Notes applications by default. If this value is not enabled, Transporter cannot accurately report this information.

  • Transporter must run on the target computer that is running Microsoft Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server in order to perform application migrations.

  • Private documents do not migrate because access is limited to the document author. The document author can grant access to the Lotus Notes user ID that is used to migrate the application prior to the migration.

  • Doclinks are converted to URLs during migration. To access the linked document, the HTTP task must be loaded on the Lotus Domino server that hosts the application containing the linked document.

  • Security-enabled sections are not migrated. Data in standard sections migrates, but the section (collapsable) functionality does not migrate.

  • A PowerShell warning may appear when the Transporter Management Shell starts, or when running the report scripts from the Microsoft Transporter Tools GUI. The warning "……Windows PowerShell snap-in Microsoft.Exchange.Management.PowerShell.Admin is not installed on this machine.." is returned on computers that do not have the Exchange Management Console installed and can be ignored.

  • If the -Verbose parameter is used with the Get-DominoApplication cmdlet, the message "Mapping Content Type Template XML file,…\MappingContentTemplate.xml is not found" is returned. This information is not accurate, and it can be ignored.

Legal Notice

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2007 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, ActiveSync, Internet Explorer, Outlook, and SharePoint are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.