Domino Access for Microsoft Outlook - IBM Redbooks · Domino Access for Microsoft Outlook ... 243 Debugging parameters in the notes.ini file ... marketing, or distributing

ibm.com/redbooks

Domino Access for Microsoft OutlookDeployment and Migration Guide

John BerglandLisa A. Chase

Peter HamptonPrashant Pandya

Overview of features and functionality

Installation and configuration information

Migration from Exchange to Domino

Front cover

http://www.redbooks.ibm.com/


Domino Access for Microsoft Outlook: Deployment and Migration Guide

August 2005

International Technical Support Organization

SG24-6754-00

© Copyright International Business Machines Corporation 2005. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

First Edition (August 2005)

This edition applies primarily to Domino Access for Microsoft Outlook 6.5.4 and the Domino Migration Tool 6.5.4. Please note that Appendix D, “Updates to Domino Access for Microsoft Outlook 6.5.5” on page 239 contains the latest information on Release 6.5.5.

Note: Before using this information and the product it supports, read the information in “Notices” on page vii.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixThe team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Additional Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiBecome a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Part 1. Overview of DAMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Introduction to DAMO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 Overview of DAMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 Business value overview, migration, and DAMO . . . . . . . . . . . . . . . . . . . . 71.3 Key advantages of using DAMO and Outlook with Lotus Domino . . . . . . . 91.4 Overview of typical DAMO deployment topologies . . . . . . . . . . . . . . . . . . 121.5 Why Outlook support is important . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.5.1 Common platform for messaging and collaboration . . . . . . . . . . . . . 161.6 Migration and DAMO — the total solution . . . . . . . . . . . . . . . . . . . . . . . . . 171.7 Multiple client strategy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.8 Version compatibility between DAMO, Outlook, and Domino . . . . . . . . . . 181.9 Structure of this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 2. Features and functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.1 Overview of new features in DAMO 6.5.4 . . . . . . . . . . . . . . . . . . . . . . . . . 222.2 Mail and Calendar interface features comparison. . . . . . . . . . . . . . . . . . . 232.3 Performance improvements within DAMO 6.5.4 . . . . . . . . . . . . . . . . . . . . 28

2.3.1 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.4 Domino-specific functionality added to Outlook through DAMO . . . . . . . . 30

2.4.1 Domino Preferences tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.5 Using the Domino Directories for name lookups . . . . . . . . . . . . . . . . . . . . 512.6 Domino versus Exchange functional comparison . . . . . . . . . . . . . . . . . . . 552.7 Replication in DAMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

2.7.1 Replication overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.7.2 Replicator thread and interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.7.3 Property mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.7.4 How and when is replication invoked . . . . . . . . . . . . . . . . . . . . . . . . 59

2.8 Calendering and scheduling within DAMO . . . . . . . . . . . . . . . . . . . . . . . . 602.8.1 Calendar and scheduling considerations for a mixed Notes and DAMO

© Copyright IBM Corp. 2005. All rights reserved. iii

environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612.9 Clustering and failover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652.10 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

2.10.1 Single sign on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672.10.2 Multi-directory install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682.10.3 X.509 and Notes decryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692.10.4 Certificate management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

2.11 Unsupported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722.11.1 Overview of functional differences between DAMO, Outlook, and Notes

722.11.2 Detailed functionality comparison . . . . . . . . . . . . . . . . . . . . . . . . . . 74

2.12 DAMO futures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Part 2. Architecture and deployment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 3. Understanding the DAMO architecture. . . . . . . . . . . . . . . . . . . 893.1 DAMO architecture in detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

3.1.1 Key design criteria for DAMO architecture . . . . . . . . . . . . . . . . . . . . 903.1.2 Overview of DAMO architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.1.3 The DAMO architecture in detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.1.4 The DAMO layer elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953.1.5 The DAMO Extension Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953.1.6 The DAMO replication layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.1.7 The DAMO mapping module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033.1.8 Outlook service providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043.1.9 Add-ins integrated with Outlook . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Chapter 4. Deployment approaches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094.1 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

4.1.1 Migration deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104.1.2 Benefits of migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114.1.3 Key steps that are involved in the migration . . . . . . . . . . . . . . . . . . 111

4.2 Proof of concept deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.2.1 Benefits of proof of concept deployment. . . . . . . . . . . . . . . . . . . . . 1124.2.2 Key steps that are involved in the proof of concept deployment. . . 113

4.3 Mixed environment: client coexistence . . . . . . . . . . . . . . . . . . . . . . . . . . 1144.3.1 Definition of a mixed environment. . . . . . . . . . . . . . . . . . . . . . . . . . 1144.3.2 Benefits of running in a mixed environment . . . . . . . . . . . . . . . . . . 1144.3.3 Key differences between running the Notes and DAMO clients . . . 114

4.4 Mobile, PDA, or Smartphone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194.4.1 Definition of mobile, PDA, or Smartphone deployment using DAMO120

4.5 Automated Deployment Toolkit for Domino Access for Microsoft Outlook1204.5.1 Overview of the ADT tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204.5.2 Configuring ADT to deploy DAMO . . . . . . . . . . . . . . . . . . . . . . . . . 122

iv Domino Access for Microsoft Outlook

4.5.3 Automating the DAMO client setup . . . . . . . . . . . . . . . . . . . . . . . . . 1244.5.4 DAMO client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274.5.5 Deployment considerations for ADT . . . . . . . . . . . . . . . . . . . . . . . . 133

Part 3. Migration and installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Chapter 5. The Domino Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . 1435.1 Preserving Exchange data for use in DAMO or Notes . . . . . . . . . . . . . . 1445.2 How the migration process works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

5.2.1 DAMO-specific components of the Domino Migration Tool . . . . . . 1455.3 Migration and functionality enhancements since the 6.0 release . . . . . . 145

5.3.1 Workflow is enabled for single meetings after migration. . . . . . . . . 1465.3.2 Repeating meetings are fully functional after migration . . . . . . . . . 1465.3.3 Workflow is enabled for Group ToDo's after migration . . . . . . . . . . 1475.3.4 Contacts are fully integrated in the migrated Domino mail file . . . . 147

5.4 How to “Domino enable” your Exchange data. . . . . . . . . . . . . . . . . . . . . 1475.4.1 Preparing for the migration process . . . . . . . . . . . . . . . . . . . . . . . . 1475.4.2 Managing coexistence of Domino and Exchange . . . . . . . . . . . . . . 1485.4.3 Migrating Exchange users and their data to Domino . . . . . . . . . . . 1495.4.4 Installing Exchange as a Foreign Directory Source . . . . . . . . . . . . 1585.4.5 Migrating users from the Exchange server to Domino . . . . . . . . . . 1585.4.6 Converting Exchange addresses to Notes Canonical format . . . . . 163

Chapter 6. DAMO installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696.1 Prerequisites for installing DAMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

6.1.1 System prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1706.1.2 Microsoft Outlook 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

6.2 Installing DAMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1726.2.1 Post installation setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

6.3 Creating a new MAPI profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1886.4 Uninstalling DAMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Part 4. Instant messaging with DAMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Chapter 7. Instant TeamMessenger for Microsoft Outlook . . . . . . . . . . . 1997.1 Instant messaging with Microsoft Outlook. . . . . . . . . . . . . . . . . . . . . . . . 2007.2 Instant TeamMessenger 3.0 overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2017.3 Key features of Instant TeamMessenger . . . . . . . . . . . . . . . . . . . . . . . . 202

7.3.1 Presence awareness, instant messaging, and buddy lists . . . . . . . 2037.3.2 Logging chats to the journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2057.3.3 Calendar entries and Contact List functionality . . . . . . . . . . . . . . . . 2077.3.4 Deployment scenarios for Instant TeamMessenger . . . . . . . . . . . . 209

Part 5. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Contents v

Appendix A. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215The inotesoutlookaddin.dll file and Domino preferences . . . . . . . . . . . . . . . . 216Images not appearing within e-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Password protecting the local .PST file for multi-user DAMO installations . . 219Names are displayed in last name, first name format in the Outlook contact list .

219

Appendix B. Tips for performing a successful migration . . . . . . . . . . . . 221List of issues and solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Appendix C. Functionality comparison between Outlook with Exchange and DAMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Detailed functionality comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Appendix D. Updates to Domino Access for Microsoft Outlook 6.5.5 . . 239New functionality in DAMO 6.5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Silent Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Personal Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Other Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

DAMO 6.5.5 usage hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Connection documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Outlook Deleted Items folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Managed Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Automating DAMO install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Changing the default replication settings . . . . . . . . . . . . . . . . . . . . . . . . . 242

Troubleshooting tips for DAMO 6.5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Domino server access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Debugging parameters in the notes.ini file . . . . . . . . . . . . . . . . . . . . . . . . 243

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

vi Domino Access for Microsoft Outlook

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

© Copyright IBM Corp. 2005. All rights reserved. vii

TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:

Eserver®Eserver®Redbooks (logo) ™iNotes™z/OS®AIX®

Domino®EasySync®Everyplace®IBM®Lotus Notes®Lotus®

Notes®Passport Advantage®Redbooks™S/390®Sametime®Workplace™

The following terms are trademarks of other companies:

Solaris, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

ActiveSync, ActiveX, Hotmail, Microsoft Internet Explorer, Microsoft, NetMeeting, Outlook, SharePoint, Windows server, Windows NT, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Pentium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.

viii Domino Access for Microsoft Outlook

Preface

This IBM® Redbook discusses IBM Lotus® Domino® Access for Microsoft® Outlook®, the software solution that allows Outlook client users to easily access mail and calendar data that is stored on Lotus Domino servers. The target audience for this redbook includes Domino Administrators who are looking to deploy DAMO and migrate from Exchange, business executives who want to understand the advantages of deploying a DAMO solution, and finally, users who wish to better understand how DAMO enables them to continue using their Outlook client in a Domino messaging environment.

If you want to improve the reliability and scalability of your messaging infrastructure and to add collaboration, upgrading from Microsoft Exchange to IBM Lotus Domino Access for Microsoft Outlook (DAMO) provides the solution. With DAMO, you have reliable, scalable, and secure Lotus Domino Messaging to Microsoft Outlook users without requiring users to change from the Outlook client — users simply work with mail, calendar, and task data on Lotus Domino instead of Microsoft Exchange. Familiar Microsoft Outlook features are supported, including rich text, folders and Directory Catalog. Lotus Domino Access for Microsoft Outlook also gives Microsoft Outlook users the additional benefits of Domino Messaging features, including full text search capability for their mailbox and native support for Internet standards (SMTP/MIME and HTML).

This redbook describes the features, functionality, architecture, and typical deployment scenarios for Domino Access for Microsoft Outlook release 6.5.4. This redbook also provides information about a total solution approach with the Domino Migration Tool that is provided with the Domino 6.5.4 Administration Client, which enables migration from Exchange to Domino. Finally, it explains how to integrate Outlook and Lotus Instant Messaging (Sametime®) using Instant TeamMessenger.

© Copyright IBM Corp. 2005. All rights reserved. ix

The team that wrote this redbookThis redbook was produced by a team of specialists from around the world working at the International Technical Support Organization (ITSO), Cambridge, MA.

John Bergland is a project leader at the ITSO, Cambridge Center. He manages projects that produce Redbooks™ about Lotus Software products. Before joining the ITSO in 2003, John worked as an Advisory IT Specialist with IBM Software Services for Lotus (ISSL), specializing in Notes and Domino messaging and collaborative solutions.

Lisa A. Chase is an engineer in the Lotus Software division of the IBM Software Group. She has been part of the IBM Messaging and Collaborative Software group for the past four years, has been a member of the Lotus Notes® Client team, and is currently part of the team engineering the Domino Access for Microsoft Outlook client. Drawing on her knowledge of the Notes Client Calendar and Scheduling functionality and of Microsoft Outlook and Exchange, she is responsible for the current incarnation of the Domino Migration Tool.

Peter Hampton is a Technical Specialist working in the Lotus Messaging and Collaboration Competitive team based in Staines, UK. He has 15 years of experience in Lotus technology, including Notes and Domino migration and co-existence. He has worked at IBM for nine years, joining as a Support Account Manager and working for six years within the Support organization both as a SAM and as a Lotus Service Manager, LSM. His areas of expertise include Domino Architecture and Implementation, Lotus extended products (including Sametime and Quickplace), and Linux®.

Prashant Pandya is a Global Notes Architecture Domino Architect with the IBM Domino Infrastructure for EMEA team with Application Hosting Services, based in Portsmouth, UK. He has seven years of experience in Lotus Notes Administration. His areas of Domino expertise include Domino Administration and support. He holds a degree in Law from Staffordshire University, UK, and a Post Graduate Diploma in Legal Practice from Bournemouth University, UK.

x Domino Access for Microsoft Outlook

Additional ContributorsThanks to the following people for their contributions to this project:

Sarah BoucherSoftware Development Manager, Messaging and Collaboration Development, IBM USA

Brendan CrottyIBM Software Group, Lotus Product Management, IBM, Westford, MA

Paul A. JoviakSoftware EngineerIBM, Westford, MA

