Microsoft Transporter Suite

7/31/2019 Microsoft Transporter Suite

1/185

Microsoft Transporter Suitefor Lotus Domino

1 Microsoft Transporter Suite for Lotus Domino1


2/185

This is a preliminary document and may be changed substantiallyprior to final commercial release of the software described herein.

The information contained in this document represents the currentview of Microsoft Corporation on the issues discussed as of the date

of publication. Because Microsoft must respond to changing marketconditions, it should not be interpreted to be a commitment on thepart of Microsoft, and Microsoft cannot guarantee the accuracy ofany information presented after the date of publication.

This white paper is for informational purposes only. MICROSOFTMAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility ofthe user. Without limiting the rights under copyright, no part of thisdocument may be reproduced, stored in, or introduced into aretrieval system, or transmitted in any form or by any means(electronic, mechanical, photocopying, recording, or otherwise), orfor any purpose, without the express written permission of MicrosoftCorporation.

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

2009 Microsoft Corporation. All rights reserved.

The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted hereinare fictitious. No association with any real company, organization,product, domain name, e-mail address, logo, person, place, or eventis intended or should be inferred.

Microsoft, Active Directory, Internet Explorer, Outlook, SharePoint,Windows, and Windows NT are either registered trademarks ortrademarks of Microsoft Corporation in the United States and/orother countries.

All other trademarks are property of their respective owners.



3/185

Table of Contents

Table of Contents .......................................................................................... 3

Introduction ................................................................................................... 6

Gathering Information ................................................................................... 9

Lotus Domino Servers ...................................................................................... 9

Routing and Replication Topologies ............................................................... 10

Network Information ...................................................................................... 10

Backup and Restore Procedures .................................................................... 11

Client Information .......................................................................................... 11

User Data ....................................................................................................... 12

Other Information .......................................................................................... 12Diagramming ................................................................................................. 14

Building a Test Lab and Evaluating Options ................................................. 16

One Phase or Two ........................................................................................ 18

Single-Phase Migration .................................................................................. 18

Advantages ............................................................................................. 18

Disadvantages ........................................................................................ 19

Multiple-Phase Migration ................................................................................ 19

Advantages ............................................................................................. 19

Disadvantages ........................................................................................ 20

Coexistence ............................................................................................ 20

Long-Term Coexistence .......................................................................... 21

Installation Tasks ......................................................................................... 21

Installing Transporter Suite Components on an Exchange Server ................22

Dependencies ......................................................................................... 22

Installing Transporter Suite Components on a Windows SharePoint ServicesServer ............................................................................................................. 24

Dependencies ......................................................................................... 24

Installing Transporter Suite Components on a Migration Workstation ..........24

Dependencies ......................................................................................... 24Installing Transporter Suite Components on a Domino Server ......................24

Dependencies ......................................................................................... 24

Single-Phase (Big-Bang) Migrations ............................................................. 26

Configuring One-Way DirSync ........................................................................ 26

Domino to Exchange ............................................................................... 26

Two-Phase (Coexistence) Migrations ............................................................ 34



4/185

Namespace Design ........................................................................................ 34

Using disparate namespaces to route mail............................................34

Shared Namespace Design ..................................................................... 35

Address Book Design ..................................................................................... 37

Using a single Name and Address Book .................................................38

Using multiple Name and Address Books ...............................................38Configuring Two-Way DirSync ........................................................................ 41

Prerequisites .......................................................................................... 41

Configuration .......................................................................................... 41

Use .......................................................................................................... 46

Configuring Free/Busy Lookup ....................................................................... 50

Exchange configuration .......................................................................... 50

Domino Configuration ............................................................................. 58

Configuring SMTP Connectivity ...................................................................... 61

Using Disparate or Shared/Subdomain Namespace design ...................61

Using Shared/Smarthost Namespace design .......................................... 77Testing and Other issues to note ............................................................ 86

Removing SMTP connectors ...................................................................88

Tasks Common to All Migrations .................................................................. 89

Migrating Users .............................................................................................. 89

Prerequisites ........................................................................................... 89

Configuration/Use ................................................................................... 90

Migrating Groups ........................................................................................... 94

Prerequisites ........................................................................................... 94

Configuration/Use ................................................................................... 94

Migrating Mailboxes ....................................................................................... 99

Prerequisites .......................................................................................... 99

Configuration/Use ................................................................................. 100

Post-migration tasks ............................................................................. 105

Migrating PABs and Personal Archives ......................................................... 106

Prerequisites ........................................................................................ 106

Configuration/Use ................................................................................. 107

Troubleshooting ......................................................................................... 115

Troubleshooting Directory Synchronization ................................................. 115

Domino to Exchange ............................................................................. 116Exchange to Domino ............................................................................. 116

Troubleshooting Free/Busy Requests .......................................................... 118

Make sure Notes.ini file is Available ..................................................... 118

Verify Servers Configuration ................................................................. 118

Verify Firewall Port Configuration ......................................................... 120

review Domino Person Documents ..................................................... 122



5/185

Turn On Additional Logging .................................................................. 125

Additional Information on the Free/Busy Architecture .........................127

Troubleshooting Mail Flow ........................................................................... 139

Diagramming the message paths ......................................................... 139

Messages stuck in Exchange (no NDR) ................................................. 139

Additional logging ................................................................................. 145Known compatibility issues .................................................................. 147

Troubleshooting User Migration ................................................................... 149

Active Directoryrelated issues ............................................................ 149

Exchange Serverrelated issues ........................................................... 150

Other items to note .............................................................................. 151

Logging ................................................................................................. 151

Troubleshooting Group Migration ................................................................ 151

Logging ................................................................................................. 152

Troubleshooting Mailbox Migration .............................................................. 153

Extraction Versus Injection ................................................................... 153Extraction issues ................................................................................... 153

Transformation/Injection issues ............................................................ 154

A note on addressing ............................................................................ 157

Logging ................................................................................................. 158

Troubleshooting PAB and Personal Archive Migration .................................159

Extraction versus injection ................................................................... 159

Extraction issues ................................................................................... 160

Transformation/Injection issues ............................................................ 161

Logging ................................................................................................. 161

Appendixes ................................................................................................ 162

Customizing Directory Synchronization ....................................................... 162

Adding and Removing Attributes .......................................................... 163

Mapping Functions ................................................................................ 169

Determining the Internal Name of Directory Attributes .......................176

Other Directory Synchronization Topics ...................................................... 177

MIIS ....................................................................................................... 177

Using a different Domino domain name to represent Exchange Server.............................................................................................................. 177

Upgrading DirSync from Exchange Server 2003 Lotus Notes Connectors

.............................................................................................................. 178Directory Migration Matching Algorithm ...................................................... 180

Multiple Free/Busy Connectors .................................................................... 182

General PowerShell Information .................................................................. 184

Additional Information ............................................................................... 185



6/185

IntroductionThe Microsoft Transporter Suite for Lotus Domino is used for coexistencebetween Lotus Domino and Active Directory with Exchange Server 2007, and

migration from Lotus Domino to Active Directory, Exchange Server 2007 andWindows SharePoint Server 3.0.

The suite can be used to configure Directory and Free/Busy interoperabilitybetween Lotus Domino version 6 or 7 and Active Directory with ExchangeServer 2007.

The suite can also enable migration of users and groups from Lotus Notes 5, 6,or 7 to Active Directory; mail, address books and personal archives from thesesame versions to Exchange Server 2007; and facilitate the migration ofapplications to Microsoft Windows SharePoint Services 3.0 or Microsoft OfficeSharePoint Server 2007.

The Microsoft Transporter Suite for Lotus Domino includes the following tools:

Directory Connector: Synchronizes users, groups, and Domino mail-indatabase information between the Windows Active Directory and the LotusDomino Directory.

Free/Busy Connector: Used in the coexistence phase to enable Lotus Notesand Microsoft Office Outlook users to perform free/busy queries against bothLotus Domino and Microsoft Exchange Server 2007 servers when schedulingmeetings.

Directory Migration: Creates or merges Active Directory accounts forDomino user objects.

Group Migration: Creates or merges Active Directory groups for Dominogroup objects.

Mailbox Migration: Migrates information from Domino Mail databases toExchange Server 2007 mailboxes.

PAB and Archive Migration: Migrates information from PAB (PersonalAddress Book) and Personal Archive databases to Exchange Server 2007mailboxes.

Application Analysis: Gathers and reports information from Dominoapplications.

Application Migration: Migrates information from Domino applications toWindows SharePoint Services 3.0 and Office SharePoint Server 2007.

The Transporter Suite provides two management interfaces: the ManagementConsole and the Management Shell.

Management Console: Provides a graphical user interface (GUI) and can beused for basic migrations.

Management Shell: Adds functionality to the Microsoft Windows PowerShellcommand-line interface used to run single commands or to script a series ofcommands. It is typically used for complex command line or scriptedmigrations.



7/185

This document provides conceptual information, how-to information, and somebasic troubleshooting instructions for each migration phase using both the

Transporter Management Console and the Management Shell.

Note:The third-party Web site information referenced in this document isprovided to help you find the technical information you need. The URLs aresubject to change without notice.