Steve SterkaManager, Product Development and SupportWolcott Group, LLC (http://www.wolcottgroup.com)

Carl TylerChief Technology OfficerInstant Technologies (http://www.instant-tech.com)

Ravinder DhaliwalSoftware Services Manager Software Group ServicesIBM Australia

Graeme PovallTechnical Specialist IBM UK

Michael Rowe, Software EngineerIBM, Portsmouth, NH

Preface xi

http://www.wolcottgroup.com

http://www.instant-tech.com

Become a published authorJoin us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners, or customers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

Comments welcomeYour comments are important to us!

We want our Redbooks to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways:

� Use the online Contact us review redbook form found at:

ibm.com/redbooks

� Send your comments in an e-mail to:

[email protected]

� Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. HYJ Mail Station P0992455 South RoadPoughkeepsie, New York 12601-5400

xii Domino Access for Microsoft Outlook

http://www.redbooks.ibm.com/residencies.html

http://www.redbooks.ibm.com/residencies.html



http://www.redbooks.ibm.com/contacts.html

Part 1 Overview of DAMO

Part 1

© Copyright IBM Corp. 2005. All rights reserved. 1

2 Domino Access for Microsoft Outlook

Chapter 1. Introduction to DAMO

IBM Lotus Domino Access for Microsoft Outlook provides a way for companies to experience the robust messaging and group scheduling capabilities of Domino while running Microsoft’s Outlook client on the desktop. Based on Domino's advanced streaming replication algorithm architecture, DAMO allows users to easily access mail and calendar data that is stored on Lotus Domino servers.

This chapter provides a basic introduction to IBM Lotus Domino Access for Microsoft Outlook (DAMO).

1


1.1 Overview of DAMOBeginning with the release of the Domino 6.5.1 and continuing forward to subsequent releases, IBM Lotus has delivered all Domino-based collaboration products on a common set of operating systems, languages, and supported browsers. A significant step in the release, testing, and support of these products, this release strategy ensures that when installing or upgrading, you can be confident that all of the 6.5.1 or later products work seamlessly with one another and are backwards compatible with previous releases.

DAMO is an important part of the 6.5.1 or later platform. It represents the continuing commitment of IBM Lotus to integrate its technology with software from other vendors, while maintaining the inherent strengths of the Lotus Domino Messaging and Collaboration products.

DAMO delivers the leading messaging, calendaring, scheduling, and personal information management of Domino to the Outlook 2000, 2002, XP, and 2003 client. When installed, users continue to read their mail, perform calendar and scheduling tasks, and manage their contacts in Outlook just as they always have. Behind the scenes, however, DAMO enables the Outlook client to work seamlessly with the Domino server. Because users can continue to use the Outlook client, only minimal retraining is required.

Figure 1-1 on page 5 illustrates an overview of an Outlook client that is accessing data on a Domino Server.


Figure 1-1 Outlook client - accessing data through a Domino Server

Key benefits of the DAMO solution include:

� Allowing companies a means of delivering messaging, calendar, group scheduling, and contacts features of Domino, while leveraging their investment in Microsoft Outlook.

� Letting users continue using their Outlook client with virtually no retraining. Users can continue to read mail, perform calendar and scheduling tasks, and manage PIM data, with the added benefits of Domino network security, replication, and clustering.

� Installing easily using standard MSI technology. You can easily update desktops using your company's standard software delivery system.

� Allowing access to messaging and calendaring capabilities from a variety of clients, including the Notes Client and Domino Web Access.

Chapter 1. Introduction to DAMO 5

� Migrating to security-rich, reliable, and scalable Domino servers. You can take control of your messaging infrastructure as well as reduce unwanted SPAM.

� Using the server platform and directory that is best for your company. You can run Lotus Domino servers on multiple hardware platforms and software operating systems.

� Reducing network traffic. You can transport messages throughout your infrastructure using Domino's advanced streaming replication and built-in data compression.

DAMO is unique, because it installs as an interface layer between the user’s existing Outlook client on the user’s workstation and the Domino Server. It is virtually transparent to the user.

DAMO takes the form of a standard MSI installer package which can be easily installed through your existing software distribution tool, allowing for minimal administration and user intervention. An MSI package also has the advantage of being easily tailored for you organization’s specific needs.

The main product components for DAMO include the following:

� Installation Package and Client upgrade

– Installation program is standard Windows® MSI

– Similar to the Notes Client Setup

– Compatible with SMS and Others

� Core Client Files

– Enable data synchronization between Outlook and Domino

� Outlook Plug-in

– Out of Office and User Password Change

– Help Files

– Domino Preferences

DAMO also has a very small desktop footprint (approximately 30 MB, excluding the users mail data), which also helps ease its deployment.


When DAMO is installed, instead of accessing Microsoft Exchange servers, Outlook users access Lotus Domino servers. This activity is virtually transparent to the Outlook users and provides an increased quality of service due to the following benefits of Domino:

� Integrated SPAM prevention

� Streaming replication

� Network compression

� Increased network security

� Advanced automated server failover, load balancing and data restore, and recovery features

1.2 Business value overview, migration, and DAMOOrganizations can greatly improve the reliability and scalability of their messaging infrastructure by upgrading from Microsoft Exchange to Domino for a number of major reasons, including:

� Scalability: Because most Lotus customers deploy Domino with a single mailbox per user approach, scaling up to thousands of users has little impact on serviceability. A problem with a mailbox affects one — and only one — user on a server. This architecture is what has allowed IBM to consolidate its own environment to 11,000 mailboxes per Domino server. Domino also supports the same concept of a shared mailbox (one store, multiple users) just as Exchange uses. However, this approach can create a single point of failure, and as such, Lotus customers rarely use this configuration.

� Reliability: The NSF architecture is also what makes Domino reliable. Because of the one-database-per-user architecture, Domino supports individual mailbox backup and recovery. Further, these mailboxes can be clustered across multiple Domino servers, on a per-user basis, in a true "shared nothing" architecture for "hot site" recovery. The Exchange store is also a single point of failure when it comes to clustering. Exchange's clustering capability provides what a Windows server™ offers — a shared-disk cluster model. That makes the already vulnerable data store a single point of impact in a cluster. If the disk storage goes away, all cluster nodes necessarily fail. Thus, "hot site" disaster recovery is typically not an option for Exchange customers.


� Forward and backward compatibility: Because the Notes/Domino data store has been so consistent, backward and forward compatibility has been possible throughout Notes' history. A Notes R2 application can quite successfully run on a Domino 6 Server, with no modification. As Domino servers are upgraded from Release 4 to 5 to 6, there is no technical requirement to migrate or convert existing databases. While it is certainly beneficial in new releases to convert to later versions of the "on disk” structure, this is an invisible process to users and administrators and can be planned as part of a customer-controlled upgrade timetable.

The consistency of the data store is what provides coexistence during Domino release upgrades and even allows for fallback during an upgrade process. Domino can always save an NSF in the format of a previous release. This is why direct upgrade from Domino Release 4 or later to Domino 6 is supported. The consistent architecture allows for Releases 4, 5, and 6 to inter-operate, and this same principle will apply with the forthcoming release of Notes and Domino 7.

DAMO allows organizations to accomplish migration without needing to change clients. This is significant in minimizing user disruption and drastically reducing the costs of messaging migration, client deployment, and most importantly user training.

Also, by moving from Exchange to Lotus Domino, organizations are migrating to a secure, reliable, and scalable Lotus Domino messaging infrastructure that can use the hardware and operating system platforms that are supported by Lotus Domino. This gives organizations far more server side deployment flexibility than Microsoft Exchange and allows them to more effectively leverage the performance, scalability, and reliability of different types of hardware and, more significantly, a multitude of non-Windows-based operating systems. Finally, it helps administrators control IT costs that are associated with this change.

Domino Access for Microsoft Outlook also provides a number of benefits for users. The primary benefit is that it gives companies a means of delivering the messaging, calendar, group scheduling, and contacts features of Domino while leveraging their investment in Microsoft Outlook. Those users who are familiar with Microsoft Outlook need relatively little training to install and use Domino Access for Microsoft Outlook. Users or groups that have a requirement or desire to run Outlook can continue to do so and still be able to work side-by-side with Notes users.

Important: All of these features (and many others not covered here) are built in to Domino and, therefore, require no additional product purchases or installation.


These benefits are discussed in more detail in the next section and throughout the rest of this chapter.

1.3 Key advantages of using DAMO and Outlook with Lotus Domino

DAMO gives Microsoft Outlook users the additional benefits of numerous out-of-the-box Domino features that are not available with Microsoft Exchange. Some of these key benefits are:

� Multiple operating system support: Lotus Domino servers are supported on multiple hardware platforms and software operating systems (such as Linux, Solaris™, AIX®, OS400, S/390®, and Windows). This gives organizations far more deployment choices and allows them to leverage the increased scalability, reliability, and performance that is available on non-Windows-based operating systems.

� Clustering: A cluster is a group of Domino servers that provide clients with automatic load balancing and failover if a server or servers in the group are not available. Servers might be inaccessible due to planned outages, such as upgrades, or due to unplanned outages, such as hardware failures.

Clustering is a built-in Domino server feature and has been available since Release 4. It works at the Domino server level and is completely independent of the underlying hardware and operating system. Thus, it allows a cluster to contain servers with completely different hardware and operating systems. This gives organizations far more deployment choices for load balancing and failover and also allows them to leverage the scalability, reliability and performance available with different operating systems. For example, a cluster can contain servers running Windows 2000, Linux, Solaris, and AIX, but the load balancing and failover is automatic and transparent to the client regardless of whether the client is Outlook, the Notes client, or even a browser using Domino Web Access (DWA).

DAMO, therefore, takes full advantage of Domino’s built-in advanced clustering features, providing Outlook users with a fully reliable messaging system at all times without any client side configuration or having to purchase any additional failover and load balancing products.

Note: DAMO is part of the 6.5.1 or later platform and can be downloaded from the Lotus Passport Advantage® Web site. It is also important to note that DAMO ships as a standard feature of Domino Release 6.5.4.


� Replication and network compression: DAMO enables the Outlook client to use Domino’s advanced streaming replication technology to synchronize the native Outlook PST storage file, which is located on the user’s machine, to a Domino-based mail file that resides on the Domino server. Users work with their mail and calendar offline, and their data is synchronized with the server each time they connect, thus greatly improving user performance while at the same time reducing network bandwidth use.

DAMO takes full advantage of the Notes Remote Procedure Call (NRPC) protocol to send mail from client workstations to the Domino server and for mail routing between servers. Domino’s built-in compression significantly decreases the number of bytes of data that is sent during these transactions, thus reducing network bandwidth usage and leading to reduced costs and increased network availability.

� Preventing unwanted or unsolicited e-mail: DAMO allows Outlook users to leverage the Domino server’s anti-spam technology. This allows administrators to manage SPAM at the server level, therefore drastically reducing the amount of unwanted mail that reaches the user’s inbox. Some of the many Domino anti-SPAM features include:

– Domino Name System (DNS) Blacklists which allow incoming e-mails to be checked against lists of known SPAM offenders.

– Server-based mail rules where administrators can set filtering conditions based on specific criteria and then define actions to take.

Reducing the amount of unwanted mail makes users more productive, eliminates wasted storage, and reduces network bandwidth usage.

� Ease of installation: One of the biggest costs that is associated with messaging infrastructures and messaging migrations is the cost in deploying new client software and re-training users.

Because DAMO installs easily using standard MSI technology, user workstations can be updated automatically using a company's standard software delivery system (such as SMS or Active Directory Services).

As a result of using standard MSI technology, DAMO installations can be fully scripted and tailored to your organization’s specific needs. There are also many solutions and consulting services available from IBM and IBM Business Partners that can assist with migration and installation.


� Choice of client access: DAMO supports inter-operability between Lotus Notes, Domino Web Access, and Outlook users, including the ability to send and receive e-mail and perform free and busy time lookup and calendar functions for users, as well as support for rooms and resources. For example, if you have some users on the Lotus Notes client, some on the Domino Web Access client, and others on Outlook, they can each view the others’ busy time calendar information and send meeting invitations, seamlessly, without knowing which client the other is using. In addition, you can also provide your Outlook users access to their mail, calendar, and contacts data via a Web browser (including users running Mozilla on Linux or Mac).

� Domino preferences in Outlook: DAMO adds a new Domino Preference tab to Outlook’s Options display menu. This integrated display add-in provides access to many Domino features and settings, such as:

– Changing the password for Notes ID. Retaining the Notes ID ensures the continued high level of security that is inherent in all Domino environments.

– Enabling or disabling the Out of Office agent to notify others of availability.

– Managing replication settings to control the time and schedule of automatic data replication between the DAMO Outlook client and the Domino Server.

– Setting some general preferences for mail and calendar, including Calender Scheduling, Auto Process and Mail, and managed Calender Access.

– Allowing for user security with the ability to import X.509 certificates to the Notes ID.

– Managing a local address book with the ability to pull down a copy of the Domino Directory local for mobile users.

� Greatly reduced migration costs: When migrating existing Exchange users and servers to Domino, you can choose to switch all users over at a single time or, more typically, to have periods of co-existence where both systems are in production.

Domino includes a built-in set of automated migration tools for migrating from Exchange (as well as numerous other messaging and directory products) to Domino. This full set of tools is referred to as Domino Upgrade Services (DUS). For information about the Domino Migration Tool, see Chapter 5, “The Domino Migration Tool” on page 143.


With the Domino Migration Tool, you have complete flexibility when it comes to the migration and configuration of users from Exchange to Domino, with no additional costs for migration tools. The Domino Migration Tool, in conjunction with DAMO, gives you complete flexibility and control because it allows you to automate the migration and configuration of user’s mail and calendar entries either on an individual basis or for logical groups of users (for example, by Exchange server, department, or geographic location) without the cost of purchasing additional migration tools. Finally, there are a number of IBM Business Partners who produce well respected migration and distribution tools and who provide migration services that are used to migrate to Domino. These tools include Binary Tree with the Common Migration Tool (CMT) and Wolcott with the ADT offering.

1.4 Overview of typical DAMO deployment topologiesFigure 1-2 on page 13 shows a typical scenario of an Outlook client with DAMO installed that is accessing mail on a Domino Server. The Outlook client user simply logs on to the Windows file server as normal (for example, a Windows 2000 or Windows 2003 server), and through the single sign on feature in DAMO, the user is able to access their mail which is now on a Domino server.

Note: While Domino includes a full set of automated tools for migrating messaging and directory products. This book focuses specifically on the Domino Migration Tool. The Domino Migration Tool enables the migration of data from Exchange to Domino and, more specifically beginning with Domino 6.5.1, began supporting migration of data from Exchange for use in the DAMO client.

Note: Notice how the Domino servers in this scenario are clustered for failover, despite being on completely different operating systems. Domino clustering allows for active users on both servers, and these users can be any mixture of Notes client, Web browser, or DAMO users


Figure 1-2 Using DAMO with Domino mail servers

Figure 1-3 on page 14 and Figure 1-4 on page 15 show how DAMO fits into a topology that also incorporates the use of instant messaging using the IM technology that is provided by Instant Tech, both using Domino for Directory services and an external LDAP.

User is accessing the data locally and replicating data (Mail, Calendar, Contacts, and so forth)between the PST (locally) and NSF (server) file


Figure 1-3 Using DAMO with Domino mail servers and instant messaging

Figure 1-4 on page 15 illustrates a scenario in which DAMO can be used in an environment of clustered Domino Servers, using Lotus Instant Messaging (Sametime) Instant TeamMessenger. Additionally, it shows how the Domino Directory is used for authentication with DAMO. If the Domino server you authenticate with has Directory Assistance (DA) configured to point to other directories (including LDAP, then DAMO can use or query those LDAP directories for mail addressing purposes.


Figure 1-4 Using DAMO with Domino mail servers, a corporate LDAP directory and instant messaging


1.5 Why Outlook support is importantDomino offers a consistent, enterprise grade architecture that provides greater levels of scalability, better reliability, built-in automated failover, and load balancing together with virus handling and anti-spam protection features that are more robust than those of Microsoft Exchange or which Exchange does not provide.

Even with these features, changing the Outlook client is often strongly resisted by users because with change comes uncertainty and the requirement to learn new skills. This uncertainty in turn can lead to a loss in user productivity and, therefore, an overall rise in costs. If users are resistant to change, then offering users the ability to retain what they already know can help to ensure acceptance from your user base. More importantly, your user base can remain productive and satisfied while your organization takes advantage of the multitude of benefits from moving to a Domino based backend infrastructure.

1.5.1 Common platform for messaging and collaborationIn such cases, standardizing on a common Lotus Domino backend for messaging and collaboration helps reduce Total Cost of Ownership (TCO). Alternatively, the cost of deploying a new messaging client and retraining users can prove to be prohibitive and, to a certain degree, could start to negate any TCO savings realized by implementing the Lotus Domino infrastructure.

By providing a common platform for all client messaging options, this helps reduce the TCO of a messaging and collaboration environment as an overall entity, taking advantage of the Lotus Domino benefits from a server perspective and ensuring minimal disruption to your user base from the client side. Ultimately, users remain as productive as possible.

It is also quite common for organizations to operate multiple messaging systems comprised of both Lotus Domino and Microsoft Exchange. This is often the case when organizations merge or when one company purchases another. With this in mind, the DAMO solution is a valuable option for many organizations who are concerned about mitigating risks and costs in order to achieve a more robust messaging and collaboration infrastructure. Therefore, DAMO can be best used by:

� Existing Outlook or Exchange customers who are looking for alternatives to Microsoft fault tolerance and who want to improve server end security, scalability, and reliability. While gaining from the benefits of Domino, they also want to retain existing Outlook user base.


� Mixed environments that are moving towards standardization on a Domino messaging server. The emphasis is on reaching a suitable, value add solution for coexistence, rather than simply replacing one e-mail system with another.

1.6 Migration and DAMO — the total solutionDAMO and the continued use of your existing Outlook client user base is only half of the story. The other half of this scenario is the migration of user mail data from the incumbent Exchange mail system to a Lotus Domino infrastructure. This migration is performed using the built-in migration technology that is included with the Lotus Notes Administrator client.

Using the Domino Migration Tool, you have the opportunity to move away from your existing Exchange environment. You can move as much or as little of your existing client messaging and calendering data as is required. Then, after the user accounts are created in Domino and the user data is migrated, the existing Outlook user base, using DAMO, can gain access to this historical data and all new data.

The migration of historical user mail data presents not only technical and administrative requirements but can also support certain legal and political requirements as well. Depending on industry regulation or the local laws that affect a particular territory, it might be a requirement to preserve all data for a predefined amount of time.

Accordingly, this book discusses how to move data from the existing Exchange data store to Domino using the Domino Migration Tool to migrate messaging data in a way that is both simple to accomplish and also satisfies user and customer requirements relating to the access of that data. In addition, this book also includes the options around retired data, namely data that has been migrated to a user’s local PST data store and is accessed using the Outlook client on a local machine. This data is not considered to be live data because it is not replicated to the Lotus Domino server.

1.7 Multiple client strategyThe principle behind the development of all of the IBM Lotus Messaging and Collaboration client technologies is to offer increased choice and opportunity, rather than steering you down any particular technology path. In addition to offering choice, the Domino server is platform independent so that you can choose the hardware and operating system that best suits your business need.


With the continued improvements to DAMO client, IBM Lotus continues to deliver on their commitment to provide flexibility and choice of using more than one messaging client. Users of Domino messaging technology can choose between using the Notes Client, Domino Web Access, DAMO, or the Domino plug-in for the IBM Workplace™ Managed client to access messaging data. These options have significant and beneficial impact for the user as well as system administrators, both from a TCO and an administrative perspective. You can use utilize IBM Lotus technology to best fit with you business needs. DAMO further realizes this commitment from IBM Lotus.

1.8 Version compatibility between DAMO, Outlook, and Domino

Table 1-1 illustrates version compatibility between the DAMO 6.5.4 client, the various Outlook client versions, and the Domino Server version.

Table 1-1 Compatibility reference

DAMO version Outlook version Domino Server Windows

DAMO 6.5.4 Outlook 2000 with SP3Outlook 2002/XP/SP3Outlook 2003 with sp1

6.5.1 or higher running:� Mail6.ntf� Mail6ex.ntf � iNotes6.ntf

Windows XP ProfessionalWindows 2000

Note: When referring to versions of Outlook, Outlook 2002 is frequently referred to as Outlook XP. These versions are the same.


1.9 Structure of this bookThis book is divided into four parts that provide a comprehensive overview of DAMO. Here is a synopsis of the topics that are covered in this book:

� Part 1, “Overview of DAMO” on page 1

Chapter 1, “Introduction to DAMO” on page 3 is the chapter that you are reading now.

Chapter 2, “Features and functionality” on page 21 describes the features and functionality of the DAMO client in detail. More specifically, it covers the following topics:

– Overview and comparison between native Outlook and DAMO functionality

– Retained Microsoft Outlook features

– Additional DAMO features for Microsoft Outlook

– Usability of added DAMO functionality to Outlook

� Part 2, “Architecture and deployment considerations” on page 87

Chapter 3, “Understanding the DAMO architecture” on page 89 describes the architecture of DAMO and its design criteria. It also discusses in detail how the DAMO layer links Outlook to Domino. The DAMO architecture and design is key to providing familiarity of the current Outlook client together with the stability and scalability of Domino in the background.

Chapter 4, “Deployment approaches” on page 109 discusses the major deployment scenarios where DAMO would likely be used to satisfy the requirements of existing or potentially new Outlook users who need to integrate messaging and calendering with Lotus Domino. These deployment scenarios are:

– Migration– Proof of concept– Mixed environment (co-existence)– Mobile, PDA, or Smartphone

Within the context of these basic scenarios, this chapter covers the basic requirements for a rollout, what deployment result you should expect to see, and the varying benefits of each of these defined deployment scenarios. Finally, this chapter also discusses the Automated Deployment Tool (ADT) for DAMO that is provided by Wolcott Systems Group, LLC as a solution for a larger scale DAMO deployment.


� Part 3, “Migration and installation” on page 141

Chapter 5, “The Domino Migration Tool” on page 143 offers an overview of how to migrate users from Microsoft Exchange to Domino using the Domino Migration Tool (formerly known as Domino Upgrade Services). This chapter gives an overview of the took and provides step-by-step instructions on how to use the tool.

Chapter 6, “DAMO installation” on page 169 discusses and illustrates the procedure for installing DAMO.

� Part 4, “Instant messaging with DAMO” on page 197O

Chapter 7, “Instant TeamMessenger for Microsoft Outlook” on page 199 discusses Instant TeamMessenger 3.0, the product by Instant Technologies (http://www.instant-tech.com), which provides both the instant messaging and presence awareness capabilities of Sametime for use with the Outlook client.

� Part 5, “Appendixes” on page 213

Appendix A, “Troubleshooting” on page 215 identifies and discusses how to troubleshoot some of the more common issues that we experienced while using DAMO.

Appendix B, “Tips for performing a successful migration” on page 221 provides tips for a successful migration from Exchange to Domino.

Appendix C, “Functionality comparison between Outlook with Exchange and DAMO” on page 225 provides a detailed functionality comparison between using Outlook 2003 in a native Exchange environment and using the Outlook 2003 client with DAMO 6.5.4 within a Domino environment.


http://www.instant-tech.com

Chapter 2. Features and functionality

This chapter covers the various features and functionality of the IBM Lotus Domino Access for Microsoft Outlook client (DAMO). It is this comprehensive set of features that make DAMO such a valuable asset to your Messaging infrastructure for Outlook users. DAMO allows users to retain Outlook as their mail client within a Domino messaging infrastructure, which is designed to provide an easy means for companies that use Outlook and Exchange to move users to Domino.

Outlook is a fully functioning Mail and Calender client. The primary goal of DAMO is to retain the existing Outlook functionality to which current users have become accustomed. At the same time, DAMO adds specific Domino functionality to the Outlook client in order to take advantage of the messaging improvements that are gained by implementing a Domino infrastructure. All of this is accomplished while minimizing to the greatest degree any visible changes to a user.

Users who are familiar with Outlook and desire to continue using the Outlook client can now do so without any significant loss of functionality. With minimum training and education, these users can understand and take advantage of the added functionality that DAMO brings.

2


2.1 Overview of new features in DAMO 6.5.4With the release of the DAMO 6.5.4 client, Lotus has made significant improvements on the usability of existing functionality and has also managed to include many additional features that customers have requested. A selection of these improvements and additions are listed here:

� Local Directory Catalog (Dircat) Support

� User support for DAMO / DWA or NOTES with no additional configuration using a single server-side mail file built using the mail6ex.ntf or inotes6.ntf

� New Graphical Mail Alert support indicating new mail on Server

� Enabling of windows single sign on (SSO) post DAMO installation by "Modify Install" option

� Multi-User Install Option - LockDown Desktop

� X 509 / Internet Certificate Support

� Greatly improved performance over DAMO 6.5.3, in some situations better than Outlook on Exchange

� Initial setup provides a Progress Bar for the initial replication to local PST and user can continue to send or receive mail

� Sending e-mail is instant, no replication on "Send"

� Port Encryption

� Directory Assistance and Cascaded Directory

� Calendar and Mail Delegation

� Contacts are now migrated and are part of the NSF and "travel" with you (between DAMO, Notes and DWA)

� Migration now includes an "Address Resolution" tool for resolving SMTP addresses to Domino names

� Doclinks are converted to Notes URLs (Word as default editor)

� Minimal user training


2.2 Mail and Calendar interface features comparisonThis section discusses the interface features that are available within DAMO in Outlook using a backend Domino Server in comparison with Outlook using a Microsoft Exchange server. It provides examples, as well as a table (Table 2-1 on page 28) that summarizes the interface feature comparison.

We begin with a look at the DAMO user interface. This is an important area to concentrate on, as users in most cases are already familiar with the Microsoft Outlook client. Additionally, it is in this user interface where new users will most likely form their first impressions of the product.

Figure 2-1 on page 24 illustrates the DAMO interface.

Important: This section highlights the interface functional comparison. A subsequent section (2.6, “Domino versus Exchange functional comparison” on page 55) provides a more comprehensive functional comparison.

Chapter 2. Features and functionality 23

Figure 2-1 DAMO Outlook inbox view

As you can see, the appearance of Outlook using DAMO is exactly the same as an Outlook client that is used to connect to an Exchange server. In the same way that an Outlook client accesses a local .PST file when used in an Exchange environment, the Outlook client does the same with DAMO. The inbound data is translated by DAMO and placed into the local .PST file. Accordingly, due to the translation process, nothing is different as far as Outlook is concerned. Outlook only sees its native data store, therefore negating any potential compatibility issues. Likewise, outbound mail that is generated in the Outlook client is translated by DAMO and forwarded to a Domino data store that is located on a Domino server. Again, due to the translation performed by DAMO, Domino receives the information in its own data store format as well.

Migrated Folder StructureInbox View Preview Pane


The same integrity is also true for the Calender, as shown in Figure 2-2.

Figure 2-2 DAMO Outlook calender overview

Note: The technical details of the DAMO translation are described in detail in 3.1.6, “The DAMO replication layer” on page 96.


Additionally, as shown in Figure 2-3, the DAMO generated Calender entries show as busy time, just as they would if generated within an Exchange or Outlook environment.

Figure 2-3 Schedule and busy time dialog


Finally, the same standard view theme carries through to the Tasks view as well, as shown in Figure 2-4.

Figure 2-4 DAMO Outlook Tasks overview

One of the primary design goals of DAMO is to ensure that the user experience is as close to that of a regular Outlook client as possible. With this latest 6.5.4 release of the DAMO client, you can see that the Domino-specific additions have been implemented in such a way to compliment the existing structure of the Outlook client and to ensure compatibility with Lotus Domino. This provides users currently experienced in using Outlook with the best of both worlds.


Table 2-1 details the currently available DAMO features in Outlook (with a Domino Server) in a comparison with using Outlook with a Microsoft Exchange server:

Table 2-1 Interface features

Table 2-1 illustrates how all of the Interface features of Outlook are preserved with DAMO, including the Local Folders, Navigation Pane, Help, and Shortcuts.

2.3 Performance improvements within DAMO 6.5.4With the 6.5.4 release of DAMO, there have been considerable performance improvements over the 6.5.3 release.

� DAMO using Outlook 2000 is up to three times faster� DAMO using Outlook XP is up to 48 times faster� DAMO using Outlook 2003 is up to 16 times faster

Interface features Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Research Library Task Pane Yes Yes

Reading Layout mode Yes Yes

Get address properties from Reading Pane

Yes Yes

Notification area icon Yes Planned for 6.5.5 2H '05

Outlook Today Yes Yes

Group items by any field Yes Yes

Local folders Yes Yes

Reminder window Yes Yes

Customizable toolbars Yes Yes

Help Yes Yes

Navigation Pane Yes Yes

Shortcuts Yes Yes


Table 2-3 on page 56 shows a comparison of startup times between DAMO 6.5.4 on Outlook running against Exchange.

Table 2-2 Comparison of startup times

Startup times are an area to which users are particularly drawn. To satisfy user needs, 6.5.4 has been designed to ensure that the DAMO Outlook mail client performs as quickly as possible for high levels of user satisfaction and productivity.

2.3.1 System requirementsThis section highlights the user and administrator system user requirements. the system requirements for the use of DAMO with Outlook are relatively low, helping to ensure that any existing PC that is currently running Outlook successfully will be able to use DAMO without the need for any hardware upgrade. This again fits the requirement to minimize the need for desktop visit, thereby further expediting the success of a DAMO rollout.

User minimum hardware requirements

� Intel® Pentium® P133 processor or higher

� 136MB RAM

� 135MB disk space

User software requirements

� Microsoft Outlook 2000/2002 with SP 3 or Outlook 2003 with SP1

� Microsoft Windows 2000 and Windows XP (Professional Edition)

Administrator software requirements

� Lotus Domino server 6.5.1 or higher,

� Domino Administrator Client 6.5 or higher (6.5.1 or higher recommended)

DAMO 6.5.3 DAMO 6.5.4 Exchange

Outlook 2000 XP 2003 2000 XP 2003 2000 XP 2003

Seconds until user ready

24 48 48 8 1 3 6 1 10

Tip: As a best practice, we recommend using the latest version of Domino and DAMO for optimal versions of Domino Upgrade Services (DUS) and the Notes client.


2.4 Domino-specific functionality added to Outlook through DAMO

There are a number of minor visual differences made to the Outlook client after the DAMO add-in has been installed. These changes mostly relate to the addition of the Domino Preferences tab, which is located within the standard Outlook Options dialog, and its associated options and the additional DAMO associated Help. Over the following few pages, we provide an overview of these features to show you what Domino-specific functionality has been added through the installation of the DAMO client.

Figure 2-5 shows details about the Domino Preferences tab. All of the newly added Domino-specific options have been neatly added to a single tab that is located within the regular Outlook Options dialog. You access this tab from the main Outlook menu by selecting Tools → Options. Additionally, the DAMO About and Help documentation, which is accessible via the mail Outlook Help menu option, discusses each of these features in detail.

Figure 2-5 Domino Preference tab in Outlook Options dialog


2.4.1 Domino Preferences tabThe Domino preferences tab is added to the Outlook options from an installed .dll file, inotesoutlookaddin.dll. Within a default install, this file can be located within the following directory:

C:\Program Files\DominoforOutlook\inotesoutlookaddin.dll

We now examine in greater detail the DAMO features that are installed and displayed in the Domino Preferences tab.

Change PasswordThe first of these features is the Change Password option, as shown in Figure 2-6.

Figure 2-6 Domino Preferences — Change Password


Selecting Change Password opens the Change Password dialog, as shown in Figure 2-7.

Figure 2-7 Change Password prompt

This change password dialog prompts you to enter your old password, a new password, and a confirmation of the new password.

After you have entered the required information, which is hashed on display, DAMO makes the appropriate changes to the user.ID file, which is located in the C:\..\dominoforoutlook directory. This file is a Domino created .ID file, which is created when the user account is created on the Domino Server. It is responsible for the security and access of the Domino data that is contained within the Outlook .PST file, which is accessed via the Outlook client.

Note: When single sign on is used, changing your password for DAMO will also change your Windows log on password to the new value.


Out of OfficeThe next option in the Domino Preferences tab is the Out of Office function, as shown in Figure 2-8.

Figure 2-8 Domino Preferences — Out of Office

Selecting Out of Office opens the Out of Office dialog, as shown in Figure 2-9 on page 34.


Figure 2-9 Out of Office dialog

Alternatively, you can also open the Out of Office dialog from the Outlook menu by selecting Tools → Out of Office, as shown in Figure 2-10.

Figure 2-10 Out of Office menu selection


There are a number of options within the Out of Office dialog. Within this dialog you can:

� Enable or disable the out of office functionality.� Select the start and finish dates.� Edit the automatic reply message that is sent when Out of Office is enabled.

Similar to the use of a Lotus Notes client, the DAMO client sets the Out of Office parameters, and these settings are enacted on the server, negating the need for the client to be active for Out of Office to operate.

Additionally, just as with the Notes client functionality, at the due back date, the user receives a mail from the server that details a list of every person that has mailed them while they have been away. This mail message also prompts the user to disable Out of Office. If the user forgets to disable Out of Office, the server sends a reminder each time the client is started.

Replication settingsNext down the list of Domino preferences is Replication , as shown in Figure 2-11.

Figure 2-11 Domino Preferences — Replication


When you select Replication, the dialog shown in Figure 2-12 displays.

Figure 2-12 Domino Preferences Replication Settings

There are a number of available options within the replication settings, including the name of the preferred server, the mail file size limit, and mail encryption, much as in the Lotus Notes replication options. These settings are user configurable.

Preferred serverThe name of the preferred server relates to the user’s home mail server and uses this server name information to attempt the connection in order to replicate the user’s mail. If this server is part of a cluster, the replicator tool attempts to replicate mail data with this server first. If it cannot make a connection, it then looks through the list of server names (cluster members) in the cluster.ncf file, located in the ..\DominoforOutlook director. The cluster.ncf file contains information about all servers within the cluster and attempts to connect to the next server in the list. The replicator continues working through the list until it connects to a mail server within the cluster. When this connection has been established, it then replicates the user’s mail. This is done without any notification or prompt to the user. The connection is established in the back ground and appears seamless to the user.


Server mail file thresholdThe server mail file threshold relates to the size of any mail file limit, in increments of 25 MB to a maximum of 1.6 GB (or 1600 MB). The value in this field is set by Outlook to 200 MB by default. The mail file size is a limit and not a quota, for which if the server mail size is greater than the limit set in this field, the number of days to replicate is invoked. The number of days refers to the number of days of documents to retrieve from the server, not the number of days to keep the documents. It is used as a way to limit the amount of data read into the local cache.nsf and then the .PST file

Replication of outbound messages, encryption and compressionThe next option relates to the replication of outbound messages. You can allow a number of outbound messages to accumulate before actually being sent. However, the default is set to 1, meaning that as soon as a mail has been created, replication is initiated as soon as Outlook registers that a new mail message is ready for delivery. The next option sets encryption of network data, and the final option sets compression of network data. You can configure all of these settings.


PreferencesThe next option within the Domino Preferences tab is called Preferences, as shown in Figure 2-13. The Preferences option allows you to specify mail and calendar formatting preferences as well as mail delegation rules.

Figure 2-13 Domino Preferences — Preferences

When you select Preferences, a dialog opens that contains the following tabs:

� Calendar Scheduling� Autoprocess� Access to Your Mail & Calendar� Access to Other’s Mail


Calendar schedulingThe first Preferences option that is available is Calender Scheduling (Figure 2-14).

Figure 2-14 Calender Scheduling in Domino Preferences

With Calendar Scheduling, you can select the time range of your calender within any given week. Each day of the week is selectable individually via a check box. You can also define the time range for each day. This also sets the start and finish times with regards to free or busy time look ups and indicates to anyone attempting to schedule a meeting with you the range of time in which you are available. In the example shown in Figure 2-14, the user is available only between the hours of 9 a.m. and 5 p.m.

Figure 2-14 also illustrates the option for selecting the appropriate time zone setting. By default, this field displays the same time zone information as provided by the operating system.


AutoprocessThe next tab in the Preferences option is Autoprocess, which allows you to automate the process of responding to calender invitations (Figure 2-15).

Figure 2-15 Autoprocess preferences

This dialog gives you the opportunity to select predefined actions to meeting invitations that you receive. These include, for example, the ability to respond to anyone automatically or the definition of a selected group of people to a meeting invite with an acceptance notice on the basis that you have free time.

Delegating or gaining access to a user’s mail fileThe final two tabs within the Preferences option focus on granting access to a user’s calender and mail. One tab allows you to specify which users have access to your mail and calendar, while another tab indicates who has delegated access of their mail file to you.


An overview of the dialog is shown in Figure 2-16.

Figure 2-16 Access to Mail and Calender

Access to your mail and calendarThe dialog is divided into two parts. The first portion of the dialog, (the upper part), allows the user to select specific names or groups to the list who will be granted access to your mail and calendar. After the names have been added to the list, the lower part of the dialog allows you to specify exactly which level of access will be granted for each selected user within the list. Figure 2-17 on page 42 illustrates how you can determine just how much (which functions) of the mail file for which you wish to delegate access and which specific rights you wish to assign.

Access to other mail files

People to whom you have grantedaccess


Figure 2-17 Controlling level of access for each user granted access to your mail file

Access to others’ mailThe last tab in the Preferences option is Access to Others’ Mail (Figure 2-18 on page 43). As the name suggests, it is here that you are able to add other users’ mail to your Outlook desktop, assuming that other users have granted the necessary access privileges.

Note: You are limited to selecting 13 specific entries in this selection. If you ned to add more than 13 people, you should add a group that contains the names of the people that you wish to add. This group can include a personal distribution list that is stored in your own contacts or a Domino group that is selected from the Domino address book.

Restriction: If you have not been granted access to another user’s mail file and you try to add it, you will receive a dialog stating that you do not have access rights to the mail file and that the operation is not authorized.

Level of Access

How much of mail file to delegate


Figure 2-18 Access to Others’ Mail

Shared contactsWithin DAMO 6.5.4, delegation of the mail and calendar file also allows for sharing of contacts. After you have been delegated access to another user's mail and calendar, you will also be able to access their contacts. Alternatively, it is not possible for someone to specifically share your contacts unless they have first been granted access to your mail and calendar.


Process of adding other user’s mail file to desktopFollow these steps to add a user’s mail and calendar to your desktop.

1. In the dialog shown in Figure 2-18 on page 43, click Add Person, select a name from the list, and click OK to save.

2. At the bottom of this dialog is an Advanced drop-down selection button. (Figure 2-19). By selecting this, you can select the properties to obtain more information about them, specifically which mail client they use (Figure 2-20). This can assist in compatibility issues.

Figure 2-19 Select Name

Figure 2-20 Name Properties dialog


Using people finder to locate usersYou also have the assistance of a people finder if you are having difficulty in locating a particular user. This is also selectable from the Advanced button in the Select Name dialog.

Figure 2-21 Select Name dialog, Advanced Find


Clicking Advanced → Find brings up Find dialog (Figure 2-22), where you can search for a specific name.

Figure 2-22 People Find dialog

User SecurityReturning to the Domino Preferences tab in the Outlook options dialog, the next option available is User Security, as shown in Figure 2-23.

Figure 2-23 Domino Preferences — User Security


When you select User Security, the dialog that is shown in Figure 2-24 displays.

Figure 2-24 User Security dialog

This dialog presents you with certificate and login options.

Security certificatesA certificate is a non-transferable, non-forgeable, digital file that is issued by a third party that both communicating parties already trust. When you receive new internet certificates, you can only use them in a browser with which you requested them. However, you can export internet certificates from a browser and then import them into the user.id file so that they can be used with DAMO. In the same respect, you can also export internet certificates from your user.id file so you can use them with a browser.

When you select Import Certificate, you are presented with the dialog that is shown in Figure 2-25. The dialog prompts you to enter the password of the Notes ID file that requires the certificate, together with the path to the file which contains the certificate along with that file’s password (if applicable).

Figure 2-25 Import Certificate Dialog


The same principle applies to the exportation of Internet or x.509 certificates. By clicking Export Certificate, you are asked to complete the same information, as detailed in Figure 2-26.

Figure 2-26 Export Certificate

User login settingsThe final two options within the User Security dialog refer to the user login settings, as shown in Figure 2-27.

Figure 2-27 User Security

In this dialog box:

� The first option refers to single sign on based upon the operating system login. If this option is selected to be installed at the time DAMO was installed on the user PC, this option would be active (that is, you could select or deselect it). Otherwise, it is greyed out, as shown in Figure 2-27.

� The second option refers to the DAMO client preference for remembering the users Notes user.ID file password. If selected, this preference logs in the user automatically without the user having to first enter a password each time the DAMO Outlook client is opened.


Local Directory preferencesThe last of the options on the Domino Preferences tab is the Local Directory (Figure 2-28). This option presents the user with available Directories for downloading to the local machine.

Figure 2-28 Domino Preferences — Local Directory

When you select Local Directory, the dialog that is shown in Figure 2-29 on page 50 displays, presenting all available Directories that you have access to for downloading locally.


Figure 2-29 Local Directory

This feature allows you to take a local copy of the selected directory, thereby allowing you to address messages correctly while not connected to the server that contains the server copy of the directory. The dialog displays the size of the directory file to be copied locally (Figure 2-29). Accordingly, you can make the decision as to when you feel it is most convenient to copy the data.

Other DAMO Outlook updatesIn addition to the options previously highlighted within the Domino Preferences tab, there are other visual changes that DAMO makes to the Outlook client. These include the Domino for Outlook Help and About Domino for Outlook, both accessible from the main Outlook Help menu option, as shown in Figure 2-30 on page 51 and Figure 2-31 on page 51.

Note: In addition to selecting local directory settings, 2.5, “Using the Domino Directories for name lookups” on page 51 describes how to select from various server side directories to facilitate directory lookups. This is applicable for organizations using multiple directories.


Figure 2-30 Domino Access for Outlook Help Menu

Figure 2-31 Domino Access for Outlook Help

2.5 Using the Domino Directories for name lookupsFrom within Outlook client using DAMO, you can configure which Domino or Outlook directory should be used as the default directory for name lookups. In the case that your organization uses multiple Domino directories, it is also possible to set the sequence for searching directories.


Figure 2-32 illustrates an example of a list of names that are contained within a Domino directory that has been specified as the default directory for Address Book lookups.

Figure 2-32 Default directory when selecting recipient names

To configure or change the default directory, you need access the tools menu from within the Outlook Address Book. To do this, select Address Book from within the Tools menu. When the Address Book is open, select Tools → Options as shown in Figure 2-33 on page 53.

Default Domino Directory


Figure 2-33 Configuring the address book for default directory lookup

From within the Outlook Address Book, Tools window, it is possible to set both the primary directory where Outlook looks first for name lookups, as well as specifying the sequence for subsequent directories to use for lookups when sending mail (Figure 2-34 on page 54).

1. Brings up the Address Book for Outlook

2. Tools - Options - allows you to set default


Figure 2-34 Options for specifying sequence of name lookups

Directory assistanceDirectory assistance is fully supported for DAMO. This capability allows the Domino server to look up information in a directory other than a local primary Domino Directory (NAMES.NSF). You can configure directory assistance to use a particular directory for any of these services:

� Client authentication � Group lookups for database authorization � Notes mail addressing � LDAP service searches or referrals

Show addresses in this directory first

Set the sequence of directories forname lookups on sending


2.6 Domino versus Exchange functional comparisonAn IBM Lotus solution provides the best enterprise scale requirements in today’s on-demand business environment, including an environment that requires:

� 100% system availability� The highest levels of security and stability � Ease of administration� Platform independence

With Lotus Domino as the backend messaging infrastructure, you can take advantage of the choice of clients that are offered to your workforce, whether those clients are Notes, Domino Web Access (DWA), or DAMO.

By making the decision to move from an Exchange based messaging infrastructure to a Lotus Domino based solution, customers can have the best of both worlds. You can have:

� A world-class messaging infrastructure at the backend� Client choice at the front end

It is well known that users are often resistant to change, especially when there is an comfort level already established with a specific technology. In the case of changing users’ messaging client, a primary productivity tools, this change can be considered to be very disruptive potentially.

It is exactly for this reason that the DAMO solution is so beneficial to so many customers. Outlook users gain the benefit of the Domino server on the backend, while retaining the familiar Outlook Client as their primary messaging client interface.


Table 2-3 compares features of Domino and Exchange

Table 2-3 Feature comparison between Domino and Exchange

As this comparison table highlights, Domino offers comparatively more platform options, improved performance and scalability, and better security and system management capabilities.

2.7 Replication in DAMOThe concept of data replication is at the foundation of Lotus Notes and Domino. In fact, it is this ability to replicate data between the client and server and databases efficiently, securely, and with complete data integrity that remains as one of Notes and Domino’s core strengths. When you consider how data is replicated and ultimately translated seamlessly between a Domino Server and an Outlook client running DAMO, it is crucial to understand how and where replication processes are involved.

Feature Domino 6 or later Exchange 2003

Platforms Windows (2000, 2003), Intel Linux, AIX, OS400, Solaris, z/OS®, zLinux

Windows 2003 Only

Load balancing across all active clustered nodes

Yes No

Clustering 2- to 6-way(platform-independent even across nodes in same cluster)

2-, 4-, 8-way(requires at least one passive node and Windows 2003 Enterprise Edition)

Typical scalability 10 000 users 3 000 Users

Web access to e-mail Yes No, requires IIS

Partitioning Yes No

Directory Yes No, requires Active Directory

Attention: While the following sections discuss what replication is and how it occurs within the context of DAMO, also refer to Chapter 3, “Understanding the DAMO architecture” on page 89 and, in particular, 3.1.6, “The DAMO replication layer” on page 96.


2.7.1 Replication overviewReplication is the synchronization of data between the Outlook .PST file and the Domino server copy of the users mail file that is stored in a user .NSF file.

DAMO is the replication layer. It performs the following:

� Maps fields from the Outlook message to corresponding fields in a Domino note

� Creates a Notes document

� Writes all relevant or equivalent data to the note in the Domino mail file

These installed replication files, collectively known as the replicator, allow the Outlook user to replicate mail that is stored on a Domino server with no mail template modifications required at all. This process of replication also allows the user to use any combination of client they wish, including Notes and Domino Web Access.

Because the replication technology has been the basis of Notes and Domino for many years, it is a well-proven technology that is known for its reliability and robustness. This ensures reliability of deployment and confidence in the user community. Within DAMO, the replication technology is exactly the same as that included as part of the Notes client, with the following additions:

� An Extension manager for Replication history

� On-the-fly truncation to assist in the preservation of the .NSF cache file size management

� Sequence numbers that are used to check for changes in the client

As far as the Domino server is concerned it does not know that the data stored in its mail file originated in an Outlook client, because the original data is translated from Outlook format to Domino before being stored in the server mail file.

Important: When using DAMO, keep in mind that no direct modification has actually been made to the Outlook code and Outlook has no part in the replication of the data. Replication is all handled by the DAMO code.

Attention: DAMO in its simplest sense allows the Outlook local .PST to transact via its local .NSF Domino file. The Domino server transacts only with .NSF files. With the DAMO solution, Domino is not aware of the existence of the Outlook client, and Outlook has no awareness of the Domino server. Chapter 3, “Understanding the DAMO architecture” on page 89 provides greater technical insight into how this is possible.


2.7.2 Replicator thread and interfaceThe replication thread controls the basic replication of the Domino mail data between the Outlook client and the Domino server and this is done in a Pull or Push configuration.

� Pull: The Replicator Thread pulls messages from the Domino server and converts the message data to the MAPI representation so that it can be used by Outlook.

� Push: Messages created or modified by the Outlook client are pushed to the Domino server, converting the MAPI message to its equivalent Domino (Notes) representation.

This method of replication ensures that the Domino server is always reading and writing in its native format, and likewise, the Outlook client is also always reading and writing its native format. Accordingly, this ensures a far greater level of reliability and data integrity, while at the same time ensuring that the data is distributed (replicated) in the most appropriate way to:

� Maintain best use of the available network resources

� Minimize any potential for error with both the client and the server

The Replicator Interface handles all the information gathering and the management of the replication history. These tasks include:

� Replication management

� Folder management

� Replication start and stop

� Communication between the MAPI service provider and the replicator thread

2.7.3 Property mappingThis section discusses the DAMO Mapping Module, which performs the following functions:

� Handles document mapping and translation between Notes and MAPI.� Unmapped MAPI properties are placed in a Notes item that contains a list of

MAPI properties� Unmapped Notes properties are stored in a MAPI property that contains a list

of Notes items� This method enables each client to make use of what it needs

Note: MAPI is an acronym for Messaging Application Programming Interface, the standard Microsoft mail interface protocol.


Explained in further detail in Chapter 3, “Understanding the DAMO architecture” on page 89, the Mapping Module creates new documents or updates existing documents in the .PST file for incoming messages. It then converts new DAMO created mail messages to a Domino readable form in preparation for delivery to the Domino server, via the mail.box database.

2.7.4 How and when is replication invokedWhen a user starts the DAMO enabled Outlook client for the first time during that network session, typically at the start of the working day, there is an initial one-time replication “hit” that synchronizes the client with the data on the server. The order for operation for this replication task is as follows:

1. The DAMO Outlook client reads folder and unread information from the local cache file.

2. It then gets any new folder information from the server and updates the folder structure within the Outlook client as appropriate.

3. It moves new mail data from the server replica of the user’s mail file into the local cache file on the user’s local machine.

4. It updates any folder and unread document information from the local cache, displaying these new documents and folder changes in the DAMO Outlook client.

5. This process is repeated until the local client and the server replica of the user’s mail file are in complete synchronization.

6. This process is repeated (by default) every 10 minutes and only carries out replication if new mail arrives on the server or if a significant event has occurred locally, for example a new mail created, deleted, or modified.

7. Subsequently, the order of operation from the client side is as follows:

a. All pending mail is sentb. Any changed documents are sent to the serverc. Any updated or changed folder information is synchronizedd. All unread mail is synchronized

8. If a user clicks Send/Receive within the Outlook client taskbar, a poll is done to the server to see if a replication event is required and does so if needed.

Important: The Mapping Module lies at the core of the DAMO code and is the part that actually carries out the conversion of MAPI data into Notes or Domino data in the CACHE.NSF.


9. New to 6.5.4 is On Demand replication where new mail and calender entries are sent as soon as possible, rather than waiting for the next scheduled replication event to occur.

10.Finally, there is a catch-all whereby a replication event takes place every hour (by default) to verify that the server and local mail data are always in complete synchronization. This process does not take place if there are no changes to replicate, thereby not using system resource unnecessarily

2.8 Calendering and scheduling within DAMODAMO acts in a very similar way with calendering and scheduling data as it does with mail data in that it translates the Notes calendering and scheduling entries held on the Domino server copy of the user’s mail file into Outlook readable information.

As shown in Figure 2-35, DAMO has replicated the calender and scheduling data to its equivalent Outlook representation. The net result is that the same calender entries can be viewed.

Figure 2-35 DAMO calender with Lotus Notes calender overlay in comparison


Figure 2-36 shows that the creation of a new DAMO calender entry and is completed in exactly the same way as it would be in the Outlook or Exchange environment.

Figure 2-36 DAMO Outlook New Calender Entry — Appointment

2.8.1 Calendar and scheduling considerations for a mixed Notes and DAMO environment

There are some fundamental differences in the way that Outlook and Notes operate and the area of scheduling in a mixed Notes and DAMO environment. This section highlights some of these differences in operation. All functionality that you are likely to require is functional but might operate is a slightly different way than would be expected in a purely DAMO environment.

For scheduling, Notes allows for a greater variety of options, has customer repeat sets, and Notes cares about the instance. Outlook has predefined rules, no customer repeat sets, and Outlook cares about the rule.


Creating repeat setsOutlook stores repeating meeting information as a repeat rule with exception dates.

Notes, however, uses the rule to create dates for the meetings.

DAMO result:Anything that cannot be represented as a rule in Outlook is split up into multiple single occurrences, thereby ensuring that no repeating meeting data is lost but still working within the design parameters of the Outlook client.

Changing default meeting informationIn Outlook, changing default information for a meeting only changes occurrences that are not exceptions.

In Notes, there is no default repeat information. Therefore, changing information for a series of meetings updates all occurrences of that meeting series.

DAMO result:When a Notes user modifies all instances of a repeating meeting, DAMO users can only see changes when looking at individual meetings, not the entire series. This is due to the design parameters of Outlook.

Lotus Notes allows for a greater variety of user options, including customer repeat sets (Figure 2-37 on page 63). Lotus Notes treats each calender entry as a separate entity and cares about the instance.


Figure 2-37 Lotus Notes calender schedule options

Outlook, on the other hand, has predefined Rules and has, for example, no customer repeat events (Figure 2-38). Outlook cares about the Rule.

Figure 2-38 Outlook Calender Schedule Options


Changing date information in Outlook The user can only change the date for the entire series of the meeting repeat or for a single occurrence of the meeting. Changing the date for the entire series causes the previous instances to be discarded and a new set of information created.

In Notes however, you are able to change date information as follows:

� Modify this instance Only� Modify all instances� Modify this and all future instances� modify this and all previous instances.

DAMO result:Therefore, within the DAMO client, if the rule is not supported within Outlook, multi-date changes from Notes are sent to the user as separate reschedules. This gets around the Outlook limitation and ensures that the DAMO user does not miss any of the meeting notices.

Similarly, with distinguishing changes to meetings, Lotus Notes allows the meeting notice to be rescheduled, updated, and confirmed, with each of these modification being defined as follows:

� Rescheduling constitutes a change to date or time that a user must accept or decline

� Update constitutes a change to the information other than the date or time

� Confirmation constitutes a re-send of the current information

Outlook allows updates, and a user can accept or decline any update.

As a result of this difference, multi-date differences are sent to the DAMO user as separate reschedules.

Delegation of individual meetingsFinally, another point to take into consideration is with respect to the delegation of individual meetings. Lotus Notes allows attendee delegation. Delegated invitees become part of the calender workflow, including updates and reschedules. However, Outlook does not have the concept of attendee delegation. It does not allow any invitee to invite one or more additional invitees without the chair knowing, and if they accept, they only show up as optional invitees.


Repeat forever meetingsThe default DAMO limits for repeat forever meetings are:

� Daily: 365 instances� Weekly: 52 instances� Monthly: 12 instances� Yearly: 10 instances� The default if no repeat unit is specified: 10 instances

Calender and workflow and iCal formatFinally, take note of the following issue with SMTP addresses. Calender workflow sent to an Internet address is converted automatically to iCAL format. Any mail that is received by a Domino router that contains iCAL format is converted automatically to Notes Calender Workflow.

2.9 Clustering and failoverOne feature that makes the Notes client and Domino Server so appealing to many customers is the ability of the Domino infrastructure to cluster between servers at the Domino level, rather than at the operating system level. This means that servers running on completely different operating systems, one on Windows 2003 and one on Linux for example, can be configured very easily to cluster with each other. More importantly, this clustering can be done in a way that is totally seamless to the user. This enables the Domino messaging infrastructure to manage both scheduled and un-scheduled server outages without any downtime being experienced by the users.

When DAMO was being developed, it was considered imperative that the Outlook user should also benefit from exactly the same level of administrative and infrastructure assistance as any other Domino user. To support this requirement, the DAMO client is fully compatible with Domino clustering and failover. This provides DAMO users with the ability to failover seamlessly to another server in the cluster to ensure a higher level of productivity.

As part of the DAMO installation, a file named cluster.ncf is created, in the same way as it would be created when installing a full Notes client. This file is created at install and is populated with the names of all the servers in the cluster to which the user’s mail server belongs.


An example illustrating data contained within the cluster.ncf file is shown in Figure 2-39.

Figure 2-39 Example cluster.ncf file data

As shown in Figure 2-39, the data contained within the cluster.ncf file includes:

� The names of the servers within the cluster.� The date and time the file was created.� The replica ID of the mail file to be clustered.

This ensures that the data in the server copy of the user’s mail file is consistently updated to all other replica’s within the cluster. If one of the cluster members goes down, the failover task can redirect immediately the client to an up-to-date copy of their mail file. This is done without any notification or prompt to the user. The connection is established in the background and is seamless to the user.

This clustering functionality is not available within an Outlook and Exchange environment.

2.10 SecuritySecurity is an area that is of primary concern to most organizations wishing to implement any form of messaging infrastructure. Historically within the Outlook and Exchange environment, security has been an issue with a high number of virus and worm attacks, propagating via the Outlook and Exchange address book.

Security vulnerabilities due to viruses and worm attacks require significant administrative overhead to manage. This also directly reduces user productivity due to the time that is required to clean an infected user client machine.This can be on-going problem within the Exchange and Outlook world.

With DAMO however, both users and administrators benefit from Domino’s underlying security model. In particular, improvements to the Domino server side management of security benefits users of DAMO.


Some DAMO specific highlights include:

� Single sign on (SSO)� Multi-directory install� Notes decryption on receive� X509

2.10.1 Single sign onDAMO supports the ability to use your Windows operating system credentials to log in directly to Outlook, without the need for the user to have to enter multiple passwords. This does, however, require that the DAMO and Windows passwords match. This is something that the DAMO administrator needs to recognize at the time that the DAMO user’s account is created within the Domino environment.

SSO is implemented at the time of each individual DAMO installation and is a selectable option during the installation process, as shown in Figure 2-40. To implement this, simply click the drop-down arrow next to the red cross and select Install This Option.

Figure 2-40 Installation SSO option

Note: If you did not choose SSO at the time of the initial installation, you can enable SSO via DAMO by selecting the Modify installation option via the Add/Remove Program.


2.10.2 Multi-directory installWith the introduction of the 6.5.4 release of DAMO, users or administrators installing the code have the ability to specify separation of the program and data directories. This added functionality gives DAMO users benefits that include:

� Ability to store DAMO data in a separate directory� Ability to store DAMO data on a different file store

Multi-directory installation functionalityThis added functionality in turn allows customers using Windows operating system security to have multiple users configured to operate using the same machine. This can prove beneficial to customers operating in shared hardware environments such as call centres or warehouses.

This new multi-user installation functionality has been added enabling users to share the same Outlook and DAMO installation. Just as with SSO, the user or administrator can select this functionality at the time of installation (Figure 2-41).

Figure 2-41 Single and multiple install options

While the ability to share a single workstation could potentially raise concerns about security and protecting the local .PST file from unauthorized access, you implement the following solution to password protect the local .PST file.


In Outlook XP and Outlook 2003:

1. Select File → Data → File Management.

2. Select Mailbox and Settings.

3. Change the password to the required password.

In Outlook 2000:

1. Select View → Folder List.

2. Right-click the Mailbox and select Properties → Advanced → Change Password.

This is native Microsoft Outlook functionality and further assistance can be found in the online help.

2.10.3 X.509 and Notes decryptionNew with the release of DAMO 6.5.4 is the support for X.509 and the ability to send and receive messages encrypted with X.509 certificates from external recipient (for example, those outside of the Domino Domain to which the DAMO client operates).

In addition to now supporting X.509, the DAMO 6.5.4 client is also able to decrypt encrypted mail documents that are sent to the DAMO user from a Notes client user. There is no action to take on the part of the DAMO user. This decryption process takes place automatically and with complete transparency to the user.

The greatest benefit of this functionality over previous releases is that customers working in a mixed Notes and DAMO environment are able to allow their Notes users to send encrypted mail, safe in the knowledge that if any of the intended recipients happen to be utilizing DAMO as their mail client, they can fully read all the content of the mail just as any Notes client recipients can read the content. This was not the case with previous releases of the DAMO client and could possibly lead to user frustration when an encrypted mail is received but is unreadable.

This is now fully addressed and the DAMO development team is also looking to include DAMO encryption in a future release to fully encapsulate the Domino security model.


2.10.4 Certificate managementThe Domino server can be configured to issue X.509 certificates through the Certificate Authority (CA) process.

Domino would then store the Internet Certificates (X.509) in the Domino directory as Exchange stores these in the Global Address List (GAL.) After the certificate is in the Domino directory, DAMO will get the certificate from the directory for any given user. This is a feature implemented in the DAMO Address Book Provider and, as mentioned previously, is available for the first time with the 6.5.4. release of DAMO

Sending signed messages is very intuitive after the user has installed a certificate with Outlook. To install the certificate:

1. Export the certificate from the ID file using the Domino Preferences → Security → Export Internet certificate.

2. Import the certificate into Outlook using Tools → Options → Security → Import.

3. Register the certificate with Outlook using the Security Options in Outlook and choosing the required certificate. You can have multiple internet certificates, but only one can be the default when sending signed or encrypted messages.

When the certificate is registered with Outlook, the user can begin sending S/MIME signed messages. This is a feature that is provided by Outlook. It is important to understand that the cryptography is performed by Outlook using the OS cryptographic functions (CRYPTO API), the DAMO plug-in itself does not sign or encrypt messages.

The certificate is typically contained within the ID file because this is part of the user registration process. For example, the certificate could be issued when the user is registered and it is copied to the ID file. The ID file is transferred to the user's workstation via the DAMO setup process, but the certificate is not exported. Instead, this must be exported by the user using the Domino Preferences in Outlook.

Users might already have certificates installed and these will only work if the SMTP address in the certificate is exactly as the user's SMTP address in the Domino Directory. Customers need to appreciate the importance of the SMTP address when working with S/MIME messages, because this becomes part of the user identity. A user SMTP address that does not match the SMTP address in the Domino Directory will result in an error when attempting to send a signed or encrypted message. This should be taken into consideration when planning the migration from Exchange to Domino.


Sending encrypted messages is also supported in the 6.5.4 release of DAMO. After the public keys are published, users can begin encrypting messages. The methods to make the public key available are listed as follows:

1. Method 1 – using Outlook Contacts

Users publish their public keys by sending a signed message to any given user. The recipient adds the user to the Outlook Contacts and in doing this the user's public key is stored in the Contact item. Now the recipient can send an encrypted message to the sender (who is now in the Contact folder), because it has the public key of the item in the Contact folder. This method is the preferred method for users that did not acquire the X.509 certificate using the Domino CA process.

2. Method 2 – using the Domino Directory

Users do not need to publish their public keys if this Public key is already present in the Domino directory. The DAMO Address Book will acquire the certificate from the directory before sending the encrypted message. In the event that the certificate is not accessible (that is, not present), Outlook shows a warning message that provides the option to send a decrypted message to the user that does not contain a certificate.

Important: If the deployment of the Domino server requires any change in the user's SMTP address, the administrator must issue new X.509 certificates and users must install the new certificates. Users should (must) not delete the old certificates from their Workstations, because these are probably used in existing messages, either in local .PST files or in Archived Files.


2.11 Unsupported featuresTable 2-4 contains a list of features and system limitations that are currently not supported with the 6.5.4 release of the DAMO client.

Table 2-4 Unsupported features and limitations

2.11.1 Overview of functional differences between DAMO, Outlook, and Notes

Table 2-5 provides an extensive comparison in functionality between DAMO 6.5.4, Outlook, and Notes. This table provides a better understanding of how functionality (or the approach to accomplishing a specific task) can differ between the messaging clients.

Table 2-5 Overview of differences between DAMO, Outlook, and Notes

DAMO 6.5.4

Retract messagea

a. Because of the fundamental architectural differences between Domino and Exchange, some functionality differs between these to platforms when the Outlook user moves to DAMO.

Archiving (local only). Note that this feature is planned tentatively for the next release of DAMO.

Policy-based management Shared contacts

Public foldersa Update to embedded messages

Server mail rules. Note that Client Mail Rules, including Auto Reply and Auto-Forward are planned tentatively in the next release of DAMO.

Auto-Reply and Auto-Forward

Feature DAMO 6.5.4 Outlook

Cached mode mail storage Offline mail access available with 2000, XP, and n2003

Only available with 2003

Mail storage Requires local .PST file Allows either local .PST or Server access

Archiving * No local archiving Local and server archiving

Mail rules* Available with Run Now option only

Automatically process mail


Within Table 2-6, we want to bring attention to specific functions or capabilities which vary slightly between the Lotus Notes client and the DAMO client.

Table 2-6 Specific feature comparison between Lotus Notes and the DAMO 6.5.4 client

Quota’s Can prevent receiving messages, not sending

Can prevent send and receive

2 GB file size Yes Yes for 2000 and XP, 20 GB for 2003

Search advanced address properties

Search on e-mail, first and last names

Search on all individual properties

New mail notification Available in 6.5.4 Available in all versions

Recover deleted messages Not available, Exchange Server Function

Available

Shared contacts Available in Managed Mail and Calender. Requires contacts stored in mail file.

Available

Message retraction Not available, Exchange Server Function

Available

Feature DAMO 6.5.4 Outlook

Note: Entries that have been marked with an asterisk (*) are planned to be implemented within future releases of DAMO. This is directional in nature and does not imply any formal commitment on the part of IBM.

Feature Lotus Notes DAMO

Buttons Create and Send Notes containing buttons

Does not render buttons, DAMO user cannot act upon them

Customized Forms Create and send customized forms

Does not render customized forms

Policy based management * Configure and push out standard sets of option to users

Cannot roll out custom defaults to users

User rename * User or administrator can initiate and Update user.ID automatically

Manual process to update user.ID

Embedded Messages Cannot read .MSG files Full support of .MSG files


2.11.2 Detailed functionality comparisonThe tables in this section provide a detailed functionality comparison, that allows you to look in depth at each individual Outlook function both against Exchange and with DAMO against Domino.

Table 2-7 compares the messaging feature.

Table 2-7 Messaging feature comparison

Note: Entries which have been marked with an asterisk (*) are planned to be implemented within future releases of DAMO. This is directional in nature and does not imply any formal commitment on the part of IBM.

Messaging features Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Read messages

Auto preview Yes Yes

Folder hierarchy in Navigation Pane

Yes Yes

Favorites folders in Navigation Pane

Yes Yes

Navigate hyperlinks in messages Yes Yes

Attachments can be opened from Reading and Preview Panes

Yes Yes

Can accept or decline appointments in Preview and Reading Panes

Yes Yes

Unlimited number of messages displayed in Mail view

Yes Yes

Send Messages

AutoAddress and AutoName Yes Yes

Insert hyperlinks in message text Yes Yes

Information bar available in preview and reading panes

Yes Yes

Send and receive attachments Yes Yes


Embed documents in messages Yes Yes, as attachments

Request read or delivery receipt Yes Yes

Word as e-mail editor Yes Yes

Spelling checker Yes Yes

Background and AutoCorrect spelling

Yes Yes - Word as editor

Add words to dictionaries Yes Yes

Recall message Yes, Microsoft Exchange Feature

No

Auto-select message encoding Yes Yes

Send mail message with voting buttons

Yes Yes, Outlook to Outlook

Track delivery and read receipts with original message

Yes Yes

Create messages from Address Book

Yes Yes

Receive HTML mail Yes Yes

HTML editing Yes Yes

Plain-text editing Yes Yes

Rich Text Format (RTF) editing Yes Yes

Automatic formatting of messages with color based on criteria

Yes No

Automatic text corrections Yes Yes - Word as Editor

AutoSignature Yes Yes

Insert signature on demand Yes Yes

Multiple signatures Yes Yes

Include vCard in signature Yes No

Set message importance Yes Yes



Message sensitivity Yes Yes

Message expiration Yes Yes

Deferred delivery (with or without rules)

Yes Yes

Message templates Yes Yes, PST

Default font for new messages Yes Yes

Default font for replies and forwards

Yes Yes

Redirected replies Yes Yes

File routing Yes No

Internet faxing Yes With third-party solution

Receive and reply to messages

New mail notification Yes Planned for an upcoming release

Respond to mail message (voting buttons)

Yes No

Reply in same format received Yes Yes

No indentation of Reply and Forward bodies

Yes Yes

Search for messages

Find Yes Yes

Search capabilities (Advanced Find)

Yes Yes

Search folders Yes Yes

Organize messages Yes Yes

Quick Flags and message flags Yes Yes

Categories and Master Category List

Yes Yes

Drag and drop messages Yes Yes

Multiple views Yes Yes



Arrange by Yes Yes

Grouping items Yes Yes

View by category Yes Yes

View mail by flagging for follow up

Yes Yes

Public folders Yes, accessed Through Exchange Server

No

Sort message list by standard fields

Yes Yes

Set order and size of columns in message list

Yes Yes

Enhanced conversation management

Yes Yes

Manage messages by group Yes Yes

For Follow-Up folder Yes Yes

Display custom views Yes Yes

Create custom views Yes Yes

Mark message as read or unread Yes Yes

Recover deleted messages Yes No

User saves e-mail messages to Drafts folder

Yes Yes

Mailbox cleanup Yes Yes

Ability to disable individual rules Yes Yes

AutoArchive Yes Yes (Messages are removed from the PST but are retained in the server store)

E-mail account Setup Wizard Yes Yes

Test E-Mail Account tool Yes N/A

Drafts folder Yes Yes



Table 2-8 compares the collaboration feature.

Table 2-8 Collaboration feature comparison

Table 2-9 compares the calendar feature.

Table 2-9 Calendar feature comparison

User-configurable Delegate Access permissions

Yes Yes

User configures public folder permissions

Yes - applies to Exchange N/A


Collaboration features Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Document workspaces Yes N/A

Meeting workspaces Yes N/A

Microsoft Windows SharePoint® Services and SharePoint Team Services integration

Yes N/A

Instant messaging Yes With third party solution from Instant Technologies

Calendar features Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Calendar views of different time periods

Yes Yes

Calendar preferences Yes Yes

Side-by-side viewing of multiple calendars

Yes Yes

Meeting reminders (minutes, hours, or days in advance)

Yes Yes

Color individual or recurring appointments

Yes Yes

Notification of adjacent or conflicting appointments

Yes Yes

Lunar calendar support Yes Yes


Table 2-10 compares the Address Book features.

Table 2-10 Address Book feature comparison

Table 2-11 compares the meeting management feature.

Table 2-11 Meeting management feature comparison

Offline use of calendar Yes Yes

Address Book and GAL features

Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Address Book Yes Yes

Browsable GAL Yes Yes

Access to general GAL properties (name, address, phone)

Yes Yes

Access to advanced GAL properties (organization chart, distribution list memberships)

Yes No

Synchronized offline GAL Yes No

Meeting management features Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Plan a face-to-face meeting Yes Yes

View other user's free and busy information

Yes Yes

Propose New Time Yes Yes

Appointments summarized in Outlook Today

Yes Yes

Invoke calendar from meeting request to see full schedule

Yes Yes

Include attachments in appointments and meeting requests

Yes Yes

Insert e-mail messages as attachments in appointments and meeting requests

Yes Yes, Outlook to Outlook


Table 2-12 compares contact management features.

Table 2-12 Contact management feature comparison

Create a Meeting Workspace in a meeting request

Yes N/A

Track acceptance of attendees to a meeting

Yes Yes

Attendee list visible to all attendees

Yes Yes, chair option

Send or receive requests over the Internet as calendar attachments

Yes No

Publish and retrieve free and busy information to the Internet with iCalendar subset

Yes No

Advanced, automatic meeting request processing options

Yes No

Plan online meeting (Microsoft NetMeeting®)

Yes No

Exchange conferencing Yes No

Use Address Book to pick attendees

Yes Yes

Free and busy view Yes Yes

Forward or reply to a meeting request

Yes Yes

All-day events Yes Yes


Contact management features Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Business Contact Manager Yes With Microsoft third-party application, not currently tested or supported

Contact picture Yes Yes


Table 2-13 compares the task management feature.

Table 2-13 Task management feature comparison

Use e-mail properties to add Contacts data

Yes Yes

Use contact information in mail merge

Yes Yes

Contact activity tracking Yes Yes

View by company Yes Yes

Print address cards Yes Yes

Important dates (birthdays and anniversaries) in Contacts listings

Yes Yes

Exchange virtual business cards (vCards)

Yes Yes

Shared contacts Yes No

View contacts by follow-up flag Yes Yes

Internet addresses listed in Contacts

Yes Yes

Multiple addresses in Contacts items

Yes Yes

Add and edit contacts Yes Yes

Send new message to contact Yes Yes

More than one physical and e-mail address listed in Contacts

Yes Yes


Task management features Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Create and manage tasks Yes Yes

Create task from e-mail message Yes Yes

Simple and detailed task views Yes Yes

View tasks by category Yes Yes


Table 2-14 compares client services.

Table 2-14 Client services comparison

View by active, completed, and overdue status

Yes Yes

Edit tasks in view Yes Yes

Task reminders Yes Yes

Task requests and tracking Yes Yes

Tasks time line view Yes Yes

TaskPad view in Calendar Yes Yes


Client services Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Alerts

New Mail Tune Yes Planned for an upcoming release

Outlook Custom Installation Wizard

Yes Yes

Out of Office Assistant Yes Yes

Recover Application Yes N/A

Read-only Delegate Access to messages and other information

Yes Yes

Editable Delegate Access of messages to other accounts

Yes Yes

Import and export files Yes Yes

Client-side Setup Wizard Yes Yes


Outlook Hotmail® support Yes No

Custom forms Yes No

Consolidated offline settings Yes Yes

Support for IMAP4, POP3, and SMTP

Yes Yes


Table 2-15 compares security and content management features.

Table 2-15 Security and content management features

Domino provides capabilities to help prevent the delivery of unsolicited e-mail (spam) at the server level, potentially reducing the need for client-side configuration and user involvement. Pertinent features include server-based mail rules, anti-relay controls, and DNS blacklist filtering.

Security and content management features


Information rights management Yes No

Junk e-mail filter lists Yes No*

Junk e-mail folder Yes No

Trusted Senders and Trusted Recipients lists

Yes No

Block external content Yes No

Block attachments Yes No

Antivirus enhancements Yes No

Digital signature Yes No

Digital encryption Yes No

SSO Yes Yes

Certificate management Yes Yes, External (x509)

Kerberos authentication Yes Yes

Automatic logging off after inactive period

Yes N/A

Journal Yes Yes, local only

Notes Yes Yes, local only


Table 2-16 compares the performance optimizing features.

Table 2-16 Performance optimizing features

Performance optimizing features


Integration with Microsoft SharePoint Portal Server

Yes No

Microsoft Office Live Communications Server 2003 integration

Yes No

Cached Exchange mode Yes Accomplished through local replica capability

Intelligent connectivity Yes N/A

Remote procedure call connectivity to Exchange (RPC over HTTP)

Yes N/A

Synchronization groups Yes No

Background synchronization of local and server folders

Yes Yes

Differential, offline Address Book synchronization with server

Yes No

Incremental change synchronization

Yes Yes

Smart change synchronization Yes N/A

Presynchronization reporting Yes No

Offline synchronization Yes N/A

Buffer packing Yes N/A

MAPI compression Yes Accomplished through Notes Remote Procedure Call (NRPC) compression

Skip bad items Yes Yes

Outlook performance monitoring Yes N/A

Unicode .PST support Yes N/A

Cancel request to server Yes N/A


2.12 DAMO futuresThe following a list of areas where the DAMO development team are looking to add improved specification, performance, and functionality within future releases.

� Server mail rules� Auto reply and forward� Better integration with policy based management� Serviceability

Send and Receive groups Yes Yes

LDAP support and default list Yes No



Note: The features and functionality suggested above are only goals at the time of this writing. As with any planned functionality, actual features included in future releases might change.



Part 2 Architecture and deployment considerations

Part 2



Chapter 3. Understanding the DAMO architecture

This chapter discusses how the DAMO layer links Outlook to Domino.

The DAMO architecture and design is the foundation for providing the familiarity of the current Outlook client together with the stability and scalability of Domino in the background.

What does DAMO do? Effectively DAMO is the code that allows the Outlook client to interact with a Domino server. The Outlook user accesses a normal Outlook client, and DAMO completes the transactions between the Outlook client and the Domino server in the background. Whether sending or receiving mail, sending or receive calendar invites, or reschedules, DAMO is the task in the background that makes use of the Domino server.

Outlook in the Exchange environment transacts with a central message store and its native .PST file. Whereas Domino contains individual mail files and uses server-based and local replicas of the user’s mail files (.NSF).

DAMO in its simplest sense allows the Outlook local .PST to transact via its local .NSF Domino file. The Domino server transacts only with .NSF files. With the DAMO solution, Domino is not aware of the existence of the Outlook client, Outlook has no awareness of the Domino server.

3


3.1 DAMO architecture in detailThis section describes the design criteria of DAMO and its architecture

3.1.1 Key design criteria for DAMO architectureThe key considerations for DAMO are:

� Synchronization of the user’s mail file on the Lotus Domino server with the Outlook storage file (.PST).

� Using Domino replication between the Outlook client and Domino, which allows data between Domino and Outlook to be interchanged.

� Reduced network bandwidth as Domino data is replicated to a local .PST file, resulting is faster performance for the Outlook user.

� Lotus Notes users already have the ability to change the preferences of their mail file. With this in mind, DAMO adds a new Domino Preferences page to Outlook’s option window allowing the Outlook user to access many Domino features and settings. Some of the features accessible from Outlook include:

– The ability to change the Notes ID Password– Use the Domino Out Of Office feature– Manage mail file replication settings– Manipulate available days and times in calendar

� Standardization of the installation package and client upgrade. The DAMO installation program is written using the standard Windows MSI installer and as such can be distributed in many ways using various software distribution tools. Being an MSI package, the installation can be scripted easily to meet each organization’s specific needs.

� Following on, consider how the DAMO installation code will be distributed to your users. Bearing in mind the size of the install MSI file, most remote distribution systems are able to deliver and install the code relatively quickly. All that might be required is some instructional guidance in the form of an e-mail or Web site posting for users to configure their DAMO client (see Chapter 6, “DAMO installation” on page 169).

� Domino clustering and load balancing allows for seamless failover to secondary Domino servers, ensuring the Outlook user has replication and access to mail and calendar data.

Note: The DAMO MSI package itself is approximately 30 MB in size and, when installed, takes approximately 70 MB of disk space (not including the user’s .PST file and before the initial replication).


� The ratio of DAMO users to Notes users for scalability calculations is 1 to 1.2. This means if you have 1200 Notes users, the equivalent is1000 DAMO users on the Domino server.

� Because most Lotus customers deploy Domino with a single mail file per user approach, scaling up to thousands of users has little impact on serviceability. A problem with one mail file effects only that one user on a server. This architecture is what has allowed IBM to consolidate its own environment to 11,000 mail files per Domino server.

� The NSF architecture is what makes Domino reliable. Because of the one database per user architecture, Domino supports individual mail file backup and recovery. Further, these mail files can be clustered across multiple Domino servers. The Exchange store is also a single point of failure when it comes to clustering. Exchange's clustering capability only provides what a Windows server offers, namely a shared-disk cluster model. That makes the data store a single point of impact in a cluster; if the disk storage is lost, all cluster nodes necessarily fail.

� The recommended Domino and Notes mail template fro registering new users as part of the migration from Exchange to Domino process for DAMO V6.5.4 is the Extended Mail template (mail6ex.ntf)

� The access level of the Domino mail file by way of the Access Control List (ACL) can range from Editor to Manager to allow most mail and calendaring functions. With Domino manager, access is usual, allowing the user to fully control the mail file. For example, where access to the mail needs to be authorized or delegated and for the manipulation of the user’s calendar with authorized assistants.

Note: Domino also supports the same concept of a shared mail, with one store and multiple users, just as Exchange uses. However, this approach can create a single point of failure, and as such, Lotus customers rarely use this configuration.

Chapter 3. Understanding the DAMO architecture 91

3.1.2 Overview of DAMO architectureWithin a three layer architecture, DAMO is the layer that sits between the Outlook client layer and the background (or silent) Domino layer on the Outlook user’s client. Thus, when viewed from the perspective of an Outlook client, DAMO provides the link between Outlook and the Domino Server.

Figure 3-1 on page 93 demonstrates a simplified view of the DAMO architecture, with the goal to highlight the following key concepts:

� The Outlook Client communicates directly with its .PST file.

� The Domino backend communicates directly with the user’s corresponding mail file or cache (.NSF).

� DAMO serves as the layer in between, mapping the data between the .PST file and the .NSF mail store.

Key Point: Due to the architecture of DAMO, the Domino mail server communicates natively via NRPC with the .NSF mail file, while the Outlook client also communicates natively with its .PST file.

The Outlook client is unaware that it is actually working with a Domino mail server on the backend. Alternatively, the Domino server communicates natively with the .NSF mail file, unaware that is actually working with an Outlook mail client.


Figure 3-1 Basic Overview of the DAMO architecture

3.1.3 The DAMO architecture in detailThe Outlook client is layer one. Layer one does not have any of its native code altered and continues to perform its normal operations by interacting with various service providers such as access its message store (the .PST file) and its address book.

The Domino server is layer three. This now hosts the user’s mail file. The Domino mail file contains the user’s mail and calendar data. In many cases, this data was migrated previously from the Microsoft Exchange server using Domino’s built-in Domino migration tool, formerly known as Domino Upgrade Service (DUS).


In between layer one and three is DAMO, acting as the binding or translation layer between the Outlook client and the Domino layer.

The DAMO layer consists of:

� Programming extensions to allow Outlook and Domino to interact.

� A replication layer to enable the synchronization of data between the user’s Domino server mail file and the user’s corresponding Outlook client.

� A mapping module used to determine how specific Domino elements map to corresponding Outlook element.

In addition, the DAMO layer provides add-ins to exploit fully Domino’s calendar and scheduling features. Plus, an add-in to modify Domino-specific features from the Outlook client is provided.

Note: Chapter 5, “The Domino Migration Tool” on page 143 discusses migration from Microsoft Exchange to Domino.

For additional information about Domino Upgrade Services, refer to Migrating from Microsoft Exchange 5.5 to Lotus Domino 6, SG24-6955.


3.1.4 The DAMO layer elementsFigure 3-2 illustrates a more detailed architecture for DAMO. In the diagram, the middle DAMO layer consists of the following elements: the Extension Manager, the Replication Layer and the Mapping module.

Figure 3-2 Detailed overview of Damo architecture.

3.1.5 The DAMO Extension ManagerThe Extension Manager allows an executable program library (DLL) to register a callback routine called when Domino performs selected internal operations. It is used to tie in to the Domino replication engine. The Extension Manager interface details notification events and data types and is exposed in the Domino software development kit. Exposing the interface allows the extension manager to be modified easily. As future Domino versions are released and features added, enhancements can easily be made to DAMO.


3.1.6 The DAMO replication layerThe replication layer represents the key DAMO layer that binds all the Domino and Outlook components together. It is the replication layer that provides the replication management options in the Outlook client, such as the interval for scheduled replication, as shown in Figure 3-3.

Figure 3-3 Replication options

The polling interval in the replication layer is optimized to use the mail database sequence number. These means there are less transactions and no open database sessions, limiting the load on network and the backend domino server. For Outlook users, there is an improvement in performance with this optimization.

The replication layer also controls, among other items, folder management (creates, deletes, and renames of folders) and also Outlook events, such as, send mail, send invitation, and so forth.

The management of the local cache information is also handled by the replication layer for such features as read or unread marks. Caching locally leads to a performance gain for the Outlook client user.

The replication layer processesThis section explains the following key replication processes:

� First time replication, (initial setup replication) � Replication process when mail is received by the Domino Server� Replication process when a DAMO user sends mail


First time replicationWhen the user starts Outlook 2003 with DAMO for the first time, a series of events occurs:

1. The DAMO client authenticates with the Domino server because the DAMO client is essentially a Domino client running silently in the background.

2. Similar to a Domino user starting a Notes client for the first time, DAMO creates a number of .NSF files which sit in the DominoForOutlook directory. These files consist of a local address book (names.nsf), a log file (log.nsf), a local mail box (mail.box), and a replica of the user’s mail file. Along with these files, the Outlook storage file .PST is also created.

3. The data from the Domino server replica mail file is then pulled from the Domino server using the Domino replication engine nwrdaemn.exe, which is installed during the DAMO setup.

4. All folder information that is contained in the Domino Server replica is pulled to the local mail file (hereafter, referred to as the cache). This folder information is then copied over to the .PST.

5. Data pulled into the local cache is also copied into the .PST.

6. Calendar data is processed.


Figure 3-4 illustrates the process of events during first time replication.

Figure 3-4 Initial set-up replication process

After this first replication is complete, users can work with Outlook as usual.


When mail is received by the Domino serverThe next stage to mention is what happens when mail is received by a DAMO user. Again the replication layer is the key, and an inbound mail follows a set process.

If a user is sent mail, it is delivered to the Domino mail server through the usual route mail routes in a Domino environment, where the mail item is eventually delivered to the user’s mail file on the Domino server itself. Under a Domino-only user base, the user can access the mail file directly on the mail server and retrieve mail, or the user can choose to replicate to the mail file on the server to a local replica on the client.

In a DAMO environment where there might not be a Domino client, replication is used to retrieve mail. Through the DAMO installation, the user’s Outlook Client has an extension called inotesoutlookaddin installed. This extension creates an extra tab in the Outlook options menu that allows the user to control how often replication occurs with the Domino mail server respectively.

The process when mail is received by the Domino server is as follows:

1. DAMO polls the Domino server mail file replica (for example, user.nsf) for new mail data (and not any Domino design elements other than folder information).

2. The DAMO replicator (nwrdaemn.exe) finds new mail and changed documents on the Domino server replica of the mail file. The replicator pulls the new mail and changed documents to the local cache (the user.nsf file in the DAMO user’s DominoForOutlook directory).

3. The mapping module (described in 3.1.7, “The DAMO mapping module” on page 103) creates new or updates existing Outlook messages in the Outlook .PST file.


Figure 3-5 illustrates the process that inbound mail follows in a DAMO environment.

Figure 3-5 Inbound mail process


When a DAMO user sends mailThe follow describes the process when a DAMO user sends mail:

1. Using the Outlook client, the user creates a message and then sends the message using the Send button.

2. The mail item is then deposited in the Outlook client’s Outbox within the .PST file.

3. The Outlook Outbox notifies DAMO that there is a pending outbound message, and the DAMO code processes the new message and maps a MAPI message to a Note in the local mail.box.

4. The replicator moves the mail message from the local mail.box to the mail.box of the mail-enabled Domino server.

5. The mail item is delivered by Domino following the Domino environment’s mail routing topology.


Figure 3-6 illustrates the outbound mail flow.

Figure 3-6 Outbound mail process

We can see then that replication is the key element for DAMO. All the processing is done at the client level, and interaction with the Domino server is minimized, resulting in greater stability and less network bandwidth use.


3.1.7 The DAMO mapping moduleThis is a very important part of the DAMO architecture because it is the Mapping Module that handles the mapping and translation between the Outlook client’s mail storage (.PST) and the Domino mail file (.NSF). It is also the feature that translates to NRPC for Domino mail routing because it is the Domino server that routes mail.

Figure 3-7 shows that when a Notes document (mail or calendar item) is sent, it is mapped to and from the corresponding Outlook entry (mail or calendar). The mapping module itemizes the entry properties and document items for translation and interacts with the replication layer to map them appropriately when replication occurs. The mapping module ensures that outgoing Outlook client mail is mapped to the Domino mail.box for mail routing and includes attachment support.

Figure 3-7 The DAMO mapping module

Note: The practice of also saving unmapped properties within Outlook allows for the DAMO development team to add support easily. Because the items are not discarded, users can take advantage of fixes and can re-convert data as items are added (similar to service provider architecture).


Figure 3-8 illustrates how the mapping module maps and translates between Domino and Outlook during replication.

Figure 3-8 Replication with the DAMO mapping module

3.1.8 Outlook service providersThe operations of an Outlook client are dictated by service providers. These service providers are specified in a user profile and include the following:

� The message store, which stores and retrieves messages from the .PST file.� The address book provider for contact information.� A transport provider perform the sending and receipt of messages.

The DAMO layer actually hooks into these standard Outlook service providers, which means the Outlook client can function as normal. It is the components of that DAMO layer that interact with the Domino server.


Using Figure 3-9 as a guide, we can see that DAMO’s hook into the transport provider is to send and receive messages from the Outlook client through the replication layer (which handles the synchronization with the Domino server). At the same time, the DAMO hook in to the address book provider makes available a Domino hosted address book to the Outlook user.

Figure 3-9 Outlook service providers


Figure 3-10 illustrates how the Outlook transport provider and address book provider function.

Figure 3-10 Service providers in use

3.1.9 Add-ins integrated with OutlookThe DAMO architecture brings with it add-ins that are installed as part of the DAMO layer. DAMO has been designed to enhance existing Outlook capabilities.

Two prime add-ins that are installed as part of the DAMO layer include the free or busy time add-in and the Domino Preferences add-in. These add-ins are integrated seamlessly with the Outlook user interface as additional items in the Outlook client options menu.

Figure 3-11 on page 107 shows the Outlook options menu before and after the DAMO installation.


Figure 3-11 Outlook options before and after DAMO installation

The free or busy time add-in integrates also into the Outlook client (Figure 3-12 on page 108), and for its users, the look and feel are familiar and easy to use.

Domino Preferences tab added


Figure 3-12 Free or busy time add-in

These add-ins are designed using the Component Object Model (COM) add-in architecture and are housed in ActiveX® DLLs (in-process servers).

The integration of these add-ins with the Outlook client is achieved via the Outlook object model and the Windows Registry.


Chapter 4. Deployment approaches

This chapter presents four typical deployment approaches where Domino Access for Microsoft Outlook would likely be used to satisfy the requirements of existing or potentially new Outlook users who need to integrate messaging and calendering with Lotus Domino.

These four deployment scenarios are:

1. Migration

2. Proof of concept

3. Mixed environment (co-existence)

4. Mobile, PDA, or Smartphone

This chapter discusses the basic requirements for migrating users from Exchange to Domino, as well as provides suggestions for a Pilot rollout. For each deployment approach, it presents the benefits and considerations of which you should be aware, particularly when operating in a co-existence environment. Finally, this chapter also discusses the Automated Deployment Tool (ADT) for DAMO, a solution for a larger scale DAMO deployment, that is provided by Wolcott Systems Group, LLC (http://www.wolcottgroup.com).

4



4.1 MigrationThis section discusses the approach of migrating users from an Exchange server to Domino server. While the backend data is migrated to Domino, this action is relatively transparent to a user through the use of the DAMO client. The user is able to use the Outlook Mail Client, while leveraging the benefits of the Domino mail server.

4.1.1 Migration deployment So why use a DAMO client? The basic concept allows existing Outlook users to maintain their comfort and experience with Outlook, at the same time afford them the many advantages of the Domino server. The DAMO solution offers existing Exchange and Outlook users the ability to migrate existing Exchange data to a Notes Domino server, and then run either the DAMO client or the Notes Client over the new Domino database.

Because the permanent data storage resides in an .NSF file on a Domino server, DAMO allows the user to switch back and forth between the two clients, sending and receiving e-mail messages and meeting invitations from both environments, while accessing the same central mail file. The coding at the root of DAMO allows the flow of data back and forth through replication process between Outlook client and the Domino server.

So what happens when you want to migrate from Exchange to Domino?

DAMO is the layer that allows your Outlook client to remain generally the same in terms of look and feel. When you migrate your users to Domino, you reap the benefit of greater scalability, personalized mail stores (.NSF file for each user), full backup and restore capability, and many other Domino advantages. At the same time, you will not need to train your Outlook users with a new product, because ostensibly the Outlook client remains the same with a some enhancements.

Thus, it is advantageous to migrate user data to a Domino infrastructure prior to rolling out DAMO. The Domino server can provide a service that is not only stable but has the features that can provide its users with a secure mail environment that can be controlled at the server level. See 2.6, “Domino versus Exchange functional comparison” on page 55 for a list of key advantages afforded by Domino.

Customers who are moving from the Exchange to Domino server need to preserve their historic data for use in the DAMO client. Ideally, the user should see no appreciable difference in the client experience. It is essentially the same data in the Outlook client function that the user would expect in the DAMO client.


Thus, we need a tool that can migrate existing Exchange hosted mail and calendar data to Domino. The Domino Migration Tool becomes the key player at this point. The Domino Migration Tool allows the Domino administrator to migrate Exchange users and their associated mail data to the Domino server, enabling DAMO users to work with their mail, calendar, and task entries just as they would in Outlook. Additionally, the Domino Migration Tool simplifies the configuration of new DAMO users on the Domino server.

4.1.2 Benefits of migrationSo why migrate? The Domino server can provide a service that is not only stable, but has the features that can provide its users with a secure mail environment that can be controlled at the server level. See 2.11.2, “Detailed functionality comparison” on page 74 for a list of key advantages afforded by Domino.

4.1.3 Key steps that are involved in the migrationThe following are the key steps that are involved in the migration process:

1. The Domino Migration Tool is accessed via the Domino Administration Client.

2. Having obtained a copy of the Exchange directory of users, the administrator uses the Register - Migrate People GUI through the Domino Administrator client to select the Microsoft Exchange users to migrate from the Foreign Directory Source and to enter the profile of the administrator for the Exchange server from which you are migrating.

3. Select the users and groups to migrate from the Foreign Directory, and then select Migrate.

4. When selecting Done, the entire list of users and groups are added to the registration queue in the Register Person dialog.

5. Select Register All in the Register Person dialog, at which point all users are added to the Domino Address Book and their mail files are migrated.

After the users have migrated, the administrator ensures that all Exchange addresses have converted to the Domino canonical format, using the Mail Convert tool. This tool only converts the addresses of Exchange user names that exist in the Domino Address book. Thus, all migrated users must have an entry in the Domino server’s name and address book.

Note: You can modify the migration options (for example, you can elect not to have a password created). However, you might want to accept the default options.

Chapter 4. Deployment approaches 111

After the above steps are complete, the users are ready to install DAMO.

4.2 Proof of concept deploymentAssuming that you are rolling out the DAMO client to a large group of users or that you still wish to gain some key feedback from specific users about using the product, we recommend beginning with a smaller scale pilot or proof of concept deployment. The goal or a proof of concept deployment is to begin the rollout with a small group of selected users who can provide useful feedback and serve to further champion the larger scale deployment initiative.

You should plan one or more pilots to validate the functionality and deployment procedures that are planned by your organization. Lessons learned from such pilot activities can help make the general upgrade process smoother.

4.2.1 Benefits of proof of concept deploymentBeginning with a smaller scale proof of concept deployment, prior to a larger rollout, can help ensure the success of your DAMO deployment. This approach allows you to select your initial audience for the introduction of the technology, manage expectations more effectively, and gain valuable knowledge and feedback which can be incorporated into your full scale deployment.

Key benefits include:

� Ability to determine test audience.

When determining the initial team to participate in the proof of concept, you want to select participants who represent a broad range of users in your organization, from those who are early adopters of new technology to users who are especially resistant to change. Pilot participants can include:

– IT staff – Administrative assistants– Key executive(s) (choose judiciously)

– People who are more resistant to change– Some volunteers

Note: Chapter 5, “The Domino Migration Tool” on page 143 details the migration process using this tool.

Note: Choosing administrative assistants and the specific executives with whom they work is especially important, given that DAMO 6.5.4 now allows for Calendar Delegation.


� Solicit continued feedback and use this going forward.

In order to maximize the benefits of a pilot deployment, you want a proper feedback mechanism or channel in place. This allows you to document and improve upon your initial deployment plan and to implement a more effective rollout plan to the larger audience.

4.2.2 Key steps that are involved in the proof of concept deploymentWhen preparing to implement a pilot rollout of DAMO, we recommend that you follow these general steps:

1. Determine the group of pilot users.

2. Ensure that the following has been identified and communicated:

a. Pilot users responsibilities and expectations of their participation

b. Pilot users testing instructions

c. Pilot critical success factors

3. Provide proper training and manage user expectations. Because pilot users are operating in a mixed environment, most likely with both Exchange and Domino users, train users on DAMO. In particular, focus training on any of the subtle differences between what is supported with Outlook when using Exchange versus using Outlook with DAMO against a Domino Server. In particular, you might wish to have users review Chapter 2, “Features and functionality” on page 21.

4. Build or validate the infrastructure to be used for pilot team, including:

a. If users need to first be migrated from Exchange to Domino, follow the appropriate steps outlined in 4.1.1, “Migration deployment” on page 110, or for a more detailed approach to migrating users, refer to Chapter 5, “The Domino Migration Tool” on page 143.

b. Install DAMO on the client machines for pilot users.

5. Initiate DAMO pilot and monitor results on a regular basis,

6. After a determined amount of time in which users have been working with the system on a regular basis, solicit final pilot user feedback and document the results.

7. Incorporate feedback or recommendations into a deployment plan for larger audience.


4.3 Mixed environment: client coexistenceThis section describes the approach of a mixed environment that has client coexistence.

4.3.1 Definition of a mixed environmentOne of the key advantages of migrating from Exchange to Domino is the ability to run either the DAMO or Outlook client over the Domino mail file. A user can, in fact, run both clients against the same file simultaneously, replicating data back and forth between the DAMO and Outlook clients. As an example, a user might run the Outlook client on a notebook computer when away from the office and the Notes client on a workstation when in the office. In this scenario, the expectation is that the user’s mail file data would be migrated from Exchange to Domino, after which time the user would run one or both clients against the migrated Domino mail file.

4.3.2 Benefits of running in a mixed environmentIn a mixed environment, because the user’s permanent mail file data resides on the Domino server, the same data can be represented in either client simply by replicating the data to DAMO or opening the Notes client against the Domino mail file. This allows the user valuable flexibility in his work environment and choice of clients and the ability to use either the DAMO or Notes client according to business needs.

4.3.3 Key differences between running the Notes and DAMO clientsWhile the Notes and DAMO clients represent the same data, the representation of that data differs somewhat according to the innate differences between the two clients. Remember that the Notes client directly accesses the Domino server mail file, while the DAMO client uses a local .PST file replicated from the Domino server mail file. So, the structure of the data being directly accessed by either client is in some cases very different. The permanent data storage resides on the Domino server, but because of the requirements of Outlook, the data created in the local .PST file that is used by DAMO can have additional components or can be missing certain components when compared to the Domino mail file data.


Differences in representation between Notes client and Microsoft Outlook client

The following tables show some of the differences between representation of the same data in DAMO and the Notes client.

Table 4-1 Comparison of Calendar features — key differences between Notes and DAMO

Calendar and scheduling features

Lotus Notes client 6.5.4 DAMO client 6.5.4

Recurring meetings display Displays the parent meeting and all instances of the recurring meeting, including any rescheduled, cancelled, or deleted instances.

Due to the limitations of Outlook, the DAMO Active Appointments view does not accurately reflect the number of occurrences in a recurring meeting; however, the calendar accurately reflects the meetings.

Recurring meeting updates (not reschedules)

The Notes client allows updates to either a single instance, a range of dates, or the entire recurring meeting. Therefore, when a change is made to a series of dates, only one update is sent.

Because Outlook does not support updates to ranges of meeting instances, meeting updates to recurring meetings (not reschedules) are sent as individual items, if a change is made to the series a number of updates will be sent. It is recommended that changes are made to single instances to avoid multiple updates being sent.

Recurring monthly meeting, first Tuesday and Thursday of month

In Notes, you can create a monthly meeting that happens on the first Tuesday and third Thursday of each month.

However Outlook does not support this as a repeat. These meetings will be distributed to multiple dates when replicated to Outlook.

New line in Subject and Location fields

Notes supports the creation of a new line in the Subject and Location fields on Calendar items.

Because Outlook does not support the creation of a new line in the Subject and Location file, new lines entered in Notes in the Subject or Location field are converted to a semicolon (;) followed by a space in Outlook. DAMO users can enter a semicolon and space so that a new line is added in Notes.


New mail notification New mail notification is on start up, notifying the user of any unread messages in the Inbox.

New mail notification occurs only when a new message arrives. New mail notification can be customized in the 6.5.4 release to specify how notification occurs, and in a future release the new mail notification will follow standard Outlook functionality.

Distribution lists Yes Distribution lists created in Notes that contain other distribution lists (nested distribution lists) cannot be resolved within Outlook. Nested distribution lists created in Notes are resolved in the Domino server and can be used to send messages. Nested distribution lists created in the Outlook Contact folders are resolved within Outlook and can be used to deliver messages.

Access existing Notes mail archives

Yes No

Comments Yes Comments sent by a Notes or Domino Chair or Notes or Domino delegator are not supported when sent to Outlook Chair.

Calendar and scheduling features

Lotus Notes client 6.5.4 DAMO client 6.5.4


Table 4-2 Comparison of messaging features — key differences Notes and DAMO Client

Messaging features Lotus Notes client 6.5.4 DAMO client 6.5.4

Buttons and custom forms Objects created using Lotus script, such as buttons and custom forms, are fully supported.

Due to the constraints of the Outlook client, DAMO does not have the ability to display buttons and custom forms created in Notes.

Tabbed, captioned, and animated tables

Tabbed, captioned, and animated tables are fully supported by the Notes client.

Tabbed, captioned, and animated tables will be converted to normal tables in Outlook.

Rich Text Formatting Yes Most Notes rich text formatting is supported, with the exception of the following: drop-shadow borders on tables and pictures, some list styles (for example, circle, square and check mark), fit to Window style tables, cell image and gradient fill (shading), fit to Window style tables, mixture of fixed and variable cell widths in a table

Autoprocessing Yes On the Autoprocess tab, if the user enables automatic responses to meeting invitations from specified users, the user has the option of choosing a name from the address book. The user must remove the "@<domain>" portion of the address for this feature to work. Also, when using Autoprocess, the Chair does not receive an acceptance notice.

Twisties Fully supported The twistie will be expanded and displayed as a series of tables. See Figure 4-1 on page 118 for an example of this behavior.


Figure 4-1 illustrates how a twistie is rendered from Notes when opened through the DAMO client.

Figure 4-1 Illustrating how a twistie is rendered in the DAMO client

Figure 4-2 on page 119 illustrates how a Notes document link is rendered in DAMO.

Document links Document links appear in e-mail messages as an active link that opens the document when selected.

Document links appear as a Notes URL which will open the document as long as the Notes client is installed on the same workstation as the DAMO client. Note that Word must be set as the default editor in order to activate the URL. An example of a DAMO document link is provided in Figure 4-2 on page 119.

Messaging features Lotus Notes client 6.5.4 DAMO client 6.5.4


Figure 4-2 Illustrating how a document link from Notes is rendered in DAMO

4.4 Mobile, PDA, or SmartphoneThe use of mobile devices, whether Personal Digital Assistants (PDAs), Smartphones, or other forms of intelligent hand-held mobile computing devices, is becoming more and more prevalent within the business world. Thus, it is important to recognize that a DAMO roll-out within an enterprise organization should not prevent a customer from either continuing to use an existing mobile device of choice or eventually embarking on a subsequent roll-out of these devices after a DAMO roll-out has been initiated or completed.

Figure 4-3 Mobile Devices

Important: Document links appear as a Notes URL which opens the document as long as the Notes client is installed on the same workstation as the DAMO client. Note that Microsoft Word must be set as the default editor in order to activate the URL.

Doc links are rendered in DAMO as active URLS


The vast majority of the major PDA and Smartphone manufacturer’s already bundle synchronization software as part of their PDA or Smartphone package. These include synchronization software that enable the synchronization of Mail, Calender, and ToDo data between the individual PDA or Smartphone device and Outlook. This synchronization takes place at the local PC level and is controlled by the user, synchronizing data directly between the local machine and the device.

This section looks at the DAMO or local setup. Both IBM and other manufacturer’s supply server-based mobile device synchronization solutions, such as IBM Lotus Domino Everyplace® and Research In Motion’s (RIM)’s Blackberry Enterprise Server. However, these solutions are not covered here.

4.4.1 Definition of mobile, PDA, or Smartphone deployment using DAMO

Many organizations either formally or informally equip their staff with hand-held mobile computing devices, such as Blackberries, Palm, Symbian, or Windows CE. Most, if not all of these devices have the capability to synchronize mail and calender data with a PC, along with device backup and program installation. This activity is generally controlled by the supplied manufacturer’s software.

Because most of the popular mobile devises already have manufacturer supplied synchronization software that enables local synchronization of Outlook data, the implementation of DAMO has no effect. The user is able to locally synchronize just as in the past when Outlook was supplied data from an Exchange backend. As far as the mobile device synchronization software is concerned, it is carrying out a synchronization with the local .PST

4.5 Automated Deployment Toolkit for Domino Access for Microsoft Outlook

This section discusses the Automated Deployment Tool (ADT) for DAMO that is provided by Wolcott Systems Group, LLC. (http://www.wolcottgroup.com)

4.5.1 Overview of the ADT toolADT now supports the deployment and upgrading of the DAMO client and provides the ability to install silently and configure the DAMO client. When combined with ADT's user ID provisioning component, ADT can fully automate the Notes ID creation, Mailbox creation, DAMO client deployment, and MAPI



profile configuration processes. ADT's process automation ensures consistency with respect to all client installations as well as apply standards to ID files, user names, passwords, and mail server assignments.

System prerequisitesThe following are the minimum system requirements identified for the IBM Lotus Domino Access for Microsoft Outlook product.

Domino Server requirements

� Lotus Domino server 6.5.1 or higher, � Domino Administrator Client 6.5 or higher (6.5.1 or higher recommended)� Mail databases created using a Mail6.ntf, Mail6ex.ntf, or iNotes6.ntf template

Windows Client requirements

� Windows 2000, Professional Edition� Windows XP, Professional Edition with Service Pack 3� 136 MB RAM, required; 256 MB or more recommended� Disk Space: 275 MB disk space minimum for ADT install1

Microsoft Outlook requirements

� Microsoft Outlook 2000/2002 with SP3 or Outlook 2003 with SP1� Microsoft Windows 2000 and Windows XP (Professional Edition) � Corporate or Workgroup configuration (Outlook 2000 only)2

� Outlook must be configured as the default mail client


� Lotus Domino server 6.5.1 or higher, � Domino Administrator Client 6.5 or higher (6.5.1 or higher recommended)

Note: The information presented here supplements the ADT Installation and Configuration Guides which are provided with the product.

1 ADT queries for the minimum client requirements during the PC Survey process. Users who do not satisfy the minimum requirements are placed in the SurveyFailure status and administrators can be notified by e-mail. 2 For Outlook 2000 users, the Outlook client is required to be configured for Corporate or Workgroup and requires reconfiguration if Outlook is set for Internet Only support. To reconfigure Outlook to Corporate/Workgroup mode, perform the following steps:1.) Start Outlook.2.) Select the menu Options: Mail Services.3.) Select Reconfigure Mail Support.4.) Select Corporate mode.


4.5.2 Configuring ADT to deploy DAMOThe ADT framework supports three workflow process types: upgrade, deployment, and migration. During the initial deployment of DAMO throughout an enterprise, ADT must be configured for either the deployment or migration process types. Subsequent upgrades of existing DAMO installations can be performed by reconfiguring ADT for the Upgrade process type.

Figure 4-4 ADT deployment configuration

In addition, to automate the DAMO client setup and MAPI profile creation processes, you must enable ADT's user ID creation component. Performing the



ID creation process using ADT provides ADT direct access to deploy the ID files during the DAMO client installation process. ADT's provisioning algorithms also apply consistent naming standards and ensure the uniqueness of various naming attributes. ADT also escrows copies of the ID files that it creates in the ADT ID Archive.

Configuring the Installation TypeWithin a single instance of ADT, you can deploy the Notes client to some users and the DAMO client to others. For ADT to deploy the DAMO client, you must first configure an Installation Type document that specifies Domino Access for Microsoft Outlook as the Installed Client (Figure 4-5).

Within the Installation Type configuration, you can direct either a Silent or Loud mode installation:

� During a Loud mode installation, users interact with the installation wizard dialogs.

� During a Silent mode installation, no user interaction with installation wizard dialogs is required.

You can also specify the program directory to which DAMO files are to be installed.

Figure 4-5 Installation Type configuration


Configuring the User OptionA User Option document is created to assign users to a DAMO client installation. The Installation - Basics tab should reference the Installation Type document that summarizes the DAMO installation options and the Installation Source that specifies the location of the installation file set, either network source or CD.

Figure 4-6 User Option configuration

4.5.3 Automating the DAMO client setupThe Installation - Setup tab on the User Option document provides the option to automate the setup of the DAMO client for new users. In addition to automating the installation of the DAMO client, ADT also automates the configuration of the DAMO client. Included in the process are the deployment of the user's ID file to the DAMO data directory and the creation of the MAPI profile to connect the Outlook client to the assigned Domino mail server. The MAPI profile that is created is configured as the default MAPI profile the next time the Outlook client is accessed.


Figure 4-7 User Option configuration - Auto Client Setup

If you do not enable the ADT New User Auto Client Setup feature, then ADT does not invoke the automated creation of the Outlook profile. The user would then be required to launch the DAMO MAPI profile creation process manually, using Start Menu → Programs → IBM Lotus Domino Access for Microsoft Outlook - Create New MAPI Profile. During the process, users would be required to supply their Notes user name, Mail Server name, and ID file location. In addition, the user must have physical access to this ID file and know where the ID file is located. The user is also required to know the password that is associated with the Lotus Notes ID file. Administrators must consider the best approach to physically deploy user ID files.

ADT can send all of this information to users automatically when ADT generates the ID files. Figure 4-8 on page 126 shows an example of what ADT can send to users with this type of configuration.


Figure 4-8 Sample of e-mail notification

When you enable the Auto Client setup, ADT pushes the user's ID file and a setup file automatically to automate the MAPI configuration to the required directories. The setup file contains all of the user-specific data, such as the user's mail server and password. Example 4-1 shows the setup text file that is generated by ADT. ADT places this file in the user's Windows temp directory until the installation is complete. It then copies the file to the DAMO installation directory with the Lotus Notes ID file. The setup file contains sensitive data. Consequently, ADT removes this file from the user's system when the installation process completes. ADT generates, configures, and deploys the file automatically on the user's machine. This process supplies the DAMO profile installer program the required information to fully automate the workstation setup and configuration.

Example 4-1 ADT_Setup Example

-u John Doe -s adtdemo01.wolcottgroup.com -f c:\lotus\DAMO\jcrawford.id -p blue123

The setup file contains the parameter definitions that are defined in Table 4-3.

Table 4-3 Setup file parameters

Sample Mail Content:

As part of the DAMO Deployment, we have created a Lotus NotesUser ID. The information you need to use and configure DAMO during the setup process has been included below.

Lotus Notes Name: John Doe/WSGDemoHome Server: adtdemo01/WSGDemoPassword: blue123Internet Address: [email protected]

Parameter Description

-u Lotus Notes user name

-s Server name, which can be server name or domain, IP, or cn=servername/domain.

-i Location of Lotus Notes ID file, for example c:\lotus\damo\tuser.id

-p Password


4.5.4 DAMO client installationThis section describes the DAMO client installation.

Preparing the client installation directoryADT can deploy the DAMO client from a network file share or CD. Follow the instructions detailed in the ADT Configuration Guide to build the standard installation package in the network or CD directory. Then, to prepare the directory for DAMO, copy the DAMO setup.exe file into the root directory. Do not mix the DAMO installation files with Lotus Notes installation files. A separate installation directory is recommended for each client type.

Preparing the Outlook clientAmong the preparation steps performed by ADT is setting Microsoft Outlook as the default mail program. This is a requirement for the Domino Access for Microsoft Access program. No additional configuration is needed to enable this feature.

ADT DAMO installation processThis section details step-by-step the actions that are performed by ADT during the client installation process.

First, ADT extracts all necessary files (Figure 4-9). For example, if you configure ADT to perform the automated client setup, then ADT extracts the user ID file and setup file along with any other necessary installation files to the user's temp directory.

Figure 4-9 ADT file extraction


ADT also detects if Microsoft Outlook is active in memory and, if found, prompts the user to close the application to ensure a successful install of the DAMO client. Close Outlook cleanly terminates the program from memory (Figure 4-10).

Figure 4-10 Outlook detection

ADT also detects if Lotus Notes is active in memory and, if found, prompts the user to close the application. Close Lotus Notes cleanly terminates the program from memory (Figure 4-11). Other applications that interface with Notes DLL files are also terminated prior to the installation process. In addition, several identified applications that interface with most mail applications, such as Blackberry Desktop Manager, IntelliSync, ActiveSync®, HotSync, EasySync®, and so forth, are closed prior to the installation.

Figure 4-11 Notes detection


After ADT has determined that both Outlook and Notes are not running, click Install to proceeds with the DAMO installation (Figure 4-12).

Figure 4-12 Client Installation

As with any of the ADT upgrades, deployments, or migrations, you can configure ADT to run up to five pre-installation programs and up to five post-installation programs. The image below shows how ADT updates the user interface during the installation process. ADT provides information according to the overall progress of the installation process relative to any additional ADT programs that you have configured.

Figure 4-13 Client Installation launch

During the DAMO installation, the progress bar displays, as shown in Figure 4-14 on page 130. If you enable the New User Auto Client Setup, this process might take longer, because the installer also generates the new Outlook MAPI Profile.


Figure 4-14 Configuration progress

When the entire installation of the DAMO code, Run Before Programs, and Run After Programs has completed, ADT displays visual confirmation that the each step of the installation has completed, as shown in Figure 4-15.

Figure 4-15 Installation confirmation

After a successful installation of the DAMO client software, ADT presents an Information dialog that states that the installation has completed successfully (Figure 4-16). If you have enabled the Auto Client Setup feature, ADT has relocated the user’s ID file to the directory that was specified in the ADT Install Type document for the DAMO client and configured a new MAPI profile connecting Outlook to the Domino mail server.

Figure 4-16 Installation completed message

By default, the DAMO installer creates a profile in the format of "User Name's mail on Server Name." For example, the new DAMO profile displayed is "Jason


Crawford's mail on adtdemo01" and is the default profile that Outlook selects when launching Outlook. The DAMO installer currently does not allow the manipulation of this Profile name during the installation. If the Profile name format is an issue, contact Wolcott Systems Group to discuss profile name options.

Figure 4-17 Profile selection

After you select the newly created DAMO Outlook Profile, the Outlook profile prompts for the password. You must enter the password that corresponds with the Lotus Notes ID file.

Figure 4-18 Profile password prompt

The Outlook client recognizes the newly installed DAMO layer and starts the Initial setup. DAMO displays the dialog that is shown in Figure 4-19 until the initial setup of the DAMO client completes within the Outlook client. DAMO displays a progress bar indicating the progress of the initialization.

Figure 4-19 Initialization

The first time that the Outlook mail client opens with the new DAMO profile, a welcome message is readily available in the user's inbox, as shown in


Figure 4-20. This message states that the mailbox automatically starts a synchronization process and that the estimated time of completion is largely dependent on the size of the user's mail file.

Figure 4-20 Welcome message

Outlook users also have the new Domino Preferences available while in the Outlook mail client, as shown in Figure 4-21 on page 133. You can navigate to these preferences by selecting Tools → Options, and selecting the Domino Preferences tab.


Figure 4-21 Outlook Domino Preferences

4.5.5 Deployment considerations for ADTThis section highlights some important considerations when using ADT as the tool of choice for a large scale, automated DAMO client deployment. It also discusses some of the most common errors and troubleshooting issues and describes the key log files that are generated during the process.

Advantages of using ADT's Create User ID or New User Auto Client Setup processes

If ADT is not configured for the New User Auto Client Setup, then you must execute the DAMO Create New MAPI Profile program from the Start menu to successfully complete the use of DAMO. If you create this profile manually, then DAMO prompts you for the Notes User Name and the name of your Mail Server and Domain. DAMO also prompts the user to supply your ID (for example jdoe.id) and the password for that ID File.

Note: You can learn more about the options and functionality within the Domino Preferences tab in 2.4.1, “Domino Preferences tab” on page 31.


The disadvantage to this approach is that you have to determine how to best get the users all of this required information and the ID file. If you have a wide spread distribution of users across multiple domino servers, the profile generation process could easily become confusing and extremely time consuming to ensure everything you are communicating is accurate. In addition, you risk sending the incorrect ID to the wrong user. There is also a risk that your users will not key this required information into the DAMO setup program properly.

With the Auto Client Setup feature of ADT enabled, the user only has to know what the password for the new DAMO profile that ADT automates.

DAMO client initializingAfter the DAMO client installation process is complete, you can launch the Outlook client. Select the profile that refers to the user name just configured during setup. If the mail file contains a significant quantity of data, it can take a several minutes to make this data available within Outlook. It is important that you not interrupt this process.

Troubleshooting DAMO installation errors The DAMO installation can fail in several areas. It is important to identify where in the process the failure occurred. Additionally, to troubleshoot any issues properly, you need the log files that ADT generates. For example, the DAMO installer can fail if the user executing the installation does not have the proper rights to install software on the machine.

If you have not configured ADT to run the installation with elevated execution rights, you will have a problem. You should follow all of the standard troubleshooting tactics described in the ADT manual to resolve any issues pertaining to the actual installation of the DAMO client code.

It is important to understand that the DAMO installation can be successful, but fail during the profile generation component. If you configured ADT to use the New User Auto Client Setup and the setup file that is generated is incorrect, the installation will fail.

Here are the areas where the automated profile generation can fail with an improperly configured setup file.

� If the User Name specified is incorrect.� If the Domino server is not accessible during the installation.� If the Domino server specified is incorrect.� If the path specified for the users ID is incorrect.� The ID file did not copy to the client machine successfully.� If the user’s password is incorrect.


In addition to those areas, the installation can also fail if there is a problem with the user’s ID file. If the installer encounters any issues after ADT properly dispatches the ID file to the machine, but fails during the ID file copy process to the DAMO program directory, the automated setup fails. Using the UserIDGeneration component in ADT greatly reduces the percent of errors that users might encounter during the profile generation. ADT ensures the accuracy and consistency of the users specific data contained in the setup file and greatly reduces any potential profile issues. Outlook uses the new profile used with DAMO, so this is a vital piece of the overall success of the DAMO installation.

If the installation was successful but there were errors detected during the profile generation component, the DAMO installer displays the message that is shown in Figure 4-22. The DAMO installer does not display the actual cause of the error to user. If the setup fails for any reason, DAMO displays the dialog. The related error is specific to the profile generation component of DAMO. The DAMO client still installs and the error does not relate to the client installation. The message only relates to the failure of the MAPI profile creation process of the DAMO Installation.

Figure 4-22 Client setup failure

However, ADT traps, records, and reports any errors during the New User Auto Client Setup silent installation while using the setup file that is generated by ADT. The ADT installer reports these errors back into the ADT process to enable administrators to easily detect, log, and resolve any issues.

Figure 4-23 ADT setup failure message

If the DAMO overall installation is successful, then you can generate a profile for the user who encountered an issue manually. During the manual profile generation, the message that is shown in Figure 4-24 on page 136 displays


when the setup program encounters an error while attempting to establish a connection to the Domino server.

Figure 4-24 Server connection error

The message that is shown in Figure 4-25 displays when the setup program encounters an error while attempting to copy the user's notes ID file to the DAMO data directory.

Figure 4-25 ID file error

DAMO installation logs and setup file that are used during ADT installation

The following files are involved in the installation process:

user.id File for the DAMO user

adt_setup.txt File extracted to the temp directory by damoinst.exe that contains parameters to automate the MAPI profile creation (for example, -u Test T User -s labsrv01/wsg -f c:\lotus\notes\tuser.id -p password)

adt_damoinstall.log Log file that is generated by the DAMO setup.exe

adt_clientinstall.ini ADT configuration file for the DAMO installer (see Figure 4-26 on page 137)

adt_clientinstall.log Log file that is generated by the file extraction and installation launch process (see Figure 4-27 on page 138)

adt_damoinst.log Log file that is generated by the DAMO client installer (see Figure 4-28 on page 139)


Figure 4-26 Sample of the adt_clientinstall.ini file

[Install]UserName=Test T User10InstalledClient=2InstallationUNC=\\labsrv01\adt22instNetworkAuthenticationOption=1InstallationOption=0VerifyAdminRights=1MultipleMachines=0AutoClientSetup=1KeyFileName=tuser10.idTransformFile=InstallationMode=1InstallLocation=0ClientDataFolder=ClientProgramFolder=c:\lotus\note\RunBeforeErrors=0[RunBefore]NumProgs=1ProgName1=OutlookUpgradeProgParms1=InstallPath=Office2000sr1\setup.exe LogRoot=OutlookUpgradeLog MST=corpfinal.mst TARGETVERSION=9.0.0.6627ProgSource1=0[RunAfter]NumProgs=0[Mail]SMTPMailInAddress=ADTV22SMTPHostAddress=labsrv01SMTPFromAddress=joe.adminUserDocID=398635584809CFA885256EE000695DDD[Help]UserHelpString=Please contact the Lotus Notes help desk.


Figure 4-27 Sample of the adt_clientinstall.log file

8/3/2004 3:53:12 PM - Log opened8/3/2004 3:53:14 PM - Extracting files to C:\DOCUME~1\ADMINI~1.WSG\LOCALS~1\Temp\8/3/2004 3:53:14 PM - Checking drive C8/3/2004 3:53:14 PM - Checking drive D8/3/2004 3:53:14 PM - Found CD ROM Drive (D)8/3/2004 3:53:14 PM - User has local administrator privileges8/3/2004 3:53:14 PM - Installer: damoinst.exe8/3/2004 3:53:14 PM - Validating installation path8/3/2004 3:53:14 PM - Verifying IP connectivity using address labsrv018/3/2004 3:53:14 PM - Completed: Logging on8/3/2004 3:53:14 PM - Validating Installation UNC8/3/2004 3:53:14 PM - Attempting connection using user context8/3/2004 3:53:14 PM - Server Name = labsrv018/3/2004 3:53:14 PM - Share Name = adt22inst8/3/2004 3:53:14 PM - Connection established to network installation directory8/3/2004 3:53:14 PM - Installation location: \\labsrv01\adt22inst\8/3/2004 3:53:14 PM - Launching damoinst.exe8/3/2004 3:53:14 PM - Successfully launched damoinst.exe8/3/2004 3:53:14 PM - Log closed


Figure 4-28 Sample of the adt_damoinst.log file

8/3/2004 3:53:14 PM - ********************************************************8/3/2004 3:53:14 PM - ADT Installer for DAMO8/3/2004 3:53:14 PM - Version: 1.0.0.28/3/2004 3:53:14 PM - Copyright 1999-2004 Wolcott Systems Group8/3/2004 3:53:14 PM - ********************************************************8/3/2004 3:53:14 PM - 8/3/2004 3:53:14 PM - Windows temporary folder: c:\docume~1\admini~1.wsg\locals~1\temp\8/3/2004 3:53:14 PM - Program folder: \\labsrv01\adt22inst\8/3/2004 3:53:14 PM - Launch path: \\labsrv01\adt22inst\setup.exe8/3/2004 3:53:14 PM - SMTP logs enabled8/3/2004 3:53:14 PM - Ini file name: c:\docume~1\admini~1.wsg\locals~1\temp\adt_clientinstall.ini8/3/2004 3:53:14 PM - Reading configuration data from c:\docume~1\admini~1.wsg\locals~1\temp\adt_clientinstall.ini8/3/2004 3:53:14 PM - User has local administrator privileges8/3/2004 3:55:21 PM - 22 processes remain active8/3/2004 3:55:21 PM - Checking for active processes that have loaded Notes dlls8/3/2004 3:55:21 PM - Unable to retrieve loaded module list for process System Idle Process8/3/2004 3:55:21 PM - Unable to retrieve loaded module list for process CSRSS.EXE8/3/2004 3:55:21 PM - Unable to retrieve loaded module list for process WMIPRVSE.EXE8/3/2004 3:55:21 PM - Shut down 0 process(es) that had loaded Notes dlls8/3/2004 3:55:21 PM - Initiating pre-install program sequence8/3/2004 3:55:21 PM - Number of pre-installation programs = 18/3/2004 3:55:21 PM - Setting temporary environment variables8/3/2004 3:55:21 PM - Starting Pre-Install Program 18/3/2004 3:55:21 PM - Resetting error flag8/3/2004 3:55:21 PM - Clearing RunBeforeErrors parameter from c:\docume~1\admini~1.wsg\locals~1\temp\adt_clientinstall.ini8/3/2004 3:55:21 PM - Program Name = \\labsrv01\adt22inst\OutlookUpgrade8/3/2004 3:55:21 PM - Program Parameters = InstallPath=Office2000sr1\setup.exe LogRoot=OutlookUpgradeLog MST=corpfinal.mst TARGETVERSION=9.0.0.66278/3/2004 3:55:21 PM - Successfully launched OutlookUpgrade8/3/2004 3:55:21 PM - Running pre-install program 18/3/2004 3:56:01 PM - Pre-install program 1 completed8/3/2004 3:56:01 PM - Reading RunBeforeErrors from c:\docume~1\admini~1.wsg\locals~1\temp\adt_clientinstall.ini8/3/2004 3:56:01 PM - Client Installation: Configuring silent installation8/3/2004 3:56:01 PM - Initiating Auto Client Setup8/3/2004 3:56:01 PM - Created directory structure - c:\lotus\note\8/3/2004 3:56:01 PM - Copying c:\docume~1\admini~1.wsg\locals~1\temp\tuser10.id to c:\lotus\note\tuser10.id8/3/2004 3:56:02 PM - ID file successfully copied to c:\lotus\note\tuser10.id8/3/2004 3:56:02 PM - Auto client configuration completed8/3/2004 3:56:02 PM - Setting default mai client to Outlook8/3/2004 3:56:02 PM - Setting Software\clients\mail\ to Microsoft Outlook8/3/2004 3:56:02 PM - Registry value set8/3/2004 3:56:02 PM - Client Installation: Dialog parameter = /qb



Part 3 Migration and installation

Part 3



Chapter 5. The Domino Migration Tool

This chapter offers an overview of the Domino Migration Tool (formerly known as Domino Upgrade Services “DUS”) and provides step-by-step instructions to use the tool.

5


5.1 Preserving Exchange data for use in DAMO or NotesMost customers who are moving from an Exchange to a Domino server environment have a strong need to preserve historic data for use in the DAMO client. Ideally the user should see no appreciable difference in the client experience. So, it is essential that the data that they worked with in the Outlook client function as expected in the DAMO client. To that end, the Domino Migration Tool is a key component of the DAMO solution.

The Domino Migration Tool allows the Domino administrator to migrate Exchange users and their associated mail data to the Domino server, enabling DAMO users to work with their mail, calendar and task entries just as they would in Outlook. Additionally, the Domino Migration Tool simplifies the configuration of new DAMO users on the Domino server, which is illustrated in the setup instructions.

The Domino Migration Tool was designed originally to allow users to migrate their Exchange data to Domino for use in the Notes client. With the 6.5.1 release, the tool supports migration of data from Exchange for use in the DAMO client, which enables users to run their client of choice against the migrated Domino mail file. Users can even switch back and forth between the two clients, sending and receiving e-mail messages and meeting invitations from both environments.

5.2 How the migration process worksThe migration of data from Exchange to Domino is accomplished by mining the fields of each message and calendar entry in the Exchange data store, then translating those data fields to their corresponding data fields in the target Domino mail file. As an example, if a user creates a meeting entry in the Outlook client over Exchange, a message is composed containing an Exchange data store. When this meeting is migrated to the Domino mail file, the Exchange data store is used to create all the corresponding fields in Domino that are required for a Notes meeting entry. The meeting entry in Domino can then be viewed and edited in either the Notes client or the DAMO client.

Remember that the data storage for the DAMO client resides on Domino, so the messages and calendar entries in the Domino mail file must have the data integrity of a Domino Note. However, the DAMO client must be able to present the messages and calendar entries from the Domino mail file as they would appear in the Outlook client. In many cases, there is not a one-to-one correspondence between the data fields in the Exchange message and the resulting Domino message, and the data field types are often different. For example, the data field that contains the sender of a mail message in an


Exchange e-mail message can be of a different type than the resulting field created on the migration Domino e-mail message. This is why the Domino Migration Tool is an integral component of the DAMO solution, because it translates a user’s Exchange data into a format that both the DAMO and the Notes client can use.

5.2.1 DAMO-specific components of the Domino Migration Tool There are some fundamental differences in the data structure of messages and calendar entries created in Exchange and those created in Domino. For example, the structure of Task entries in Exchange is very different from Domino, and contains fields not found in a Domino ToDo (Task). If a Task from Exchange were migrated to Domino with the corresponding fields necessary to make the Task function and display correctly in Domino, it would no function properly in the DAMO client, because it would be missing key fields necessary for the Outlook client.

Therefore, when migrating the Task from Exchange to Domino, the extra fields are added to the Task so that it operates in the DAMO client just as it would in the Outlook client. These additional data fields do not affect the functionality of the ToDo (Task) in the Notes client because they pertain only to Outlook and Exchange. We refer to these fields as unmapped data because there is no correspondence or mapping between those Exchange Task fields and a Domino ToDo. However, they are required for DAMO and Outlook functionality.

5.3 Migration and functionality enhancements since the 6.0 release

In Lotus Notes version 5.0, a feature was added to the Administrator client to allow users and associated mail stores to be migrated from an Exchange server to a mail database residing on a Domino server. In one simple operation, multiple users could be registered in the Domino server name and address book, and their mail and calendar data migrated into a standard Domino mail file.

While the concept behind the data migration feature was a good starting point, the functionality had a few shortcomings. Most notably, data migrated from an Exchange data store to Domino mail file was essentially static. The user was unable to do any type of workflow on existing meetings (for example, sending reschedule notices or cancellation notices, sending changes to the meeting subject, and so forth) after migration to the Domino mail database. Workflow refers to the messaging functionality of a meeting, essentially any communication connected to and pertaining to a given meeting, and is a key

Chapter 5. The Domino Migration Tool 145

component of the Notes Calendar and Scheduling architecture.

Also, unprocessed meeting invitations or reschedule notices could not be processed after migration, so any meeting invitations that had not been dealt with before migration from the Exchange data store would need to be recreated in the Notes client after migration to the Domino mail database. For group tasks migrated to the Domino mail database as Group ToDo's, none of the workflow associated with these ToDo's was migrated correctly, and workflow could not be performed on the ToDo's after migration.

Finally, changes made to the repeating meeting in Outlook were lost, repeat instances could not be modified, and associated worfklow did not migrate properly.

In 6.5.4, users find a wealth of functional changes to ensure that after a user's Exchange data is migrated to Domino, it functions in either the DAMO or the Notes client just as though it had been created in that client.

5.3.1 Workflow is enabled for single meetings after migrationAfter migration to Domino, an invitee can accept, decline, or tentatively accept unprocessed meeting invitations (invitations sent to him before migration, but not responded to in the Outlook client) or reschedule notices. The appropriate workflow is sent back to the chair of the meeting and the meeting is applied to the invitee's calendar.

The meeting chair can send updates (reschedule of time, subject text change, and so forth) to the meeting to the invitees, or the chair can cancel the meeting, and the invitees to the meeting receive the appropriate workflow. The invitees are able to respond to the workflow in Notes and see the appropriate changes reflected on their calendar entries.

5.3.2 Repeating meetings are fully functional after migration After migration to Domino, repeating meetings, appointments, and all-day-event entries display the correct dates and times, including any changes made to the meeting in Outlook. The repeat meeting is created (and visible in the Meetings view) with the correct parent-child hierarchy, and it reflects the original repeat set and any changes to the child repeat instances. If portions of the meeting have been modified before migration, the user's calendar correctly reflects the modified instances. Also, the chair has the ability to modify the repeating meeting after migration to Domino.


5.3.3 Workflow is enabled for Group ToDo's after migrationAfter migration to Domino, an invitee can accept or decline unprocessed ToDo assignments (task assignments sent to him before migration, but not responded to in the Outlook client). The appropriate workflow will be sent back to the Chair of the ToDo and the ToDo will be applied to the ToDo view.

The Chair can send updates (reschedule of the start date or due date, and so forth) to the ToDo to the assignee, or he can cancel the ToDo, and the assignee will receive the appropriate workflow. The assignee will be able to respond to the workflow in Notes, and see the appropriate changes reflected on ToDo entries.

5.3.4 Contacts are fully integrated in the migrated Domino mail filePrior to 6.5.4, Contacts were migrated from Exchange to Domino as a separate .NSF file, requiring users to subsequently move their contacts into a personal address book in the Notes client. This did not work well when trying to use those Contacts in the DAMO client. So, in the 6.5.4 release, the Contacts are migrated from Exchange as part of the user's mail file. Thus, when replicating the Domino mail file to the DAMO client, the user's Contacts are immediately viewable and usable in the DAMO client.

5.4 How to “Domino enable” your Exchange dataThis section discusses the key issues you need to consider and specific steps you need to take to prepare for the migration from Exchange to Domino.

5.4.1 Preparing for the migration processSizing the migration workstations is a critical component for the overall success of the actual migration. The main factors in determining the size and number of migration workstations are:

� The size of the Exchange Information Stores to be migrated� The number of users to be migrated� The amount of time available for the migration

The actual migration process can be accomplished via several workstations at once, each handling a different portion of the user community. If you have a large number of users to migrate, with lots of data and a short time frame, we suggest using several migration workstations working in tandem, as illustrated in Figure 5-1 on page 148.


You should use workstations that have the following characteristics:

� The fastest CPU� The most RAM� 100 MB network card� Windows 2000 or higher

Figure 5-1 Migration architecture: Multiple migration workstations

5.4.2 Managing coexistence of Domino and ExchangeWhile this chapter assumes that all users and their data within an organization will be migrated from Exchange to Domino, it is expected that there can be a period of coexistence of both the Exchange and Domino servers while the migration is in process. The discussion of server coexistence is beyond the scope of this redbook. Tor information about managing this scenario, refer to the Redbook Migrating from Microsoft Exchange 5.5 to Lotus Notes and Domino 6, SG24-6955.


5.4.3 Migrating Exchange users and their data to DominoIn addition to discussing specific prerequisites for a migration, this section highlights additional steps which need to be taken in advance of the actual migration process.

Prerequisites for performing the migrationPrior to beginning the migration, verify that your organization meets the following prerequisites.

� Must be running Domino 6.5.1 or greater.

� The Extended Mail Template (Mail6ex.ntf) or iNotes™ Template (iNotes.ntf) must be used for all migrated Domino mail files.

� Must have the Administrator ID (admin.id) and Certifier ID (cert.id) for the Domino server to which Exchange users will be migrated.

� Must have Administrator profile set up in Outlook for the Exchange server from which you will be migrating users and their mail files. Follow the instructions in “Creating the Administrator profile in Outlook” on page 154 to set up an Administrator profile in the Outlook client.

� Must have Microsoft Exchange installed as a Foreign Directory Source (part of Administrator install, described in 5.4.4, “Installing Exchange as a Foreign Directory Source” on page 158.

Specifying an Exchange Administrator mail profileTo migrate users from Microsoft Exchange, you must connect to the Exchange server storing the mail files you want to migrate. You connect to an Exchange server by selecting the Administrator mail profile for the Exchange server from which you want to migrate users and their associated mail files. The Administrator account, which must have the Service Account Administrator role for the Exchange site and server, gives you full access to all accounts and all mailboxes in the Exchange server directory.

The profile you use should connect to the Microsoft Exchange server service only. Do not use a profile that connects to multiple messaging services. If necessary, create a new profile for use during migration. The profile must be available locally or on a network drive accessible from the workstation where you are running the Domino Administrator. In our test environment, the Windows NT user account with Service account administrator role was the Administrator.

Verifying the service account administrator roleTo verify that the Administrator account exists and has the correct privileges, complete the following steps to see the user with the service account administrator role on the Microsoft Exchange site and server:


1. Launch the Microsoft Exchange Administrator program, and select the site name. In our example, the site was called Headquarters. See Figure 5-2.

Figure 5-2 Exchange Administrator in Site Headquarters


2. Select File → Properties as shown in Figure 5-3.

Figure 5-3 Microsoft Exchange site properties


3. Click the Permissions tab on the pop-up window to display the Windows NT® accounts with permissions in the Service Account Admin role for this site. See Figure 5-4.

Figure 5-4 Exchange Site Permissions


4. To see the user account with the Service Account administrator role on the Exchange server, select the Microsoft Exchange server name, as shown in Figure 5-5. In our example, the Exchange server was EX01.

Figure 5-5 Microsoft Exchange Administrator: Exchange server

5. Select File → Properties.


6. Click the Permissions tab on the window that appears to display the Windows NT accounts with permissions, Service Account Admin role, for this server. See Figure 5-6.

Figure 5-6 Private information store.

You control access to objects in the directory by using the Microsoft Exchange Administrator program to assign roles to Windows NT user accounts and groups. Roles are sets of permissions that define how much and what type of access a user or group has to an object.

Creating the Administrator profile in OutlookTo create the Administrator profile, follow these steps:

1. Select the Outlook client icon on the desktop and right-click the mouse to display the menu. Note that for this example we are using the Outlook 2000 client, but the display might vary slightly, depending on the version of Outlook you are using.

2. Select the Properties item, and the Mail setup dialog is displayed.


3. Click Show Profiles, and the Mail dialog ID displayed with a list of all the Outlook profiles that exist for the Outlook client. (Figure 5-7).

Figure 5-7 List of Outlook profiles

4. Click Add and the New Profile dialog is displayed. (Figure 5-8.)

Figure 5-8 Profile name box

5. In the Profile Name box, type the name of the Administrator profile for the Exchange server from which you are migrating data.


6. Click OK and the E-mail Accounts dialog is displayed (Figure 5-9). Select Add a new e-mail account.

Figure 5-9 Add a new e-mail account

7. Click Next, and a dialog displays that allows you to select the server type for the Administrator profile.

Figure 5-10 Server type for administrator profile

8. Select the radio button next to Microsoft Exchange Server and click Next. The Exchange Server Settings dialog is displayed.


9. In the box next to Microsoft Exchange Server, type the name of the Exchange server from which you are migrating users.

Figure 5-11 Enter the name of the Exchange Server

10.In the box next to User Name, type the name of the Exchange Administrator. Click Check Name, and a dialog displays requesting the password for the Exchange Administrator.

11.Type the password for the Administrator, and click OK. The E-mail accounts dialog displays with the name of the Administrator underlined.

12..Click OK and the Administrator profile is created.


5.4.4 Installing Exchange as a Foreign Directory SourceExchange is available to install as a Foreign Directory Source during the Notes client installation. During the setup of the Notes client, expand the Migration Tools option and ensure that the Exchange Migration option is enabled (Figure 5-12).

Figure 5-12 Installing Exchange as a foreign directory source for migration

5.4.5 Migrating users from the Exchange server to DominoIf you who have not used the Domino Migration Tool, you will be amazed at how easy it is to use. After you have satisfied the prerequisites in “Prerequisites for performing the migration” on page 149, follow these steps to migrate users and their associated mail stores from Exchange to Domino.

1. Start the Domino Administrator client and log on using the Domino server Administrator’s user ID.

2. Ensure that you are connected to the correct Domino server. From the Server pane of the Domino Administrator, select your target Domino server by selecting File → Open Server and choosing the Domino server to which you want to migrate the Microsoft Exchange server users (Figure 5-13 on page 159).


Figure 5-13 Server to administer

3. Click OK. Select the People and Groups tab, then select People from the right hand menu, and select Register (Figure 5-14).

Figure 5-14 Registering users

4. Click Migrate People.

5. When the Migrate People dialog opens, select Microsoft Exchange Users from the Foreign Directory Source. When prompted, enter the profile of the administrator for the exchange server from which you are migrating, as shown in Figure 5-15 on page 160.


Figure 5-15 Exchange Users from the Foreign Directory Source

6. From the drop-down list of Exchange users, select all users to migrate and add to the People and Groups to Migrate list (Figure 5-16).

Figure 5-16 Selecting users to migrate

John DoeLisa Chase

Carl Smith

John DoeLisa Chase

Carl SmithPeter Hampton

Peter Hampton


7. Select Options to modify the default settings. The options that are most relevant to the migration process are:

– Generate random passwords for users with no passwords

This option and the “Overwrite existing passwords with random passwords” option are mutually exclusive. If you select one of the options and then attempt to select the other, an error message appears.

– Add full name provided to the Notes person document

The User name field of a Person document lists one or more full names (as opposed to name components) by which a user is known in Domino. For a registered user, the first name listed in this field, the primary Notes name, is a hierarchical name based on the certifier ID used to register the user. This same name is checked when authenticating a user's right to access Domino resources

Figure 5-17 Options to modify the default settings

– Convert mail

If you choose to convert mail, during the registration process, the Domino Migration Tool creates a new Domino mail file for the user in question, then automatically converts data from the mail file on the Exchange server to the new Domino mail file.

– Mail files are created on the Domino server that is specified in your registration preferences. If the migration tool cannot create a user's mail file for any reason, such as though the specified mail server lacks sufficient disk space, the user remains unregistered, and an error is logged. Because mail conversion requires mail files to be created immediately, you cannot choose the option on the Mail pane of the Register Person dialog box to create mail files using a background process (adminp). An error message is displayed if you attempt to select this option.

– Add Administrator to mail file access control list

When you create a mail file for a user during migration, by default, your Domino Administrator ID is placed temporarily in the ACL of the new mail file and is assigned Manager access. After the migration completes and the migrated user is successfully registered in Domino, the administrator


ID is removed from the ACL and replaced with the name of the mail file owner. At this point, only the mail file owner can open the mail file.

Figure 5-18 Convert mail only - select when a user has already been registered

– Convert mail ONLY

Select this option if a user has already been registered, and a Notes .ID created for the user, on the Domino server. When this option is selected, in contrast to the Convert mail option, no mail file is created for the user in question. However, data from the mail file on the Exchange server is converted to the user’s existing Domino mail file.

8. Select Migrate. Select Done, and the entire list is added to the registration queue in the Register Person dialog, as shown in Figure 5-19.

Figure 5-19 Users added to the registration queue

9. In the Register Person dialog, select Register All, and all users are added to the Domino Name and Address Book (NAB) and their mail files are migrated to Domino.

Smith, CarlDoe, JaneHampton, PeterBergland, John

PandyaPrashant PPandya


10.After migrating all users, ensure that all addresses are converted from Exchange to Notes canonical format by using the Mail Convert tool.

5.4.6 Converting Exchange addresses to Notes Canonical formatThe Mail Convert tool converts addresses contained within the migrated Domino mail file from Exchange format to Notes Canonical format, to ensure that calendar entries and messages migrated to the Domino server are fully functional in the Notes or DAMO client. Examples of fields requiring address conversion would be the From or To fields in an e-mail message, or the Chair or Required fields in a meeting entry.

The Mail Convert tool only converts addresses of Microsoft Exchange users who exist in the Domino Directory, so all migrated users must have an entry in the Domino server Name and Address Book. If migration is carried out for smaller groups, the tool should continue to be run each time a group is migrated. Also, in order for the address conversion tool to successfully resolve addresses in the migrated mail file, the migrated users should be registered using the migration tool. If the users are registered individually on the Domino server, then their mail file data migrated from Exchange to Domino, the address conversion tool is only able to resolve the migrated users’ addresses successfully if the Domino Administrator elects to update the existing Domino user during the migration process.

The Domino Migration Tool tool resolves the Exchange addresses contained within a user’s mail file to Notes Canonical format through two stages. First, during the migration process fields containing Exchange addresses are replaced with an entry containing the user name combined with the string WTD or WTDIO. This string indicates the field needs to be converted to Notes Canonical format. For example, if you view a migrated user’s mail file prior to converting the Exchange addresses to Notes Canonical format, the address fields will contain a name followed by the string WTD or WTDIO, as shown in Figure 5-20 on page 164.


Figure 5-20 Address fields will contain a name followed by the string WTD or WTDIO

If you view the Person Document in the Domino address book for a user who has been migrated from Exchange to Domino, the Primary Name contains an entry appended with the string WTD. As with the address fields contained in the migrated mail file, the WTD string indicates that the user has been migrated from Exchange to Domino and that the Mail Convert tool needs to be run against the user’s migrated mail file. An example of the Person Document for a newly migrated user is shown in Figure 5-21 on page 165.


Figure 5-21 Person Document for a newly migrated user

The Mail Convert tool represents the final stage of the address conversion process, in which the address fields in the migrated Domino mail file are replaced with a Notes Canonical address.

When the Mail Convert tool is run against a migrated Domino mail file, the tool uses the entries in the Domino address book to resolve the address fields in the migrated mail file to Notes Canonical format. For example, Lisa Chase’s migrated mail file contains entries in the Chair field for another migrated user, William Chase. When the Mail Convert tool is used to convert the address fields in the migrated mail file for Lisa Chase, the tool uses the primary name for William Chase from the Domino address book to resolve the Chair field containing his name in Lisa Chase’s migrated mail file. The WTD string is removed from the Chair field and replaced with the appropriate server and domain information, forming a Notes Canonical address.


Figure 5-22 demonstrates the Chair field containing William Chase’s name resolved to Notes Canonical format.

Figure 5-22 Chair field containing William Chase’s name resolved to Notes Canonical format

Steps to convert addresses to Notes Canonical formatComplete the following steps to convert Microsoft Exchange addresses to valid Notes Canonical addresses in the migrated Domino mail file:

1. For the address conversion process to work correctly, the cache for Name and Address Book (NAB) entries on the Domino Server which is used for Exchange Mail to Domino migration must be current. Perform the following tasks on the Domino Server Console to make sure the cache is updated and current (note that it is not necessary to do perform a dbcache, because we’re starting and stopping the router):

'tell router q'''load updall <Domino Address Book>' (e.g., 'load updall names.nsf')'load router'


2. To perform the address conversion on all migrated mail files on the Domino server (in the mail subdirectory), type the following on the Domino Server Console:

load convert -w mail\*.nsf [-w specifies conversion of Exchange addresses only]

Other available commands include those shown in Table 5-1.

Table 5-1 Additional migration commands

Command Example

load convert -w <specific mail file path> Runs the address conversion on a specified migrated mail file:

load convert -w mail\chair.nsf

load convert -w -l <text list file path> Generates a text list file with all migrated primary mail file paths on the server, excluding any replica mail databases. You can then run the Address Fix by using the second command below with that text file:

load convert -w -l c:\tmp\mailfilelist.txt

load convert -w -f <text list file path> Runs the address conversion on all migrated mail files listed in the specified text file:

load convert -w -f c:\tmp\mailfilelist.txt

Note: In addition to the steps that are outlined in this chapter, we recommend that you review the tips in Appendix B, “Tips for performing a successful migration” on page 221.



Chapter 6. DAMO installation

This chapter discusses and illustrates the procedure for installing DAMO. It explains the system prerequisites and user minimum hardware requirements for DAMO as well as the Administrator software requirements. This chapter also provides information about the installation of DAMO, post-installation setup, and uninstallation of DAMO.

6


6.1 Prerequisites for installing DAMOThis section details the prerequisites and the hardware and software requirements for installing DAMO.

6.1.1 System prerequisitesThe following are the minimum system requirements identified for the IBM Lotus Domino Access for Microsoft Outlook product.

Domino Server Requirements

� Lotus Domino server 6.5.1 or higher� Domino Administrator Client 6.5 or higher (6.5.1 or higher recommended)� Mail databases created using a Mail6.ntf, Mail6ex.ntf or iNotes6.ntf template

Windows Client Requirements

� Windows 2000, Professional Edition� Windows XP, Professional Edition with Service Pack 3� 136MB RAM, required; 256 MB or more recommended� Disk Space: 135 MB disk space minimum, 275 MB disk space

Microsoft Outlook

� Microsoft Outlook 2000/2002 with SP3 or Outlook 2003 with SP1� Microsoft Windows 2000 and Windows XP (Professional Edition)


� Lotus Domino server 6.5.1 or higher� Domino Administrator Client 6.5 or higher (6.5.1 or higher recommended)



6.1.2 Microsoft Outlook 2003The prerequisites, installation, and post-installation instructions for DAMO version 6.5.4 for Microsoft Outlook 2003 are as follows:

1. The user’s computer must be running the Microsoft Windows 2000 or Microsoft Windows XP (Professional Edition) operating system.

2. Microsoft Outlook 2003 must be installed on the system prior to installing DAMO 6.5.4.

3. Microsoft Outlook must be set as the default e-mail client. To verify, open your Microsoft Internet Explorer® (IE) browser and select Tools → Internet Options → Programs.

4. If you wish to take advantage of specific Rich Text features within e-mail, you need to have Microsoft Word 2003 installed on your computer, as described in detail in step 6 on page 186.

5. If you are running Microsoft Outlook 2000, it must be installed in Corporate or Workgroup mode as opposed to Personal mode or No E-mail mode. To verify the release and mode of Microsoft Outlook, select Help → About Microsoft Outlook from its menu. A dialog box displays your Outlook release and mode at the top (Figure 6-1).

Figure 6-1 About Outlook 2003

Chapter 6. DAMO installation 171

6. Your Domino Server(s) must be Domino Server 6.5.1 or higher.

7. You must know the hierarchical name of the users home Domino Server (for example, ServerA/East/Acme) or that servers IP address. You need to enter this information during the installation and setup process.

6.2 Installing DAMOTo install DAMO, follow these steps:

1. Run the setup.exe file, where setup is the name of the distributed DAMO executable file.

2. The InstallShield Wizard loads and displays the Welcome to IBM Lotus Domino Access for MS Outlook Window (Figure 6-2).

Figure 6-2 Welcome to Lotus Domino Access for Microsoft Outlook

3. Select Next. The License Agreement displays (Figure 6-3 on page 173).


Figure 6-3 Licence agreement

4. After reading the License Agreement, accept the terms of the agreement.

5. On the next install window, type your user name and organization, then select Single User Install, as shown in Figure 6-4

Figure 6-4 Single user install


6. Click Next. You are prompted to select the installation directory. The default is C:\Program Files\DominoForOutlook\ . You can change this to another path or keep the default.

Figure 6-5 Installation directory

7. The Custom Setup window, Figure 6-6 on page 175, enables you to select the Single Logon Feature if desired. Click Next.

Note: If multiple users will be accessing the workstation, you can opt for Multi-User Install. You can create additional profiles on a single workstation later if required. See 6.3, “Creating a new MAPI profile” on page 188.

Attention: If you select the Multi-User Install option, this also allows you to store a user’s data files in a different directory. For additional details, refer to “Multi-directory installation functionality” on page 68.

Attention: The sub-directory DominoForOutlook is created in the path C:\ProgramFiles\.


Figure 6-6 Custom setup

8. You are prompted to complete the installation stating that the program is ready to install (Figure 6-7). Click Install.

Figure 6-7 Ready to install


A progress bar appears showing you the installation in progress, as shown in Figure 6-8.

Figure 6-8 Progress bar

Table 6-1 Files installed in the DominoForOutlook directory

Attention: At this point, the DominoForOutlook directory has been populated with the files listed in Table 6-1. You might want to verify that these files exist using Windows explorer at this stage of the installation.

Files Function or Content

log.ntf Creates a local Domino log file when MS Outlook is launched for the first time after the DAMO installation.

mailbox.ntf Creates a local Domino mail.box file when MS Outlook is launched for the first time after the DAMO installation.

pernames.ntf Creates a local Domino address book (names.nsf) file when MS Outlook is launched for the first time after the DAMO installation.


notes.ini This is a Domino system file which includes the client configuration settings equivalent to the notes.ini file for a Domino Notes Client.

nwrdaemndll.dll This extension controls the replication between Outlook and Domino.

nwrdaemn.exe The replication daemon.

nsd.exe Domino debug application.

DA_OUTLOOK_WINHELP.hlp DAMO help file accessible from within MS Outlook.

inotesoutlookaddin.dll This extension add the Domino Preferences tab to the Microsoft Outlook options dialog.

License directory License Agreement files “Lic_**.rtf”.

IBM_TECHNICAL_SUPPORT directory Contains console.log, semdebug.txt, dfosetup.adr

Note: If you are familiar with Lotus Domino you will notice the existence of NOTES.INI, along with Domino template (*.ntf) files.

Files Function or Content


Table 6-2 lists the remaining files that are installed onto the local machine during the DAMO installation process.

Table 6-2 Remaining files that are installed

9. You are prompted to specify your full hierarchical Notes name and the full hierarchical name of your Domino Mail Server, as shown in Figure 6-9.

Figure 6-9 Notes name and server name prompt

dfosetup.exe ndyncfg.exe nminstallr.exe nmuninstr.exe

nnotesmm.exe dfoseten.dll js32.dll mfc42.dll

nabpr32.dll namhook.dll ncrcert.dll ndgts.dll

nfb32.dll nirtf.dll nlsccstr.dll nmsp32.dll

nmstringsr.dll nnetbios.dll nnotes.dll nnotesinprocserver.dll

nntcp.dll npnotes.dll npropertymapping.dll nreplmap.dll

nstrings.dll ntcp.dll nwnspr32.dll nxmlcommon.dll

nxmlpar.dll nxppr32.dll nxrtf.dll da_outlook_winhelp.cnt

icudt18l.dat LotusNotes.sym ini.nbf pid.nbf

cvs310.res ltsci3.tlb


10.Click Next.

11.You are prompted for the location of the Domino ID file, as shown in Figure 6-10. Enter the full path, and click Next. See Figure 6-10.

Figure 6-10 Domino ID path

12.You are prompted to indicate whether your would like the ID file to be copied to your data directory, as shown in Figure 6-11. Click Yes.

Figure 6-11 Option to copy ID to DAMO data directory

Note: For users using both Outlook with DAMO and Lotus Notes, it is important to note that the data directory for DAMO is distinct from the data directory within Lotus Notes.


13.At the next prompt, you are required to enter the password associated with your Domino ID (Figure 6-12).

Figure 6-12 Domino ID password prompt

14.If the correct password has been entered, the prompt that is shown in Figure 6-13 appears. Click Finish to proceed.

Figure 6-13 Creation and configuration of MAPI profile


15.Another installation window appears and shows the status of the setup (Figure 6-14).

Figure 6-14 Installation and MAPI creation progress bar

16.After installation is complete, you see the window as shown in Figure 6-15 on page 182. Click Finish to complete the installation.

Attention: Steps 9 to 12 are the point at which the user authenticate with the Domino server for the first time. The user name and Domino Server name assist the DAMO installation to locate the user’s Domino mail server and the mail file of that user.

The .ID file and its associated password assist the DAMO installation to authenticate the user with the Domino mail server and gain access to the Domino mail file.

The MAPI profile creation can now occur and all the mail data necessary for Microsoft Outlook to work with the Domino server are translated and mapped to the local Outlook client.

Attention: Now a Domino Environment is being created effectively a Domino backend that is mapped to an Outlook frontend.


Figure 6-15 Successful Installation

Note: If you now explore the DominoForOutlook directory, the following files have been created:

log.nsf User’s personal Domino log file which can be accessed via a Domino Client

names.nsf Local address book which can be accessed via the Outlook client for addressing and addition of contacts locally

User A.nsf A local replica of the users Domino server mail file. This file is that is accessible via a Domino client although it is important that although this is a replica not all design elements and contents are replicated to this particular replica. User A in this example is the user’s Domino mail file name.

cluster.ncf If the user’s mail file is located on a Domino server that is clustered, this file is populated with the information that the Outlook client needs to failover to a secondary clustered server if the primary clustered server is not be available.

User A.PST A local .PST file also is created from which the Outlook client sees mail and calendaring data.


6.2.1 Post installation setupTo setup the DAMO client:

1. On your Windows client, click Start → All Programs → Microsoft Outlook 2003.

2. You are prompted for the Profile that you wish to use (Figure 6-16). Select the profile, and click OK. By default, the profile name is the user’s name on server name (for example, John Doe’s mail on Server A)

Figure 6-16 Profile prompt

3. The next prompt (Figure 6-17 on page 184) asks for the Domino Password that is associated with your Domino ID file.

Enter the password and click OK.

Note: You will notice there is an option to save this password. Select this option to modify the User Security options that are stored in the Domino Preferences in the Outlook Options. Review Chapter 2, “Features and functionality” on page 21 for further information about how to modify these settings.


Figure 6-17 Domino Password prompt

4. After entering the correct password, the default Outlook Inbox view opens (Figure 6-18).

Figure 6-18 Default DAMO Outlook inbox view

Note: Here the user’s Outlook client is authenticating with the Domino Server and, as such, an authorized password is required.


5. After the default DAMO Outlook inbox view has been displayed, a smaller dialog also appears detailing that replication of data starts with the user’s home Domino server so that the latest mail is brought to the users inbox.

Figure 6-19 Outlook Send / Receive Progress

Note: The users mail and calendar data that is stored on the Domino server is now pulled to Outlook client. You see that the Domino mail file folders (and subfolders) are created. Then, all data that is contained within those folders is pulled, including the inbox.


Figure 6-20 shows the DAMO Outlook Inbox.

Figure 6-20 Send or receive progress dialog in inbox

Depending on the size of your Domino mail file, the initial replication into your DAMO .PST file takes longer than subsequent replications.

DAMO is now installed,

6. Outlook mail creation, edition, and preview are best viewed in rich text format. For this reason, the user must configure the DAMO Outlook client to create, edit, or read e-mail in rich text format.

Note: Within a test environment for the purposes of this redbook, a Domino mail file (.NSF) roughly 600 MB in size took between 15 to 30 minutes to complete the initial replication to the DAMO .PST file. The length of time depends very much on the quantity of data, the network speed, and bandwidth that is available.


If Microsoft Word 2003 is installed, the user can take advantage of these functions. First, select Tools → Options and navigate to the Mail Format tab.

Then, select Use Microsoft Office Word 2003 to edit e-mail messages and Use Microsoft Office Word 2003 to read Rich Text e-mail messages, as shown in Figure 6-21.

Figure 6-21 Outlook 2003 Mail Format option

After the format options are set, the Outlook client is ready for use with a Domino server.

Note: This option is greyed out and not available if versions before Microsoft Word 2003 are installed on the user’s workstation.


6.3 Creating a new MAPI profileWhen DAMO has been fully installed, there is an option to create a new or further MAPI profiles that allow the Outlook client to access multiple Domino hosted accounts should the workstation be a shared machine. To create a new MAPI profile:

1. Click Start → Programs → IBM Lotus Domino for Microsoft Outlook → Create New MAPI Profile.

2. You are prompted to input the Domino name for the new user and the Domino server name. Remember to include the hierarchical names for both as shown in Figure 6-22. Click Next.

Figure 6-22 User name and Domino server name

3. There is a short delay while DAMO connects to the Domino server and locates the user information in the Domino Address Book. After this authentication has occurred, you are prompted to input the location of the user’s Domino ID file, as shown in Figure 6-23 on page 189.

Note: This is the first part of the MAPI profile creation process where DAMO identifies a user and the Domino mail server to which that user is associated.


Figure 6-23 ID file location

4. You are asked whether you would like to copy the ID file into the data directory. Click Yes, as shown in Figure 6-24.

Figure 6-24 Copy ID file to data directory

Attention: Note the earlier distinction between the Domino data directory (where the Domino ID file resides) and the Domino Access for MS Outlook data directory (where the copy of the Domino ID file is placed).


5. As part of the Domino server authentication process, you are prompted for the Domino password that is associated with the Domino ID file (Figure 6-25). Type the password, and click OK.

Figure 6-25 Domino password prompt

6. The first part of the MAPI creation is now complete. Click Finish.

Figure 6-26 First part of MAPI set up complete


7. Launch Microsoft Outlook 2003.

8. You are prompted to opt for a profile. You will notice there is now more than one profile available in our example, as shown in Figure 6-27.

Figure 6-27 Profile option

9. Choose the appropriate profile and enter the Domino password (that is associated with the profile now).

Figure 6-28 Password prompt

Note: As shown in Figure 6-28, you can save the password.


10.What follows next is described in steps 4 to 6 in 6.2.1, “Post installation setup” on page 183.

6.4 Uninstalling DAMOThere can be various reasons for uninstalling the DAMO client, such as switching fully to Lotus Notes and this section describes the process for the installation. To uninstall DAMO, first remove any profiles that were created during the DAMO installation process by following these steps:

1. Exit the Outlook Client and locate the Microsoft Outlook shortcut icon on your desktop.

2. Right-click the icon and select Properties.

Figure 6-29 Outlook Properties selection

3. In the Mail Setup window (Figure 6-30), click Show Profiles.

Figure 6-30 Mail setup


4. In the Mail dialog (Figure 6-31), highlight the profile to be removed, and click Remove.

Figure 6-31 Profile removal

5. You are prompted to confirm this action. Click Yes to confirm.

Figure 6-32 Profile removal confirmation

6. The profile is deleted immediately. Click Apply followed by OK to complete this part of the uninstallation.

Attention: Although profiles can be removed using this method, profiles must not be created using the Microsoft Outlook Properties action for use with DAMO. The DAMO installation process and the DAMO Create New MAPI Profile should be the only methods by which DAMO profiles are created.


Having removed the profiles, the uninstallation of DAMO can commence.

1. Exit the Outlook client, and then click Start → Control Panel if using Windows XP or Start → Settings → Control Panel if using Windows 2000).

2. Within the Control Panel window, select Add or Remove Programs. From within the window, scroll to IBM Lotus Domino Access for Microsoft Outlook, highlight it, and click Remove.

Figure 6-33 Add or remove programs window

3. You are presented with a confirmation pop-up (Figure 6-34). Click Yes.The uninstallation begins.

Figure 6-34 Uninstallation confirmation


4. After this process is complete, you can close the Add or Remove Programs window and the Control Panel window.

Note: By this stage, the DAMO application will no longer be available. However, during the initial installation, a local folder (C:\Program Files\DominoForOutlook\) was created on the workstation which contains, among other files, the user’s Domino ID file, local DAMO .PST file, names.nsf, and a local replica of the Domino mail file, including various Domino templates.

These files are not removed automatically during the uninstallation process. You should retain this directory, because it contains not only a local archive of mail but files that assist in a re-installation of DAMO. If retained and a new installation of DAMO occurs, the installation will be relatively faster than a fresh installation.

Alternatively, if the directory is no longer required, you can delete it from the workstation using Windows Explorer.



Part 4 Instant messaging with DAMO

Part 4



Chapter 7. Instant TeamMessenger for Microsoft Outlook

IBM Lotus has been the leading provider of secure and scalable enterprise wide instant messaging and presence awareness with its IBM Lotus Instant Messaging product (formerly Sametime). For users of the Microsoft Outlook client however, it was not possible to leverage Sametime for seamless instant messaging and presence awareness capabilities. With the release of Domino Access for Microsoft Outlook, IBM has partnered with Instant Technologies to address this issue through the product Instant TeamMessenger. For details on Instant Technologies on their suite of products which leverage IBM Lotus Instant Messaging and Web Conferencing (Sametime), visit:

http://www.instant-tech.com/

This chapter discusses Instant TeamMessenger 3.0, the product that provides both the instant messaging and presence awareness capabilities of Sametime for use with the Outlook client.

7



7.1 Instant messaging with Microsoft OutlookFor a number of years now, IBM Lotus has been the leading provider of secure and scalable enterprise wide instant messaging and presence awareness with its IBM Lotus Instant Messaging product (formerly Sametime).

Microsoft also offers an Instant messaging and presence awareness solution for the Outlook / Exchange environment, if an organization has implemented the Office Live Communication server. More importantly, implementing the Office Live Communication server involves organizations having to “rip and replace” their entire file and print infrastructure and upgrade to Windows 2003 Server, as well as designing and implementing an Active Directory solution. Finally, Microsoft’s Live Communications Server needs to be deployed and then presence awareness is only available for Office and Outlook 2003.

For many organizations, it is not feasible to replace an entire network infrastructure, and every Outlook Client simply to get Instant Messaging and presence awareness functionality. This effort involves too much disruption, time, and has a significantly large cost.

IBM has partnered with Instant Technologies to provide the instant messaging and presence awareness capabilities of Sametime for use with the Outlook client. Instant TeamMessenger for Microsoft Outlook supports IBM Lotus Sametime and the Outlook 2000 client and higher.

Similar to IBM Lotus Domino Server, Lotus Instant Messaging (Sametime) runs on a multitude of operating systems, such as Windows, AIX, and Solaris. This gives organizations more hardware and software options, together with a greater level of deployment flexibility, while at the same time helping them to leverage the inherent scalability, reliability, and performance of many of the non-Windows based operating systems.

While providing a highly secure and scalable solution, IBM Lotus Sametime also fully supports the LDAP protocol. This allows organizations to leverage existing corporate directories with no need to maintain and administer additional user and group repositories and passwords.

More significantly, by using IBM Lotus Sametime with the Outlook client there is no requirement to “rip and replace” the underlying operating system. Also, because Instant TeamMessenger supports Outlook 2000 and higher there is no need to upgrade the user’s Outlook client either.

As a result, by using IBM Lotus Instant Messaging with the Outlook client and Instant TeamMessenger, organizations gain massive total cost of ownership savings (while having the added benefit of not disrupting users).


7.2 Instant TeamMessenger 3.0 overviewWith the advent of the DAMO client for Outlook, Instant Technologies has produced the Instant TeamMessenger product, providing an integrated solution to fully enable DAMO Outlook users to participate in Instant Messaging and Presence Awareness from within their DAMO enhanced Outlook mail client.

Some of the highlights of Instant TeamMessenger 3.0 are:

� Automatically login to Sametime when your Microsoft Outlook client is started.

� Archive your Instant Messaging conversations directly into the Microsoft Outlook Journal.

� Pull names of team members from currently selected items, including: contacts, appointments, distribution lists, and e-mails.

� Makes Outlook e-mails, contacts, and calendar appointments dynamic with Lotus Sametime awareness.

� Automatically generate a dynamic buddy list based on the selected item(s) in Microsoft Outlook.

� Use your Microsoft Outlook contacts folder to create personal buddylist lists.

� Create Sametime Instant Meetings and multi-person chats.

� Manage and change your Sametime IM Status from within Outlook.

� Automatically monitor your Outlook calendar and change your Sametime status based on calendar events.

� Use and configure you existing Sametime buddy list.

� Take part in Sametime encrypted chats conversations, similar to the Sametime Connect Client.

� Store a list of common places or frequently used chat rooms.

Note: For more information about Instant TeamMessenger, refer to Instant Technology’s Web site at:


Chapter 7. Instant TeamMessenger for Microsoft Outlook 201


7.3 Key features of Instant TeamMessengerSimilar to the functionality within the Lotus Notes client 6.5.1 and higher with integrated instant messaging and presence awareness, Instant TeamMessenger allows an Outlook user using DAMO to see if the sender of a mail in the inbox is online and available to chat.

Instant TeamMessenger simply installs as a plug-in to the user’s existing Outlook client. When you have installed Instant TeamMessenger, you see the Instant TeamMessenger toolbar as shown in Figure 7-1. This toolbar allows you to access the awareness and instant messaging features.

Figure 7-1 Instant TeamMessenger toolbar

Instant TeamMessenger Toolbar


7.3.1 Presence awareness, instant messaging, and buddy listsFigure 7-2 shows the Who is Online feature that Instant TeamMessenger installs in the Outlook client.

Figure 7-2 Who is online feature in Outlook

Presence awareness and user status are available as a simple pop-up.

Awareness based on names of recipients


Figure 7-3 shows the user Buddy List that Instant TeamMessenger installs into the Outlook client.

Figure 7-3 Buddy List feature in Outlook with Instant TeamMessenger

The buddy list can be added to manually from a corporate directory (which for IBM Lotus Sametime can be any LDAP V3 compliant directory), or dynamically by selecting names from the user’s mail messages.


Figure 7-4 shows a number of e-mail messages that have been selected by the user and added automatically to the buddy list.

Figure 7-4 Adding users to the buddy list automatically

7.3.2 Logging chats to the journalIncreasingly for legal and compliance reasons, organizations are required to keep copies of e-mail and instant messages. IBM Lotus Sametime has the facility to log all chats at the server. However, it might also be convenient for day-to-day working purposes for users to be able to save chats locally and retrieve them for future reference.


With Instant TeamMessenger, chat sessions can be stored to the user’s journal. Aside from being readily available for reference, the chat sessions are also stored by date and time order. This can be particularly useful for following the progress of a chat over a period of time (for example, the status of a current project).

Figure 7-5 shows an example of journaled chats stored by date, together with a meaningful description.

Figure 7-5 Journaling chats


7.3.3 Calendar entries and Contact List functionalityInstant TeamMessenger also has the ability to show presence awareness for a user’s contacts, as shown in Figure 7-6.

Figure 7-6 Presence awareness for a user’s contacts


Instant TeamMessenger does not only function from within a user’s e-mail. It is also possible for users to add and check presence awareness from within the Outlook calendar, as depicted in Figure 7-7.

Figure 7-7 Presence awareness in the Outlook calendar


7.3.4 Deployment scenarios for Instant TeamMessenger

By using IBM Lotus Sametime together with Instant TeamMessenger, an organization can very easily leverage the strengths of both the Domino and Sametime server platforms, while continuing to use their present file and print infrastructure and desktop mail client software. There is no need to “rip and replace” or change the network operating system or user’s Outlook client software with the IBM Lotus solution.

Figure 7-8 shows a typical scenario of an Outlook client with DAMO installed that accesses both a Domino mail server and uses the Lotus Instant Messaging Infrastructure (Sametime) for presence awareness and instant messaging capabilities.

Figure 7-8 Outlook with DAMO and Instant TeamMessenger using Domino mail and Sametime

Attention: The various scenarios in this section refer to both DAMO and Instant TeamMessenger being installed with the Outlook client. It should be noted that these products are independent of each other and can be installed together or individually, depending on an organization’s requirements.


The Outlook client user logs on to their Windows file server as normal (for example an NT4 or Windows 2000 server) and, through the Single Log On feature in DAMO, is able to access their mail which is now on a Domino server. With the Instant TeamMessenger software also installed in the Outlook client, the user also has Instant Messaging and presence awareness available which is now using the IBM Lotus Sametime server.

Notice how the Domino servers in this scenario are clustered for failover despite being on completely different operating systems. Domino clustering allows for active users on both servers, and these users can be any mixture of Notes client, Web Browser, or Outlook with DAMO users.

Notice also how the Sametime server is also using a different operating system. This ability to use a variety of operating systems gives organizations far greater deployment flexibility than with Microsoft’s instant messaging solution which is based entirely around migrating to the Windows 2003 and Active Directory platform.


In some instances, an organization might want to use an existing corporate LDAP directory for user and group names. Because Domino and Sametime both fully support the LDAP protocol, DAMO, and Instant TeamMessenger could be used in a scenario where an Outlook user’s mail is stored on a Domino mail server, but the Domino mail server and Sametime server are both using a corporate LDAP directory for name and group lookups.

Figure 7-9 illustrates this scenario.

Figure 7-9 Outlook with DAMO and Instant TeamMessenger using Domino mail and Sametime with LDAP

Note: If the user in this scenario was logging in to Active Directory (as opposed to, say, Windows NT) then Active Directory could also act as the Corporate LDAP directory for both the Outlook client and the Domino and Sametime servers. It should also be noted, that the Domino Directory itself can also be used as a corporate LDAP directory and is frequently deployed by organizations as one.



Part 5 Appendixes

Part 5



Appendix A. Troubleshooting

This appendix discusses how to troubleshoot some of the more common issues that we experienced while using DAMO. Additionally, it provides a section including tips for a successful migration from Exchange to Domino.

A


The inotesoutlookaddin.dll file and Domino preferencesOccasionally, we observed that Outlook does not activate the inotesoutlookaddin.dll file, the .dll file that adds the Domino Preferences tab into the Outlook options by default when DAMO is installed. This is a simple task to complete and can be done either locally or remotely, depending on your deployment scenario. Follow these steps:

1. Open the Outlook Options and select the Other tab, as shown in Figure A-1.

Figure A-1 Outlook Options Other tab


2. Select Advance options to display the dialog that is shown in Figure A-2.

Figure A-2 Outlook Advanced Options

3. Click COM Add-Ins to display the dialog shown in Figure A-3.

Figure A-3 Outlook COM Add-Ins Dialog

4. As shown in Figure A-3, the inotesoutlookaddin.dll file is selected. If your Outlook client is shown and is not selected, simply select it, and click OK.

5. Close and restart your Outlook client.

It has been noted that when Office 2003 is installed, of which Outlook 2003 is a part, a number of the .dll files within the Outlook directory get updated. As a

Appendix A. Troubleshooting 217

consequence of this, DAMO initiates a full synchronization of mail and calender data. Although not a problem in itself, you should be aware that this can add some time to your upgrade project.

Images not appearing within e-mailIf you have not selected Microsoft Office Word 2003 as your default e-mail editor, there will be occasional e-mail messages in which the graphics do not appear as in-line images.

Outlook mail creation, edition, and preview are best viewed in rich text format. For this reason, you must configure the DAMO Outlook client to allow the creating, editing, or reading of e-mail in rich text format. To do this:

1. Select Tools → Options and navigate to the Mail Format tab on the options window.

2. Select Use Microsoft Office Word 2003 to edit e-mail messages and Use Microsoft Office Word 2003 to read Rich Text e-mail messages, as shown in Figure A-4.

Figure A-4 Outlook 2003 Mail Format option


Password protecting the local .PST file for multi-user DAMO installations

With the release of the 6.5.4 release of DAMO, users are now offered the additional functionality of having a multi-user installation.This allows users to share the same Outlook installation and the same DAMO installation as well on the same PC. However, this sharing can raise a concern regarding the security of the mail data that is contained on the local machine in the local .PST file and protecting it from unauthorized access.

To ensure that this issue is not a problem, in Outlook XP and 2003:

1. Select File → Data File Management.

2. Select Mailbox and Settings

3. Change the password.

In Outlook 2000, follow these steps:

1. Select View → Folder List.

2. Right-click the mailbox and select Properties → Advanced → Change Password.

This functionality is native to the Outlook client and is not affected by the DAMO code.

Names are displayed in last name, first name format in the Outlook contact list

When DAMO is installed, the contacts continue to be stored using the native Outlook format of first name, last name. if you need to change this format, then follow these steps, In Outlook XP and 2003:

1. Select Tools → E-mail Accounts.2. Select View or Change Existing Directories or Address Books.3. Click Next.4. Select Outlook Address Book and select Change.5. In the Outlook Address Books dialog, select Contacts: Personal Folders.6. In Show Names By dialog, select File As (Smith John).

You need to restart Outlook to effect your changes. Again, this is functionality native to the Outlook client and not affected by the DAMO installation.

Appendix A. Troubleshooting 219


Appendix B. Tips for performing a successful migration

This appendix helps you identify and resolves some potential issues during the process of migrating from Exchange to Domino.

B


List of issues and solutionsTable B-1 lists a few situations that you can encounter during the migration process that require some simple troubleshooting.

Table B-1 Troubleshooting tips

issues Solution

If you need to migrate a user more than once… The Domino Migration Tool is designed as a "run once" utility, which registers users and creates associated mail files on the Domino server. You can migrate a user more than once, but remember that if you migrate to the same Domino mail file, the existing data is not replaced, just appended.

If you need to "re-migrate" a user, delete the existing Domino mail file from the Domino server, then perform the migration for that user again. You are informed that the user is already registered on the Domino server and prompted to update the existing user. Do this, complete the migration, and a new mail file is created for the migrated user on the Domino server.

If the address conversion for a user's mail file fails…

While running the address conversion utility, you might see the message, Address conversion failed for this user.

It's crucial that the server name and address book be up to date before running the address conversion. Update the name and address book following the instructions previously outlined, then perform the address conversion again.

If after migration, a user's mail file displays addresses (such as in the Chair item or From item) in Microsoft Exchange format…

If addresses are displaying in Exchange format, you might have forgotten to perform the address conversion on this mail file.

To be on the safe side, perform the address conversion on all the migrated mail files on the Domino server. Also, it is possible that you have not yet migrated the user whose address is displaying in Exchange format. After that user has been registered on the Domino server and the associated mail file migrated, run the address conversion utility again.


If the Domino Migration Tool fails while users are in the process of being migrated…

If the migration process fails, which can happen if the server connection is lost, it is best to start the process again, beginning with the user in transit during migration.

If the migration process fails while migrating a user, that user and any others in the Registration Queue, are saved in preparation for registration and migration. Because the user was in transit when the failure occurred and might be partially migrated, it is best to delete that user's mail file from the server when the server connection is restored. Then, resume the migration process by selecting Register All in the Register Person dialog.

issues Solution

Appendix B. Tips for performing a successful migration 223


Appendix C. Functionality comparison between Outlook with Exchange and DAMO

This appendix provides a detailed functionality comparison between Outlook 2003 in a native Exchange environment versus using the Outlook 2003 client with DAMO 6.5.4 within a Domino environment.

C


Detailed functionality comparisonThe tables in this appendix provide a detailed functionality comparison, allowing you to look in depth at each individual Outlook function both against Exchange and with DAMO against Domino.

Table C-1 Messaging features functional comparison


Read messages

Auto Preview Yes Yes

Folder hierarchy in Navigation Pane

Yes Yes

Favorites folders in Navigation Pane

Yes Yes

Navigate hyperlinks in messages Yes Yes

Attachments can be opened from Reading and Preview Panes

Yes Yes

Can accept or decline appointments in Preview and Reading Panes

Yes Yes

Unlimited number of messages displayed in Mail view

Yes Yes

Send messages

AutoAddress and AutoName Yes Yes

Insert hyperlinks in message text Yes Yes

Information Bar available in Preview and Reading Panes

Yes Yes

Send and receive attachments Yes Yes

Embed documents in messages Yes Yes - as attachments

Request read or delivery receipt Yes Yes

Word as e-mail editor Yes Yes

Spell check Yes Yes


Background and AutoCorrect spelling

Yes Yes, Word as editor

Add words to dictionaries Yes Yes

Recall message Yes - Microsoft Exchange Feature

No

Auto-select message encoding Yes Yes

Send mail message with voting buttons

Yes Yes - Outlook to Outlook

Track delivery and read receipts with original message

Yes Yes

Create messages from Address Book

Yes Yes

Receive HTML mail Yes Yes

HTML editing Yes Yes

Plain-text editing Yes Yes

Rich Text Format (RTF) editing Yes Yes

Automatic formatting of messages with color based on criteria

Yes No

Automatic text corrections Yes Yes, Word as editor

AutoSignature Yes Yes

Insert signature on demand Yes Yes

Multiple signatures Yes Yes

Include vCard in signature Yes No

Set message importance Yes Yes

Message sensitivity Yes Yes

Message expiration Yes Yes

Deferred delivery (with or without rules)

Yes Yes

Message templates Yes Yes - PST


Appendix C. Functionality comparison between Outlook with Exchange and DAMO 227

Default font for new messages Yes Yes

Default font for replies and forwards

Yes Yes

Redirected replies Yes Yes

File routing Yes No

Internet faxing Yes With Third Party Solution

Receive and reply to messages

New mail notification Yes Planned for an upcoming release

Respond to mail message (voting buttons)

Yes No

Reply in same format received Yes Yes

No indentation of Reply and Forward bodies

Yes Yes

Search for messages

Find Yes Yes

Search capabilities (Advanced Find)

Yes Yes

Search folders Yes Yes

Organize Messages Yes Yes

Quick Flags and message flags Yes Yes

Categories and Master Category List

Yes Yes

Drag and drop messages Yes Yes

Multiple views Yes Yes

Arrange by Yes Yes

Grouping items Yes Yes

View by category Yes Yes

View mail by flagging for follow up

Yes Yes



Public folders Yes, Accessed through Exchange Server

No

Sort message list by standard fields

Yes Yes

Set order and size of columns in message list²

Yes Yes

Enhanced conversation management

Yes Yes

Manage messages by group Yes Yes

For Follow-Up folder Yes Yes

Display custom views Yes Yes

Create custom views Yes Yes

Mark message as read or unread Yes Yes

Recover deleted messages Yes No

User saves e-mail messages to Drafts folder

Yes Yes

Mailbox Cleanup Yes Yes

Ability to disable individual rules Yes Yes

AutoArchive Yes Yes (Messages are removed from the PST but are retained in the server store)

E-mail account Setup Wizard Yes Yes

Test E-Mail Account tool Yes N/A

Drafts folder Yes Yes

User-configurable Delegate Access permissions

Yes Yes

User configures public folder permissions

Yes - applies to Exchange N/A



Table 7-1 Collaboration features functional comparison

Table 7-2 Calendar features functional comparison

Collaboration features Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Document workspaces Yes N/A

Meeting workspaces Yes N/A

Microsoft Windows SharePoint Services and SharePoint Team Services integration

Yes N/A

Instant messaging Yes With third party solution from Instant Technologies

Calendar features Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Calendar views of different time periods

Yes Yes

Calendar preferences Yes Yes

Side-by-side viewing of multiple calendars

Yes Yes

Meeting reminders (minutes, hours, or days in advance)

Yes Yes

Color individual or recurring appointments

Yes Yes

Notification of adjacent or conflicting appointments

Yes Yes


Offline use of calendar Yes Yes


Table 7-3 Address book features functional comparison

Table 7-4 Meeting management features functional comparison

Address Book and GAL features


Address Book Yes Yes

Browsable GAL Yes Yes

Access to general GAL properties (name, address, phone)

Yes Yes

Access to advanced GAL properties (organization chart, distribution list memberships)

Yes No

Synchronized offline GAL Yes No


Plan a face-to-face meeting Yes Yes

View other user's free and busy information

Yes Yes

Propose New Time Yes Yes

Appointments summarized in Outlook Today

Yes Yes

Invoke calendar from meeting request to see full schedule

Yes Yes

Include attachments in appointments and meeting requests

Yes Yes

Insert e-mail messages as attachments in appointments and meeting requests

Yes Yes - Outlook to Outlook

Create a Meeting Workspace in a meeting request

Yes N/A

Track acceptance of attendees to a meeting

Yes Yes


Table 7-5 Contact Management features functional comparison

Attendee list visible to all attendees

Yes Yes - Chair Option

Send or receive requests over the Internet as calendar attachments

Yes No

Publish and retrieve free and busy information to the Internet with iCalendar subset

Yes No

Advanced, automatic meeting request processing options

Yes No

Plan online meeting (Microsoft NetMeeting)

Yes No

Exchange conferencing Yes No

Use Address Book to pick attendees

Yes Yes

Free and busy view Yes Yes

Forward or reply to a meeting request

Yes Yes

All-day events Yes Yes



Business Contact Manager Yes With Microsoft third-party application, not currently tested or supported

Contact picture Yes Yes

Use e-mail properties to add Contacts data

Yes Yes

Use contact information in mail merge

Yes Yes

Contact activity tracking Yes Yes


Table 7-6 Task management functional comparison

View by company Yes Yes

Print address cards Yes Yes

Important dates (birthdays and anniversaries) in Contacts listings

Yes Yes

Exchange virtual business cards (vCards)

Yes Yes

Shared contacts Yes No

View contacts by follow-up flag Yes Yes

Internet addresses listed in Contacts

Yes Yes

Multiple addresses in Contacts items

Yes Yes

Add and edit contacts Yes Yes

Send new message to contactY Yes Yes

More than one physical and e-mail address listed in Contacts

Yes Yes



Create and manage tasks Yes Yes

Create task from e-mail message Yes Yes

Simple and Detailed task views Yes Yes

View tasks by category Yes Yes

View by active, completed, or overdue status

Yes Yes

Edit tasks in view Yes Yes

Task reminders Yes Yes


Table 7-7 Client services functional comparison

Task requests and tracking Yes Yes

Tasks time line view Yes Yes

TaskPad view in Calendar Yes Yes


Client services Microsoft Outlook 2003 IBM Lotus Domino Access for Microsoft Outlook 6.5.4

Alerts

New Mail Tune Yes Planned for an upcoming release

Outlook Custom Installation Wizard

Yes Yes

Out of Office Assistant Yes Yes

Recover Application Yes N/A

Read-only Delegate Access to messages and other information

Yes Yes

Editable Delegate Access of messages to other accounts

Yes Yes

Import and export files Yes Yes

Client-side Setup Wizard Yes Yes


Outlook Hotmail support Yes No

Custom forms Yes No

Consolidated offline settings Yes Yes

Support for IMAP4, POP3, and SMTP

Yes Yes


Table 7-8 Security and content management functional comparison

Domino provides capabilities to help prevent the delivery of unsolicited e-mail (spam) at the server level, potentially reducing the need for client-side configuration and user involvement. Pertinent features include server-based mail rules, anti-relay controls, and DNS blacklist filtering.

Security and content management features


Information rights management Yes No

Junk e-mail filter lists Yes No*

Junk e-mail folder Yes No

Trusted Senders and Trusted Recipients lists

Yes No

Block external content Yes No

Block attachments Yes No

Antivirus enhancements Yes No

Digital signature Yes No

Digital encryption Yes No

Single sign on Yes Yes

Certificate management Yes Yes - External (x509)

Kerberos authentication Yes Yes

Automatic logging off after inactive period

Yes N/A

Journal Yes Yes - local only

Notes Yes Yes - local only


Table 7-9 Performance optimizing functional comparison



Integration with Microsoft SharePoint Portal Server

Yes No

Microsoft Office Live Communications Server 2003 integration

Yes No

Cached Exchange mode Yes Accomplished through local replica capability

Intelligent connectivity Yes N/A

Remote procedure call connectivity to Exchange (RPC over HTTP)

Yes N/A

Synchronization groups Yes No

Background synchronization of local and server folders

Yes Yes

Differential, offline Address Book synchronization with server

Yes No

Incremental change synchronization

Yes Yes

Smart change synchronization Yes N/A

Presynchronization reporting Yes No

Offline synchronization Yes N/A

Buffer packing Yes N/A

MAPI compression Yes Accomplished through Notes Remote Procedure Call (NRPC) compression

Skip bad items Yes Yes

Outlook performance monitoring Yes N/A

Unicode .PST support Yes N/A

Cancel request to server Yes N/A

Send and Receive groups Yes Yes


LDAP support and default list Yes No





Appendix D. Updates to Domino Access for Microsoft Outlook 6.5.5

This appendix offers an overview of the updates to Domino Access for Microsoft Outlook (DAMO) client functionality in the 6.5.5 release. Additionally, it provides usage hints for DAMO 6.5.5 and a troubleshooting section.

D


New functionality in DAMO 6.5.5The DAMO 6.5.5 release includes functional additions and improvements, including a new Silent Install option, changes to the handling of Personal Contacts, and the addition of an Other Messages folder.

Silent InstallThe Silent Install option installs Domino Access for Microsoft Outlook and creates a profile without end user involvement, using the inherent InstallShield capabilities that call a setup file containing the user's connection information to the Domino server. There is one setup file for each user containing the following connection information:

-u <User Name> -s <Server IP address> -f <Full path to ID file> -p <id file Password>

For example:

-u Homer Simpson -s 1.11.11.111 -f c:\lotus\notes\data\homer.id -p 123456

In the 6.5.5 release of DAMO, the silent install connection information can use the "-d" parameter to indicate a Multi-User installation and the data directory specific to this user. Additionally, the "i" parameter can be used to insert multiple notes.ini parameters:

-u <Notes common name> -s <Domino Server name> -a <Server IP address> -f <path to Notes ID file> -p <password> -d <Path to data directory> -i <ini parameter 1> -i <ini parameter 2>

For example:

-u Homer Simpson -s Springfield -a 9.22.35.119 -f C:\IDs\HSimpson.id -p Marge2005 -d C:\DAMOData\Homer Simpson -i CONSOLE_LOG_ENABLED=1 -i STX9=1

Personal ContactsWhen a managed user grants access of his tasks, mail and calendar items to a delegated user, regardless of the access level the managed user specifies, the delegated user will at least have read access to the managed user's Personal Contacts. However, when the delegated user accesses the managed user's file through Domino for Web Access (DWA), the behavior is as it is in Notes. With only the lowest access level, the delegated user does not have access to the Contacts tab in DWA.


Other MessagesMessages that do not belong in the standard Outlook folders are now created in the Other Messages folder during replication from the Domino server. Previously these messages were placed in the Inbox.

DAMO 6.5.5 usage hintsBased on customer feedback, we’ve compiled detailed hints for using the DAMO 6.5.5 client.

Connection documentsThe DAMO client enables you to create server connection documents in the Domino address book.This is particularly useful if you move your laptop between home and the office, which can cause connectivity issues between DAMO and the Domino server.

Follow these steps to create a connection document in the Domino address book:

1. From the DAMO menu bar, select Tools → Options, then select the Domino Preferences tab.

2. From the Domino Preferences tab, select the Replication button to display the Replication Settings dialogue.

3. In the Preferred Server field, enter the IP address of the Domino server to which you want to connect. Select the OK button and a connection document will be created if the Domino Server is running and port 1352 is being monitored.

Outlook Deleted Items folderA common misunderstanding is that deleting a mail message, calendar item or contact in DAMO will remove the item from the Domino server. In order for deletions in the DAMO client to be replicated to the Domino server, you must empty the Deleted Items folder replicating to Domino. Also, DAMO does not recognize Outlook’s "Hard Delete" shortcut of SHIFT+DELETE to delete a message. Although the item will be removed from the local .PST file, this deletion will not be replicated to Domino.

Appendix D. Updates to Domino Access for Microsoft Outlook 6.5.5 241

Managed CalendarThe Managed Calendar capabilities of DAMO can be used to allow users to share databases or to enable multiple users to access a Mail-In Database. To accomplish this functionality, register a mock user and grant all members of the group access to the mock user’s mail file.

An Enhancement Request for a full featured Group Calendar has been submitted to Quality Engineering. There are no current plans to address this request.

Automating DAMO installThe DAMO installation can be initiated from a batch file that calls setup.exe, where setup is the name of the distributed DAMO executable file. Note that Microsoft Windows requires that a user have Administrator privileges to install software and Power User rights to create a DAMO profile. In the following example, a single line of text is contained in the batch file:

setup.exe /s /v" /qn SETUPFILE=c:\DAMOSetup\HomeSimpson.txt"

A batch file can also be used to uninstall DAMO without the need for user intervention. The following command line would accomplish that (note that there are no spaces between /v and /q):

setup /s /x /v/q

The configuration settings are as follows:

– /s = Silent

– /x = Remove

– /v = Pass the next value to Windows msiexec.exe

– /q = The value passed to msiexec.exe. This means "quiet"

Changing the default replication settingsBy default, DAMO does not replicate messages older than 90 days from the Domino server to the local Outlook .PST file. If you would like to replicate messages older than 90 days, you may change the replication settings after the first DAMO initialization. Following these steps to change your default replication settings:

1. From the DAMO menu bar, select Tools > Options, then select the Domino Preferences tab.

2. From the Domino Preferences tab, select the Replication button to display the Replication Settings dialogue.


3. In the field next to If the server file exceeds the threshold above, do not replicate messages older (in days) than, set a value up to 365 days. If you would like to replicate older documents, you may add the following parameter to the notes.ini file in the Domino for Outlook directory, where “xxxx” can be any value:

<user>_<server>_PURGE=xxxx

For example:

testuser_testserver_PURGE=500

Troubleshooting tips for DAMO 6.5.5The DAMO 6.5.5 release includes additional options for capturing debugging information, as well as workarounds for inconsistencies between native Outlook and DAMO client functionality.

Domino server accessWhen a Domino server has a common name that is different from the host machine on which it is installed, the DAMO client may have difficulty connecting to that Domino server. The work around is to create a connection doc as described in section 5.2.1, entering the IP address of the machine hosting the Domino server in the Preferred Server field.

When the DAMO client attempts to present secondary directories as configured in Directory Assistance on your Domino server, DAMO may be unable to access a Domino server residing in another domain. To resolve this problem, you should create a server connection document as described in section 5.2.1. The success of this feature is also dependant on correct cross certification and mail server configuration.

Debugging parameters in the notes.ini fileTo capture debugging information for the DAMO client, a number of parameters outlined in table 0-1 may be added to the notes.ini file in the Domino for Outlook directory on the client machine. Typically if you encounter a problem when running the DAMO client, you should add the appropriate debugging parameters to your notes.ini file, then repeat the DAMO client action which caused the issue. The resulting log file will be useful for the IBM support team in troubleshooting DAMO problems, and they will assist you with transferring the log file to IBM support when reporting DAMO issues. Before adding specific debugging parameters to the notes.ini file, you must first add the following parameter to the


notes.ini file so that debugging information will be written to the file console.log in the Domino for Outlook/IBM_TECHNICAL_SUPPORT directory:

CONSOLE_LOG_ENABLED=1

Table D-1 DAMO debugging parameters

Table 0-2 analyzes the possible output messages from the address book debugging parameter (REPL_PST_DEBUG=8):

IBM Lotus Domino Access for Microsoft Outlook 6.5.5 Debugging parameters

Output written to IBM Lotus Domino Access for Microsoft Outlook log file

REPL_PST_DEBUG=1 Captures all available debugging to the console.log file

REPL_PST_DEBUG=2 Captures information about problems during the startup process

REPL_PST_DEBUG=4 Captures information regarding offline, failover and connectivity to the server

REPL_PST_DEBUG=8 Captures information about problems with address book availability, refreshing, and ordering of rooms and resources views. Please see table 0-2 for an analysis of the possible output from this parameter.

REPL_PST_DEBUG=512 Captures information about problems with Microsoft Outlook mail rules

REPL_PST_DEBUG=1024 Captures information regarding problems with removing items from the DAMO mail file. This does not deal with the actual movement of items to the archive folder, but rather with the deletion of removed items from the server mail file

REPL_PST_DEBUG=2048 Captures information regarding problems where unexpected data is in the "Allow Others Access to your Mail" dialog and the "Access to Other People's Mail" dialog

REPL_PST_DEBUG=4096 Captures information about problems with access control

REPL_PST_DEBUG=8192 Captures information about problems with messages going to or not going to the Other Messages folder

REPL_PST_DEBUG=16384 Captures information regarding problems with general folder movement


Table D-2 Output messages from address book debugging parameter

Output written to DAMO log file Explanation and recommended action

OFFLINE: We have a connection, so we will continue in AcquireAB

DAMO will attempt to open the address book from the server

AB: Attempting to get the address book itself: sem is xxxxxxx

Each address book has a separate semaphore value (xxxxxxx) here.Only one area of code can access an address book at a time and DAMO is attempting to gain permission to be that area.

AB: Address book locked The request has been granted and DAMO has access to that particular address book. If this line does not output to server console, a lockout issue has occurred that will cause a crash/hang.

AB: Current thread ID is: Captures information about problems with address book availability, refreshing, and ordering of rooms and resources views.

AB: Address book= CN=<server>/OU=<ou>/OU=ou/O=<org>!!I<address book>.nsf opened

There is sometimes a long delay between this and the line “AB: Current thread ID is:” writing to the server console. This delay occurs while DAMO is opening the address book and may be longer during initial replication.

AB: Handle for this address book has already been opened

When DAMO has a handle to the address book, subsequent attempts will cause this message to appear

AB: We are in ReleaseAB. Sem: xxxxxxx , Qty: 7, Idx: 0

DAMO is releasing the address book to allow other areas of code to access it. The "xxxxxxx " is the semaphore value

AB: Releasing the address book: sem is xxxxxxx .. If this line does not appear in the console.log file, something went wrong and DAMO did not release the semaphore locking the address book.

REPL_PST_DEBUG=8192 Captures information about problems with messages going to or not going to the Other Messages folder

Troubleshooting the address book output

"ERROR: ModifyRecipients( MODRECIP_ADD ) failed at SetRecipientList"

Examine the console.log file for the following line which supplies the error code): "ERROR: ModifyRecipients( MODRECIP_ADD ) failed at SetRecipientList with <Error Code>"

AB: We need to create a cross certificate Contact Support/Development if you see this message



Related publications

The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook.

IBM RedbooksFor information about ordering these publications, see “How to get IBM Redbooks” on page 248. Note that some of the documents referenced here might be available in softcopy only.

� Migrating from Microsoft Exchange 5.5 to Lotus Notes and Domino 6, SG24-6955

Online resourcesThese Web sites and URLs are also relevant as further information sources:

� Domino Access for Microsoft Outlook and the Domino Migration Tool

http://www-128.ibm.com/developerworks/lotus/library/damo/

� Trial: Domino Access for Outlook 6.5.4 Trial for Windows 2000 and NT English

http://www14.software.ibm.com/webapp/download/search.jsp?q=Domino+Access&rs=ESD-NTSDOMTRL

� Information about Domino Access for MS Outlook (DAMO) 6.5 or later

http://www-1.ibm.com/support/docview.wss?uid=swg21161211


http://www-128.ibm.com/developerworks/lotus/library/damo/

http://www14.software.ibm.com/webapp/download/search.jsp?q=Domino+Access&rs=ESD-NTSDOMTRL

http://www-1.ibm.com/support/docview.wss?uid=swg21161211

How to get IBM RedbooksYou can search for, view, or download Redbooks, Redpapers, Hints and Tips, draft publications, and Additional materials, as well as order hardcopy Redbooks or CD-ROMs, at this Web site:

ibm.com/redbooks

Help from IBMIBM Support and downloads

ibm.com/support

IBM Global Services

ibm.com/services




http://www.ibm.com/support/

http://www.ibm.com/support/

http://www.ibm.com/services/

http://www.ibm.com/services/

Index

AAccess Control List (ACL) 91, 161Access to others’mail 42Access to your mail and calendar 41Add-ins integrate with Outlook 106Address Book 42, 52, 93, 97, 111, 145, 147, 227, 231address conversion 163, 165, 222Administrator software requirements 121, 170ADT

configuring 122ADT DAMO Installation Process 127ADT tool 120

Overview 120Advantages of Using ADT's Create User ID or New UserAuto Client Setup Processes 133appropriate workflow 146–147Automated Deployment Tool (ADT) 19, 109, 120Automated Deployment Toolkit for Domino Access for Microsoft Outlook 120Automating the DAMO Client Setup 124Autprocessing 40

Bback ground 36, 66Benefits of running in a mixed environment 114Benefits of this approach 112Benefits of This Approach® 111Business Value Overview, Migration & DAMO 7busy time

add-in 106–107calendar information 11

CCalendar & Scheduling considerations for a mixed Notes/DAMO environment 61Calendar entries and Contact List functionality 207Calendar Scheduling 39Calender / Workflow and iCal format 65Calendering and Scheduling - how is it working with-in DAMO? 60Certificate Management 70

© Copyright IBM Corp. 2005. All rights reserved.

Certificate management 70, 83, 235Changing date information in Outlook 64Changing Default Meeting Information 62Client Installation

Directory 127Launch 129Screen 129

client-side configuration 83, 235cluster.ncf file 36, 66Clustering and Failover 65Coexistence 17, 19, 109, 113Common Migration Tool (CMT) 12Common platform for messaging and collaboration 16Configuring ADT 122Configuring ADT to Deploy DAMO 122Configuring the Installation Type 123Configuring the User Option 124Connecting to an Exchange server 149Contacts are fully integrated in the migrated Domino mail file 147Converting Exchange addresses to Notes Canonical format 163corresponding field 57, 144–145Creating a new MAPI profile 188Creating repeat sets 62Creating the Administrator profile in Outlook 154

DDAMO 6.5.4 18, 20, 22, 28, 112, 171, 225

client 69, 73Outlook 2003 client 225Performance improvements 28

DAMO architecture 89DAMO architecture in detail 90DAMO Client

Initializing 134DAMO client

code 134data storage 144deployment 120, 133initial setup 131installation process 123–124, 127, 134

249

installer 136preference 48previous releases 69setup 122, 124software 130Type document 130

DAMO Client Initializing 134DAMO Client Installation 127DAMO code 59, 101, 130, 219

entire installation 130DAMO Futures 85DAMO Installation 65, 68, 90, 99, 124, 126, 129, 169, 176, 178, 219

first time installation 176DAMO installation

MAPI profile creation process 135overall success 135process 192–193

DAMO installation code 90DAMO installation directory 127DAMO installation file 127DAMO Installation Logs and Setup File used during ADT installation 136DAMO installation process 192–193DAMO layer

element 95links Outlook 19, 89

DAMO ResultChanging date information in Outlook 64Changing Default Meeting Information 62Creating repeat sets 62

DAMO setupprogram 134

DAMO setup process 70DAMO user 12, 62, 65, 91, 111, 144, 210

user.nsf file 99DAMO-specific components of the Domino Migra-tion Tool 145data directory 68, 179

ID file 189Definition of a Mixed Environment 114Definition of Mobile/PDA/Smartphone deployment using DAMO 120Delegating/ Gaining access to a user’s mail file 40Delegation of individual meetings 64Deployment Approaches 109Deployment Considerations for ADT 133Deployment scenarios for Instant TeamMessenger 209

Detailed Functionality Comparison 74Differences in representation between Notes client and Microsoft Outlook client 115Directory Assistance 54Directory Assistance (DA) 14, 22, 54disk space 29, 90, 121, 170Domino Access 3, 21, 28, 109, 172, 177, 199

comprehensive overview 19for Microsoft Outlook 3–4, 21, 59, 109–110, 144–145, 169–170, 201–202Overview 4, 19

Domino Access for Microsoft Outlook (DAMO) 109–110, 169–170Domino Address Book 164–165Domino address book

Person Document 164Domino Administrator

client 111, 121, 158Client 6.5 29, 121, 170Id 161

Domino IDfile 183, 188password 180path 179

Domino mail file 91, 103, 114, 144, 147, 185–186local replica 195

Domino Migration Tool 11, 93, 143Domino Name System (DNS) 10Domino preferences - User Security 46Domino Preferences Tab 31Domino Server 4, 6, 28–29, 89, 110–111, 144–145, 170, 172, 222

Key Benefits 5, 9replica 97, 99Requirement 121version 18

Domino server 4–5, 23–24, 89, 110, 144–145, 158, 170, 172, 200, 210, 222

advantages 110equivalent is 1000 DAMO users 91existing Domino mail file 222following tasks 166migrated mail files 222migrated user 222new DAMO users 111nsf file 110Outlook client interact 89

Domino Server 6.5 .1 170Domino Server 6.5.1 172


Domino Server Requirements 121, 170Domino specific functionality added to Outlook through DAMO 30Domino Upgrade Service (DUS) 11, 93, 143Domino Upgrade Services

additional information 94optimal versions 170

Domino vs. Exchange - Functional Comparison of key features for enterprise messaging 55Domino Web Access (DWA) 5, 9, 55, 57DominoFor Outlook directory 32, 97, 99, 176, 182DUS

adding administrator to ACLs of mail files 161connecting to an Exchange server 149converting mail 161Exchange administrator mail profile 149mail files 161migration setup 148passwords 161service account administrator role 149starting 148

Ee-mail address 81, 233e-mail message 77, 79, 187, 205, 218, 229, 231e-mail system 17Exchange Server 12, 23–24, 110–111, 145, 149, 229Exchange server

Administrator mail profile 149Administrator profile 155mail file 161–162Migrating users 158

Exchange Site Permissions 152

FFeatures and Functionality 21First Time Replication 97

HHow and when is Replication invoked 59How the migration process works 144How to 'Domino enable' your Exchange data 147

IIBM Lotus Domino Access 74, 78, 120, 125, 226, 230

IBM Lotus Instant Messaging 199IBM Lotus Instant Messaging product 17, 199–200IBM Lotus Sametime 200, 204IBM Lotus Sametime server 210IBM Lotus solution 55, 209IBM Lotus technology 18ID file 32, 47, 121, 123, 179, 181

copy process 135location 125, 189

Installation directory (ID) 120, 122, 174Installation process 172Installation Type 123Installing DAMO 170Installing Exchange as a Foreign Directory Source 158instant message 205Instant messaging with Microsoft Outlook 200Instant TeamMessenger 14, 199

3.0 20, 2013.0 Overview 201install 203product 201software 210toolbar 202

Instant TeamMessenger 3.0 Overview 201Instant TeamMessenger for Microsoft Outlook 199Internet address 65, 126, 233internet certificate 47Introduction 3invitee 64, 146–147

KKey Advantages Of Using DAMO And Outlook With Lotus Domino 9Key design criteria for DAMO architecture 90Key differences between running the Notes and DAMO clients 114Key features of Instant TeamMessenger demon-strated 202Key Steps involved in the migration 111Key steps involved in the Proof of Concept / Pilot de-ployment 113

Llocal cache 37, 59, 96–97

unread document information 59Local Directory preferences 49log file 97, 133–134

Index 251

Logging Chats to the Journal 205Lotus customer 7, 91Lotus Note 36, 145, 148, 179, 192Lotus Notes data directory 179

MMail and Calendar Interface Features Comparison 23mail file 10, 40, 42, 89, 91, 110, 114, 144–145, 149, 161, 181–182, 222

replica ID 66Managing coexistence of Domino and Exchange 148MAPI profile

creation 125, 136, 181creation process 122, 135, 188

meeting request 79–80, 231–232Meeting Workspace 231

Microsoft Exchange 7, 93–94, 148–149Microsoft Outlook 3, 21, 23, 109, 115, 121, 170, 199–200

2000/2002 1706.5.4 28, 74, 78–79, 226, 230, 244Additional DAMO Features 19client 120, 123, 201contacts folder 201Domino Access 170, 172features 19IBM Lotus Domino 188IBM Lotus Domino Access 170, 194Instant TeamMessenger 200Journal 201Lotus Domino Access 194product 121Properties action 193short-cut icon 192use Domino Access 8

Microsoft Outlook 2003 28, 74, 78, 171, 183, 226, 230, 244Microsoft Outlook user 9, 120, 125Migrated Domino mail file

address fields 165valid Notes Canonical addresses 166

Migrated mail fileaddress conversion 167address fields 165

Migrating Exchange users and their data to Domino 149

Migrating users from the Exchange server to Domi-no 158Migration 110Migration and DAMO - the total solution 17Migration and Functionality Enhancements since the 6.0 release 145Migration Deployment 110Migration process 144, 147, 149

existing Domino user 163migration process 112, 122, 222–223Mixed Environment 17, 19, 109, 113

client coexistence 114Definition 114

Mobile / PDA / Smartphone 119Mobile/PDA/Smartphone deployment 120

Definition 120Multi Directory Install 68Multi Directory strategy 67–68Multi-directory installation functionality 68Multiple Client Strategy 17

NName and Address Book (NAB) 162, 166New DAMO users 111Notes client 5–6, 9, 29, 57, 97, 110, 114, 144–145, 158, 170, 177, 202, 210

personal address book 147Notes Decryption 67, 69Notes Remote Procedure Call

full advantage 10Notes Remote Procedure Call (NRPC) 10, 84, 236Notes URL 118–119NSF file 57, 89, 97, 110, 147

OOther DAMO Outlook Updates 50Out of Office 33Outlook 2000 4, 18, 28–29, 121, 200, 219Outlook 2003 18, 28–29, 97, 121, 170, 200, 217–218, 225–226

detailed functionality comparison 225Outlook client 3–4, 6, 21, 30, 89, 110, 144–145, 181–182, 199, 211, 217–218

Administrator profile 149binding or translation layer 94Corporate LDAP directory 211design parameters 62Domino replication 90


Domino-specific features 94existing structure 27folder structure 59IBM Lotus Instant Messaging 200IBM Lotus Sametime 200icon 154Instant TeamMessenger installs 204interact 89layer 92options menu 106replication process 110software 209typical scenario 209user 12, 17, 96, 210version 18

Outlook desktop 42Outlook message 57, 99Outlook Option

Domino Preferences 183Outlook option 30–31, 99, 106, 177, 183, 216

Change Password Domino Preference 32Domino Preferences tab 216

Outlook service providers 104Outlook user 7, 89–90, 109–110, 202, 211

Domino layer 92Outlook XP 18, 28, 69, 219Overview of DAMO architecture 92Overview of Domino Access for Microsoft Outlook 4Overview of functional differences between DAMO, Outlook & Notes 72Overview of New Features in DAMO 6.5.4 22Overview of the ADT tool 120Overview of typical DAMO deployment topologies 12

PPerformance improvements within DAMO 6.5.4 28PM 138–139Post installation Set-up 183Preferences 38Preferred Server 36Preparing for the migration process 147Preparing the Client Installation Directory 127Preparing the Outlook Client 127Prerequisites for performing the migration

149presence awareness 199Presence Awareness, Instant Messaging and Bud-

dy Lists 203Preserving Exchange data for use in DAMO or Notes 144Process of adding other user’s mail file to desktop 44Proof of Concept Deployment 112Property Mapping 58PST File 24, 32, 89–90, 114, 182, 186, 219

RRedbooks Web site 248

Contact us xiiRemote procedure call (RPC) 84, 236Repeat forever meetings 65Repeating Meetings are fully functional after migra-tion 146Replication - what is happening in DAMO? 56replication layer 57, 94–96

Outlook client 105polling interval 96

Replication of Outbound messages, encryption and compression 37Replication Overview 57Replication Process - What happens when a DAMO user sends mail? 101Replication Settings 35replicator 36, 57, 99, 101Replicator Thread 58Replicator Thread and Interface 58Research In Motion (RIM) 120Rich Text

e-mail message 187, 218feature 171Format 75, 186, 218, 227Formatting 117

robust messaging 3, 16

Ssame principle 8, 48same time 10, 21, 105, 110, 200Security 66Security Certificates 47Server Mail File Threshold 37server name 36, 125–126, 178, 181, 222setup file 126, 136Shared Contacts 43single sign on (SSO) 22, 32, 48, 67SMTP address 22, 65

Index 253

following issue 65Specifying an Exchange Administrator mail profile 149SSO 67Steps to convert addresses to Notes Canonical for-mat 166string WTD 163–164Structure of this book 19system prerequisite 121, 169–170System Prerequisites 121, 170System Requirements 29

TThe DAMO architecture in detail 93The DAMO Extension Manager 95The DAMO layer elements 95The DAMO mapping module 103The DAMO replication layer 96The Domino Migration Tool 143The Replication Layer processes 96ToDo 145, 147Total Cost 16Total Cost of Ownership (TCO) 16, 18Troubleshooting DAMO Installation Errors 134

Uunsolicited e-mail 10, 83, 235Unsupported Features 72user 10, 21, 110, 120, 200

significant and beneficial impact 18user Id 126–127, 133, 158User login settings 48User Option 62, 124

Configuration 125document 124

user.ID file 47–48users mail 36, 59, 185Using people finder to locate users 45Using the Domino Directories for name lookups 51

VVerifying the service account administrator role 149Version compatibility between DAMO, Outlook and Domino 18

WWeb Site 9, 201

What happens when a mail is received by the Dom-ino server? 99Why Outlook Support Is Important 16Windows Client Requirements 121, 170Windows NT

account 152, 154user account 154

Windows XP 29, 121, 170–171Wolcott 19, 109, 120Wolcott Systems ADT 120Workflow is enabled for Group ToDo's after migra-tion 147Workflow is enabled for single meetings after migra-tion 146

XX.509 and Notes Decryption 69


(0.5” spine)0.475”<

->0.875”

250 <->

459 pages

Domino Access for M

icrosoft Outlook: Deployment and M

igration Guide

®

SG24-6754-00 ISBN 0738490180

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICALINFORMATION BASED ONPRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.

For more information:ibm.com/redbooks

Domino Access for Microsoft Outlook: Deployment and Migration GuideOverview of features and functionality

Installation and configuration information

Migration from Exchange to Domino

This IBM Redbook discusses IBM Lotus Domino Access for Microsoft Outlook, the software solution that allows Outlook client users to easily access mail and calendar data that is stored on Lotus Domino servers.

If you want to improve the reliability and scalability of your messaging infrastructure and to add collaboration, upgrading from Microsoft Exchange to IBM Lotus Domino Access for Microsoft Outlook (DAMO) provides the solution. With DAMO, you have reliable, scalable, and secure Lotus Domino Messaging to Microsoft Outlook users without requiring users to change from the Outlook client — users simply work with mail, calendar, and task data on Lotus Domino instead of Microsoft Exchange. Familiar Microsoft Outlook features are supported, including rich text, folders and Directory Catalog. Lotus Domino Access for Microsoft Outlook also gives Microsoft Outlook users the additional benefits of Domino Messaging features, including full text search capability for their mailbox and native support for Internet standards (SMTP/MIME and HTML).

Back cover




Documents

Domino Access for Microsoft Outlook - IBM Redbooks · Domino Access for Microsoft Outlook ... 243 Debugging parameters in the notes.ini file ... marketing, or distributing