You can download the Microsoft Transporter Suite for Lotus Domino andrelated documentation, including this document, from Resources forInteroperability and Migration from Lotus Domino(http://www.microsoft.com/technet/move) on TechNet.

The following flowchart captures the tasks and decision points of the mailmigration process.

http://www.microsoft.com/technet/movehttp://www.microsoft.com/technet/movehttp://www.microsoft.com/technet/movehttp://www.microsoft.com/technet/movehttp://www.microsoft.com/technet/movehttp://www.microsoft.com/technet/move


8/185

Co-existence phase

You appear to

be finished

One ortwo phases?

Migrate users and groups

Migrate PABs and archives

Gather information

Configure test lab

Evaluate options

Youve decided

to migrate

Configure DirSync

Notes to Exchange

Update MX records to

Exchange as appropriate

One or

two phases?

Remove Connectors

Namespace

design

Address

book design

See configuration

guidance

See configuration

guidance

See configuration

guidance

Configure two -way DirSync

Free/Busy lookup

required?

See configuration

guidance

Configure SMTP Connection

between environments

See configuration

guidance

See configuration

guidance

Yes

No

Single NAB Multiple NABs

Shared

SubdomainsDisparate

Single phase /big bang

Twophase/co-exist

Single phase /big bang

Two phase/

co-exist

Shared

design

Smarthosting

Migrate mailboxes

Figure 1 Migration Flowchart



9/185


10/185

Mailbox-only servers may be easily retired after mail migration

Mail routing servers may also be retired, after the mailbox-only servers theyroute for have been retired

Application servers may be retired or consolidated after the migration of someapplications, but may remain in production if it is impractical to migrate the

applications hostedDesignated administrator contact information

Routing and Replication TopologiesFrequently, the replication topology will be similar to the routing topology, butnote that this is not always the case. Replication latency can be the cause ofNDRs (Non Delivery Reports) if the Name and Address books are not in syncacross the environment.

Information collected should include:

Intra-domain (server to server) messaging protocol Notes Remote Procedure

Call (NRPC) or Simple Mail Transfer Protocol (SMTP)

It is possible that some servers will be different from the standard; all serverdocuments should be checked.

Inter-domain gateways

Internet gateways (SMTP in and out)

All Domain and Connection documents

Foreign domains

Foreign SMTP domains

Adjacent/non-adjacent domains

Other messaging add-ons, such as fax, pager, BlackBerry, and so on

Traffic statistics, if kept

Replication schedules and exclusions/formulae (particularly for the directory)

Designated administrator contact information

Ideally, a diagram of the current topology should be created if it does notcurrently exist, because this makes it easier to determine where potentialproblems may arise.

Network InformationThe network information gathered may suggest optimal locations for ExchangeServer 2007 servers for example, if slow links connect some sites, thesesites may require a server presence or that links be upgraded.

A topology diagram or detailed information that provides the following:

Local area network (LAN) configurations

Wide area network (WAN) configuration



11/185

Include speed and latency

Firewalls and the restrictions

Routers

Low-bandwidth, high-latency, and intermittent links

Internet connectivityClient locations

Traffic statistics if kept

Designated administrator contact information

As with the mail routing topology, you should create a network diagram if itdoes not currently exist, because this makes it easier to determine wherepotential problems may arise.

Backup and Restore Procedures

In order to perform proper backup and restore procedures, you must first:Identify current backup schedule and validation policies for individual servers

Specify storage location of backup media

Specify storage location of product media

The restoration of the backups of production systems into a test lab can saveconsiderable time in configuration and the population of data into the testsystem.

Client Information

Different versions of the Lotus Notes client produce slightly different behavior,and various configuration options on the client can affect how mail is createdand accessed. You should therefore get a sample set of data from clients thatinclude:

Version of Lotus Notes client in use

Browser usage for example, iNotes or Domino Web Access (DWA)

Use of Domino Designer and Domino Administrator

Configuration standards and known deviations

Hardware for example, x86, x64, other

Operating system version, service pack, and hotfixes/updates

Lotus Notes client configurations

Variations in Location documents

Online/Offline usage



12/185

User DataUser data such as the following can be useful, especially when you determinerisk:

List of users by domain/server

A matrix of user to database templateQuotas in force

Designated help desk contact information

In addition, you will need data on how users are stored in the directory; forexample, single NAB, multiple NABs with Directory Assistance, DirectoryCatalogs, and so on.

Other InformationYou may want to obtain the answers to the following questions to help youwith your migration efforts.

Are there any known problems in the current infrastructure that might adverselyaffect the migration project?

Beware of overtaxing existing connections, transmission problems caused byinadequate software components, and inefficient or incorrect message routing.For example:

Bottlenecks or malfunctioning connectors are the likely cause whenmessages are queued on a bridgehead server.

Non-delivery reports (NDRs) are signs of incorrect message routing.

Message loops, another common problem, are created if messages arerouted multiple times through the same bridgehead.

Exchange Server 2007 adds trace information to all transferredmessages to detect message loops and to drop looping messages with anon-delivery report (NDR). However, if the message's path includesmultiple messaging systems, the trace information might be lost duringmessage conversion between the systems. In this situation, messagesmay loop indefinitely. The effect can be similar to that of an e-mail floodcaused by a worm or virus therefore you should review the existingmessaging topology carefully to make sure that the implementation ofExchange Server 2007 does not lead to message loops.

What servers must remain?

Does the organization have workflow dependencies or mail-in databasefunctionality that requires that certain Lotus Domino servers must remain?

How do you want SMTP messages to flow?

Are you familiar with every application that is involved in sending e-mailmessages?

Understanding what applications send e-mail messages is critical to minimizinge-mail transmission problems. While administrators may be familiar with the



13/185

UNIX and mainframe systems that are part of the overall message flow, whoare sending e-mail messages and where they are sending to are generally notwell documented.

When you start retiring servers, or if you are trying to resolve odd e-mailaddressing problems, you may have an issue with a rogue application that issending messages in a non-standard way. Additional logging on all Dominoservers with the SMTP listener task enabled may help you find these rogueelements.

Are you planning to consolidate messaging resources when you deploy ExchangeServer 2007?

Exchange Server 2007 can support a very large number of mailboxes on asingle server, and deployment of fewer but more powerful servers can helpsimplify your environment's messaging infrastructure. Identifying thehardware, bandwidth options, and physical user locations you plan toconsolidate helps to determine the number of Exchange servers that must bedeployed.

What are the average and maximum e-mail database sizes in the Lotus Dominomessaging system?

Look at the current size of users mail databases. This information is veryimportant when you define the Exchange Server 2007 servers storagecapacities. At a minimum, the new environment should let all users store thesame amount of data or more in their mailboxes. It is not a good idea toenforce more restrictive mailbox quotas on the new system as this mightprevent users from experiencing the new mail environment as a positivechange.

Do the users send encrypted e-mail?

The Transporter Suite migration tools do not migrate encrypted information.

We recommend that you decrypt mail messages before migration. IBMprovides the following documents:

How to remove encryption from documents(http://www-1.ibm.com/support/docview.wss?

rs=0&uid=swg21089495); andRemoving encryption from all documents in your mail file

(http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21110567).

Third-party tools are also available for you to use to migrate encrypted mail.These tools decrypt the e-mail by having each end-user run the tool, which

decrypts the e-mail message before migration. To locate partner solutions formigrating encrypted e-mail message, see the Microsoft Solution Finder(https://solutionfinder.microsoft.com/default.aspx).

Regardless of which method that you choose, the migrated e-mail items willnot be encrypted in Exchange Server. If you do not want to store sensitiveinformation in Exchange Server 2007 without decrypting it, you should notmigrate these items.

http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21089495http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21089495http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21089495http://www-1.ibm.com/support/docview.wss?rs=0&q1=%2Bhow+%2Bto+%2Bdecrypt+%2Bmail+%2Bdomino&uid=swg21110567&loc=en_US&cs=utf-8&cc=us&lang=allhttp://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21110567http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21110567https://solutionfinder.microsoft.com/default.aspxhttps://solutionfinder.microsoft.com/default.aspxhttp://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21089495http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21089495http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21089495http://www-1.ibm.com/support/docview.wss?rs=0&q1=%2Bhow+%2Bto+%2Bdecrypt+%2Bmail+%2Bdomino&uid=swg21110567&loc=en_US&cs=utf-8&cc=us&lang=allhttp://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21110567http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21110567https://solutionfinder.microsoft.com/default.aspxhttps://solutionfinder.microsoft.com/default.aspx


14/185

Do users require training on Microsoft Office Outlook?

Users who are familiar with Outlook will find the migration to ExchangeServer 2007 straightforward. However, novice users might face a steeplearning curve because Outlook offers a comprehensive set of messagingfeatures. You can ease this situation by providing appropriate user training.

Other messaging clients such as Eudora are supported because ExchangeServer 2007 supports POP3 and IMAP4. However, remember that Internetclients are usually not as powerful as Outlook especially with respect tocalendaring capabilities and this lack of features might become aproductivity issue for users.

Is the help desk prepared for increased workload related to directory and mailcoexistence and migration?

The interoperation and migration phases put pressure on help desk personnelbecause the support call volume increases when users start to use their newmessaging clients. We recommend that you dedicate a help desk specialistspecifically to Outlook-related questions and that you train this person

thoroughly.

To maintain productivity in larger organizations, the Outlook task force mayconsist of a number of experts. You might want to temporarily increase theheadcount in the help desk department. It is reasonable to assume that thecall level will return to normal within six months after migration is completed.

How will you keep management, IT administrators, user help desk personnel, andusers updated about the migration progress?

It is important to keep everyone in your organization fully informed about themigration progress. For example, the users must know when they arescheduled for Outlook training, and the IT administrators, user help desk

personnel, and management need information about project progress. Werecommend that you create a detailed communication plan. Manyorganizations implement a dedicated intranet site to facilitate communicationabout the migration.

DiagrammingDiagrams of the beginning state do not take much time to produce. Thebenefits of diagrams are that they can communicate information quickly andmore easily than a large list of tables and text.

Beginning state diagrams should contain the basic information. More detailedinformation (such as version information) should be stored in spreadsheets or

by other means.

A simple routing topology diagram such as the following would be much easierto understand than text indicating the same information.



15/185

Sydney/AsiaRouter1/RoutingNewYork/Americas Paris/EuropeLondon/EuropeTokyo/Asia

Router2/Routing

Internet

Figure 2 Sample Routing Topology Diagram

The Domino Administrator client includes some functionality to diagram e-mailflow and replication paths as shown in the following figure:

This can provide the beginnings of the routing topology diagrams. Note: thatthe mapping functions provided do not map connections between Dominodomains.



16/185

Building a Test Lab and Evaluating OptionsEvery migration has similarities to every other migration. At the same time,every migration differences from every other migration. While this documentwill be sufficient for most scenarios, it will not cover them all. The importanceof configuring a test lab that mirrors the production environment as closely aspossible cannot be overestimated.

The test lab should include servers similar to (if not copies of) productionsystems so that any problems can be discovered and diagnosed, and any fixesor workarounds documented, without impact on the end-user.

Ideally, devices that generate latency and reduce bandwidth, firewalls, androuters would all be used in the test lab to mirror the production networksrestrictions.

Microsoft Virtual Server, and the associated P2V (Physical to Virtual) tools canbe useful in building a test lab without having to re-create the data center.

When testing, consider the namespace and address book design choices, andwhich makes sense given your results. Pay attention to any odd addressing orNDR (Non-Delivery Reports) generated in testing.

Make sure that you test migration of items from a variety of sources. Variousdatabase templates for e-mail users may be in production use, and evaluatingthe results of migration in testing is critical to a smooth migration inproduction.

Test Group migrations from Domino, observing any special groups such asthose containing symbols that may be lost in translation. Test each type of

group note that Domino allows free-text in group membership; ActiveDirectory requires strict references to existing objects.

Try migrating Personal Address Book and Archives, and consider how thesetypes of files will be harvested for a server-side migration.

If you need additional third-party tools to migrate encrypted e-mail or rooms orresources defined in Lotus notes, have those tools available and tested beforeyou perform the migration. See the Microsoft Solution Finder(https://solutionfinder.microsoft.com/) for help locating third-party tools.

At this time you should also consider how to deploy Outlook, and how toprovide training to end-users. We highly recommend that you provide Outlooktraining for the users before you perform the migration.

Microsoft provides free Outlook training on the Outlook 2007 Courses page(http://office.microsoft.com/en-us/training/CR100654581033.aspx). Forinformation about how to deploy Outlook 2007 and its templates, seeDeployment for the 2007 Office release(http://technet2.microsoft.com/Office/en-us/library/264e7da6-b7a8-4ada-b2ac-90eb5266b0c01033.mspx?mfr=true ) in the 2007 Office Resource Kit onMicrosoft TechNet.

https://solutionfinder.microsoft.com/https://solutionfinder.microsoft.com/http://office.microsoft.com/en-us/training/CR100654581033.aspxhttp://office.microsoft.com/en-us/training/CR100654581033.aspxhttp://technet2.microsoft.com/Office/en-us/library/264e7da6-b7a8-4ada-b2ac-90eb5266b0c01033.mspx?mfr=truehttp://technet2.microsoft.com/Office/en-us/library/264e7da6-b7a8-4ada-b2ac-90eb5266b0c01033.mspx?mfr=truehttp://technet2.microsoft.com/Office/en-us/library/264e7da6-b7a8-4ada-b2ac-90eb5266b0c01033.mspx?mfr=truehttps://solutionfinder.microsoft.com/https://solutionfinder.microsoft.com/http://office.microsoft.com/en-us/training/CR100654581033.aspxhttp://office.microsoft.com/en-us/training/CR100654581033.aspxhttp://technet2.microsoft.com/Office/en-us/library/264e7da6-b7a8-4ada-b2ac-90eb5266b0c01033.mspx?mfr=truehttp://technet2.microsoft.com/Office/en-us/library/264e7da6-b7a8-4ada-b2ac-90eb5266b0c01033.mspx?mfr=truehttp://technet2.microsoft.com/Office/en-us/library/264e7da6-b7a8-4ada-b2ac-90eb5266b0c01033.mspx?mfr=true


17/185

Remember that the success of any migration depends on your preparation:gather the information, configure the lab, test as much as possible before youmove to a production environment.



18/185

One Phase or Two

Decide Whether to Coexist for a Time

Migrating to a new messaging and collaboration platform is a complicatedprocess. Proper planning and preparation will help minimize user disruptionwhile providing additional functionality beyond current e-mail and collaborationcapabilities. It is important to understand the migration strategies, select theappropriate one, and then document and diagram the current infrastructure.

Thorough planning and preparation will ensure a successful migration.

Migration to a new collaboration platform can be performed in one of twodifferent strategies:

Single-phase migration: This strategy bypasses any coexistence with otherinfrastructure; it begins with the migration of relevant data to the newplatform.

Multiple-phase migration: This strategy utilizes coexistence with the oldcollaboration platform while both platforms are in use. The length of migrationdepends on the customers specific requirements.

Single-Phase MigrationPerforming a single-phase migration excludes the coexistence phase andmigrates all the users, groups, mailboxes, and user data in a single pass.Before the migration, all users use Lotus Notes and Domino for messaging.After the migration, all users use Microsoft Office Outlook and Microsoft

Exchange Server 2007, and the Lotus Domino e-mail servers aredecommissioned.

Single-phase migration is typically only implemented at small organizationswith a simple messaging infrastructure. It still requires significant planning andtesting to make sure that the whole organization will move seamlessly fromLotus Domino to Microsoft Exchange Server 2007 without overwhelming thehelp desk.

AdvantagesThe most significant advantages of a single-phase migration are:

All users migrate at the same time, yielding quick results.

Time is saved in the planning phase because coexistence does not have to betested, supported, or implemented.

There is no requirement for message or calendar connectivity between the twomessaging environments.

Note: Some directory synchronization must still occur from Domino toActive Directory to make sure that migrated messages can be repliedto.



19/185

Preserving existing e-mail addresses is straightforward because the newExchange Server 2007 messaging system replaces the Lotus Dominomessaging system.

DisadvantagesThe most significant disadvantages of a single-phase migration are:

The migration of large numbers of users or large amounts of data can result inunacceptable downtime.

The whole Exchange Server environment must be implemented beforemigrating users.

The pace of the migration cannot be controlled by migrating divisions ordepartments individually.

Flexibility is limited. For example, it is not possible to leave a particular groupof users on the Lotus Domino e-mail system.

Multiple-Phase MigrationMultiple-phase migration is recommended for larger organizations and thoseorganizations with more complex messaging infrastructures. Largerorganizations typically have multiple e-mail servers, frequently located indifferent physical locations. There may be several messaging clients thatconnect to the e-mail servers. It might not be feasible for all the e-maildatabases to be migrated and for all the clients to be reconfigured at one time.In these situations, the migration process must occur over an extended periodof time and include multiple phases.

A multiple-phase migration allows for time to test, evaluate, and update themigration plan during the migration period. The migration is implemented inphases by migrating groups and physical locations simultaneously, while at the

same time providing adequate support throughout the transition. Multiple-phase migrations require coexistence, during which time e-mail users must besupported on both the Lotus Domino and Exchange Server 2007 platforms.

One of the most important issues that you must consider in a multiple-phasemigration is coexistence between the directories and messaging systems,because users on the old e-mail system must be able to exchange messageswith users who have already migrated to the new e-mail platform. Becauseusers usually exchange e-mail messages primarily with other users in thesame workgroup or department, we recommend migrating related workgroupsor departments at the same time. Migrating these groups of userssimultaneously can help to reduce the number of messages that must berouted between the two disparate messaging environments.

AdvantagesThe most significant advantages of a multiple-phase migration are as follows:

Control the pace of migration. Stage server and client deployments accordingto migration phases. There is no need to establish the whole Exchange Serverenvironment before migrating users.

Complete migration in incremental and manageable steps.



20/185

Migrate related departments, business units, or teams simultaneously andmigrate users who require access to each other's calendars and e-maildatabases during the same migration phase.

Synchronize reconfiguration of the messaging client and end-user training withthe migration of mailboxes.

Minimize risk. If one particular operation in the multiple-phase migration is notsuccessful, a limited number of people are affected. If migration of a group ofusers fails for any reason, users can continue to work with their Lotus Dominoe-mail databases until the issues are resolved.

DisadvantagesThe most significant disadvantages of a multiple-phase migration are:

Multiple-phase migrations are more time-consuming, and therefore, moreexpensive when compared to single-phase migrations.

Connectors must be deployed and supported. Directory synchronization mustbe configured between the systems to enable the Lotus Domino messaging

system and the Exchange Server 2007 organization to interoperate asseamlessly as possible.

Both the Lotus Domino and Exchange Server 2007 messaging systems mustbe maintained and supported for a period of time.

CoexistenceIn any multiple-phase migration, there will always be a phase in which theLotus Domino messaging environment must coexist with the MicrosoftExchange Server 2007 environment. Because not all users are migrated at thesame time, some users will remain in the Lotus Domino messagingenvironment while other users are in the Microsoft Exchange Server 2007environment.

For these users to route e-mail to one another, the Active Directory and theLotus Domino Directory must synchronize user and e-mail address information,e-mail must route between the two environments, and users should be able toperform free/busy calendar lookups regardless of the other users' e-mailplatform.

The key components involved in coexistence are:

The Directory Connector tool in the Transporter Suite handles directorysynchronization.

An SMTP Connector handles message transfer, preservation of messagepaths, and message conversion.

The Free/Busy Connector handles the free/busy calendar lookupsbetween the systems.

AdvantagesAs described in Multiple-Phase Migration, temporary coexistence allows forcontrolled migration in phases.



21/185

DisadvantagesCoexistence is costly, support-intensive, and requires administrator knowledgeof multiple messaging systems therefore many companies considerstandardizing their communication infrastructure on a single messagingsystem as a key element in their messaging strategy.

Long-Term CoexistenceLong-term coexistence is basically a multiple-phase migration without an end.After users have been migrated to Microsoft Exchange Server 2007, theDomino messaging system continues to coexist. Some companies choose thisstrategy to preserve investments in existing technologies, such as complexline-of-business applications that rely on Domino.

Installation TasksVarious components in the Transporter Suite can be installed on differenttypes of computers:

All connector components (Directory Connector and Free/BusyConnector): Can only be installed on Exchange Server 2007 servers with theHub and/or Client Access Server (CAS) roles installed; optionally, other roles(such as Mailbox or Unified Messaging) can also be installed.

E-mail Migration components (both the GUI and PowerShell cmd-lets):Can be installed on an Exchange Server 2007 server, or a separateworkstation. Running migrations from a separate workstation has theadvantage of not affecting production should problems arise (such as a LotusNotes session crash, for example).

Application Analysis and Migration components (both the GUI andPowerShell cmd-lets): should be installed on a Windows SharePoint Services

server.

An add-in task for Lotus Domino: Must be installed on a Domino serverdesignated as the bridgehead for Free/Busy queries to provide lookups fromNotes clients requesting Exchange Server users Free/Busy data.

The most recent version of the Transporter Suite can be downloaded fromhttp://go.microsoft.com/fwlink/?linkid=82688, in both 64-bit and 32-bitversions:

The 64-bit version of the Transporter Suite is used on production ExchangeServer 2007 servers and 64-bit migration workstations

The 32-bit version of the Transporter Suite is used on 32-bit migration

workstations, and test Exchange Server 2007 servers on a 32-bit operatingsystem.

Note:The 32-bit Exchange Server 2007 servers are not supported forproduction use.

http://go.microsoft.com/fwlink/?linkid=82688http://go.microsoft.com/fwlink/?linkid=82688


22/185

Installing Transporter Suite Components on anExchange Server

DependenciesExchange Server 2007 server with Hub or CAS role

Lotus Notes client (preferably 7.0.2 or later)

Installation is relatively straight-forward:

1. On the Welcome page, click Next.

2. Accept the terms of the license agreement, and then click Next.

3. Note: that Microsoft Transporter Tools is selected, choose analternate installation location if you want, and then click Next.

4. Click Install, and then click Finish.

Configuration guidance for the various components and use instructions can befound under the appropriate headings in this document.

Screen captures of the installation process follow.



23/185



24/185

Installing Transporter Suite Components on aWindows SharePoint Services Server

DependenciesWindows SharePoint Services 3.0 or Office SharePoint Server 2007


The installation process is the same as for installing on an Exchange server.

Remember to install the correct version (64-bit or 32-bit) , depending on theoperating system of the server running Windows SharePoint Services or OfficeSharePoint Server.

Note: Although we provide instructions for installing the MicrosoftTransporter Suite onto a Windows SharePoint Services server, this

document does not discuss application migration.

Installing Transporter Suite Components on aMigration Workstation

DependenciesExchange Server 2007 Administration Tools (and associated dependencies)


The installation process is the same as for installing on an Exchange server.Remember to install the correct version (64-bit or 32-bit), depending on theoperating system of the migration workstation.

Installing Transporter Suite Components on a DominoServer

Installing these Transporter Suite components is only required for two-phasemigrations.

DependenciesLotus Domino server

Microsoft Windows operating system

Note: The Microsoft Remote Procedure Call (MSRPC) protocol used forcommunication between Domino and Exchange has not been ported toother platforms.

Again, installation is relatively straight-forward:



25/185

1. On the Welcome page, click Next.

2. Accept the terms of the license agreement, and then click Next.

3. Select Free Busy Connector Add-In Task For Lotus Domino. Theinstallation location is determined based on information the Dominoservers places in the Registry upon installation.

4. Click Install, and then click Finish.

Configuration guidance for this component can be found in the ConfiguringFree/Busy Lookup section of this document.



26/185

Single-Phase (Big-Bang) MigrationsAlthough no messages will be routed between the systems in the case of asingle-phase migration, synchronization of the Domino directory to the ActiveDirectory is required so that users will still be able to reply to the messagesthat are migrated to the new system.

Migrated messages will generally contain the Domino address of a user (forexample, John Smith/Certifier). A One-way DirSync guarantees that these typesof addresses are correctly stamped on objects in Active Directory so that whena user replies to a e-mail message in Exchange Server, their reply is routed tothe correct mailbox.

Configuring One-Way DirSyncThis section lists the procedures required to perform one-way directorysynchronizations.

Domino to Exchange

PrerequisitesThe Transporter Suite has been installed

The Lotus Notes client has been installed (preferably as a single-userinstallation) and configured with an ID file that has permissions to read thedefault address book (NAMES.NSF) and any other address books containingusers who are to be migrated. This is known as Reader access in Domino

parlance.Required permissions are as shown:



27/185

ConfigurationTo begin, a new connector must be created.

To create a new directory connector

1. Open the Transporter Management Console. In the left pane, clickConnect, and then, in the right pane, click Create DirectoryConnector.

2. Click Next, click Create, and then click Finish.



28/185

To configure the new directory connector

To configure the connector, double-click the newly created object, and you arepresented with tabbed property pages to fill in, the first being the Generaltab.

1. On the General tab, choose a global catalog by clicking the Browsebutton. You are presented with a list of global catalog servers,including their site information. Choose a global catalog in the samesite as the Exchange Server 2007 server.

2. Next, type a Domino Server name. This server should containreplicas of all Name and Address Books containing users that will be

migrated to Exchange Server.3. Then, enter and confirm the password for the user whose ID file is

installed on the Exchange Server 2007 server. If the typedpasswords do not match (note that they are not verified against the

ID file yet), a red flashing exclamation point ( ) will be displayed.

Once this information has been entered, you can move to the Sync toActive Directory tab. Here, you enter the Name and Address Booksand other associated information.



29/185

4. Click the Add button to enter the following information:The source Name and Address Book (for example, NAMES.NSF)

The source Domino domain name (for example, Domino Domain)

The associated SMTP domain name (for example, contoso.com): The

associated SMTP domain name is used to construct a targetAddress for thecontact that will be created. It will not be used in a single-phase migration.

5. If there are multiple source NSFs, repeat this process for each ofthem.

6. Then, choose a Target Organizational Unit for the contacts to becreated by clicking the Browse button.

Note:The server account (COMPUTERNAME$) must have Full Controlpermissions on the chosen organizational unit (OU) and on all sub-containers for the account to be able to write, modify, and deleteobjects. After you set the permissions usingActive Directory Users and Computersas shown, click Advanced andchoose This container and all sub containers:

7. Because no migration back to Domino will occur, the Sync toDomino tab can be skipped.

8. On the Advanced tab, you can choose to synchronize groups toActive Directory. The Directory Synchronization component creates

contact objects to represent Domino groups; later, you can migratethe groups including membership by using the Group Migration tool.See the Migrating Groups section in this document for additionalguidance.

A screen capture of a completed connector configuration follows:



30/185

UseAlthough configured, Directory Synchronization will not automatically occur.

To perform the synchronization, you can either use the Transporter

Management Console or a command in the Transporter Command Shell.

To perform Directory Synchronization using the Transporter Management Console

1. Open the Transporter Management Console. In the left pane, clickConnect, in the middle pane highlight the Domino DirectoryConnector, and then in the right pane, click Synchronize Now.



31/185

2. A new page will be displayed that indicates the task to beperformed. Click Next.

3. On the following screen, there are several synchronization options.

Choose Full Synchronization, make sure that the Full one waysynchronization from Domino option is selected, and then clickNext.

4. On the summary screen that follows, click Next. A completionscreen will be displayed, and should indicate that the wizardcompleted successfully.



32/185

The following are example screen captures:

Note: The Elapsed Time displayed represents the time taken to starttheprocess the process is not yet complete.

To perform Directory Synchronization using the Transporter Command Shell

To perform the same task in the Transporter Command Shell, use the Start-DominoDirectoryConnector cmdlet as shown:



33/185

The next step in a single-phase migration is to migrate users. See theMigrating Users section later in this document for guidance.



34/185

Two-Phase (Coexistence) MigrationsTwo-phase migrations involve a period of coexistence, and require severaladditional decisions to be made before you start.

Namespace DesignNamespace design here refers to the SMTP domain names of the organizationexposed to the Internet. Some options in use are described in the followingtable.

Unified namespace [email protected]

Divisional or geographical [email protected] or

[email protected]

Technology-specific [email protected] or

[email protected]

Disparate [email protected] and

[email protected]

Additionally, division, geographical, or disparate namespaces may be usedinternally, but a unified namespace exposed to the Internet. A unifiednamespace means that even though within the corporate network users mayhave a divisional, geographic or technology-specific address, a unified view ofthe organization is presented outside the corporate network.

Using disparate namespaces to route mail

Using disparate namespaces requires the least configuration changes, but mayonly make sense during the merger of two companies. In this case, configuringmail routing and Free/Busy lookup between the systems is less complex andless prone to error because Exchange Server users can be easily distinguishedfrom Domino users simply by domain name. Additionally, troubleshooting sucha design is also easier.

External DNS configuration could contain MX records for both domains to thesame location, or different locations.

Internal routing configuration would generally be configured to exchange maildirectly between the systems, or over a trusted path. It is also possible to allowmessages between the systems to pass across the Internet, rather than havinga dedicated message routing path. In any case, the configuration is similar.

Depending on whether MX records for the separate domains point to the samelocation, the implementation of mail routing on such a system might look likeone of the following diagrams.



35/185

Configuration of Edge Transport servers is beyond the scope of this document.Additional guidance can be found at Planning for Edge Transport Servers(http://technet.microsoft.com/en-us/library/aa996562.aspx) on the TechNet

Web site.

Shared Namespace DesignIn general however, shared or unified namespace design is desirable, becauseit presents a unified view of an organization to the outside world, whichincludes partners, vendors, and customers.

The question is then whether divisional, technology-specific or geographicsubdomains will be used internally. The decision is usually determined bywhether the existing infrastructure can use smarthosts correctly.

Using subdomains to route mail

Using subdomains works like using disparate namespaces with an Edge serveror outbound processor to rewrite addresses on messages before they leave theorganization.

External DNS configuration contains MX records for the shared domain to anauthoritative system.

Internal routing configuration must be configured to exchange mail directlybetween the systems, possibly using smarthosts.

Internal DNS configuration could be configured such that records exist for thesubdomains to systems authoritative for the subdomain.

The implementation of mail routing on such a system might look similar to thefollowing diagram.

http://technet.microsoft.com/en-us/library/aa996562.aspxhttp://technet.microsoft.com/en-us/library/aa996562.aspxhttp://technet.microsoft.com/en-us/library/aa996562.aspxhttp://technet.microsoft.com/en-us/library/aa996562.aspx


36/185



37/185

Using smarthosts to route mailIf no subdomains are used, internal systems must have a way to determinewhich mail system will be the end destination for a particular recipient.

Typically, one of the systems must be authoritative for the domain, and havethis information. Mail routing in such cases is usually point to point, and

increases the possibility that a misconfiguration will cause mail loops.

Note: 1:If Exchange Server 2003 is part of the Exchange Server 2007organization, the shared domain name must not be authoritative inExchange Server 2003. Unlike Exchange Server 2007, Exchange Server2003 will not route mail to a contact whose targetAddresss domain namematches an authoritative domain.

Note: 2: Using smarthosts to route mail between Domino servers reliesupon connectivity over SMTP between Domino servers. Domino will notroute mail over NRPC to a Person whose ForwardingAddresss domainname matches an authoritative domain.

External DNS configuration contains MX records for the shared domain to an

authoritative system.

Internal routing configuration must be configured to exchange mail directlybetween the systems, generally using smarthosts to prevent loops caused bymessages following the path dictated by MX records.

Internal DNS configuration would be prone to error, and not recommended.

The implementation of mail routing on such a system might resemble thefollowing diagram.

Address Book DesignDepending on how the Domino system currently operates, it may make senseto use either the single address book model or the multiple address booksmodel.

Evaluate the advantages and disadvantages of each model to determine whichis appropriate.



38/185

Using a single Name and Address Book

AdvantagesA single configuration change is required allowing the ID of the userassociated with the Transporter to write to the main Name and Address Book(NAMES.NSF).

DisadvantagesThe ID of the user associated with the Transporter gains any additionalpermission to the main Domino directory. Should the ID file and associatedpassword be compromised, configuration changes can be made to the Dominoenvironment.

UseThe ID of the user associated with the Transporter must be granted access tocreate, modify, and delete documents in the default address book(NAMES.NSF). This is known as Manager with Delete Documents access inDomino parlance.

The required permissions are as shown:

Using multiple Name and Address Books

AdvantagesThe ID of the user associated with the Transporter does not have anyadditional permission to the main Domino directory. Should the ID file andassociated password be compromised, configuration changes cannot be madeto the Domino environment.



39/185

DisadvantagesMore complicated to configure.

UseThe ID of the user associated with the Transporter must be granted access toread the default address book (NAMES.NSF). This is known as Reader access

in Domino parlance.

Required permissions are as shown:

Furthermore, a new Exchange address book must be created, and the ID of theuser associated with the Transporter must be granted access to create,modify, and delete documents in this address book. This is known as Managerwith Delete Documents access in Domino parlance. Because documents arecreated programmatically rather than through the UI, adding the ID file tospecific roles (UserCreator, UserModifier) is not required.



40/185

Required permissions are as shown:

The Directory Profile document should have the Domain defined by thisDomino Directory set to Exchange (or the ForeignDomain value of theDirectory Connector in Exchange Server 2007).

Additionally, this address book should be made available to all servers andclients either through replication and Directory Assistance or the use ofDirectory Catalogs. Some changes to server documents may also be required.In general, organizations that choose to use multiple address books will



41/185

already be using one of these two methods to make other address booksavailable.

Configuring Two-Way DirSync


The Lotus Notes client has been installed (preferably as a single-userinstallation) and configured with an ID file that has appropriate permissions onthe address books. See the section Address Book Design for the requiredpermissions.

ConfigurationTo start, a new connector must be created.

To create a new directory connector

1. Open the Transporter Management Console, and in the left pane,click Connect. Then, in the right pane, clickCreate Directory Connector.

2. Next, click Next, click Create, and then click Finish.



42/185

3. To configure the connector once created, double-click the newlycreated object. You are presented with tabbed property pages to

fill in, the first being the General tab.4. First, determine how often automatic Directory Synchronization

should occur. This depends on several factors, such as:How large are the directories?

How frequently do the directories change?

Typically, most installations will be set to synchronize somewherebetween every hour and every four hours.Note: By default, the Microsoft Exchange Directory Connector Servicefor Lotus Domino is set to Manual. You should configure this service tobe Automatic if you want scheduled directory synchronization to occur.If the service remains set to Manual, the service will not be started after

a reboot.You can change the server startup using the Services MMC snap-in asshown:



43/185

5. Second, choose a global catalog by clicking the Browse button.You are presented with a list of global catalog servers, includingtheir site information. Choose a global catalog in the same site asthe Exchange Server 2007 server.

6. Next, type a Domino Server name. This server should containreplicas of all Name and Address Books containing users that willbe migrated to Exchange Server.

7. Then, enter and confirm the password for the user whose ID fileis installed on the Exchange Server 2007 server. If the typedpasswords do not match (note that they are not verified against

the ID file yet), a red flashing exclamation point ( ) will bedisplayed.

8. Once this information has been entered, you can move to theSync to Active Directory tab. Here, you enter the Name andAddress Books and other associated information.

9. Click the Add button to enter the following information:The source Name and Address Book (for example, NAMES.NSF)

The source Domino domain name (for example, Domino Domain)

The associated SMTP domain name (for example, contoso.com): Theassociated SMTP domain name is used to construct a targetAddress for thecontact that will be created.

10.If there are multiple-source NSFs, repeat this process for each ofthem.

11.Then, choose a Target Organizational Unit for the contacts to becreated by clicking the Browse button.

Note:The server account (COMPUTERNAME$) must have Full Controlpermissions on the chosen organizational unit (OU) and on all sub-contaners for the account to be able to write, modify, and deleteobjects. After you set the permissions using



44/185

Active Directory Users and Computersas shown, click Advancedand choose This container and all sub containers.:

12.Next, move to the Sync to Domino tab. On this tab you selectwhich OUs and users will be synchronized back to Domino.

13.Click the Add button under Source Organizational Units toadd OUs to synchronize with the Domino directory. Click Browseon the new dialog box to choose an OU to add.

Note:The server account (COMPUTERNAME$) must have Readpermissions on the OU chosen to be able to read objects. You can setand verify the permissions using Active Directory Users and Computersas shown:

14.Enter a Domino Directory Filename next. Depending on theaddress book model used, this may be NAMES.NSF, or the nameof another address book.

15.Finally, click the Add button under Routable ExchangeDomains to add SMTP domains that contain Exchange Server



45/185

users. These domains should be reachable from the Dominoservers, but not necessarily available from the Internet.

16.On the Advanced tab, you may decide to prevent thesynchronization of Domino groups to Active Directory, as theDirectory Synchronization component creates contact objects torepresent Domino groups. Later, you can migrate the groups

including membership using the Group Migration tool. See theMigrating Groups section in this document for additionalguidance.

Whether to synchronize groups and/or contacts from the ActiveDirectory back to Domino depends on several factors:

The timing of Group Migration

The destination OU of Group Migrations

Whether there are contacts in the Active Directory that it makes sense tosynchronize

Options to control the synchronization are the last items on theAdvanced tab.

The following figure is a screen capture of a completed connectorconfiguration.



46/185

UseAlthough configured, Directory Synchronization will not automatically occur.

To perform the synchronization, you can either use the TransporterManagement Console or a command in the Transporter Command Shell.

To synchronize directories using the Transporter Management Console

1. Open the Transporter Management Console. In the left pane, clickConnect, in the middle pane, highlight the Domino DirectoryConnector, and then, in the right pane, click Synchronize Now.



47/185

2. A new page will be presented indicating the task to be performed.Click Next.

3. On the following screen, there are several synchronization options.Choose Full Synchronization, make sure that the Full one way

synchronization from Domino option is selected, and then clickNext.

4. On the summary screen that follows, click Next. A completionscreen will be displayed, and should indicate that the wizardcompleted successfully.



48/185

The following figure shows example screen captures.

Note: The Elapsed Time displayed represents the time taken to starttheprocess the process is not yet completed.

To synchronize directories using the Transporter Command Shell

To perform the same task in the Transporter Command Shell, use theStart-DominoDirectoryConnector cmd-let as shown:



49/185

Options include:-FullReloadtoAD: Rewrites all Active Directory objects into the Dominodirectory

-UpdateToAD: Writes changes to Active Directory objects into the Dominodirectory

-FullReloadToDomino: Rewrites all Domino objects into Active Directory

-UpdateToDomino: Writes changes to Domino objects into Active Directory

Other options can be found using theGet-Help Start-DominoDirectoryConnector command in the

Transporter Command Shell.



50/185

Configuring Free/Busy LookupMany organizations rely heavily on the ability to review the availability (or

Free/Busy information) of parties to attend meetings. The Free/BusyConnector relies upon many other components to provide Free/Busy lookupbetween Exchange and Domino.

Configuration of the Free/Busy connector and its dependencies is prone toerror and misconfiguration, which makes troubleshooting very difficult. Takesome time to check and recheck each setting before you apply that settingand moving on to the next step.

Exchange configuration


The Lotus Notes client has been installed (preferably as a single-userinstallation) and configured with an ID file that has permissions to read thedefault address book (NAMES.NSF) and permissions to access the BUSYTIMEdata for users

The Microsoft Exchange Server MAPI Client and Collaboration Data Objects1.2.1 package, available on the Microsoft Download Center(http://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611e).

ConfigurationThere are several items to configure on Exchange Server 2007 that arerequired in order to enable the lookup of Free/Busy information for Dominousers:

Public Folders

Availability

Client Access Server Settings

Free/Busy Connector

Public FoldersA Public Folder server must be available in the Exchange Server 2007Administrative Group. When first installing Exchange Server 2007, you areasked to choose whether compatibility with earlier versions of Outlook isrequired. Selecting the appropriate check box causes a Public Folder store tobe created. Installations that contain Exchange Server 2003 will automaticallyhave a Public Folder store created.

In the event that a Public Folder store does not exist, one can be created. ThisPublic Folder store is created on one of the servers with the Mailbox role.

Note: Unless there is only a single Public Folder store in an ExchangeServer 2007 organization, a Public Folder store cannot be created on

http://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611ehttp://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611ehttp://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611ehttp://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611ehttp://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611ehttp://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611ehttp://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611ehttp://www.microsoft.com/downloads/details.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611e


51/185

Storage Groups that use Cluster Continuous Replication (CCR), LocalContinuous Replication (LCR), or Standby Continuous Replication (SCR).

To use the Exchange Management Console to create a new Public Folder store

1. In the left pane, click Server Configuration/Mailbox, and thenchoose a server from the middle pane. A Public Folder store can be

created in an existing or new Storage Group.

A single screen creates and optionally mounts the new Public Folderdatabase after configuration information has been entered.2. In the Public Folder database name box, type the name of your

database. If you are using the Exchange Management Console onthe server where the database will reside, you can also click Browseto browse for an alternative location for the database files.



52/185

To use the Exchange Management Shell to create a new Public Folder store

1. Use a command of the form:

New-PublicFolderDatabase Name "PF database name" StorageGroupName "SG name"

This should be run on the server to host the new Public Folder store.

To use the Exchange Management Shell to verify the existence of the Schedule+Free/Busy public folder

1. A specific folder must exist to store items representing theFree/Busy information for Domino users. Verify the existence of thisfolder using the following command in the Exchange ManagementShell:

Get-PublicFolder Identity"\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY" -Recurse

Output should be similar to:

Note: that the second entry, beginning with /ou=Exchange indicatesthe presence of the correct folder.

Note: If an error message that resembles the following is returned, youmust create the top-level folder.

There is no existing PublicFolder that matches the followingidentity: \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY

The command required to create the top-level folder is:

New-PublicFolder Name "\NON_IPM_SUBTREE" Path"SCHEDULE+ FREE BUSY"

Note: If you created the top-level folder above after the error, or if no

error was returned, but the folder was not displayed, the subfolder willhave to be created. The command required is of the form:

New-PublicFolder Name "\NON_IPM_SUBTREE\SCHEDULE+ FREEBUSY" Path "EX:/o=OrgName/ou=Exchange Administrative Group(FYDIBOHF23SPDLT)"

For more information about Public Folders, see Understanding Public Folders(http://technet.microsoft.com/en-us/library/bb397221.aspx) on the TechNetWeb site.

http://technet.microsoft.com/en-us/library/bb397221.aspxhttp://technet.microsoft.com/en-us/library/bb397221.aspxhttp://technet.microsoft.com/en-us/library/bb397221.aspxhttp://technet.microsoft.com/en-us/library/bb397221.aspx


53/185

AvailabilityAvailability settings must be changed to cause the Availability service to usethe Public Folder when gathering Free/Busy information for Domino users. Thischange must be performed using the Exchange Management Shell.

Depending on the namespace design you chose, there may be multiple

address spaces (SMTP domains) that need to be configured, including theaddress space used by Exchange Server.

The command required is of the form:

Add-AvailabilityAddressSpace ForestName dominodomain.com-AccessMethod PublicFolder

Output is as shown:

For more information about Availability, see Understanding the AvailabilityService (http://technet.microsoft.com/en-us/library/bb232134.aspx) on the

TechNet Web site.

Client Access Server SettingsThe Transporter Suite for Lotus Domino communicates with the ExchangeServer that performs the Client Access server role. If the Exchange Server thathosts the Client Access server role also hosts the Mailbox server role, the FreeBusy Connector for Lotus Domino will not work until secure sockets layer (SSL)is disabled on the /Public virtual directory of the server hosting both roles.

http://technet.microsoft.com/en-us/library/bb232134.aspxhttp://technet.microsoft.com/en-us/library/bb232134.aspxhttp://technet.microsoft.com/en-us/library/bb232134.aspxhttp://technet.microsoft.com/en-us/library/bb232134.aspxhttp://technet.microsoft.com/en-us/library/bb232134.aspxhttp://technet.microsoft.com/en-us/library/bb232134.aspx


54/185

Free/Busy ConnectorFinally, the Free/Busy Connector must be created.

To create the Free/Busy Connector

1. Open the Transporter Management Console. In the left pane, clickConnect, and then in the right pane, clickCreate Free/Busy Connector.

2. Then, click Next, click Create, and then click Finish.



55/185

To configure the Free/Busy Connector

1. To configure the connector once created, double-click the newlycreated object. You are presented with tabbed property pages to fillin, the first being the General tab.

NotesOn the General tab, the Schedule setting controls how often theFree/Busy connector will search for new objects representing Dominousers in the Active Directory, and will create associated Public Foldermessages to represent them. This setting does notcontrol whenFree/Busy information will be gathered for users.

Other settings on the General tab include:

Days of Free/Busy information: As the name suggests, this many daysworth of availability data will be collected upon request.

Maintain information in cache (seconds): When availability information iscollected for Domino users it is cached; subsequent requests for the usersavailability information during this time will be returned from the cache.

Timeout (seconds): The maximum amount of time a request can beoutstanding to Domino; when this timeout is exceeded, cached information willbe returned to the requestee.



56/185

Note:The timeout setting should not be set above oneminute. If the timeout is set too high, Availability could mark aPublic Folder server as bad. If all Public Folder servershosting a replica of the Free/Busy folder are marked as bad,no Free/Busy information will be retrieved for Domino users.

2. Next on the General tab, type a Domino Server name. This serverwill act as a bridgehead for Free/Busy requests to and fromExchange Server.

3. Then, enter and confirm the password for the user whose ID file isinstalled on the Exchange Server 2007 server. If the typedpasswords do not match (note that they are not verified against the

ID file yet), a red flashing exclamation point ( ) will be displayed.4. Once this information has been entered, you can move to the

Advanced tab. Click the Add button under Connected DominoSMTP Domains to add domains containing Domino users.

This information is used to generate Free/Busy messages in the PublicFolder. Typically, this list will match the data on the Directory Connectorcreated during the Configuring Two-Way DirSync part of theinstallation, described earlier in this document.



57/185

Details of the General and Advanced tabs are shown here:

Note: By default, the Microsoft Exchange Free Busy Connector for LotusDomino service is set to Manual. You should configure this service tobe Automatic. If the service remains set to Manual, the service willnot be started after a reboot.



58/185

5. You can change this using the Services MMC snap-in as shown:

Domino ConfigurationDomino uses domain documents to determine how to route Free/Busy requeststhroughout the system. Exchange Server users are represented as belongingto a foreign domain. Therefore, a Foreign Domain document must be createdto indicate to Domino servers how to route requests.

PrerequisitesThe add-in task from the Transporter Suite has been installed

Configuration

To create a Foreign Domain document in the Domino Administrator

1. In the Domino Administrator, go to the Configuration tab, and inthe left pane, select Messaging/Domains. Choose Add Domain.

2. In the document presented, set the following options:Domain type: Choose Foreign Domain.

Foreign domain name: Typically, this will be Exchange, but should matchthe ForeignDomain attribute on the Directory Connector created during theConfiguring Two-way DirSync part of the installation, described earlier in thisdocument.

Gateway server name: Enter the name of the Domino server that will act asa bridgehead for Free/Busy requests to/from Exchange Server. This shouldmatch the Domino Server name configured on the Exchange Free/Busyconnector.



59/185

Gateway mail file name: Enter mail.box.

Calendar server name: Enter the name of the Domino server that will act asa bridgehead for Free/Busy requests to/from Exchange Server. This shouldmatch the Domino Server name configured on the Exchange Free/Busyconnector.

Calendar system: Typically this will be mail.box1

.

3. Click Save, and then click Close. This new document will have toreplicate to other servers in the Domino domain.

Note: For multiple domain installations, additional Nonadjacent Domaindocuments must be created to allow Free/Busy requests from thesedownstream domains to Exchange Servers users.

4. Finally, add the ExCalCon add-in task to the list of tasks the serverwill begin on startup.

This can be performed by one of two methods:Using the Domino Administrator (or at the Domino console): Use the followingcommands in bold from the following screen capture.

Input: show conf servertasks

Output:

Replica,Router,Update,AMgr,AdminP,Sched,CalCon,RnrMgr

Input: set conf servertasks=[output] ExCalConExchangeServername CalendarSystem

1 * Some companies will choose to use mail.box here also.

Some versions of the Lotus Notes client will always send Notes RTF meeting requests to the first participant of a meeting.Notes routing then attempts to deliver this RTF message to a database with the same name as the Calendar Systemon

the Calendar Server.

Setting this to mail.box causes the message to be delivered to the default Mail Router mailbox, the message is converted

and delivered correctly.



60/185

Editing the NOTES.INI (or SERVER.INI) file that controls the startup of theDomino server, adding the same information:

It is possible to use more than one Free/Busy connector to provide fasterresponse times to remote users. Whether it is appropriate to install additionalFree/Busy connectors depends heavily on the overall network structure.

Typically, such an installation would only be in the largest of organizations,with several network locations where Exchange Server users and Domino userscoexist, and there is high speed, low latency connectivity between the systemsat that location.

Additional Free/Busy Connector guidance can be found in the appendix of thisdocument titled Multiple Free/Busy Connectors.



61/185

Configuring SMTP ConnectivityDepending on the namespace or address book design you use, SMTPconnectivity is configured differently, and has slightly different Prerequisites.

Some slight differences in the layout of the document pages may occurdepending on the version of Domino.

This section covers the following:

Using Disparate or Shared/Subdomain Namespace Design

Using Shared/Smarthost Namespace Design

Testing and Other Issues to Note

Removing SMTP Connectors

Using Disparate or Shared/Subdomain Namespace

designIn order to use disparate or shared/subdomain namespace design, you need tomake conf

Microsoft Transporter Suite

Documents

Transcript of Microsoft Transporter Suite