Professional Documents
Culture Documents
Robert Bry Pascal Bourgeois Lisa Chase Gregory Engels Robert Ryan Graeme Povall John Bergland
ibm.com/redbooks
International Technical Support Organization Migrating from Microsoft Exchange 2000/2003 to Lotus Notes and Domino 7 November 2006
SG24-7777-00
Note: Before using this information and the product it supports, read the information in Notices on page xiii.
First Edition (November 2006) This edition applies primarily to Domino 7, Release 7.x and Microsoft Exchange 2000 and Exchange 2003.
Copyright International Business Machines Corporation 2006. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv The team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Special acknowledgements for their contributions to this project. . . . . . . . . . xviii Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Part 1. Reasons to migrate from Exchange to Notes and Domino. . . . . . . . . . . . . . . . . . . . 1 Chapter 1. Benefits of migrating from Exchange 2000 / 2003 to Domino 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 The structure of this IBM Redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.1 Convergence between synchronous and asynchronous communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2.2 The trend toward service-oriented architecture. . . . . . . . . . . . . . . . . . 5 1.2.3 Decision points involved in the migration or upgrade path . . . . . . . . . 6 1.3 Benefits to migrating to IBM Lotus Domino . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.3.1 Comparison of capabilities between Exchange and IBM Lotus Domino . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.3.2 Advantages of Domino Server over Exchange Server . . . . . . . . . . . 12 Chapter 2. Overview of the Domino clients . . . . . . . . . . . . . . . . . . . . . . . . 27 2.1 Thinking outside the inbox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.2 Flexibility in features and offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 2.2.1 Overview of the Client Offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 2.2.2 Common PIM Portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.2.3 Potential coexistence scenario using the PIM Portlet approach . . . . 41 Part 2. Planning for migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Chapter 3. Migration project overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 3.1 The key steps in a coexistence or migration project . . . . . . . . . . . . . . . . . 48 3.2 The sponsor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 3.3 The project vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 3.4 The project team . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 3.5 The schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
iii
3.6 The scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.7 Documenting the business requirements . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.7.1 The basic requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 3.7.2 Further requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 3.8 The communication plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 3.9 Setting the expectations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 3.10 Documenting the current messaging environment . . . . . . . . . . . . . . . . . 59 3.10.1 Documenting the Microsoft Exchange environment . . . . . . . . . . . . 59 3.10.2 Documenting the hardware profile . . . . . . . . . . . . . . . . . . . . . . . . . 64 3.10.3 Documenting the network infrastructure . . . . . . . . . . . . . . . . . . . . . 64 3.10.4 Administration and support infrastructure . . . . . . . . . . . . . . . . . . . . 65 3.11 Developing the training plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 3.12 Risk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 3.13 Plan, design, and document the new environment . . . . . . . . . . . . . . . . . 69 3.13.1 Determining the characteristics of the servers needed . . . . . . . . . . 70 3.13.2 Client selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 3.14 Developing a coexistence and migration strategy. . . . . . . . . . . . . . . . . . 82 3.14.1 Levels of coexistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 3.14.2 Pros and cons of migrating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 3.14.3 What to migrate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 3.15 Deployment approaches: Proof of concept deployment . . . . . . . . . . . . . 86 3.15.1 Benefits of proof of concept deployment. . . . . . . . . . . . . . . . . . . . . 86 3.15.2 Key steps involved in the proof of concept deployment . . . . . . . . . 87 3.15.3 Overview of the migration process . . . . . . . . . . . . . . . . . . . . . . . . . 88 3.15.4 Migration tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 3.15.5 Acquiring the necessary information for migration . . . . . . . . . . . . . 90 3.16 Realigning the expectations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 3.17 Deploying the coexistence and migration strategy . . . . . . . . . . . . . . . . . 94 3.18 Final phase: Closure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Chapter 4. Overview of the migration procedures . . . . . . . . . . . . . . . . . . . 99 4.1 Migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 4.1.1 Step 1: Deploying and configuring Domino . . . . . . . . . . . . . . . . . . . 100 4.1.2 Step 2: Setting up a coexistence strategy and implementation plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 4.1.3 Step 3: Defining the migration plan . . . . . . . . . . . . . . . . . . . . . . . . . 101 4.1.4 Step 4: Beginning with a proof of concept or pilot deployment . . . . 102 4.1.5 Step 5: Migrating users at the server level . . . . . . . . . . . . . . . . . . . 102 4.1.6 Step 6: Deploying user data migration option . . . . . . . . . . . . . . . . . 106 4.1.7 Step 7: Backing up Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 4.1.8 Step 8: Cleaning up mail routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 4.1.9 Step 9: Cleaning up the infrastructure. . . . . . . . . . . . . . . . . . . . . . . 109 4.1.10 Step 10: Decommissioning Exchange . . . . . . . . . . . . . . . . . . . . . 109
iv
Part 3. Coexistence: Tools and strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 5.1 Overview of the Exchange Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . 114 5.1.1 Conceptual overview of how Exchange Connector works . . . . . . . 114 5.2 Preparing for the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 5.2.1 Supported environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 5.3 Installing the Exchange Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 5.3.1 Register a Lotus Notes User ID for Exchange Connector. . . . . . . . 118 5.3.2 Prevent Exchange Connector ID synchronization (optional). . . . . . 126 5.3.3 Create and set up Exchange Connector Mailboxes . . . . . . . . . . . . 127 5.3.4 Create Foreign Domain Document . . . . . . . . . . . . . . . . . . . . . . . . . 130 5.3.5 Create Exchange User Directory . . . . . . . . . . . . . . . . . . . . . . . . . . 132 5.3.6 Implement Directory Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 5.3.7 Install and set up Notes Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 5.3.8 Install Exchange Connector 2000 for Lotus Notes . . . . . . . . . . . . . 150 5.3.9 Configure Exchange Connector for Lotus Notes. . . . . . . . . . . . . . . 154 5.3.10 Enable Lotus Domino proxy addresses . . . . . . . . . . . . . . . . . . . . 165 5.4 Operating the Exchange Connector Services . . . . . . . . . . . . . . . . . . . . . 168 5.4.1 Starting Exchange Connector Services . . . . . . . . . . . . . . . . . . . . . 168 5.4.2 Running directory synchronization . . . . . . . . . . . . . . . . . . . . . . . . . 169 Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 6.1 Overview of the Exchange Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . 176 6.1.1 Improvements to Exchange Connector 2003 . . . . . . . . . . . . . . . . . 176 6.1.2 Conceptual overview of how Exchange Connector works . . . . . . . 176 6.2 Preparing for the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 6.2.1 Supported environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 6.2.2 General setup information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 6.3 Installing and setting up the Exchange Connector . . . . . . . . . . . . . . . . . 181 6.3.1 Register the Exchange Connector on the Lotus Domino Server . . 181 6.3.2 Prevent the Exchange Connector ID synchronization (optional). . . 187 6.3.3 Create the Domino mailboxes for routing mail to Exchange . . . . . . 188 6.3.4 Create the Exchange and Domino Directory. . . . . . . . . . . . . . . . . . 193 6.3.5 Implement Directory Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 6.3.6 Create a Foreign Domain document . . . . . . . . . . . . . . . . . . . . . . . . 199 6.3.7 Install the Notes Client on the Exchange Server. . . . . . . . . . . . . . . 200 6.3.8 Set up the Notes Client on the Exchange Server . . . . . . . . . . . . . . 202 6.3.9 Install Exchange Server 2003 Connector for Lotus Notes . . . . . . . 205 6.3.10 Configure the Exchange Connector for Lotus Notes. . . . . . . . . . . 209 6.3.11 Enable the proxy addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Contents
6.4 Operating and monitoring the Exchange Connector Services . . . . . . . . 225 6.4.1 Starting the Exchange Connector Services . . . . . . . . . . . . . . . . . . 225 6.4.2 Running directory synchronization . . . . . . . . . . . . . . . . . . . . . . . . . 226 6.4.3 Monitoring and troubleshooting the Connector . . . . . . . . . . . . . . . . 230 6.4.4 Stopping the Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 6.5 Tips and suggestions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Chapter 7. Using Microsoft Exchange Calendar Connector . . . . . . . . . . 241 7.1 Overview of the Calendar Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 7.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 7.2 Installing the Calendar Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 7.2.1 Installing Calendar Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 7.2.2 Adding a Local replica for the SCHEDULE+ FREE BUSY public folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 7.2.3 Configuring Calendar Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . 249 7.2.4 Start Calendar Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 7.2.5 Installing Calendar Connector Add-In for Lotus Domino . . . . . . . . . 255 7.2.6 Updating Foreign Domain Document . . . . . . . . . . . . . . . . . . . . . . . 256 7.2.7 Starting Connector Add-In (EXCALCON) . . . . . . . . . . . . . . . . . . . . 257 7.2.8 Looking up results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Chapter 8. Using the CMT for Exchange and Domino Coexistence . . . . 261 8.1 Overview of the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 8.1.1 Potential benefits of CMT for Coexistence . . . . . . . . . . . . . . . . . . . 263 8.2 Technical overview of the product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 8.3 Advantages of the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 8.4 Setup and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 8.5 Using the product step-by-step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Chapter 9. Using SMTP routing for coexistence . . . . . . . . . . . . . . . . . . . 273 9.1 SMTP scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 9.2 SMTP coexistence scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 9.3 Overview of the SMTP environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 9.3.1 Microsoft Exchange SMTP overview . . . . . . . . . . . . . . . . . . . . . . . 276 9.3.2 Lotus Domino 7 SMTP environment . . . . . . . . . . . . . . . . . . . . . . . . 276 9.4 Configuring Microsoft Exchange SMTP . . . . . . . . . . . . . . . . . . . . . . . . . 277 9.4.1 Pre-configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 9.4.2 Configuring the SMTP Connector (optional) . . . . . . . . . . . . . . . . . . 278 9.4.3 Configuring SMTP Virtual Server . . . . . . . . . . . . . . . . . . . . . . . . . . 288 9.5 Configuring Lotus Domino 7 for SMTP message transmission . . . . . . . . 292 9.5.1 Modify or create the Global Domain document . . . . . . . . . . . . . . . . 292 9.5.2 Enabling Domino routing and the SMTP listener task. . . . . . . . . . . 299 9.6 Sending mail between Exchange and Domino through SMTP . . . . . . . . 306
vi
Chapter 10. Coexistence test results: What to expect. . . . . . . . . . . . . . . 315 10.1 Methodology that we used for testing . . . . . . . . . . . . . . . . . . . . . . . . . . 316 10.2 Executive overview of results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 10.2.1 Highlights of the results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 10.3 Coexistence with Microsoft Exchange Connector . . . . . . . . . . . . . . . . . 322 10.3.1 Directory lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 10.3.2 Messaging from Notes to Exchange . . . . . . . . . . . . . . . . . . . . . . . 324 10.3.3 Messaging from Exchange to Notes . . . . . . . . . . . . . . . . . . . . . . . 325 10.4 CMT for Exchange and Domino Coexistence . . . . . . . . . . . . . . . . . . . . 326 10.4.1 Messaging from Notes to Exchange . . . . . . . . . . . . . . . . . . . . . . . 326 10.4.2 Messaging from Exchange to Notes . . . . . . . . . . . . . . . . . . . . . . . 329 10.5 SMTP routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 10.5.1 Directory lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 10.5.2 Messaging from Notes to Exchange . . . . . . . . . . . . . . . . . . . . . . . 330 Part 4. Migration process: Tools and procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Chapter 11. Server-level migration using Domino Upgrade Services . . 339 11.1 Overview of DUS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 11.2 Preparing for the migration process . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 11.3 Migrating Exchange users and their data to Domino . . . . . . . . . . . . . . 341 11.3.1 Prerequisites for performing the migration . . . . . . . . . . . . . . . . . . 341 11.3.2 Creating the Administrator profile in Outlook . . . . . . . . . . . . . . . . 342 11.3.3 Installing Exchange as a Foreign Directory Source . . . . . . . . . . . 348 11.3.4 Migrating users from the Exchange server to Domino . . . . . . . . . 348 11.3.5 Converting Exchange addresses to Notes Canonical format . . . . 359 11.3.6 Tip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Chapter 12. Migrating local Outlook data using Notes Upgrade Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 12.1 Data migration using Notes Upgrade Services . . . . . . . . . . . . . . . . . . . 366 12.1.1 Why local data migration is important . . . . . . . . . . . . . . . . . . . . . . 366 12.1.2 An overview of Notes Upgrade Services. . . . . . . . . . . . . . . . . . . . 366 12.2 Preparing the workstation for local migration . . . . . . . . . . . . . . . . . . . . 367 12.2.1 Installing the Exchange Migration component for Lotus Notes . . . 368 12.2.2 Creating a Microsoft Outlook Profile . . . . . . . . . . . . . . . . . . . . . . . 368 12.3 Automating Notes Upgrade Services . . . . . . . . . . . . . . . . . . . . . . . . . . 375 12.3.1 Automating a message to initiate Notes Upgrade Services . . . . . 376 12.3.2 Initiating Notes Upgrade Services from an automated message . 383 12.4 Manual migration using Notes Upgrade Services . . . . . . . . . . . . . . . . . 385 12.4.1 Starting the migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 12.5 Troubleshooting Notes Upgrade Services. . . . . . . . . . . . . . . . . . . . . . . 394 Chapter 13. Server Level migration process using Binary Tree Common
Contents
vii
Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 13.1 What is Common Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 13.2 Installing CMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 13.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 13.2.2 Setting up the licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 13.2.3 Migrating with CMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 13.3 Setting up CMT and migrating users. . . . . . . . . . . . . . . . . . . . . . . . . . . 402 13.3.1 Configuring CMT settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 13.3.2 Adding users from foreign directory source . . . . . . . . . . . . . . . . . 408 13.3.3 Selecting users for migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 13.3.4 Migrating server data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 13.4 Troubleshooting the migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 Chapter 14. Local data migration using the Binary Tree Common Migration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 14.1 User migration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 14.2 Configuring CMT for Outlook migration . . . . . . . . . . . . . . . . . . . . . . . . . 438 14.2.1 Configuring CMT and importing users for migration . . . . . . . . . . . 439 14.3 Migrating local user data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 14.3.1 Using the send e-mail button configuration option . . . . . . . . . . . . 446 14.3.2 Using the automated trigger migration option . . . . . . . . . . . . . . . . 449 14.4 Adding users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 14.5 Sending the migration e-mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 Chapter 15. Migration results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463 15.1 Mail migration results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 15.1.1 Inbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 15.1.2 Mail message migration results. . . . . . . . . . . . . . . . . . . . . . . . . . . 466 15.2 Calendar migration results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481 15.3 Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486 15.4 Tasks and To Do entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 Part 5. Directory considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 Chapter 16. Directory coexistence using LDAP . . . . . . . . . . . . . . . . . . . . 495 16.1 LDAP directory configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496 16.1.1 Common directory requirements for coexistence . . . . . . . . . . . . . 496 16.1.2 LDAP architecture overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 16.1.3 Interaction between the LDAP enabled server and client . . . . . . . 498 16.2 LDAP implementation in Domino and Exchange . . . . . . . . . . . . . . . . . 499 16.2.1 Enabling LDAP during Domino server installation . . . . . . . . . . . . 499 16.3 Enabling Directory Assistance for LDAP authentication . . . . . . . . . . . . 503 16.3.1 Entering the directory assistance database file name to a Server document manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
viii
16.4 Enabling client LDAP lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 16.4.1 Creating LDAP address book in Outlook . . . . . . . . . . . . . . . . . . . 505 16.4.2 Finding an address in the Domino directory from Outlook . . . . . . 512 16.4.3 Creating and LDAP account in Notes . . . . . . . . . . . . . . . . . . . . . . 515 Chapter 17. Integrating Active Directory. . . . . . . . . . . . . . . . . . . . . . . . . . 519 17.1 Understanding the role of Active Directory . . . . . . . . . . . . . . . . . . . . . . 520 17.1.1 Active directory remains the corporate directory . . . . . . . . . . . . . . 520 17.1.2 User and data migration coexistence . . . . . . . . . . . . . . . . . . . . . . 522 17.1.3 User migration coexistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523 17.1.4 Non-migration coexistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 17.1.5 Using Lotus ADSync for long-term user management . . . . . . . . . 524 17.2 Installing Lotus ADSync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 17.2.1 Synchronizing with the Domino Directory . . . . . . . . . . . . . . . . . . . 526 17.2.2 Registering existing users in Domino from Active Directory . . . . . 532 17.2.3 Managing users with Active Directory . . . . . . . . . . . . . . . . . . . . . . 535 17.2.4 Registering new Domino users in Active Directory . . . . . . . . . . . . 545 17.2.5 Managing users with Active Directory . . . . . . . . . . . . . . . . . . . . . . 551 Part 6. Public folders and shared data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563 Chapter 18. Public folders for Domino administrators . . . . . . . . . . . . . . 565 18.1 Public Folder overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 18.1.1 Public Folder structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 18.1.2 Public Folder Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 18.1.3 Required permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567 18.2 Creating Public Folders and administering them. . . . . . . . . . . . . . . . . . 567 18.2.1 Tools used to create public folders . . . . . . . . . . . . . . . . . . . . . . . . 568 18.2.2 Required permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 18.2.3 Creating a Public Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 18.3 Considerations for Public Folder migration . . . . . . . . . . . . . . . . . . . . . . 580 Chapter 19. Public Folder migration and coexistence using ecKnowledge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583 19.1 Pre-installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 19.1.1 Exchange considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584 19.1.2 Domino considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585 19.1.3 Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585 19.1.4 Application design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586 19.2 Setting up ecKnowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587 19.2.1 Entering the product keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593 19.2.2 Post-installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594 19.2.3 Creating the connection between Domino and Exchange . . . . . . 595 19.2.4 Running the coexistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Contents
ix
19.3 Working with a blank database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613 19.3.1 The Exchange Public Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614 19.3.2 Migration results using a blank database . . . . . . . . . . . . . . . . . . . 616 19.3.3 Using Domino Designer to modify the view . . . . . . . . . . . . . . . . . 617 Chapter 20. Public Folder migration using CMT . . . . . . . . . . . . . . . . . . . 625 20.1 Binary Trees CMT for Exchange Public Folders . . . . . . . . . . . . . . . . . 626 20.2 Setting up CMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626 20.2.1 Configuring the import of Public Folders tool . . . . . . . . . . . . . . . . 627 20.3 Importing Public Folder names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632 20.4 Name resolution, security, and migrated permissions. . . . . . . . . . . . . . 634 20.5 Migrating Public Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636 Chapter 21. Migrating shared and public data manually . . . . . . . . . . . . . 651 21.1 Pre-requisites for manual migration . . . . . . . . . . . . . . . . . . . . . . . . . . . 652 21.2 Using DUS to migrate Public Folders . . . . . . . . . . . . . . . . . . . . . . . . . . 652 21.3 Using a spreadsheet as an intermediary. . . . . . . . . . . . . . . . . . . . . . . . 653 21.4 Migrating the contacts Public Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . 660 21.5 Migrating shared calendars Public Folder . . . . . . . . . . . . . . . . . . . . . . . 665 21.6 Archiving or sending Public Folder data elsewhere . . . . . . . . . . . . . . . 665 Chapter 22. Migrating shared data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669 22.1 Migrating shared mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670 22.2 Sharing data in a mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670 22.2.1 Creating and configuring a shared mailbox. . . . . . . . . . . . . . . . . . 670 22.2.2 Connecting to another users shared folder . . . . . . . . . . . . . . . . . 674 22.3 Migrating shared data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675 22.3.1 Using CMT to migrate shared data . . . . . . . . . . . . . . . . . . . . . . . . 675 22.3.2 Using DUS to migrate shared data . . . . . . . . . . . . . . . . . . . . . . . . 676 Chapter 23. Migration project wrap up: Removing the Microsoft Exchange environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693 23.1 Removing Exchange servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694 23.1.1 Reasons to remove Exchange carefully . . . . . . . . . . . . . . . . . . . . 694 23.1.2 Reasons for leaving things alone . . . . . . . . . . . . . . . . . . . . . . . . . 694 23.1.3 Additional resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694 23.1.4 Before you begin removing Exchange . . . . . . . . . . . . . . . . . . . . . 695 23.2 Single server, single site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696 23.2.1 Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696 23.2.2 Removing the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700 23.3 Removing a server from a multi-server site. . . . . . . . . . . . . . . . . . . . . . 704 Appendix A. Other migration tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707 A.1 CoexLinks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
A.1.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708 A.1.2 Value add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709 A.1.3 Using this tool in a migration and coexistence project . . . . . . . . . . 709 A.1.4 Technical background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710 A.1.5 Installing CoexLinks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711 A.1.6 Configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712 A.2 ICODEX Client Genie . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713 A.2.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713 A.2.2 Value add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714 A.2.3 Using this tool in a migration and coexistence project . . . . . . . . . . 714 A.2.4 Technical background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716 A.2.5 Installing Client Genie. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718 A.2.6 Configuring Client Genie. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720 A.3 Transend Migrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721 A.3.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721 A.3.2 Value Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721 A.3.3 Using this tool in migration and coexistence project. . . . . . . . . . . . 723 A.3.4 Technical background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724 A.3.5 Installing Transend Migrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730 A.3.6 Configuring Transend Migrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731 A.4 GMI Infopath_2_Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731 A.4.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731 A.4.2 Value Add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731 A.4.3 Using this tool in a migration and coexistence project . . . . . . . . . . 732 A.4.4 Technical background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738 A.4.5 Installing Microsoft InfoPath_2_Notes . . . . . . . . . . . . . . . . . . . . . . 741 A.4.6 Configuring Microsoft InfoPath_2_Notes . . . . . . . . . . . . . . . . . . . . 741 A.5 Tools that might be helpful for a UNIX migration . . . . . . . . . . . . . . . . . . 742 A.6 Nash!Com Domino on UNIX/Linux Start script . . . . . . . . . . . . . . . . . . . . 742 A.6.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742 A.6.2 Value add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742 A.6.3 Using this tool in a migration and coexistence project . . . . . . . . . . 743 A.6.4 Technical background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743 A.6.5 Installing Nash!Com Domino on UNIX/Linux Start script . . . . . . . . 745 A.6.6 Configuring Nash!Com Domino on UNIX/Linux Start script . . . . . . 745 A.7 Nash!Com Trace & Lowercase Conversion Extension . . . . . . . . . . . . . . 746 A.7.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746 A.7.2 Value add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747 A.7.3 Using this tool in a migration and coexistence project . . . . . . . . . . 747 A.7.4 Technical background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747 A.7.5 Installing Nash!Com Trace & Lowercase Conversion Extension . . 748 A.7.6 Configuring Nash!Com Trace & Lowercase Conversion Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Contents
xi
Appendix B. Migration procedures: an overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751 B.1 Overview of the procedure for migrating users . . . . . . . . . . . . . . . . . . . . 752 B.2 Considerations for migrating the mail account using CMT . . . . . . . . . . . 761 B.3 Considerations for migrating the mail account using DUS . . . . . . . . . . . 762 Appendix C. Integrating Domino with Sharepoint Portal . . . . . . . . . . . . 765 C.1 Domino Web access in Sharepoint Portal . . . . . . . . . . . . . . . . . . . . . . . 766 Appendix D. Tips for performing a successful migration . . . . . . . . . . . . 795 D.1 List of issues and solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796 Appendix E. Exchange Connector installation checklist . . . . . . . . . . . . 799 E.1 General setup information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800 Appendix F. Installing Domino . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801 F.1 Installing Domino. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802 F.2 Installing Domino Administrator and Lotus Notes Client . . . . . . . . . . . . . 814 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819 Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819 How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820 Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
xii
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 illustrate 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.
xiii
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: Redbooks (logo) developerWorks ibm.com iNotes i5/OS z/OS AIX Domino Designer Domino DB2 IBM IMS Lotus Notes Lotus Organizer Lotus Notes Redbooks Sametime System i System p System z Tivoli WebSphere Workplace Workplace Managed Client
The following terms are trademarks of other companies: SAP, and SAP logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries. ITIL, is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. Java, JavaScript, J2EE, Solaris, Sun, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Access, Active Directory, Excel, Hotmail, InfoPath, Internet Explorer, Microsoft, MSN, Outlook, SharePoint, Visio, Visual Basic, Windows Server System, Windows Server, Windows, Win32, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, 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. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.
xiv
Preface
Messaging and collaboration tools are critical components in todays enterprise. The choice of tools impacts your organizations ability to process and to share information. The underlying messaging and collaboration infrastructure is the foundation that determines your ability to deliver a core set of communication and collaboration services. While messaging and collaboration capabilities within an organization prove to be mission critical, the requirements of users and the choice of tools that are available continues to evolve. For example, organizations have increased security needs, require the flexibility of various client types, and are based upon increasingly complex infrastructures. This IBM Redbook presents the strategic and market benefits of IBM Lotus Domino over Microsoft Exchange and provides an overview of the tools and strategies that are available to help you with that migration. It also includes instructions for how to perform the migration process. The beginning of the book explores common business drivers, considerations, benefits, and scenarios that organizations find themselves in when faced with a migration decision, such as migrating from Exchange to Lotus Domino. The remainder of the book discusses the architectural planning and technical activities associated with that migration decision. For business or IT managers, the strategic portion of this book provides essential information about the what and why of migration. The remainder of the book focuses on the how of migration and the how of coexistence strategies. This IBM Redbook gives you the confidence that your organization can achieve the results you expectand deservefrom the migration process from Exchange to Domino.
xv
xvi
Gregory Engels is the founder and CEO of Kompurity, an IBM Business Partner in Frankfurt, Germany (http://www.kompurity.com). He has more then 13 years of experience in solution design and architecture, as well as in system consulting and integration, with a main focus on Lotus Notes infrastructure and migration projects since 1998. He has been involved in migration projects for over 150 000 users. His areas of expertise include operating complex messaging infrastructures, Public Key Infrastructure, and migration. Gregory is IBM Advanced Certified System Administrator and Application Developer for Lotus Notes since R5 and is fluent in German, English, and Russian. Graeme Povall is a Senior IT Specialist and Team Leader of the UK Microsoft SWAT team. He provides pre-sales consulting on Lotus competitive products (WebSphere Portal, and Messaging and Collaboration) for customers within the UK and South Africa. Graeme has 20 years of experience working with different messaging systems. He joined IBM in 1993 and, during his tenure, he has held various positions within the UK and EMEA, providing support, training, and leadership in messaging, coexistence, and migration. Graeme was a co-author of Migrating from Microsoft Exchange 5.5 to Lotus Notes and Domino 6, SG24-6955. Robert Ryan is a Staff Software Engineer for Lotus Software in North America. Rob worked as a Corporate Training in the Banking Industry before joining IBM in 2000. He holds a B.S. in Business Administration from Saint Michael's College and a Web Design Certificate from Boston University. His primary area of expertise include Mail Routing Protocols, System Administration, and Migration. He is an IBM Certified Domino System Administrator and Application Developer. Rob has spoken at multiple Worldwide TechTalks and Support Seminars, covering such topics as Troubleshooting Mail Routing, Mail Journaling, and Mail Rules. John Bergland is a project leader at the ITSO, Cambridge Center. He manages projects that produce IBM Redbooks about IBM and 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.
Preface
xvii
xviii
Comments welcome
Your 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: redbook@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400
Preface
xix
xx
Part 1
Part
Chapter 1.
1.2 Introduction
Messaging and collaboration are critical components in todays enterprise. The choice of tools impacts your organizations ability to process and to share information. The underlying messaging and collaboration infrastructure is the foundation that determines your ability to deliver a core set of communication and collaboration services. These services enable enterprises to provide communications that are secure, dependable, and flexiblecommunications that ultimately enhance the flow of information, improve productivity, and maximize cross-organizational responsiveness. While messaging and collaboration capabilities within an organization prove to be mission critical, the requirements of users and the choice of tools that are available continue to evolve. For example, organizations have increased security needs, require the flexibility of various client types, and are based upon increasingly complex infrastructures.
message. This integration represents the blending of synchronous and asynchronous communications. Terminology clarification:
Todays organizations look toward adopting solutions that can: Deliver leading capabilities to enhance productivity. Support wide range operating systems and clients. Provide extensibility into the infrastructure that can eventually deliver composite applications. Composite applications enable the integration of information from multiple applications, providing users with the content that they need based on their role and task. Composite applications are assembled quickly from reusable components and allow organizations to adapt software to changing requirements efficiently by delivering contextual collaboration and by contributing toward a lower total cost of ownership. Most vendors in the industry are helping to drive standards by building their products to support heterogeneous environments and to embrace this pattern of collaboration evolution. Alternatively, other vendors appear to be threatened by open standards and are choosing instead to perpetuate their proprietary, pre-internet models and approaches to collaboration. Rather than delivering capabilities which can be delivered with customer choice and flexibility, these vendors are instead offering solutions which mandate a single operating system. Additionally, they dictate client and desktop deployments, and other particular infrastructure like Directories. This latter, proprietary approach can ultimately impede the potential of collaboration and limit its effectiveness by restricting the collaborative tool offerings. This can prompt many organizations to seek alternative more flexible solutions that more closely align with their business objectives.
In order to use the updated messaging capabilities for Exchange 2007, both a modified infrastructure and a significant amount of effort for completing each of these tasks is required.
STOP
& Migrate
STOP
& Migrate
STOP
& Migrate
* * *
Exchange 5.5
Exchange 2000
Exchange 2003
Exchange 2007
X
Windows Server System 2007 Active Directory Updates Required 64-bit hardware & software No support for 32-bit add solutions
Windows NT Server
Microsofts rigid infrastructure migration requirement for Exchangeand lack of Exchange tools to support in-place upgrades to move from one release of Exchange to the nextcontrasts the capabilities of IBM Lotus Domino. IBM Lotus Domino conducts in-place upgrades that use the existing infrastructure, hardware, directories, skills, and tools that are built into the product. Accordingly, you can migrate easily from Microsoft Exchange to Lotus Domino.
Benefits to migrating include: Migrating to IBM Lotus Domino could be easier than migrating to Exchange 2007 Migrating to Domino might, in many cases, be easier than migrating to a new hardware and software infrastructure in order to merely use the new messaging capabilities in Exchange 2007. A move to IBM Lotus Domino allows you to benefit from the industry's leading messaging and collaboration capabilities on the platforms of your choice, including multiple variations of Windows and Linux servers. Furthermore, a migration can be accomplished with little architectural change and with support for your current directory and client deployed. Finally, this choice contributes toward reducing your total cost of ownership. Migration tools included The built-in migration tools, Domino Upgrade Services (Domino Migration Tool), helps to reduce the cost of migration by preventing the need to purchase additional third-party tools. Domino Upgrade Services (Domino Migration Tool) can be used to create new Domino mail accounts and migrate data from Exchange to Domino, thereby eliminating the need to re-create entries manually in the Domino directory or move data manually. For organizations who seek additional tools to assist with the migration, there is also a well established set of IBM Business Partner skills and tools available to assist with various migration scenarios. Several of these tools are covered in this book. Support of Microsoft clients IBM Lotus Domino offers flexibility, providing an option in which Domino exists as the back-end server, while allowing end users the option to use existing Microsoft based clients such as Outlook. Domino can support a Microsoft client community. This client support ranges from a Microsoft Internet Explorer browser based access to Domino mail, calendaring, and applications, Notes clients integrated with Microsoft Office, Office SmartTag support, and even the support of Microsoft Outlook as the primary client interface to Domino. You can find more information about client options when deploying Domino in Chapter 2, Overview of the Domino clients on page 27. Support for more than one operating system Domino runs on seven operating systems and 12 different variations of those operating systems. This enables organizations to exploit and use a diverse set of existing architecture assets and ultimately contributes toward lowering total cost of administration.
It is almost inappropriate to compare the two offerings. It is more appropriate to compare a subset, a fraction of Domino capabilitiesDomino Messaging Server to Microsoft Exchange, as shown in Figure 1-2 on page 11.
10
Microsoft Exchange
e-maill calendaring & scheduling
Windows 2000
Windows 2003
Linux
AIX
i5
Solaris
Windows 2000
Windows 2003
Linux
AIX
i5
Solaris
s/390
Figure 1-2 Comparison of offerings and functionality between Exchange and Domino
What is common between Domino and Exchange is that they do both provide e-mail, calendaring, and scheduling and associated rooms and resource reservations and so forth. However, after that, differences begin to be more and more apparent. For example, Domino has built-in collaborative capabilities to: Share information, documents Conduct workflows Embed real-time collaboration for presence awareness, and interactive instant messaging
11
Domino provides the following additional template based and services oriented functionality: A series of templates for the rapid creation of customized applications Web services support to host or consume Web services Built-in administration tools to monitor trends performance Policies Domino also provides an embedded Web application server so that e-mail, calendaring, and applications be accessed through Web browsers. It includes: Directory services for authentication, key, and credential management A rich data store for text, attachments, and audio A replication engine to synchronize data between servers and clients, including real-time access to backend enterprise systems
12
13
Users have the ability to see who is on line and initiate a live instant messaging session from within the context of specific mail messages, documents This results in more efficient decision-making directly in the context of the collaboration experiencewithout leaving your Lotus Notes client or launching a separate client interface. Alternatively, similar approaches with Exchange infrastructure require additional Microsoft Office System server middleware deployed including, additional hardware, additional software services such as Office Live Communications Server, SQL Server, SQL CALs, and desktop software such as Messenger or Communicator client.
Directory flexibility
This choice and flexibility model, or sometimes referred to as leverage without dependence, includes being able to use an organization's enterprise directory of choice for user credentials, authentication referrals, and key management. For example, most Microsoft environments have Microsoft Active Directory deployed to some degree and choose to administer their Domino accounts and account management from that preferred interface. Domino supports this model, and allows for Microsoft administrators to manage, create accounts, set up Windows Single Sign On (SSO), propagate account changes from Active Directory to Lotus Domino simplifying administration.
OS Flexibility
The Domino server runs on seven operating systems, and multiple different variations of those operating systems, including Windows 2000, Windows 2003, RedHat Linux, SuSE Linux, AIX, Solaris 9, Solaris 9, i5. This flexibility of supporting multiple client types, on multiple client operating systems, provides our customers a very adaptable and open deployment model. It allows
14
companies to use existing assets, skills and contributes toward lowering total cost of ownership.
Hardware flexibility
Microsoft's latest release of Exchange, Exchange 2007 requires both a 64-bit software and hardware architecture in order to address key memory handling constraints which impact scalability of Exchange. As mentioned earlier, this approach to require a specific server operating system, as well as specific hardware in order to run the latest release of messaging server is fundamentally different than that of the approach IBM takes with IBM Lotus Domino. Lotus Domino server is well known for supporting a wide range of hardware and operating systems. In fact, Domino (7.0.1) has already supported 64-bit platforms such as: IBM i5/OS IBM AIX IBM z/OS Sun Solaris 9 and10 Select Linux options on IBM System z, such as Red Hat Enterprise Linux 4.0 (update 3) on Intel processor-based systems and Novell SUSE Enterprise Linux 9. Updates in subsequent Domino 7 quarterly maintenance releases (7.0.2) added more choice and flexibility for the Windows environments to support 64-bit operating system choices on Intel processor-based systems: Windows 2003 Server Standard x64 Edition Microsoft Windows 2003 Server Enterprise x64 Edition Novell SUSE Enterprise Linux 10 While Microsoft not only requires 64 bit software and hardware for Exchange 2007 in an attempt to address memory and performance constraints of Exchange, IBM expands it's choice and flexibility to support a broader range of architecture.
15
This proven replication technology has been one of the key original differentiators of Lotus Notes since its inception, allowing for the bi-directional exchange and synchronization of data, design, and security levels between clients and servers. Replication means that mobile users have access to mission critical data, collaborative applications and enterprise data locally. It is encrypted, and can be seamlessly replicated through a background schedule so users can be productive and efficient even when disconnected from the network. Replication capabilities can be delivered to browser users with Domino Off-Line Services (DOLS), to work with Domino Web application in a disconnected state with similar productivity results. Replication for system administrators means an effective way to propagate administration changes, such as directory updates, user accounts, global policies, and collect statistics across the centralized or decentralized enterprise. Replication for designers and developers of applications means change management, rapidly deploying new applications to new users, design changes to applications. Finally, some of the IBM / Lotus competitors claim to have replication or to at least deliver a subset of this replication approach with document level synchronization. Keep in mind though, that none of these other vendors have a unified way to effectively disseminate: new data, updates at the document level or a way to disseminate up to the minute field level changes, security changes design changes.
16
Domino Designer 7 includes numerous features and functions to help build applications and increase developer productivity, including: Rapid development templates Object models and components that integrate with other systems by hosting industry standards-based Web services. These include: Web Service Definition Language (WSDL) as the starting point to build a new Web service within a Domino database. Domino's support for Extensible Mark-up Language (XML) for data sharing of robust standards based collaborative solutions with Domino. Note: For additional information about application development, see Lotus Domino 7 Application Development, REDP-4102, which is available at: http://www.redbooks.ibm.com/abstracts/redp4102.html
17
organizations can support multiple releases of the Notes client - all seamless to the user community. Finally, Domino supports in-place upgrades, the ability to install and apply the new release of the Domino server on the existing hardware, and on top previous release of the software. This allows for your organization to upgrade without costly, disruptive migration between releases. Competitive offerings offer little support for this flexibility and instead require more complex migration approaches moving from one infrastructure to another in order to potentially gain from new feature sets. In the case of Microsoft Exchange, the concept of an in place upgrade, namely applying a new release on top of a current installation, is not a supported model when moving from Microsoft Exchange 5.5 to Exchange 2003. Once again - as illustrated in , The Microsoft Exchange Challenge on page 7, in place upgrades are still not supported when moving from Exchange 2000/2003 to Exchange 2007. The backward compatibility, and interoperability equates to: Investment protection Return on investment maximization Mitigation of risk Straightforward, low cost upgrades
18
Note: See Chapter 2, Overview of the Domino clients on page 27 for a more in-depth review of client options.
19
metric used by server hardware vendors, show significantly enhanced scalability and performance. IBM Lotus Domino 7 uses up to 25% less CPU resources than its previous Domino 6.5 server release, and can support up to 80% more Lotus Notes users or up to 50% more Lotus Domino Web Access users for browser access on the same server hardware. Similar benefits can be gained when you move from Microsoft Exchange to Lotus Domino. You can use your existing hardware, support and exploit existing server operating systems and deliver a more scalable, reliable environment.
20
Note: For additional information about obtaining high availability and understanding performance tuning in Domino 7, see: Domino 7 Performance Tuning Best Practices to Get the Most Out of Your Domino Infrastructure, REDP-4182, which is available at: http://www.redbooks.ibm.com/abstracts/redp4182.html Domino 7 Server Consolidation: Best Practices to Get the Most Out of Your Domino Infrastructure, REDP-4181, which is available at: http://www.redbooks.ibm.com/abstracts/redp4181.html
Enterprise extensibility through portlets, built in Web services and Java support
Lotus Notes/Domino collaborative application access can easily be extended and integrated with other enterprise technologies. Integration can be achieved through programmatic, and non-programmatic means, including: Web Services Java Portlets Domino provides enterprise extensibility by embracing open standards. Lotus Domino provides a native Web services hosting service based on SOAP. This enables organizations to use Web services to integrate your applications with J2EE and Microsoft .NET environments using existing skills. Portlets can be used for integrating or extending custom built Domino applications into a an organizations enterprise portal. This can be accomplished with no programming, or without re-writing the Domino application in a WebSphere Portal Server environment. Note: For additional information about how to integrate Domino applications with enterprise Portals, see Portalizing Domino Applications: Integration with Portal 5.02 and Lotus Workplace 2.0.1, SG24-6466, which is available at: http://www.redbooks.ibm.com/abstracts/sg246466.html This ability to extend and integrate Domino with other enterprise applications, allows organizations to derive rapid value from Domino. Companies gain from the collaborative nature of Domino applications and avoid costly disruptive migration approaches associated to other platforms.
21
IT Governance requirements
Recent developments in the area of IT Governance have arisen that might impact the decision to migrate from one messaging platform to another. Domino not only meets stringent security requirements, but stands out as the leader in terms of high availability, accessibility, and ability to archive information. Domino 7 has the ability to meet or exceed IT governance requirements. Legislation such as Sarbanes/Oxley, Graham-Leach Bliley, Patriot Act, and HIPPA as well as civil lawsuits are impacting messaging systems in that legal discovery is often dictating messaging architecture. Increased server consolidation is one area that is a direct result of the desire to better control the information life cycle of e-mail. IT Governance in the form of CoBIT 4.0, ISO 17799, ITIL and ValIT are requiring vendors to demonstrate that their products can be managed within those frameworks. Confidentiality, availability and integrity of data are seen as essentials feature sets in any deployment of new software. Applications that due not meet these criteria are unlikely to be accepted not because of their technical capabilities but more because of a perceived lack of these vital characteristics by independent auditors. Microsoft's Exchange product can be portrayed as vulnerable in several of the aforementioned areas. Exchange 2003 cannot support large numbers of users on a heavily used system when disk I/O becomes an issue. Virtual memory fragmentation becomes a problem. The inability to support large number of users impacts efforts at server consolidation which in turn hampers efforts at information life cycle management. Microsoft's answer is the 64-bit architecture of Exchange 2007 which reduces disk I/O by putting more transactions into cache. Availability is still a weakness with Exchange. Clustering over any geographic distance to provide quick recovery in the event of a facilities disaster requires third party products which introduce high levels of complexity. As messaging is used by many automated controls to provide notification of control failure, the availability of a messaging system can impact the reliability of systems considered by external auditors to be critical. AD and DNS are also vulnerable to denial of service attacks which in turn can reduce Exchange's availability. Auditing of changes made to a Microsoft environment or event failures can require third-party software simply to manage the large number of events. If software policies require action be taken and documented, this can prove to be a costly control.
22
Domino 7 has the ability to meet or exceed IT governance requirements. It provides scalability on secure Unix servers This allows for industry leading asynchronous clustering and high availability. Messaging systems contain automated controls for event notification and Domino provides the reliable messaging and high availability required to avoid consequences of not receiving those notifications.
Security
Domino has established itself as the clear leader in terms of providing secure messaging and collaboration. Advanced and proven security features, including: Granular access control. End-to-end encryption of data. Both locally on the desktop and at the server, At the ports and in transit giving the ability to deliver strong cryptography for Notes protocols, and Internet protocols. Includes digital signatures to digitally sign e-mail messages, and electronic documents for non repudiation. Includes x.509 certificate services, and ability to support dozens of third party x.509 Certificates of Authority (CA). Includes Server level spam control, with DNS Black lists and White lists support. Supports SmartCards and the ability to customize the LDAP scheme. Note: For additional information about Domino Security, see Security Considerations in Notes and Domino 7: Making Great Security Easier to Implement, SG24-7256, which is available at: http://www.redbooks.ibm.com/abstracts/sg247256.html
23
Lotus Notes/Domino also integrates a new concept called activity-based computing. Activity-based computing extends the value of content created in the course of everyday work, including e-mail messages, meetings, documents, chats and notes, by associating them with specific projects or processes. The ability to bring together all of the content related to an activity in an intuitive shared repository helps ensure team members have the same, up-to-date view of all aspects of the activity, helping to increase productivity and speeding time-to-completion of the activity.
Hannover includes a new activity centric computing model that lets users
organize, navigate, manage, and share information around a particular activity or project,
24
Notes, while at the same time naturally extending the products openness to new programming techniques This ultimately results in real innovation.
25
26
Chapter 2.
27
28
29
Figure 2-2 illustrates the client offerings in terms of functionality versus frequency of use.
Deskless workforce
For the deskless workforce, there are two typical categories of users and requirements: Fixed Function Kiosk The fixed-function kiosk usually runs only one or two specialized applications and can be served by other Workplace client technologies such as the browser or the mobile client. Transactional workstation Desktop machines typically run multiple customized business applications, most of which are structured or forms-based. Users browse the Web and collaborate through basic e-mail. The use of e-mail is limited to within the company, and generally users do not have operating system expertise. These users might use simple server-based office productivity applications that can be remote or available through HTML.
30
Office workforce
For the office workforce, there are two typical categories of users and requirements: Technical workstation Technical workstations are usually workstations in a development or engineering environment. Users communicate through e-mail and instant messaging and make extensive use of development tools or graphical CAD/CAM applications. Basic office workstation Employees in the business world use desktop computers to drive company processes and productivity using word processing, presentation, and spreadsheet applications. These users use the applications to create and view simple documents such as memos, letters, presentation, and spreadsheets. Generally, these users require only basic compatibility (including basic import and export compatibility) with other document formats, such as Microsoft Office. These are not power office users, so they do not require complex functions such as scripting. They require basic browser functionality to access information such as corporate guidelines, parts information, and loan information. They use e-mail to communicate information and to send documents through attachments.
Knowledge workforce
For the knowledge workforce, there is one typical category of users and requirements: Advanced office workstation Advanced office workstations users use desktop computers to drive company processes. They use arbitrary Windows applications that are dependent on Windows application program interfaces (APIs) such as MFC, IE, and WIN APIs. They are highly skilled in the Windows user interface, and they depend on being able to interact with the Windows operating system and Windows-based applications to do their jobs. Users of these general-purpose desktops employ applications to create and modify complex documents for use within and outside of their companies.
31
32
33
and administrators can now control mail preferences through policies. Finally, visual tags have been provided to indicate whether an e-mail was sent to the recipient only, and a user can now determine what folders hold a document using the Discover Folders action. To increase your options, the Lotus Notes Application plug-in is now included as part of the Lotus Notes and Domino 7 release. It is designed to work with the IBM Workplace Managed Client. For additional information, consult the product documentation for IBM Workplace Collaboration Services 2.5 at: http://www-10.lotus.com/ldd/notesua.nsf/6c87a7297ac2aa71852569810051910 9/865ed40240bc25ae852570060050eb40?OpenDocument Finally, a number of improvements have been made to the archiving process. For details about these and other new client features, see the Lotus Notes and Domino 7 release notes on the Lotus developerWorks site: http://www-10.lotus.com/ldd/notesua.nsf/e18d5eb0b8be97d9852567e50052ad1 6/ec099861d91381fc852570360051903c?OpenDocument
34
Lotus Domino Web Access 7 has many improvements in the areas of performance and usability. Highlights include: Opportunity for improved client and server performance Enhanced security features Expanded presence awareness and instant messaging integration Updated user interface Added mail and calendar productivity features Enhanced support for Linux New administration and management features Improved offline access to personal data IBM Lotus Domino Web Access 7 software is a sophisticated Web client for Lotus Domino server. Lotus Domino Web Access software gives your employees
35
the power to create rich text messages, schedule meetings, manage tasks, and collaborate with colleagues whether they are using their own workstation, an Internet kiosk, or another user's PC. With Lotus Domino Web Access 7, you get the best of both worlds: access to a robust, reliable, enterprise-class messaging and collaboration platform, with the ease of simply opening a browser. Note: Lotus Domino Web Access 7 takes advantage of Lotus Domino 7 Server performance improvements, both in the core server functionality and in HTTP.
36
Among the highlights of Lotus Domino Access for Microsoft Outlook 7 are: Opportunity for improved client software performance, reducing the time to launch the application compared to 6.5.3. Native support for Internet standards, including X.509 and Secure Multipurpose Internet Mail Extensions (S/MIME) Installation option for separate program and data directories, allowing multiple users to share the same machine, using Microsoft Windows operating system security. New mail notification options, including playing a sound, briefly changing the mouse cursor, and showing an envelope icon in the notification area. Option to use a local copy of your global address book, which can be a full copy of the directory or a condensed directory catalog to save space on your workstation.
37
Additionally, Lotus Domino Access for Microsoft Outlook 7 users can use Lotus Domino applications through a browser, dramatically increasing access to existing Lotus Domino applications. Finally, because, Lotus Domino Access for Microsoft Outlook 7 does not require a Lotus Domino 7 server, you can take advantage of these improvements today, before you complete your server upgrade, as long as your users mail files reside on Lotus Domino release 6.5.1 or above. For more information about Domino Access for Microsoft Outlook, refer to the product homepage at: http://www-142.ibm.com/software/sw-lotus/products/product1.nsf/wdocs/ac cessmsoutlookhome
38
Workplace
Domino
POP3 Server
Exchange 2000
IMAP Server
Figure 2-5 Common PIM Portlet integrating different back-end systems to a single portal
For a company that has multiple PIM systems, such as Exchange, Domino, and POP3/IMAP servers, Common PIM Portlets give users a common user experience while accessing different back-end systems. As a result, it could be argued that Common PIM Portlets lower the total cost of ownership (TCO) in terms of training and technical support.
39
Figure 2-6 illustrates the Mail Portlet for the Common PIM Portlets.
Advantages to the Common PIM Portlet include: Provides a Browser client user interface to Mail functions such as e-mail composition, viewing, and inbox management Can connect to multiple e-mail service providers, including Domino, Exchange, POP3, and IMAP Adapts to the capabilities of the service provider, not a least common denominator approach Can launch DWA or Notes as a secondary client for Domino if enabled by Administrator
40
When using the Common PIM Portlet, you can select with which back-end system that you want to connect.
Figure 2-8 Configuration of the Mail Portlet where you can select different back-end mail systems
41
back-end. This functionality remains valid before, during, and after a migration or coexistence scenario. Figure 2-9 illustrates how using the calendaring PIM Portlet provides a seamless, consistent interface that uses either a Domino back-end server or an Exchange environment. Exchange Back-end Domino Back-end
Figure 2-10 illustrates again how using the Common PIM Messaging Portlet (Mail Portlet) allows a consistent, seamless interface, with flexibility to work with either a Domino messaging system or an Exchange messaging server.
42
Domino Back-end
Exchange Back-end
Figure 2-10 Common PIM Portlet (Mail Portlet) working with either a Domino Server or an Exchange server
Finally, while this example presents one potential coexistence option, we discuss several possible approaches to coexistence and what to expect in Part 3, Coexistence: Tools and strategies on page 111.
43
44
Part 2
Part
45
46
Chapter 3.
47
Note: This chapter is not intended to be a complete project management handbook, even for a migration project. Every organization, environment, and project is different, and expert project management skills are needed to manage the project successfully. The goal of this chapter is to increase your awareness of the topics that you need to consider and act upon when planning and implementing the project. For information about project management, refer to the Project Management Institute Web site at: http://www.pmi.org
48
Document business requirements The first task the migration project team must tackle is fully documenting the
business requirements and the scope of the migration. This exercise involves
expanding on the requirements that are laid out in the messaging evaluation study and detailing any additional requirements. The result of this step is a set of clearly defined and realistic goals for the project. We discuss this phase in detail in 3.7, Documenting the business requirements on page 54. Develop the communication plan The objective of a communication plan is to educate, inform, energize, and engage all parties of a project. Without adequate communication throughout the migration project, you run the risk of creating an excellent plan that never has the opportunity to be implemented. Developing a communication plan can be regarded as a internal marketing campaign and can help keep the amount of FUD (fear, uncertainty, and doubt) to a minimum. We discuss this phase in detail in 3.8, The communication plan on page 57. Set project expectations
This information defines the current messaging environment. It includes such things as the network topology and the current naming scheme. We discuss this phase in detail in 3.10, Documenting the current messaging environment on page 59. Note: Being very thorough in this phase avoids unpleasant issues later, because forgotten or neglected functionality can escalate to be a show stopper.
49
Develop the training plan New skills might be required for the new messaging system. Training everyone involved with and affected by this project can be a key factor in its success. In addition to the technical training necessary to enable IT staff to design, test, deploy, and support the new environment, all those who will use the new system need to be trained on its features, functions, and any new or migrated applications. Training should be an ongoing activity throughout the course of the project. Communicating the reasons for the migration can be a part of the training, and developing the training plan can actually begin concurrently with the documentation of the current environment. The plan can then be updated during subsequent steps. We discuss this phase in detail in 3.11, Developing the training plan on page 66. Plan, design, and document the new Domino and Notes environment In this step, the project team designs the new environment, one which reflects the companys strategic infrastructure plans, meets current needs, and provides opportunities for future enhancements. The team must design a well researched and carefully conceived messaging infrastructure, to support not only users e-mail needs, but a variety of other messaging applications. The activities in this step of the project include: Planning the new environment Designing the new environment Documenting the new environment We discuss this phase in detail in 3.13, Plan, design, and document the new environment on page 69. Perform risk analysis Identify potential risks which could occur during the project For each risk, assign a likelihood of the issue occurring, For each risk, assign a severity associated with the occurrence of the risk, Finally, for the most severe risks, document a risk mitigation plan and a potential fallback strategy.
Pilot the new environment to a select group of users Develop, pilot, and implement a coexistence and migration strategy
50
The coexistence and migration strategies are the plans that define how to join the old and new messaging systems and describe the steps in which users stop using the old system and begin using the new system. These strategies are dependent upon: Business requirements and the scope of migration Setup of the old system or systems The design and implementation of the new Domino and Notes environment At this point, the design of the new environment has been validated, as well as the coexistence and migration strategies for the company. Now, the actual migration of users to the new environment can take place. Key activities in this step are: Training Publishing the migration schedule Announcing the kickoff of the migration Starting the coexistence and migration
We discuss this phase in detail in 3.14, Developing a coexistence and migration strategy on page 82. Implement the final phase or project closure When the migration is done, there are still a few tasks necessary to close out the project, which we discuss in detail in 3.18, Final phase: Closure on page 97.
51
project and its goals. This communication enables the sponsor to emphasize the importance of this project and helps ensure that the project team gets the cooperation that they need from all areas of the company. It is recommended that the project sponsor work with the project manager to hold an initial kickoff meeting for company management. The goal of the kickoff meeting is to gain the needed management cooperation to build the project team and the advisory panel. Further into the process, having the project sponsor acknowledge the work of the test users and participants in the pilot fosters a positive attitude about the migration throughout the company.
52
The team can consist of one or more persons in each of the following roles (and multiple roles can be filled by a single individual): Project manager Sponsor (does not have to be a member of the team but needs to be kept informed regularly) Domino architect Exchange administrator Domino administrator Domino application developer Network administrator IT/IS manager Migration specialist Support team representative Specialists (these individuals can be on call) Users from key interest groups Some training might be required for members of the project team or for those designated as part of the initial support team. You need to allow sufficient time for this training at the beginning of the project. You also need to involve experienced users from the organizations that are affected by the change. They can help communicate the progress of the project and assist with choosing appropriate test users. They can also provide early feedback on plans and schedules, as well as ensure that any requirements unique to their areas are accounted for in the design of the new environment. Be sure to involve the Exchange administrators and others who have been involved in the administration of the Exchange environment who might resistant to the change. Because people in these roles have a precise knowledge of how the old messaging infrastructure works, they can be great advocates for the upcoming migration. Getting access to the right personnel for the project team and the panel will require buy-in on the project from all levels of management.
53
54
structure brought about by a merger or acquisition, changes in the companys business model, or the constant shifts in focus that are necessary to keep up in todays fast-paced business environment. The need to deal quickly with change and to communicate efficiently with employees, customers, and business partners can also be motivating factors. The use of a messaging infrastructure need not be confined to just sending and receiving simple messages and attachments. It can be a whole collaborative environment supporting e-mail, instant messaging, group discussions, virtual team workspaces, corporate intranets, quick publishing to the Internet, and custom applicationsall within a reliable, scalable, secure, and integrated framework that is manageable and cost-efficient. Documenting the business reasons for the migration project and the business uses of the new functionality that will be provided is one of the first tasks the migration project team must undertake. The project sponsor and the project manager must communicate the reasons and goals of the migration project to the project team. The project team must then communicate the reasons, goals, and other project information to the user community. Open communication facilitates cooperation and helps ensure success.
55
has a requirement that is unrealistic, this is the time to modify the expectation to be within the boundaries of what is possible or feasible.
56
Depending on the number and complexity of these applications, separate workgroups might need to be established to complete these applications within the timeline of the migration project. It might be the case that only one or two key applications are considered important enough to be part of the overall migration project, and the remaining applications could be placed outside the scope of the migration project, to be handled separately at a later time or selected to be discontinued. At this point, it is necessary to realign the expectations. After studying the current environment and making plans for what functionality will be available in the new environment initially, at a later stage, or not at all, the revised expectations are communicated to the sponsors and the user community.
57
Some of the topics to consider including in your communication plan: Migration project in general Goals set for the project Implementation schedule Pilot project New environment Where and how the education is available How to contact support Progress of the project
58
Examples of expectations set for the new environment Delivery of messages internally: 90% < 5 sec, 5% < 20 sec. Open mailbox view: 90% < 5 sec, 8% < 20 sec. Send file and store: 90% < 5 sec, 8% < 15 sec. (Sums not equal to 100%; remainders are for special exceptions.)
59
The current Exchange topology. Is this a single site/single server, single site/multi server, or even a multi site/multi server environment? This information can affect other decisions (for example, server consolidation). The organizations name (assuming a single organization). In case of multiple sites, the site names. Connections to other internal/external mail systems. (If there are none, go on to documenting the Microsoft client topology.) What Mail Transfer Agents (MTAs) and connectors are in use? In a multi-site environment, it is expected that site-to-site connectors will be in place. The connectors/MTAs we are addressing here could be CCMail, MSMail, SNADS (if so, state what system), Internet, X.400, Lotus Notes, Exchange 2000/2003 to Active Directory, Novell Groupwise, and others. Are calendaring and scheduling services/connectors provided across the connections? If this is the case, state what connections are being used for this functionality. With regard to multiple sites, is free busytime replicated across the connections? If this is the case, state between what sites. Are there any directory services provided over the connections? If there are, you need to know what type (LDAP, Native Dirsync, Gateway, or third party), and finally, if the import or export process is automated or manual. List the server names, and determine which server is the first Exchange server. What is the server name; is it a bridgehead server; is it a Public folder server; where is it located (organization and site); and how many users are on this server?
60
Are there mobile users? List types and amounts of mobile devices. How is access to mobile users provided (RAS, Wireless, Web, PDA, or other)? Detail the functionality used with the mobile devices. Be detailed; loosing functionality will act as a showstopper to the mobile workers. List of users per locations (include mobile). Are personal storage (PSTs) and personal address books (PABs) being used, and if so, where is the user data stored? If PST files are being used, can this affect the use of Migration tool and the Migration strategy? How about mobile users and the OST file? Are mail rules used? Is voting used? Are there distribution lists? Who is allowed to create folders?
61
e-Mail How many registered/active/concurrent users are there in Exchange? How many peak time users are there? (Peak time, for example, during the beginning of a business day)? If possible, try to obtain statistics that show the peak number of users on an hourly basis for a full month. There might be very big variations in different companies. This information will be used for the design of the new infrastructure. How many mail items, on average, are sent per day (average per user)? If there are variances in how the users act on different sites, then state this as well. What is the average size of a typical e-Mail? Are there heavy sites or user groups that needs special handling? What is the average size of the users mailboxes (PSTs)? Is mail quota being used? (If yes, state the limit.) Do users send attachments through the mail? If they do, are there any restrictions, and how are those restrictions handled? Are there restriction in size, file types, where they are being sent (intrasite, site-to-site, external)? Are there any procedures/applications using the mail APIs? These might be plug-ins, third-party software, or in-house developed software. Maintaining this kind functionality might involve the developers or other separate handling. Is message tracking being used? User Directory What type of information fields are kept in the Exchange Directory? How many documents are stored (per user; in total)? Where are forms stored? Are forms stored on the server (Organizational), in the users inbox (Personal) or in public folders (Folder)? Public folders Are public folders being used? If so, collect details on the folder names, describe the usage, access restrictions, number of entries, and so forth. Are there custom forms?
62
If custom forms are being used, make sure to collect the details on usage, size, interaction with Exchange and with other applications (for example, embedded OLE). Is Outlook Web Access used for Web access? Applications Are Event Services used? Event Services are scripts running against items posted in a public folder. If Event Services are used, collect details on purpose, usage, the script itself. Are there any third-party or in-house applications that interact with Exchange? Exchange Security (key management?) Is the Key management system being used? If yes, is Signing or Sealing (encryption) used? Encrypted documents cannot be migrated because the keys cannot be migrated. Therefore, it is crucial to know if this function is being used, and users should be informed about this. A solution is to decrypt the documents before migration. Is there any other form of e-Mail or Web security? Other services: Is any form of instant messaging being used? If yes, what type (MSN Messenger, IRC, Sametime, AIM (AOL), Yahoo or other)? Is there an e-Mail enabled fax solution? List the details of any e-Mail fax solution used: Send fax only, Receive only, Send/Receive, how faxes are stored (personal/public folders). Is any externally hosted e-Mail service being used? This might be Hotmail, AOL or other provider. Be aware of a potential security risk. Mail that is sent or received through those channels might not be secure, on backup, or accessible for later use. Are there other applications running on the Exchange Servers? If yes, list the applications and the servers those applications are available on. Is antivirus software being used? If yes, gather details on the antivirus software and where it runs (on server, on client, on firewall, or other). Is backup software being used? If yes, gather detail on the backup software and where it runs (on server or on client). Record the backup schedule for incremental and full backups.
63
64
Other essential functionality What are the most common types of information that the WAN transmits: text, data, images, graphics, voice, video, phone, or other? Are there future plans for the network that might need to get incorporated? Are there identifiable bottlenecks in the network? What are the problem areas and has a resolution been planned?
Support
For support, considering the following questions: Has support been outsourced and, if so, can the new environment be supported? How many people are involved for user support in general: Are they placed centrally or distributed? Where are they placed? How many are specifically involved in messaging service for: Administration? Training support? Help desk? Project implementation?
Detail any specific applications for managing user requests and questions. Detail any specific training guide/program for Exchange users. What kind of education is provided to new users, and does this include e-mail usage training? Are there any automated archive policies or applications; if yes, list the details. What backup/restore and disaster recovery policies are in place?
65
Service delivery
For service delivery, consider the following questions: Are there Service Level Agreements (SLAs), and if so, what values do they specify for the following categories? Message delivery internal Directory latency Message delivery external (only to Relay or IMS) Server response time Network response time Web page delivery Max outage Notice of outage List any details on SLAs with ISP
Are there specific rules to inform users about system management and reported downtime? Are there any statistics available for mail flow, network performance and downtime?
Administration procedures
You need to know if any of the following procedures are created and distributed to the users: Is there a Retention Management system in place for deciding how long you maintain your electronic documents, and what the users responsibilities are for each kind of document. This includes Archive and Backup. Is there a user guide with details about security, delegation, access authorization for messaging and office services (how to manage passwords, departmental user IDs for special needs, and so forth)? Are there standard definitions of specific structured forms for mail (that is, format for external letters, fax forms, internal communications, and so forth)? Is there a naming policy? Is there a procedure for users to request new or additional user IDs, resources, password changes, and so forth?
66
In addition, adequate training must be given to all users who are going to use the new system. Training will be an ongoing activity throughout the course of the project. Creating the training plan can actually begin concurrently with the documentation of the current environment. The plan can then be updated during subsequent steps of the project. Depending on the size and scope of your project, you might want to dedicate one or more project team members to training to ensure it receives appropriate attention and focus.
Training requirements
Define your training requirements by answering the following questions: Who needs training? What features and functions must be presented? What applications must be presented? What services must be presented (fax, Internet, connections to other environments)?
67
Here we have identified some of the parties whose training requirements you must address: Executives with a special training needs (time restraints, PDAs. and so forth). System administrators Application developers Help desk personnel (if applicable) Test and pilot users Standard users
Training resources
Consult the following training resources: http://www.lotus.com/education The Lotus site is a comprehensive education source that includes links to a variety of training locations, descriptions of selected courses, and many other materials. http://www.recor.com/ This site has a full suite of learning product for Domino/Notes 7. Some of the Recor products can integrate with the ADT tool for deployment.
3.12 Risk
The risk in not performing the activities described in this chapter is that key features of the existing environment will not be included in the planning and design of the new environment. It is much simpler to design all the features in at the beginning than it is to try to retrofit a feature after deployment of the system has begun. The latter will impact negatively the project schedule and the users perceptions of the viability of the new messaging environment.
68
The current environment has a dramatic impact on both the coexistence and migration strategies. The information collected during this phase is invaluable in designing the strategies. Also, this process highlights potential problems with the current environments that must be addressed before a successful migration to Notes and Domino can take place.
Risk management
Risk is a natural part of any system integration project, and proper management can determine the success or failure of the project. You should begin risk management during the proposal process by identifying the foreseeable risks in the project and developing an associated Risk Management Plan, which quantifies the risk and includes your recommendations for handling it. Here are some actions you can choose to take to deal with a certain risk: Avoidance: Eliminates the cause of the risk through clearly-defined actions/events/tasks. Mitigation: Acknowledges that the risk is not avoidable, but defines steps to mitigate the level of risk. Acceptance: Acknowledges the risk and documents the associated consequences. If new or different risks are identified during the implementation of the project, they should be added to your risk management plan. The project manager utilizes this plan as an instrument to verify the progress against avoidance or mitigation plans, with the focus being to reduce the overall risk of the initiative.
69
sign-off on the design received from all project team members and the project sponsor. Many of the key areas which must be considered when designing the new environment are discussed in the following sections.
Is bigger better
One common stumbling block when choosing a platform is the bigger-is-better attitude. People so often get caught up in getting the biggest, fastest box, that they lose sight of what they need. If your organization only consists of 100 mail users and is unlikely to grow significantly, you probably do not need one of the large platforms. It will support growth for a long time, but the startup costs would be great. However, you might have a large, powerful server which is under-utilized, and you also have lots of in-house expertise in that server platform. You might want to add the Domino server to that machine rather than buying a new server and training your staff in a new operating system. In this case, your 100 mail users might not take much of that particular servers resources.
70
However, you should bear in mind that this does not necessarily reduce the number of logical Domino servers. On the smaller platforms, such as NT, you would typically have one logical Domino server per physical machine. On the large platforms, such as System p, System i, and System z, you would typically run one physical machine with several logical Domino servers on that machine, using Domino partitioning. So in the end, you can have the same number of logical Domino servers.
Scalability
Characteristics of a highly scalable system include, among other factors: Ability to support the processing of large applications. Ability to manage the resource requirements of multiple applications (that is, mixed workloads). Large file systems support. Ability to accommodate from one user to thousands of simultaneous users. Hardware scalability, meaning from a single CPU to SMP configurations with up to 64 processors. Large I/O subsystems that can support a lot of controllers and large volumes of data and files. Supporting higher numbers of controllers means you can distribute your I/O more efficiently. Storage capacity and bandwidth can be further extended with high-speed RAID boxes. With Domino 7, changes have been made to improve the way Domino scales to take advantage of the larger platform architecture. Table 3-1 shows examples of platform scalability features, and how Domino exploits those features.
Table 3-1 Platform scalability features used by Domino 7 Platform scalability feature/metric Ability of platform to support large I/O subsystems (large number of controllers and volumes of data/files). Means that I/O can be distributed more efficiently. How Domino utilizes the scalability metric 1. Optimization of the database format (the on-disk structure or ODS) to minimize I/O contention. Writes to disk are fewer and more efficient. 2. Transaction logging: Database operations are recorded sequentially, which reduces I/O activity while increasing data integrity and significantly improving server restart time. Thread pool model: Results in less memory and CPU utilization.
CPU scalability: Scaling application performance across multiple processors, using single version of the operating system.
71
More efficient memory utilization through: Improved memory management through Unified Buffer Manager Better use of RAM for internal caches and buffers, which boosts performance The ability to use higher than 500 MB means faster throughput.
Inherent scalability features of, for example, UNIX operating systems means: Journaled file system for faster recovery following server crash Support for very large memory configurations to process large applications Large file system support provides more scalability Application resource management, meaning the ability to support mixed workloads
Cumulative effect of Domino 7 performance / scalability enhancements with underlying platform scalability features means: Lower memory and CPU utilization Faster response times More efficient use of I/O Lower network traffic
72
type of server in your new environment. Some of the factors which the project team should consider are: Cost: This includes not only the hardware cost but the total cost of ownership. Company policy: Does a companys standard vendor have the right hardware or will you need to go outside the standard for it? Footprint: How much floor space is available to house the various servers? Scalability: Choose hardware with the view that expansion will most likely be needed in the future. High availability: Review your availability needs and ensure your hardware and network topology design will meet these needs. Disk space: The amount required depends on the kind of server and the number of users. Processor: The more speed, the better for performance. Memory: The amount needed depends on usage. Skills: Do your support personnel have the necessary skills to work with the platforms you choose? Protocols: Will the chosen platforms support the network protocols already in use within your company? Domino 7 is currently supported on the following operating system platforms: Windows Microsoft Windows 2000 Intel (Server and Advanced) Microsoft Windows NT4 Intel UNIX IBM AIX 4.3.3x, 5.1 Sun Solaris/SPARC 8 Sun Solaris/SPARC 9 Linux (Intel) - Red Hat 7.2, SuSE 8.0 IBM System i, V5R1 and later IBM System z, z/OS V1R2 and later
Further platform support might be added, so be sure to check with your local representative or the IBM Web site for the most up-to-date information.
73
Outlook, or a Web browser. The best choice is different for each organization. Our purpose here is to give an overview of the differences between the clients and discuss some of the issues to consider when choosing a client. This section covers the following topics: Single desktop client policy Web browsers User training Platform support Cost considerations Offline usage Standard browsers Performance considerations Security considerations How do I decide?
74
investments. Integration with IBM Workplace products allows organizations to extend and use their existing infrastructure investments. Enhanced integration with instant messaging and Web conferencing enables users to have immediate access to the people and tools they need to do their jobs more effectively and make better, more-informed business decisions. And productivity enhancements in e-mail and calendar functions enable users to better manage daily information and resources.
75
Lotus Notes 7 is much closer integrated with Lotus Sametime. Integration has been added to templates for the mail file, Teamroom and Discussion databases, the Personal Name and Address book, the Lotus Domino Directory, and the Rooms and Resources databases. In these databases, not only can users see who is online, they can initiate an instant messaging session directly by clicking on the status icon. Also, several preferences have been added for Lotus Sametime Integration that allow a user to specify automatic or manual logging in, to save transcripts of instant messaging conversations to the mail file, and support set preferences about how Screen Sharing, Whiteboarding, Audio and Video are used through the Lotus Notes client. Numerous usability improvements have been made to Mail. Among the highlights are a no subject warning, the ability to sort by subject out of the box, quick access to flag items for follow-up, and the ability to see mail threads within an e-mail. The right-click menu has been expanded as well, and administrators can now control Mail Preferences through policies. Finally, visual tags have been provided to indicate whether an e-mail was sent to the recipient only, and a user can now determine what folders hold a document using the Discover Folders action.
76
Highlights include: Opportunity for improved client and server performance Enhanced security features Expanded presence awareness and instant messaging integration Updated user interface Added mail and calendar productivity features Enhanced support for Linux New administration and management features Improved offline access to personal data IBM Lotus Domino Web Access 7 software is a sophisticated Web client for Lotus Domino server. Lotus Domino Web Access software gives your employees the power to create rich text messages, schedule meetings, manage tasks and collaborate with colleagues-whether they are using their own workstation, an Internet kiosk or another user's PC. With Lotus Domino Web Access 7, you get the best of both worlds: access to a robust, reliable, enterprise-class messaging and collaboration platform, with the ease of simply opening a browser. Note: Lotus Domino Web Access 7 takes advantage of Lotus Domino 7 Server performance improvements, both in the core server functionality and in HTTP.
77
Lotus Domino Web Access 7 has many improvements in the areas of performance and usability. Highlights include: Opportunity for improved client software performance, reducing the time to launch the application compared to 6.5.3. Native support for Internet standards, including X.509 and Secure Multipurpose Internet Mail Extensions (S/MIME) Installation option for separate program and data directories, allowing multiple users to share the same machine, using Microsoft Windows operating system security. New mail notification options, including playing a sound, briefly changing the mouse cursor, and showing an envelope icon in the notification area. Option to use a local copy of your global address book, which can be a full copy of the directory or a condensed directory catalog to save space on your workstation. Additionally, Lotus Domino Access for Microsoft Outlook 7 users can use Lotus Domino applications through a browser, dramatically increasing access to your existing Lotus Domino applications. Finally, because, Lotus Domino Access for Microsoft Outlook 7 does not require a Lotus Domino 7 server, you can take advantage of these improvements today, before you complete your server upgrade, as long as your users mail files reside on Lotus Domino release 6.5.1 or above. For more information about DAMO, refer to: http://www-142.ibm.com/software/sw-lotus/products/product1.nsf/wdocs/ac cessmsoutlookhome
User training
Many organizations have been using Web browsers for a while and their users have become familiar with them. Also, a lot of people are now connected to the Internet at home and are becoming proficient and comfortable with a Web browser. However, familiarity with a Web browser does not mean that no user training is required for the browser. Because of the open nature of the Web browser, every site on the Internet has designed its own user interface. Some sites use a graphical toolbar and place it in a frame on the left, right, top, or bottom of the screen. Others use text-based links or some new tool that no one has ever seen before. It is very important to compare the need for education on the browser to the need for education on the actual Notes client.
78
Platform support
The Notes 7 client is supported on the Win32 platforms as well as the Macintosh, and Domino Web Access 7 is available for Mozilla browsers, which means you can use it on machines running Linux. There are Web browsers available for just about every client platform on the market. If you are using a client platform other than Win32 or Macintosh in your organization and if you currently have no plans to implement one of those platforms, the browser might be your only choice.
Cost considerations
A number of companies look to using a Web browser because they believe it will be cost effective to implement. This might be true in some cases, but not necessarily in all, and will depend on your organization. Be aware that some important functionality your users need might not be available or easily implemented for browsers. If you already have a Web browser on the workstations that will not need to be customized, installation costs could perhaps be saved. If there is a need to update or customize the installed browser, the potential cost savings might very well be minimal or nonexistent. Other possible cost savings with a browser come from reduced training requirements for the users. If the users are already familiar with a browser, they will not need to have training on the browser. Users will usually still need training on any customization you might have performed. The amount of training, and therefore cost, might then not be lower than the cost associated with training the users on a Notes client. Maintaining the Notes client might be easier than maintaining the browser because Notes 7 includes the AutoUpgrade feature, which installs new versions and updates on the client automatically.
Offline use
One of the major benefits of Domino and Notes is replication. Replication allows users to work offline by copying down data to local hard drives. It also provides tools for synchronizing the data when needed. Replication is now available when using a Web browser for the client in the form of Domino Off-Line Services (DOLS). DOLS is, however, a modification and extra installation to the client, and it is not necessary if the Notes client is deployed rather than the browser. Refer to the Administration manuals that are provided with Domino for more information about replication.
79
Performance considerations
The Web browser relies on the server to do most of the processing for it, and only needs to be able to display a text document. The Notes client is designed to do a lot of processing by itself. This means that a Domino server needs to do much more work to communicate with a Web browser than with a Notes client. On the other hand, a computer running a Notes client needs to do more work than a computer running a Web browser. It is, of course, possible to build an infrastructure that supports both browser clients and Notes clients. In all likelihood, more servers will be required to support browser clients than will be needed to support the same number of Notes clients. For example, it is possible to do mail with Notes clients or a combination of POP3, IMAP, or HTTP-based mail with a Web browser. If you want to minimize the load on the server in order to maximize the number of mail clients that can be supported, using the Notes client is the best option. Using POP3 is next best, IMAP is third best, and using HTTP, while sometimes appropriate, will support the fewest mail users of any of these four options. Tip: For more information, check the following Web site: http://www.lotus.com/performance
Security considerations
One of the core aspects of Notes is the built-in security, which satisfies the most stringent security requirements a company might have. Domino uses ID files to identify users and to control access to servers. The ID file sits on the client workstation and is protected by a password. Web browsers do not use ID files. They are proprietary to Notes, which requires the ID files to be on the client workstation. If Domino required browser users to have an ID file on their local machine it would impact the advantages of using a browser. These include such things as being able to use any browser from any machine, or allowing users outside the organization to browse pages without any special software, to name just a few. Instead of ID files, browsers typically use user names and passwords for security. Most sites on the Internet pass user names and passwords between the client and server in clear-text format. This means that anyone can intercept the message and easily read the user name and password. While this might not be of much concern in a closed, private network, it is definitely a big issue when opening up Domino to outside users.
80
To enhance security on the Web, Domino also allows the use of Secure Sockets Layer (SSL) and X.509 certificates for Web browser authentication. The main point here is that authentication and other aspects of security are different in a Web browser and a Notes client. You must look carefully at the differences between the two when making a client decision, especially if security is a top concern in your organization. For details on Web browser security, see the Lotus Domino 7 Administrator Help database or the IBM Redbook, Lotus Notes and Domino R5.0 Security Infrastructure Revealed, SG24-5341.
How to decide
The best client choice differs for each organization. Use the information that you have gathered, combined with the points that we describe to help you decide which client works best in your organization. Here are some tips: 1. Check to see if your desktops are ready to use the Notes client. If you are not running Windows 32 or MacOS on your desktops, the Notes client is not an option. If some of your clients can run Notes while others cannot, decide if you will allow a combination of clients. 2. Can the required features be made available for Web browser users? 3. Determine if the browser will be used for other things. If the Web browser is going to be on the desktop anyway, it might be more practical to use the browser than to run the browser on some desktops and the Notes client on others. Also, if you already have Web developers in-house, they might feel more comfortable developing for the browser. 4. Try both of them out. Set up both a Web browser and a Notes client and test their functionality. Maybe the client offers some functionality you really like, or maybe the browser suits you more. 5. Determine if there is any feature of either of the two clients that you must have. If you must have replication, or your databases must be Web-capable, the decision is in favor of the Notes client. 6. Make a list of pros and cons for the Notes client, and one for the Web browser, and compare the lists. The client that turns out having the most pros and the least cons could be the winner. Many companies have decided to use a combination of the two clients. A common setup is to use the Notes client inside the building and the Web browser outside the building. Outside the building could be either another company or an employee working from home. You are then using the advantages of both clients where appropriate. Domino is unique in that it can gracefully handle this dual client setup.
81
There might be some initial development overhead to make your Notes applications work in both clients, but it might be a good investment. It gives you a lot of flexibility for the future, and it takes less time in the end to make your applications dual-client capable at the start than to go back and change them later.
82
selection of all Exchange and Domino recipients from the appropriate mail directory. Depending on the mail exchange approach selected, directory synchronization can be performed manually or automatically. Manual directory synchronization requires periodic updates to Domino and Exchange directories initiated by an authorized individual. The process can consist of executing custom programs, performing manual data entry, or a combination of the two. Automated directory synchronization is a process that automatically performs directory updates either instantly or based on a predefined schedule. Automated directory synchronization can be achieved by using Microsofts Domino Connector for Exchange, TenFours TFS Gateway, or by creating automatically invoked custom programs. This method requires a fair amount of effort to establish; however, it enables users to continue e-mail communication in a familiar way regardless of the senders or recipients migration status. This method is recommended for extended coexistence periods. Messaging with Directory Synchronization and cross-platform Calendar and Scheduling support. This coexistence method uses SMTP or other protocols for exchanging mail messages between Exchange, Domino, and the Internet; and allows selection of all Exchange and Domino recipients from the appropriate mail directory. Depending on the mail exchange approach selected, directory synchronization can be performed manually or automatically. Also, depending on the mail exchange approach selected, cross-platform Calendar and Scheduling support can be provided in a transparent or manual fashion. In the manual approach to cross-platform Calendar and Scheduling, Domino and Exchange users include users of the opposite platform in the scheduling notices, which are translated into simple mail messages when delivered to such recipients. Recipients have to manually add scheduling notices to their calendars and manually respond to invitations. Cross-platform schedule check is not possible with this approach. In the transparent approach to cross-platform Calendar and Scheduling, Domino and Exchange users are able to perform all Calendar and Scheduling functions, such as sending scheduling notices, accepting invitations, checking schedules, and so forth, regardless of the recipients platform. Transparent cross-platform Calendar and Scheduling support can only be achieved by using the Calendar Connector portion of Microsofts Domino Connector for Exchange. This method requires a great deal of effort to establish; however, it enables users to continue all of their e-mail and Calendar and Scheduling communication in a familiar way regardless of the senders or recipients
83
migration status. This method is recommended for extended coexistence periods. Messaging with Directory Synchronization, cross-platform Calendar and Scheduling support and uninterrupted Application access. This coexistence method uses SMTP or other protocols for exchanging mail messages between Exchange, Domino, and the Internet; and allows selection of all Exchange and Domino recipients from the appropriate mail directory. Depending on the mail exchange approach selected, directory synchronization can be performed manually or automatically. Also, depending on the mail exchange approach selected, cross-platform Calendar and Scheduling support can be provided in a transparent or manual fashion. Finally, depending on the nature of applications, application access can be achieved through universal application access, or manual or automatic application synchronization. Universal application access is achieved for applications that are Outlook client-independent, for example Web-enabled applications accessed through a Web browser. Users continue to access such applications regardless of their migration status. For Outlook client-dependent applications, continuous application access can be achieved by retaining the Outlook mail client on users workstations, possibly along with the Notes client, and continuing to access applications that so require it using Outlook client. Manual application synchronization requires that periodic updates to applications be performed by an authorized individual. The process can consist of executing custom programs, performing manual data entry, or a combination of the two. Automated application synchronization is a process which automatically performs application updates, either instantly or based on a predefined schedule. Depending on the nature of an application, automated application synchronization can be achieved by using a third-party product or by creating automatically invoked custom programs. Depending on the nature of applications, this method can require a great deal of effort to establish; however, it enables users to continue accessing applications regardless of their migration status. This method is recommended for extended coexistence periods.
84
messaging data is sometimes mandatory due to certain legal and industry regulations covering data retention. In some cases, however, a clean cut over to the new environment is preferred. In this case, the old system can live on as a reference for a period of time. This approach is very cost-effective in terms of migration and coexistence, but its success is heavily dependent on how the old system was used. For example, if a company uses mail and mail storage for project communication and documentation, then large amounts of the companys project documentation and communication is stored in the mail files. If this documentation is lost or not easily accessible, severe problems could be encountered.
85
Determination of what data and how much data to migrate is often dependent on several of the following factors: Data importance: How valuable is data from personal, professional, corporate, and legal points of view? Data retention: What mailbox cleanup policies and activities are in effect? Server mailbox limitation: What are the differences in quota policies and enforcement in Exchange and Domino environments? Archiving policy: Where and how frequently will data be archived? Migration Tools selection: Which migration products will be used for data migration and what are their capabilities? Migration duration: How much time is allocated for data migration? The final decision on what data to migrate might result in multiple alternatives applicable to different groups or categories of users.
86
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) Note: Choosing administrative assistants and the specific executives with whom they work is especially important, given that assistants frequently have full delegation rights to the executives mail file. People who are more resistant to change Some volunteers 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.
87
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 Part 4, Migration process: Tools and procedures on page 337. b. Install Notes on the client machines for pilot users. 5. Initiate the migration 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. Incorporate feedback or recommendations into a deployment plan for larger audience.
88
89
for each of them. Additionally, DUS is integrated into the normal user registration process of the Domino Administrator. DUS provides the smoothest migration path from Microsoft Exchange to Domino 7. With the Microsoft Exchange migration tools, you can migrate users and convert their mail and calendar information to Domino 7, with full fidelity. Best of all, mailbox conversion runs on any administrator workstation, which leaves the Domino server free to serve the users. Like all Domino Upgrade Services, the Microsoft Exchange DUS is built right into the Domino Administrator client.
90
With those questions in mind, think about the following issues. Consider the training requirements and Client deployment issues, then decide: To what Client are you migrating (this determines what data can be migrated) Notes client Domino Access for Microsoft Outlook Domino Web Access Web browser Mixed environment Rooms Materials Personnel Availability (the company) Cost
Post migration support and Helpdesk Consider what information should be migrated: Data on server, with server migration only (technically the only option for Domino Web Access) All data: server and local Locally saved data: local only No data Calendar information Distribution lists Directory information Public folders and forms. Consider the following: Not migrating redundant forms Development work required to provide the same facilities Complexities of public folders/NSF coexistence With regard to client migration, what type of information has been added to the personal address books: Entries copied from Global Access List (GAL) Custom entries Entries added from received mail No PABs used or allowed
91
It is important to review this information because the Client migration tools are not always able to resolve some addresses added through extraction from the GAL or recipient information. With regard to physical infrastructure, consider the resources available: Hardware reuse: Is it reusable? Will you need to consolidate on same or new platform? Is it redundant? With regard to the physical infrastructure, review the reuse and redeployment of any storage architecture in place. Internal IS support and Helpdesk. Network bandwidth. This issue needs to be considered in terms of both Server and Client data migration and deployment. With regard to server migration, assuming all Exchange servers are accessible from one location, consider bandwidth usage for each user migration from remote servers. With regard to Client deployment, specifically for Domino Access for Outlook, consider the bandwidth available for all connections (WAN, LAN Dialup, and so forth). The Domino Access for Outlook deployment requires you to download both code and a replication/synchronization of the users mail file. A similar situation might evolve with a remote client deployment and local replication of users migrated server-based mail files. Network support and future plans for the network. With regard to actual migration, consider the following in terms of timing and planning of the deployment: Number and types of other mail connections to Exchange Address resolution, internal and external Support of coexistence tools Mail flow restrictions Directory management Mail flow performance Scalability of coexistence tool Public folders and Workflow Calendars Instant messaging Internet addressing and message flow Facilities that will no longer be available, regardless of the Client selection (for example, voting, resource scheduling, and others).
92
With regard to the actual migration, consider the following: Number of users to be migrated Grouping of users to be migrated at the same time (this could reduce the mail flow over connectors) Number and size of documents present in public folders Access restrictions on public folders Amount of developers work required to emulate forms and integration with back-end applications Selection criteria for documents to be migrated (if not all documents) Whether all directory information must be migrated Reliability of coexistence tools Other mail systems - migration or gateway support Should directory structure/naming be emulated in Domino Internet connection migration Helpdesk retraining User training Methods of client deployment Server and client locations Passwords Post migration clean-up With regard to coexistence, consider the following: Coexistence duration Number of users on either system at the mid-stage of the migration Calendar and scheduling requirements Internet coexistence requirements Expected message throughput of the gateway at the mid-stage of the migration Support personnel training Cost Post-migration cleanup All the migration tools available are non-destructive. This means that a migrated users NT/Exchange account would still be online. It is therefore necessary to remove his account from the Exchange system, or if there is a
93
need to access data, to restrict the user sufficiently (no creation of new mail, not listed in the Exchange directory, and so forth). Be sure to back up all accounts before removing them.
Staged rollout
In this type of rollout, the rollout team takes a step-by-step approach. This approach is quite common in smaller companies, where person power might be
94
limited. For example, if you have just two people to handle the rollout, there are limits to the number of machines they can get ready in a day. The staged rollout is also used in larger companies, if the rollout can be subdivided neatly. This is supported by coexistence during the actual migration. The major advantage to this approach is that the risk if any given step goes wrong is minimal because it is only a fraction of the total project. The biggest disadvantage is that the total migration project can take a long time. Be aware that there tends to be a short span of time left between steps to determine if the one step has been successfully implemented before performing the next step.
Instantaneous rollout
This refers to a methodology where the entire rollout is done all at once, in one major step. Several underlying or background steps might have been performed prior to the rollout, though. The biggest advantage with this type of rollout is that there is no period of coexistence. Be advised that for this type of rollout, management needs to be prepared for downtime. The downtime is needed to perform several steps all at once. If you choose an instantaneous approach, management needs to be prepared for the possibility that there will be problems encountered along the way (like an operating system that refuses to install in a stable manner) that can cause the project to take a long time. Most instantaneous projects are scheduled to run over a weekend or long weekend, and if there are problems, the rollout might run into Tuesday or even Wednesday. Management needs to know this is possible.
Reality check
In the real world, you rarely have the luxury of taking a system down during production hours. At the same time, management will not want to have a project which drags on interminably. Therefore, most rollouts end up falling somewhere between the extremes of instantaneous and staged. Consider performing whatever you can separately, in controllable steps, to minimize risk. Do as much as you can at a time, after office hours. In this way, you benefit from doing big chunks at once, time-wise, but without the required production downtime a big bang requires.
95
Some of the tools available are architected for Notes client deployment, for example Automated Deployment Toolkit (ADT) from Wolcott Systems Group and InstallPump from SoftQuest. You can also use Microsoft Active Directory for distributing Notes clients. The basic idea behind automated software distribution is to make installing multiple clients more efficient. This is generally done using some kind of template file, or a profile, which is set up once and then pushed to the users desktop. Then, the only tasks left in the client installations are the user-specific setup items. ADT from Wolcott Systems Group is an automated, managed system for deploying, upgrading, or migrating an existing messaging system to Notes R5 and Notes 6. ADT centrally manages and automates the client deployment process and integrates with industry-leading data migration and training tools, saving companies significant time and expense. Another option is to use one of the software products that are architected for distributing any software to the workstation. The most commonly used tools include IBM Tivoli Configuration Manager, Microsoft SMS, and ZenWorks. Unless you work in a fairly small company, we recommend strongly that you consider using some kind of automated installation for the client installation. For further information about distributing Notes clients automatically, refer to the Web sites and product documentation from the deployment software vendors or to the IBM Redpaper Distributing Notes Clients Automatically, REDP-3693.
Recovery planning
The concept of recovery planning is to save the organization from losing data. The type of disaster you are trying to be prepared for does not matter. If youre prepared for the worst, you can get back to normal much faster. Make sure, as a minimum, to have a rollback plan in place.
96
97
98
Chapter 4.
99
Step 2
Set up coexistence
Step 3
Migrate mailboxes
Step 4
Decommission servers
End
The sections that follow provide greater details about specific steps involved in a migration project.
100
be rather simple, getting it right the first time can save time in making changes later. We fully appreciate that your main objective is to migrate your messaging environment, but Domino is a platform for advanced collaboration and application development and deployment. It is to your advantage for you to review the information in this and other Redbooks before deploying a full Domino messaging and collaboration infrastructure, because this can ensure that you get the maximum return on your investment.
101
have a critical impact on the long-term success and impression of the migration project. For example, if higher level directors are involved in the early stages of the migration, be absolutely sure to also migrate their personal assistant at the same time. Chances are that the personal assistant has important delegation rights to the directors mail file, and this ability for the director and assistant to work togetheron the same systemis critical. Important: Review Chapter 3, Migration project overview on page 47, specifically 3.8, The communication plan on page 57 for more information about defining the migration plan.
102
1. Using the migration plan, select the users for migration. Inform each selected user of the migration. You need to do this many times. Also, request that the user clean up the mailbox. If you were in the process of moving to a new home, you wouldnt take the trash with you, right? In the case of a migration, why take your non-business and unwanted e-mail messages to your new system? Tip: While it sounds obvious, make sure that users who are about to be migrated have cleaned out their mail files and emptied the trash from their mail file. This has significantly reduces the number of messages that require migration. 2. Register the user in Domino using Domino administration People and Groups Tools register Migrate. 3. After selecting the system to be exchanged and choosing the relevant profile, select the users to migrate. At this time, do not migrate the mailbox (that is, select the option do not convert mail).
Alternatively, if you are using the CMT, select ADD users Registration register. 4. Register users in Domino. If you are using Domino migration tools, deselect the option to convert mail and select Add Admin to ACL (to be able to add migrated mail documents later).
103
5. Install mail client for user being migrated (Outlook Connector or Full Notes clients) optional enable sametime). 6. Set an autoforward on the Exchange account. (The specific steps are described in Appendix B, Migration procedures: an overview on page 751.) Note: Setting the autoforward is an important step for a successful migration if non-migrated users still in Exchange reply to mail or select a recipient from local contacts, the reply to address will be the old Exchange address. Setting an autoforward ensure that all mail is received in the new mailbox on Domino. After the autoforward configuration is set, all e-mail for the user is forwarded to the Domino account. The user can be migrated any time from this point forward.
104
11.Select the users to migrate and click OK. The users are now migrated. 12.Check that the migration and mailflow changes are successful
105
In some cases, you might have customized the mail template with the additional script that is provided by Binary Tree, which migrates user data automatically when the mailbox opens. In this case, the steps to deploy user data using CMT are not required.
106
2. Open Domino administrator and go to the People & Groups tab. 3. Select the users that you have migrated and select Upgrade from the right-hand tools bar (Figure 4-4).
4. In the Upgrade Notification window (Figure 4-5), on the Basics tab: a. Select Convert local ccMail/MS Mail/MS Exchange data to Notes. b. Select Yes under Notify me when users have completed conversion.
107
You can customize the message that the user receives if you want. 5. Click the Mail Conversion tab (Figure 4-6). a. If you have chosen to have the migration tools on a shared drive, enter the path. b. Select MS Exchange from the Mail Conversion Options.
6. Click Send. The user receives an e-mail message with a button that migrates the local pst file data into Notes. Note: Outlook is required and the users local profile is used to access the pst file.
108
109
110
Part 3
Part
111
112
Chapter 5.
113
Directory Synchronization
Windows 2000 Domain Lotus Domino Domain Mail Files
Domain Controller Exchange 2000 Information Storage User 1 User 2 Mail
Outlook Clients
Active Directory
Mail.box Exchange.box
Domino Clients
- Notes Client - DWA - DAMO
114
The Exchange Connector for Lotus Notes converts messages that are sent between Exchange and Lotus Domino into a format that is understood by the receiving system. Figure 5-2 demonstrates a message that is sent from a Domino user and that is received by an Exchange user.
Domain Controller
User 1 User 2
Outlook Clients
Active Directory 4
Domino Users User 1 User 2
Mail.box
2 3 1
Exchange.box
Domino Clients
- Notes Client - DWA - DAMO
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
115
Figure 5-3 demonstrates a message that is sent from an Exchange user to a Domino user.
Domain Controller
User 1 User 2
Outlook Clients
Active Directory
2
Domino Users User 1 User 2
Exchange.box
Domino Clients
- Notes Client - DWA - DAMO
116
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
117
In our example the server name was migrate2ka/itso/FR, which is also our mail server. In your Domino infrastructure this might not be the case, so be sure you select the correct server. 4. Select the People & Groups tab.
118
5. Select People in the Tools Pane and click Register (Figure 5-6).
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
119
6. After clicking Register, you might need to choose a Certifier ID. Select your CERT.id and, if necessary, change the registration server. Then, click OK (Figure 5-7).
120
If you have not set up a Recovery ID process, a message warns you that the certifier does not contain recovery information. Click OK to continue (Figure 5-9)
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
121
8. Create a Person document for the Exchange Connector (Figure 5-10) by following these steps: a. Select Advanced. b. In the First Name field, type Exchange. c. In the Last Name field, type Connector. We used these values because they are descriptive. You can use any values that you like. However, at the least, you need a last name for the Connector person document.
122
9. Click Password Options and move the scale to Weak, setting a minimum password length field of 0 (optional). Click OK to continue (Figure 5-11). This setting is required so that you can allow the Microsoft Exchange Connector for Lotus Notes to run in unattended mode, with no password prompt.
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
123
10.Select the Mail Navigator tab. Set mail system field to None (Figure 5-12).
11.Select the ID Info tab. Complete the following steps: a. Depending on the expected length of time for the coexistence, set the expiration date of the certifier at a safe point beyond your planned contingency. b. Select the level of security for your region: North american or International. c. In the Store user ID field, select to store the ID in a file, and have the user ID stored in the default directory D:\Lotus\Notes\Data\ids\People. Note: Under Location for storing user ID, make sure that you deselect In Domino directory.
124
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
125
The Exchange connector is registered and a person document is added to the directory. The ID file is created and stored in the specified directory.
126
4. Click Edit Person. 5. On the Administration tab, for Allow foreign directory synchronization, type No. (Figure 5-15) 6. Click Save and Close.
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
127
3. In the Select a server to administer dialog box, type the name of your Lotus Domino Server in the Server text box, including the certifier information (for example, migrate2003b/itso/fr). Click OK. 4. Go to the Files tab. 5. Click File Database New. 6. In the New Database dialog box (Figure 5-16): a. From the Server drop-down list, select the server that is running Lotus Domino. b. In the Title text box, type a name for the new database (for example, Exchange Mailbox). c. In the File name text box, type a name for the new database (for example, exchange.box). You specify this name later when you configure the foreign domain document and Exchange Connector for Lotus Notes. d. Select the Template Server option. Then, from the Server drop-down list, select the server that is running Lotus Domino, and click OK. e. Select Show advanced templates. f. From the scroll box that is below the Template Server option, select Mail Router Mailbox (7), and then click OK.
128
7. The new mailbox is created. Press Escape to close the About Mail Router Mailbox message (or select File Close). 8. Click File Database Access Control, and then click Add. 9. In the People, Servers and Groups text box, click the browse icon. 10.Select the user ID for Exchange Connector for Lotus Notes, click Add, and then click OK. 11.From the Access drop-down list, select Manager, select Delete documents, and then click OK.
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
129
130
5. Go to the Basic tab, as shown in Figure 5-18, and do the following steps: a. In the Domain type field, select Foreign Domain. b. In the Foreign domain name field, type Exchange. c. In the Domain description field, type Domain for the Exchange/Notes Connector.
6. Go to the Mail Information tab, as shown in Figure 5-19, and do the following: a. For the Gateway server name, type the name of your Domino Server (for example, migrate2ka/itso/FR). b. For the Gateway mail file name, type Exchange.box.
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
131
132
Note: You might receive the following error: You are not authorized to perform that operation: Server Name DBName.nsf. If you do, consult the following Lotus Software Knowledge Base Document, Error Attempting to Create a Database From pubnames.ntf, which is available at: http://www.ibm.com/support/docview.wss?rs=899&uid=swg21086231 4. The new address book is created. Press Escape to close the About the Domino Directory message (or select File Close). 5. Click File Database Access Control, and click Add. 6. In the People, Servers and Groups text box, click the browse icon. 7. Select the user ID for Exchange connector for Lotus Notes, click Add, and then click OK. 8. From the Access drop-down list, select Manager, and then select Delete documents. 9. Select all Roles and click OK (Figure 5-21).
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
133
134
4. Select your Domino server and click Edit Server. 5. In the Directory assistance database name field, type DA.nsf (Figure 5-23).
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
135
3. From the New Database dialog box: a. From the Server drop-down list, select the server that is running Lotus Domino. b. In the Title text box, type a name for the new database (for example, Directory Assistance). c. In the File name text box, type DA.nsf. d. Click the Template Server option. Then, from the Server drop-down list, select the server that is running Lotus Domino, and click OK. e. Select Show advanced templates. f. From the scroll box that is below the Template Server option, select Directory Assistance, and then click OK (Figure 5-20).
4. Click Add Directory Assistance. 5. The Directory Assistance database is created. Press Escape to close the About the Domino Directory message (or select File Close). 6. In view action bar, click Add Directory Assistance.
136
7. On the Basics tab, complete the following fields: a. For the Domain type, select Notes. b. For the Domain name, type a unique name (for example, Unique).
8. Click the Replicias tab. 9. Paste a Database Link for Exchangename.nsf (Figure 5-26).
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
137
10.Click Save & Close. Note: Remember to restart the Domino Server.
Note: For further instructions about how to set up directory assistance, see the Lotus Domino 7 Administrators Help database. To verify that Directory Assistance is set up properly, issue show xdir from the Domino Console. You should see that the exchangenames.nsf is listed, as shown in Figure 5-27.
138
From the Exchange Server, perform the following steps to install the Notes client: 1. Launch the Notes Client Setup Utility. 2. At the welcome screen for the installation wizard, click Next (Figure 5-28).
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
139
3. After you have read the license agreement, accept the terms of the agreement and click Next (Figure 5-29).
140
4. Enter the required information about the user and organization and click Next (Figure 5-30).
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
141
5. Unless otherwise required, do not change the Path names for the Notes program and data files (Figure 5-31).
142
6. Select Install Notes Client and select to install to hard drive (Figure 5-32) to install all the necessary subcomponents. Click Next.
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
143
144
After the installation is complete, ensure that the Lotus Notes directory is in the servers system path. If you need to update the system path, do so using the following steps: 1. Right Click on the My Computer icon and select Properties. 2. From the System Properties dialog box, go to the Advanced tab and select Environment Variables (Figure 5-35).
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
145
3. In the Environment Variables dialog box, select the path names for the user and system variables for the Lotus Notes directory and click OK (Figure 5-36).
4. To update the system path, click Edit and enter the new path name. Then, click OK.
146
We placed the ID file in the D:\Lotus\Notes\Data\ids\People directory on the Domino server. The ID file needs to be copied to the Exchange Servers \Notes\data directory or, when requested, specify a path to the location of the ID file on the Notes server. Use the following steps to set up the Notes client on the Exchange Server machine: 1. To set up the client, first launch it by double-clicking the icon on the desktop. 2. At the Notes Workstation Setup dialog box, click OK. 3. At the Welcome screen, click Next (Figure 5-38).
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
147
4. In the User Information dialog box (Figure 5-39), enter the following information: a. In the Your Name field, type Exchange Connector. b. In the Domino server field, type the name of your Domino Server. Note: In the Domino Server field, you can use either the name of the server or the IP address. c. Click Next.
148
5. Enter the location of the ID file for Exchange Connector (Figure 5-40), and click Next.
Note: This ID file has no password, so you are not prompted for an authentication password. 6. The Exchange Connector does not require any of the additional services. Click Next (Figure 5-41).
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
149
7. You have successfully installed and configured the Notes Client on the Exchange Server. Click OK.
150
4. On the Component Selection page (Figure 5-44): a. In the Action drop-down menu next to Exchange 2000, select Change. b. In the Action drop-down menu next to Microsoft Exchange messaging and collaboration Services, select Change. c. In the Action drop-down menu next to Microsoft Exchange Connector for Lotus Notes, select Install. d. Click Next.
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
151
152
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
153
154
To configure the Exchange Connector for Lotus Notes: 1. Right-click Connector for Lotus Notes, and click Properties. 2. On the General tab (Figure 5-48 on page 156) complete the following steps: a. In the Notes Server field, type the name of your Domino Server. b. Click Modify, type the path to your notes.ini file (include the file name), and click OK (for example, c:\Program Files\lotus\notes\notes.ini). Note: Leave the password and confirm password fields empty. Remember that we did not require a password for the Exchange Connector ID. c. In the Connector Mailbox field, type Exchange.box. d. In the Polling interval field, type the interval (in seconds) that Exchange Connector for Lotus Notes uses to check for new messages that are delivered to Exchange. Note: For the polling interval field, we suggest using the default of 15 seconds. e. In the Notes Server language drop-down list, select the language of the server that is running Lotus Domino. f. In the Convert Notes Doclinks to drop-down list, select one of the following formats for Exchange Connector for Lotus Notes to use to convert Lotus Notes document links: OLE document link Represented by an icon in the Exchange message. When the user selects the icon, Lotus Notes is started, and the link works as it should. (Lotus Notes must be installed on the client computer.) RTF attachment (Default) Document is converted to an RTF attachment. Because this attachment is a copy of the data from the actual Notes document, users cannot edit the document. URL shortcut Link is converted to a URL. When you click the URL, the default Web browser tries to access the computer running Lotus Notes to which the link points. (The user still requires a Lotus Notes name, password, and license to access the document, unless anonymous authentication is allowed.)
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
155
3. On the Import Container tab (Figure 5-49 on page 157), complete the following steps: a. Click Modify to select the Active Directory container to which Lotus Domino users are imported. Note: We recommend that you create a special organizational unit for all your Lotus Domino users. b. On the Choose a container tab, select the appropriate container, and then click OK. c. In the Exchange System Manager Dialog box, click OK.
156
d. When replicating a mailbox whose primary Windows account does not exist in the domain drop-down list, select one of following options for Active Directory to use when new users are imported: Create a disabled Windows user account Create a new Window user account Create a Windows contact Note: We recommend Create a Windows contact.
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
157
4. On the Export Containers tab (Figure 5-50), complete the following steps: a. Click Add. b. In the choose a container tab, select the group that you want to export, and click OK. c. On the Exchange System Manager dialog box, click OK. d. Repeat the previous steps for each group that you want to export. Note: Nested organizational units are not selected for export if you select the parent organizational unit. You must select each organizational unit individually. e. Select Export contacts and Export groups.
158
6. In the Add Address Space dialog, select Notes, and click OK (Figure 5-52).
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
159
7. In the Lotus Notes Address Space Properties dialog (Figure 5-53), complete these steps: a. In the User name field, type an asterisk (*). b. In the Domain field, type the name of the Lotus Domino Domain (for example, itso3). c. Leave cost at one (1). d. Click OK.
160
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
161
9. On the Dirsync Options tab: a. From the Exchange Notes directory update schedule drop-down list, select a schedule for directory synchronization (Figure 5-55). Note: Do not schedule synchronization during peak traffic hours. If your directory information changes infrequently, schedule synchronization for once a day. If your directory information changes frequently, schedule synchronization for two or more times a day.
162
b. Click Address Book Settings (Figure 5-56). c. In the Target Name and Address Books section, type exhangenames.nsf in the default name and address book field. d. In the Source Name and Address Books section, type names.nsf. e. Click OK.
10.On the Advanced tab: a. In the Notes letterhead field, type the Lotus Notes letterhead name that you want to append to the top of message sent from Exchange 2000 users to Lotus Domino users. Note: The letter head name that you specify must match the letterhead name that is defined in the Lotus Notes mail database to which messages are sent. If the names do not match, no letterhead is used. b. In the Notes router mailbox field, enter mail.box or, if you are running multiple mail.boxes, type mail1.box.
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
163
c. From the Delivery order drop-down list, select the order in which messages are to be delivered from Exchange 2000 to Lotus Domino. The options are:
Priority priority messages, such as urgent messages, are delivered to the outbound queue first. This is the default setting. FIFO messages are delivered to the outbound queue on a first in, first out (FIFO) basis. Size Smaller messages are delivered to the outbound queue before larger messages.
d. From the Notes database maintenance schedule drop-down list, select a schedule for compacting database files. e. Under Routable domains, click Add. This will bring up the Add Routable Domain dialog box f. Within the Add Routable Domain dialog, type the name of the Lotus Domino domain to which Exchange Connector for Lotus Notes does not connect directly, and then click OK. Repeat for each additional domain. This will then bring you back to advanced tab shown within Figure 5-57 on page 165. g. Set the Message Size limit. (Optional) h. Click OK.
164
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
165
Use the following steps to enable and customize Lotus Notes proxy addresses: 1. From Exchange System Manager, expand Recipients, and then click Recipient Policies. 2. Right-click Default Policy, and then click Properties. 3. On the E-Mail Addresses (Policy) tab, select NOTES to enable the address, and then click Edit (Figure 5-58).
Note: After directory synchronization occurs, the connector creates secondary proxy addresses for Lotus Domino recipients. These addresses, which do not display bold formatting on the E-Mail Addresses tab, are used as unique identifiers for Lotus Domino recipients. Do not delete these secondary proxy addresses. In general, you should only delete addresses that you create manually.
166
4. In the Address text box, modify the address format. Use the symbols in Table 5-1 to represent various values in the format string.
Table 5-1 Proxy address configuration symbols To substitute The user's alias The user's initials An e-mail address based on the user's display name Use this symbol &M or &m &I or &i &D or &d Notes Typically the mailbox name. Typically the user's middle initial. Blanks and initials between the given name and surname are ignored. If there is a comma in the display name, the portion of the string to the left of the comma is interpreted as the surname; the portion to the right of the comma is interpreted as the given name. Typically the user's first name. Typically the user's last name. To use an ampersand, you must precede it with another ampersand.
For example, you set the address format to &d@Exchange. A user whose display name is Jacob Ryan receives a Lotus Notes address of Jacob Ryan@Exchange. Note: For additional symbols that you can use, see Knowledge Base article Q285136, How to Customize the SMTP E-mail Address Generators Through Recipient Policies, which is available at: http://support.microsoft.com/?ID=285136 5. After you configure the address formula, click OK. 6. On the Default Policy Properties tab, click OK. 7. You are asked if you want to update all corresponding recipient e-mail addresses to match the new addresses. To run Recipient Update Service immediately, click Yes. To update the addresses the next time Recipient Update Service runs, click No. Non-Exchange addresses are always updated, even if you made manual changes to specific addresses. 8. Wait for Recipient Update Service to populate the Exchange address lists. The time required varies depending on the update interval set on the service.
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
167
168
Use the following steps to start Exchange Connector Services (Figure 5-60): 1. Click Start Programs Administrative Tools Services. 2. Right-click Microsoft Exchange Connector for Lotus Notes, and click Start. Note: By starting the Connector for Lotus Notes, it starts the Connectivity controller.
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
169
3. On the Dirsync Options tab: a. Click Immediate full reload in the Exchange to Notes directory synchronization section. b. Click OK to acknowledge the full reload request. c. Click Immediate full reload in the Notes to Exchange directory synchronization section. d. Click OK to acknowledge the full reload request. 4. Click OK.
Because you have just requested an immediate full reload, the actual directory synchronization might take some time. Be patient!
170
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
171
To verify the directory synchronization from Domino: 1. Launch Administrator Client. 2. Click File Database Open and launch exchange.nsf. 3. Go to People view, as shown in Figure 5-64 on page 173.
172
Chapter 5. Using the Microsoft Exchange Connector for coexistence (Exchange 2000)
173
174
Chapter 6.
175
176
Figure 6-1 illustrates the Directory Synchronization process. Directory Synchronization keeps each Directory service up-to-date with the most recent user and group attributes.
Directory Synchronization
Windows 2003 Domain Lotus Domino Domain Mail Files
Domain Controller Exchange 2003 Information Storage User 1 User 2 Mail
Outlook Clients
Active Directory
Mail.box Exchange.box
Domino Clients
- Notes Client - DWA - DAMO
The Exchange Connector for Lotus Notes converts messages that are sent between Exchange and Lotus Domino into a format that is understood by the receiving system.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
177
Figure 6-2 demonstrates a message that is sent from a Domino user and that is received by an Exchange users.
Domain Controller
User 1 User 2
Outlook Clients
Active Directory 4
Domino Users User 1 User 2
Mail.box
2 3 1
Exchange.box
Domino Clients
- Notes Client - DWA - DAMO
Figure 6-2 Conceptual overview of Exchange Connector for Mail routing from Domino to Exchange
178
Figure 6-3 demonstrates a message that is sent from an Exchange user to a Domino user.
Domain Controller
User 1 User 2
Outlook Clients
Active Directory
2
Domino Users User 1 User 2
Exchange.box
Domino Clients
- Notes Client - DWA - DAMO
Figure 6-3 Conceptual overview of Exchange Connector for Mail routing from Exchange to Domino
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
179
180
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
181
3. From the workspace, select the Servers Domain tab and select your registration server. In our example, the server name is migrate2003b/itso/fr, which is also our mail server. In your Domino infrastructure, this might not be the case, so be sure that you select the appropriate server. 4. Select the People & Groups tab. This opens the People view of the Domino Directory (Figure 6-4).
5. Select People in the Tools pane and click Register, as shown in Figure 6-5.
182
6. After clicking Register, you might need to choose a Certifier ID. Select your CERT.id and, if necessary, change the registration server. Then, click OK If you have not set up a Recovery ID process, a message warns you that the certifier does not contain recovery information. Click Yes to continue. Note: We strongly recommend that you set up ID Recovery to prevent problems that occur when users lose or damage ID files or forget passwords. For further information, consult the Lotus Domino Administrator 7 Help (IDs, recovering). 7. The Register Person new entry window opens (Figure 6-6).
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
183
8. Create a Person document for the Exchange Connector by following these steps: a. Select Advanced to see more options. b. In the First Name field, type Exchange. c. In the Last Name field, type Connector. We used these values because they are descriptive. You can use any values that you like. However, at the least, you need a last name for the Connector person document.
9. Click Password Options and move the scale to Weak, setting a minimum password length field of 0 (optional). Click OK. This setting is required so that you can allow the Microsoft Exchange Connector for Lotus Notes to run in unattended mode, with no password prompt.
184
10.Select the Mail Navigator tab and for the Mail type field, select None. All remaining options are removed, as shown in Figure 6-8.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
185
11.Select the ID Info tab (Figure 6-9). Complete the following steps: a. Select the level of security (License type) for your region: North American or International. b. Depending on the expected length of time for the coexistence, set the expiration date of the certificate at a safe point beyond your planned contingency. Setting it too early will stop the functioning of the Connector at the specified date, whether or not you are ready. c. In the Store User ID field, select to store the ID in a file and have the user ID stored in the default directory, which is C:\Lotus\Notes\Data\ids\People. Note: In the Location for storing user ID field, make sure that you deselect In Domino directory. d. Click the green check box on the right side to complete your task, as shown in Figure 6-9. Your person is put in the Registration queue.
186
12.Click Register, as shown in Figure 6-10. The Exchange Connector is registered, and a person document is added to the directory. The ID file is created and stored in the specified directory.
13.When you receive the Register person window, click OK. 14.Click Done to return to the People & Groups view in the administration client.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
187
3. In the left pane, click People. 4. In the right pane, select the name ID that you created for Exchange Connector for Lotus Notes (for example, Connector, Exchange). 5. Click Edit Person. 6. Click the Administration tab, for Allow foreign directory synchronization, type No. 7. Click Save & Close.
188
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
189
7. The new mailbox is created. Press Escape to close the About Mail Router Mailbox message (or select File Close). 8. Select File Database Access Control, and then click Add. 9. In the People, Servers and Groups text box, click the browse icon. 10.Select the user ID for Exchange Connector for Lotus Notes, click Add, and then click OK. 11.From the Access drop-down list, select Manager, select Delete documents, and then click OK.
190
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
191
4. Open the Exchange connector database: a. Select the Files tab. b. Select File Database Open. c. From the Server drop-down list, select the server that is running Lotus Domino. d. In the Filename text box, type the name of your connector database, for example exchangeconnector.box. e. Click Open. 5. Select File Database New Copy. 6. In the Copy Database dialog box (Figure 6-14): a. From the Server drop-down list, select the server that is running Lotus Domino. b. The Title text box should show the name that you entered for your connector database, for example Exchange Connector Database. Modify the name accordingly, for example Exchange Connector Database - Bad mail. c. In the File name text box, change the extension of the existing file name to .bad. For example, if the existing file name is exchangeconnector.box, change the file name to exchangeconnector.bad. d. Select Database design only and make sure that the Access Control List check box is selected. Click OK.
Figure 6-14 Creating the Exchange Connector mailbox for bad mail
192
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
193
Note: You might receive the following error: You are not authorized to perform that operation: Server Name DBName.nsf. If you do, consult the following Lotus Software Knowledge Base Document, Error Attempting to Create a Database From pubnames.ntf, which is available at: http://www.ibm.com/support/docview.wss?rs=899&uid=swg21086231 4. The new address book is created. Press Escape to close the About the Domino Directory message (or select File Close). 5. Click File Database Access Control, and click Add. 6. In the People, Servers, or Groups text box, click the browse icon. 7. Select the user ID for Exchange Connector for Lotus Notes. Click Add, and then click OK. 8. From the Access drop-down list, select Manager, then select Delete documents. 9. Select the Roles as shown in Figure 6-16 and click OK.
194
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
195
4. Select your Domino server and click Edit Server. 5. In field Directory assistance database name, type DA.nsf (Figure 6-18).
196
3. From the New Database dialog box: a. From the Server drop-down list, select the server that is running Lotus Domino. b. In the Title text box, type a name for the new database (for example, Directory Assistance). c. In the File name text box, type DA.nsf. d. Click the Template Server option. Then, from the Server drop-down list, select the server that is running Lotus Domino, and click OK. e. Select Show advanced templates. f. From the scroll box that is below the Template Server option, select Directory Assistance, and then click OK (Figure 6-19).
4. The Directory Assistance database is created. Press Escape to close the About the Domino Directory message (or select File Close). 5. In the view action bar, click Add Directory Assistance.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
197
6. On the Basics tab, complete the following fields: a. Domain type, select Notes. b. Domain name, type a unique name (for example, Exchange).
7. Click the Replicas tab. 8. Paste a Database Link for Exchangename.nsf (Figure 6-21). (If you do not know how to create a database link, click the Database links text to display assistance.)
198
9. Click Save & Close. Note: Remember to restart the Domino server.
Note: For further instructions about how to set up directory assistance, see the Lotus Domino Administrator 7 Help database. To verify that Directory Assistance is set up properly, issue show xdir from the Domino Console. You should see that the exchangenames.nsf is listed, as shown in Figure 6-22.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
199
b. In the Gateway mail file name field, specify the name of the routing mailbox previously created (for example exchangeconnector.box).
6. Click Save & Close. The newly created Foreign Domain document opens in the Domains view (Figure 6-24).
200
Notes 6.x client on the Exchange server rather than a Notes 7 client. IBM does support a Lotus Notes 6 client that connects to a Lotus Domino 7 server. From the Exchange Server, perform the following steps to install the Notes client: 1. Launch the Notes client Setup utility. 2. At the Welcome screen click OK. 3. After you have read the license agreement, accept the terms of the agreement and click Next. 4. Enter the required information about the user and organization and click Next. 5. Unless otherwise required, do not change the Path names for the Notes program and data files. Tip: We do, however, recommend that you install the data on a separate drive or partition. 6. Select Install Notes Client and select to install to hard drive (Figure 6-25) to install all the subcomponents necessary. Click Next.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
201
7. Click Install. 8. When the installation is complete, ensure that the Lotus Notes directory is in the servers system path. If you need to update the system path, do so using the following steps: a. To get to the Systems Properties box, click Start Settings Control Panel. Double-click the System icon. b. Select the Environments tab and select Path in the Variable Field. c. Add the Lotus Notes directory at the end of the Value Field, for example, c:\Program Files\Lotus\Notes. This entry must terminate with a semicolon (;) (for example c:\Program Files\Lotus\Notes\Notes.ini;). d. Click Set. e. Click Apply. 9. Click OK. 10.Close all windows and reboot the system. Important: To ensure that this change takes effect, you must reboot the system after the update to the Environment tab. If you do not, the Exchange Connector will not work.
202
Use the following steps to set up the Notes client on the Exchange Server machine: 1. To set up the client, first launch it by double-clicking the icon on the desktop. 2. At the Notes Workstation Setup dialog box, select the office network as the location and click OK. 3. In the welcome screen (Figure 6-26), click Next.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
203
4. In the User Information dialog box (Figure 6-27), enter the following information: a. In the Your Name field, type Exchange Connector. b. In the Domino Server Name, type the name of your Domino Server. c. Click Next.
5. Select the I want to Connect to a Domino server option and click Next.
204
6. Because we selected not to save the ID file in the Domino Directory, we are presented with the window shown in Figure 6-28. Here, we are required to provide the location of the Exchange Connectors ID file. If we copied it to the local data directory, the location is: c:\Lotus\Notes\data\ids\people\econnect.id If not, click Browse, locate the ID file, and click OK.
7. Click Next. Note: This ID file has no password, so we are not prompted for an authenticating password. 8. The Exchange Connector does not require any of the additional services. Click Finish. 9. When you are presented with the Notes dialog box, click OK.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
205
3. Click Next at the Welcome dialog box. 4. After you have read the Licensing Agreement, click Yes. 5. On the Component Selection page (Figure 6-29): a. In the Action drop-down menu next to Microsoft Exchange, select Change. b. In the Action drop-down menu next to Microsoft Exchange Messaging and Collaboration Services, select Change. c. In the Action drop-down menu next to Microsoft Exchange Connector for Lotus Notes, select Install. d. Click Next.
206
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
207
8. Click Finish. Note: A newer release of Exchange Connector for Lotus Notes is available from the Microsoft Web: http://www.microsoft.com/downloads/details.aspx?familyid=D9F3A35E-10 46-47B5-B09B-BDA9DE60CD9D&displaylang=en
208
To configure the Exchange Connector for Lotus Notes: 1. Right-click Connector for Lotus Notes, and click Properties. 2. On the General tab (Figure 6-33 on page 210): a. In the Notes Server field, type the name of your Domino server. b. Click Modify, type the path to your notes.ini file (include the file name), and click OK (for example, c:\Program Files\lotus\notes\notes.ini). Note: Leave the password and confirm password fields empty. Remember that we did not require a password for the Exchange Connector ID. c. In the Connector Mailbox field, type exchangeconnector.box. d. In the Polling interval field, type the interval (in seconds) that Exchange Connector for Lotus Notes uses to check for new messages that are delivered to Exchange. Note: For the polling interval field, we suggest using the default of 15 seconds. e. In the Notes Server language drop-down list, select the language of the server that is running Lotus Domino.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
209
f. In the Convert Notes Doclinks to drop-down list, select one of the following formats for Exchange Connector for Lotus Notes to use to convert Lotus Notes document links: OLE document link Represented by an icon in the Exchange message. When the user selects the icon, Lotus Notes is started, and the link works as it should. (Lotus Notes must be installed on the client computer.) RTF attachment (Default) Document is converted to an RTF attachment. Because this attachment is a copy of the data from the actual Notes document, users cannot edit the document. URL shortcut Link is converted to a URL. When you click the URL, the default Web browser tries to access the computer running Lotus Notes to which the link points. (The user still requires a Lotus Notes name, password, and license to access the document, unless anonymous authentication is allowed.)
210
3. On the Import Container tab (Figure 6-36 on page 212): a. Click Modify to select the Active Directory container to which Lotus Domino users are imported. Note: We recommend that you create a special organizational unit for all your Lotus Domino users. b. On the Choose a container tab, select the appropriate container where to import the Lotus Domino users, and then click OK.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
211
d. When replicating a mailbox whose primary Windows account does not exist in the domain drop-down list, select one of following options for Active Directory to use when new users are imported: Create a disabled Windows user account Create a new Window user account Create a Windows contact Note: We recommend Create a Windows contact.
212
4. On the Export Containers tab (Figure 6-38): a. Click Add. b. In the Choose a container tab, select the group that you want to export, and click OK.
c. On the Exchange System Manager dialog box, click OK. d. Repeat the previous steps for each group that you want to export. Note: Nested organizational units are not selected for export if you select the parent organizational unit. You must select each organizational unit individually.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
213
214
6. On the Add Address Space dialog, select Notes and click OK (Figure 6-40).
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
215
7. In the Lotus Notes Address Space Properties dialog (Figure 6-41): a. In the User name field, type an asterisk (*). b. In the Domain field, type the name of the Lotus Domino Domain (for example, itso3). c. Leave cost at one (1). d. Click OK.
216
8. When back at the Address Space dialog, click the DirSyncOptions tab: a. From the Exchange-Notes directory update schedule drop-down list, select a schedule for directory synchronization (Figure 6-42). Note: Do not schedule synchronization during peak traffic hours. If your directory information changes infrequently, schedule synchronization for once a day. If your directory information changes frequently, schedule synchronization for two or more times a day.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
217
b. Click Address Book Settings (Figure 6-43). c. In the Target Name and Address Books section, type exchangenames.nsf, in the Default name and address book field. d. In the Source Name and Address Books section, type names.nsf. e. Click OK.
9. On the Advanced tab: a. In the Notes letterhead field, type the Lotus Notes letterhead name that you want to append to the top of message sent from Exchange users to Lotus Domino users. Note: The letterhead name that you specify must match the letterhead name that is defined in the Lotus Notes mail database to which messages are sent. If the names do not match, no letterhead is used. b. In the Notes router mailbox field, enter mail.box or, if running multiple mailboxes, type mail1.box.
218
c. From the Delivery order drop-down list, select the order in which messages are to be delivered from Exchange to Lotus Domino. The options are:
Priority priority messages, such as urgent messages, are delivered to the outbound queue first. This is the default setting. FIFO messages are delivered to the outbound queue on a first in, first out (FIFO) basis. Size Smaller messages are delivered to the outbound queue before larger messages.
d. From the Notes database maintenance schedule drop-down list, select a schedule for compacting database files. e. Under Routable domains, click Add. This will bring up the Add Routable Domain dialog box. f. Within the Add Routable Domain dialog, type the name of the Lotus Domino domain to which Exchange Connector for Lotus Notes does not connect directly, and then click OK. This will then bring you back to advanced tab shown within Figure 6-44 on page 220. Repeat for each additional domain. g. Set the Message Size limit. (Optional) h. Click OK.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
219
220
Here is what the various portions of this address signify: &d organization domain name The Lotus Notes display name (typically the full name) of the user. The name of the user's Exchange organization. The Lotus Domino foreign domain name that represents the Exchange organization.
Use the following steps to enable and customize Lotus Notes proxy addresses. 1. From the Exchange System Manager window, select your Exchange server, then expand Recipients and click Recipient Policies. 2. Click Default Policy in the details pane, as shown in Figure 6-45.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
221
3. In the E-Mail Addresses (Policy) tab, select NOTES to activate the address, and then click Edit (Figure 6-46).
4. In the Address text box, modify the address format to suit your requirements. Non-Exchange addresses are always updated, even if you made manual changes to specific addresses. Use the symbols in Table 6-1 to represent various values in the format string.
Table 6-1 Proxy address configuration symbols To substitute The user's alias The user's initials An e-mail address based on the user's display name Use this symbol &M or &m &I or &i &D or &d Notes Typically the mailbox name. Typically the user's middle initial. Blanks and initials between the given name and surname are ignored. If there is a comma in the display name, the portion of the string to the left of the comma is interpreted as the surname; the portion to the right of the comma is interpreted as the given name. Typically the user's first name.
&G or &g
222
Notes Typically the user's last name. To use an ampersand, you must precede it with another ampersand.
Note: For additional symbols that you can use, see Knowledge Base article Q285136, How to Customize the SMTP E-mail Address Generators Through Recipient Policies, which is available at: http://support.microsoft.com/?ID=285136
Note: In a multi-domain environment where it is likely to have entries matching persons with the same names (ambiguous entries), we recommend that you include the domain name in the address format. As a consequence, persons with the same names will be resolved properly. 5. After you configure the address formula, click OK. The edited address displays in the Policy Properties window.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
223
6. Click OK to close the Policy Properties window. 7. A message asks you if you want to update all corresponding recipient e-mail addresses to match the new addresses. To run Recipient Update Service immediately, click Yes. Otherwise, click No (addresses are updated the next time Recipient Update Service is run). 8. Select Programs Microsoft Exchange Active Directory Users and Computers, open the properties for any Exchange user and in the E-Mail Addresses tab check that the changes are properly taken into account.
224
3. Right-click and select Start. (Alternately, select Action Start.) This also starts the Microsoft Exchange Connectivity Controller service. You now have all services and tasks started and can continue to operate the Connector. After you have verified the operation of the Connector, you might
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
225
want to have it started automatically at server start-up. To have Connector services start automatically: 1. Select Action Properties. 2. In the Start up drop-down list, select Automatic. 3. Click OK.
Directory synchronization
Before you begin the directory synchronization, review the directories for both the Exchange and Domino servers, noting the user names listed in Active Directory and those in the Domino Directory. You will use these names to verify the directory synchronization. Use the following steps to synchronize the directories (Figure 6-50): 1. From the Exchange System Manager, go to the Connectors container and select Connector for Lotus Notes. 2. Select Action Properties. 3. On the Dirsync Options tab: a. Click Immediate full reload in the Exchange to Notes directory synchronization section. b. Click OK to acknowledge the full reload request. c. Click Immediate full reload in the Notes to Exchange directory synchronization section. d. Click OK to acknowledge the full reload request. 4. Click OK.
226
Because you have just requested an immediate full reload, the actual directory synchronization might take some time. Be patient!
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
227
3. Double-click the custom recipient representing a Notes user. In our example we used Pascal Bourgeois. Note: The e-mail fields and their address should show something similar to Pascal Bourgeois@ITSO2.US (Figure 6-52).
228
4. Click OK to close the custom recipient Properties box. To verify the directory synchronization from the Domino Administrator: 1. Open the Exchange Directory database that you created previously. 2. Select the People view and locate a person document for the Exchange user; we used Anas Bourgeois. 3. Double-click the Person document.
4. Note that the Mail system field states Other and the Domain field states Exchange. 5. Check the Miscellaneous tab. The Calendar Domain field should state Exchange.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
229
Note: If the Calendar Domain field is empty, you must perform a new directory synchronization to update the field. If you later install the Calendar Connector and the field is left empty, you will not be able to query the free/busy time of an Exchange user. 6. Close the Person document.
230
does not mean that messages are being transferred from Microsoft Exchange to Lotus Domino (and vice versa). You have to ensure that message routing works both ways. To test message transfer in the other direction, simply reply to the test message and ensure that the message is received correctly. When you test messaging connectivity, it is a good idea to increase the level of event logging in Exchange System Manager. In order to do this, proceed as follows: 1. From the Exchange System Manager, go to Administrative Groups, Servers. 2. Select the name of your Exchange server (or your bridgehead server). 3. Display the server properties, then click the Diagnostics Logging tab. 4. From the Services list, select LME-NOTES. 5. In the Categories list, select all seven entries and set the logging level to Maximum. See Figure 6-55.
In case the message transfer is not functioning properly, you need to check the individual repositories and processes involved in transferring messages.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
231
Figure 6-56 shows how the messages are transferred from Lotus Domino to MS Exchange 2003. (Figure 6-60 on page 236 shows the message flow in the opposite direction.) Exchange 2003 includes features and standard tools that can provide assistance in troubleshooting interoperability issues. Some of the tools are grouped in the Performance tool available in the Administrative Tools program group, while others are included in the Exchange System Manager. Which tools to use to troubleshoot a system and in which order depends on the problem you are facing. On the other end, troubleshooting the message queues on the Domino server is fairly straightforward as described below.
Lotus Domino mail.box Lotus Notes Client Lotus Domino Mail Router exchange.box
Lsntsmex.exe
READYIN
Lsmexin.exe
MTS-IN
SMTP Mailbox
Proceed as follows to check the message flow from Lotus Notes to Exchange: 1. Check the outgoing mailbox database (mail.box) that holds the messages that are in transit. To do so, start the Lotus Notes client and open the Mail Router mailbox.
232
If messages are held in the outgoing mailbox, verify that the Mail Router is running properly. As explained earlier, the Exchange organization must be recognized as a foreign domain for the Mail Router to transfer the messages from the outgoing mailbox to the exchange.box database (see 6.3.6, Create a Foreign Domain document on page 199). You can also issue the following commands from the Domino Administrator server console and check the queue status: Tell Router Show Queues Shows mail held in transfer queues to specific servers and mail held in the local delivery queue Tell Router Delivery Stats Shows Router delivery statistics Alternately, from the Domino Administration Client, go to the Server Status tab. Then, select Server Tasks, the Router task, and click Task - Tell (Figure 6-57). Select the appropriate check box or boxes, and then click OK.
Figure 6-57 Issuing a Router command from the Domino Administration Client
2. Check the exchange.box database by opening the appropriate database (exchangeconnector.box in our example). If messages are present, verify that
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
233
the Connector for Lotus Notes is duly started on your Exchange server (as shown on Figure 6-49 on page 225) and that the LSNTMEX process is operational. Lsntsmex.exe polls the exchange.box database according to the connector configuration, picks up the messages from the exchange.box database, converts them to Exchange format, and places them in the connectors READYIN folder in the Exchanger server. 3. Proceed to your Exchange server and launch Exchange System Manager. Select the name of your Exchange server, then go to Queues. You will see (in a few moments) the queues for the Connector. All the processes should be active. 4. Check the READYYN folder in the Queues container of your Exchange server (Figure 6-58).
5. Double-click READYIN in the details pane (or select READYIN, then click Find Messages). In the Find Messages dialog box, click Find Now to list all messages in this folder under Search Results. Messages stuck in this folder
234
indicate a problem related to the LSMEXIN process. This process also moves the messages from the READYIN folder to the MTS-IN folder.
6. Check the MTS-IN folder of Connector for Lotus Notes. Select MTS-IN in the details pane, and click Find Messages. Messages in this folder are waiting for the store driver to move them to the Exchange MTA. Ensure that the Microsoft Exchange MTA Stacks service is started. 7. Check the SMTP Mailbox Store queue. The messages are transferred from there to the SMTP transport engine which routes them to the intended recipients.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
235
The message flow (that is, the message queues) and the connector processes involved differ when messages are transferred from Exchange to Lotus Domino (Figure 6-60).
Mailbox Store Outlook Client Connector for Lotus Notes message queue
Exchange MTA
Exchange MTA
MTS-OUT
Lsmexout.exe
READYOUT
Lsmexnts.exe
Lotus Domino mail.box Lotus Domino Mail Router User mailbox Lotus Notes Client
Check the message flow from Exchange to Lotus Domino: 1. Check the Outbox folder in your Outlook client. If you are unable to send messages from Outlook, check that the SMTP service on your mailbox server is running. 2. Check the internal message queues of the SMTP transport engine. The Queues container comprises several SMTP message queues that contain the messages during their various stages in the routing process. 3. Check the Connector for Lotus Notes message queue.You can only view this queue in Exchange System Manager when the Microsoft Exchange MTA Stacks service is running. 4. Check the MTS-OUT folder of Connector for Lotus Notes. Messages accumulating in this folder might signal a problem related to the LSMEXOUT process. Lsmexout.exe moves the messages from the MTS-OUT to the READYOUT folder.
236
5. Check the READYOUT folder. The LSMEXNTS process (Lsmexnts.exe) moves the messages from this folder to the Lotus Notes Mail router database (mail.box). In the Queues container, select READYOUT, and then click Find Messages. 6. Check the mail.box database on the Lotus Domino server, as explained earlier in this section. If messages are queuing up in this database, check your Mail router.
Issue
Pictures or embedded graphics are removed when an Outlook user replies to an e-mail message that is from a Lotus Notes user.
Symptoms
Consider the following scenario. A Lotus Notes user sends an e-mail message that contains a picture or an embedded graphic to a Microsoft Outlook user. The Outlook user is in a Microsoft Exchange 2000 Server or a Microsoft Exchange Server 2003 organization. The Lotus Notes user receives a reply to the e-mail message from the Outlook user.
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
237
In this scenario, the replied to e-mail message that the Lotus Notes user receives from the Outlook user experiences one of the following symptoms: The picture or the embedded graphic is missing. There are random ASCII characters in the area where the picture should be.
Cause
This behavior occurs if the following conditions are true: The Outlook user is using Microsoft Word as the e-mail editor. The e-mail message is routed over the Microsoft Exchange Connector for Lotus Notes from Microsoft Exchange to Lotus Notes.
Resolution
To resolve this behavior, modify the text in the Exchconn.ini file on the Microsoft Exchange server that is running the Microsoft Exchange Connector for Lotus Notes. Then, you can restart the Microsoft Exchange Connector for Lotus Notes service by following these steps: a. Start Notepad. b. In Notepad, open the Exchconn.ini file. By default, the Exchconn.ini file is stored in the Drive_Letter:\Program Files\Exchsrvr\Bin directory. c. In Notepad, locate the following text in the opened Exchconn.ini file: [LME-NOTES-MEXNTS] d. Under this text, add the following two text entries: RTFStripTag=1 RTFConvertBin=14 e. Save the Exchconn.ini file, and then quit Notepad. f. In the Services snap-in, restart the Microsoft Exchange Connector for Lotus Notes service. You can find the original technote at: http://support.microsoft.com/?kbid=907977 To add the MEXOUT_INCAPSULATESMTP registry value: a. Start Regedt32.exe. b. Locate the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LME-NOTES\Pa rameters\
238
c. Click Edit Add Value and in the Value Name box type MEXOUT_INCAPSULATESMTP. Then in the Data Type box, type REG_SZ. d. When you are prompted for the string, type FALSE. e. Restart the Exchange Notes Connector service. You can find the original technote at: http://support.microsoft.com/kb/251955/EN-US/
Chapter 6. Using the Microsoft Exchange Connector for coexistence (Exchange 2003)
239
240
Chapter 7.
241
242
Calendar Connector
Exchange Server
Domino Server
Busy.nsf
Request
Response
Exchange Connector For Lotus Notes
Schedule Manager
Request
Response
Exchange CalConn
7.1.1 Prerequisites
To run the Microsoft Calendar Connector, your environment must meet the following prerequisites: Windows 2000 Server SP1 or later (SP2 recommended) Exchange 2000 SP1 or later (SP2 recommended) Installed and configured Microsoft Connector for Lotus Notes Note: Calendar Connector is also available for 2003. The steps below are written using 2000 connector. We point out the one configuration difference during the configuration of the general tab for 2003 connector, otherwise the install and configuration settings are the same.
243
244
The Select Components dialog box opens. 5. Select Full installation including required Schema updates, and then click Next.
245
7.2.2 Adding a Local replica for the SCHEDULE+ FREE BUSY public folder
Scheduling information for users in an Exchange 2000 messaging environment is stored in a special public folder called SCHEDULE+ FREE BUSY. This folder is configured for each administrative group in the Exchange organization. A local replica of each administrative group organization needs to be on the Exchange Server running the Calendar Connector. To add a local replica of SCHEDULE+ FREE BUSY: 1. From the Exchange System Manager, navigate to SCHEDULE+ FREE BUSY, as shown in Figure 7-5 on page 247,
246
2. Right-click Schedule+ Free Busy, and click Properties. 3. On the Replication tab (Figure 7-6 on page 248), do the following: a. Click Add. b. On the Select a Public Store page, select the server running Exchange 2000 with Calendar Connector, and then click OK. c. On the Public folder replication interval drop-down list, select Always Run. d. Click OK
247
Local replicas are now available on the server with the Calendar Connector.
248
2. On the General tab (Figure 7-11 on page 252), complete the following steps: a. Click Modify. Note: The next step differs from 2000 to 2003. b. For 2000 Calendar Connector: On the Select Exchange Notes or Groupwise Connector tab, select the Exchange Connector for Lotus Notes that is used to connect to the bridgehead server running Lotus Domino, and then click OK (Figure 7-8).
249
c. For 2003 Calendar Connector: On the Select Exchange Notes or Groupwise Connector, type connector, in the Enter the object name to select field and click Check Names (Figure 7-9). Then click OK.
250
Note: The remaining steps are the same for both 2000 and 2003. d. In the Number of days of free/busy information to request from foreign calendars field, enter the number of days that users are able to see free and busy information for users on the Domino server. Note: Users Calendar will appear to be free if the free and busy information is beyond the number of days specified. e. In the Maximum age in minutes of foreign free/busy data in Exchange that can be used without querying the foreign calendar field, enter the number of minutes between each query to the Domino Server. Suggest default of 5 minutes. Note: The longer the time interval the least likely chance of up to date information. f. In the Maximum number of seconds to wait for response from foreign calendars field, enter the number of seconds that Calendar Connector will wait for a response for an individual users free and busy information. Suggest default of 15 seconds.
251
3. On the Calendar Connections tab: a. Click New. b. On the Calendar Type tab (Figure 7-12), select Lotus Notes, and then click OK.
c. On the Notes Calendar Connection tab, in the NT Server Hosting the Notes Server field, type the network name of the computer that the Domino Server is running on or the IP address.
252
d. Click Modify. e. On the Notes INI File and Password tab, type the path of the notes.ini file or click Browse to browse to the file, as shown in Figure 7-14.
Note: You can leave the password field blank. We did not assign a password on the ID. f. Click OK.
253
4. On the Schedule tab (Figure 7-15), select Always and click OK.
254
After you have verified the operation of the Connector, you might want to have them stared automatically. Use the following steps for automatic start of the calendar connector: 1. Launch Administrative Tools, and then click Services. 2. Right-click Microsoft Exchange Calendar Connector, and then click Properties. 3. On the General tab, select Automatic in the Startup type drop-down list.
255
Use the following steps to install Calendar Connector Add-in (EXCALCON.EXE): 1. Locate the excalcon.exe file. It should be in a subdirectory on the Exchange Server. Generally the path is exchsrvr\BIN\calcon\excalcon.exe (as shown in Figure 7-18).
2. Either copy the file to a disk or, more conveniently, set up a mapped disk to the Microsoft server and place the Exccalcon.exe in the Domino executable directory of the Domino Server.
256
4. On the Calendar Information tab: a. In the Calendar server name field, type the name of the Lotus Domino server on which you installed the Calendar Connector add-in. You must type the full name, including the certifier information. For example: migrate2ka/itso/FR b. In the Calendar system text box, type exchange.box. 5. Click Save and Close.
257
Note: The Stats information can be understood according to the following syntax: Stats=<a> <b/c> <d>, where: <a> = the total number of calendar requests made from Lotus Domino to Exchange. <b/c> = the average number of invitees over the average response time, in seconds, per Exchange calendar request made from Lotus Domino. <d> = the maximum response time, in seconds, for all calendar requests. By default, the Calendar Connector add-in must be started manually each time the server running Lotus Domino restarts. You can automate startup of the Calendar Connector add-in by updating the notes.ini file on the server running Lotus Domino. Use the following steps to automatically startup the Calendar Connector: 1. Open the notes.ini file in a text editor, such as Notepad. 2. Edit the ServerTasks= line of the ini. At the end of the ServerTasks= line Type: excalcon <server name> <mail-file name> For example, prior to change, the line might look like this: ServerTasks=Router,Replica,Update,Amgr,AdminP,CalConn,Event,Sched ,Stats,HTTP,DIIOP,IMAP,POP3,NNTP,maps After you add the parameter for starting the Calendar Connector add-in, the line might look like this: ServerTasks=Router,Replica,Update,Amgr,AdminP,CalConn,Event,Sched ,Stats,HTTP,DIIOP,IMAP,POP3,NNTP,maps,excalcon migrate2kb exchange.box 3. Click Save and Close.
258
259
Figure 7-21 shows a meeting request by Rob Ryan from his Outlook client. A lookup is performed on invitee Phil Azer, who is a Domino User.
260
Chapter 8.
Note: The product has been deployed in production at 10+ customers of various sizes. As for lack of Lotus Domino 7 Server support, this only applies to the Coexistence Hub Server. All downstream Domino Servers that support users and applications might indeed be at release 7.
261
262
Exchange Server
Exchange Directory
mail.box
exchange.box
tempexchange.box
Mail Server
Internet
Figure 8-1 Overview over the Binary Tree CMT for Coexistence
263
Because Binary Tree's coexistence solution relies on iCAL support of the SMTP protocol, it requires that all Domino Mail Servers be at release level 6 or later and that the Microsoft Exchange Server on which the Notes Connector as well as the SMTP Connector are implemented be release level 200x. These requirements are due to the fact that iCAL support is only available in Domino releases 6 and above and Exchange release 2000 and above. Because Binary Tree does not yet support Domino Server 7 or later (because Microsoft does not support the Exchange connector working with the Domino 7), it is necessary to create a new Domino Server release 6 or later (Notes Connector Hub). A standard Notes Connector for Microsoft Exchange with Calendar Connector and an SMTP Connector are implemented on a Microsoft Exchange Server release 200x. The main purposes of the Notes Connector are: To provide automated directory synchronization between Microsoft Exchange and Lotus Domino directories. To provide free and busy lookup between Microsoft Exchange and Lotus Domino environments. To (optionally) perform certain data exchange, such as e-mail messages originating in Lotus Domino with Database/View/Document Links as well as regular mail and calendar data exchange between selected Lotus Domino domains and Microsoft Exchange. As cross-population of Exchange and Domino e-mail directories is performed by the Directory Synchronization portion of the Notes Connector, Notes, and Exchange users appear in opposite directories with the following addressing information: Microsoft Exchange users in Lotus Domino Directory are created as users at a Foreign Domain, for example Exchange. Ordinarily a Foreign Domain used by the Notes Connector would direct all Mail and Calendar data to a Notes database on Notes Hub Server matching the Notes Connector configuration (for example, exchange.box). However, Binary Tree's coexistence solution requires that the Foreign Domain is configured to send Mail and Calendar data to a different database on Notes Hub Server (for example, tempexchange.box). Lotus Domino users in Microsoft Exchange directory are created with the Name Space of Lotus Domino, indicating that any data sent to the users, including Free-Busy scheduling inquiries should be routed through the Notes Connector for Microsoft Exchange. However, after the Microsoft Exchange Public Folder responsible for routing Free-Busy scheduling inquiries is updated with the latest Lotus Domino information, the users are updated with
264
the Name Space of SMTP and a specific SMTP address pointing directly to the Notes Hub Server, so the mail transfer is being pushed to SMTP. A Server Task (BTCAL) is installed on the Notes Hub Server to continuously poll the tempexchange.box database and transfer mail to Domino Router mailbox (mail.box), so that data destined for Exchange is sent with appropriate modifications through SMTP. Optionally, depending on the need, BTCAL can move data to the Notes Connector database (exchange.box), so that data destined for Exchange is sent through the Notes Connector. Additionally, a Domino Extension Manager program (BTEX) watches the Domino Router mailbox (mail.box) for inbound messages containing iCAL attachments. These messages are placed in a DEAD routing state and a message is passed over to the Domino Server Task program. The Domino Server Task program reads the iCAL attachment and creates a $ICAL_UID field with the value of the iCAL UID value. The message is then released for delivery. A Visual Basic script is deployed on the Active Directory server to modify addresses of Lotus Domino users newly synchronized by the Directory Synchronization component of the Notes Connector. The script switch the primary e-mail address of the Notes users from Notes to SMTP namespace.
265
266
8. Update the Visual Basic script with the name of your AD LDAP. 9. Create a scheduled task to run the Visual Basic script after DirSync is scheduled to update the newly synchronized Notes addresses to use the SMTP namespace.
267
268
Notice how in Figure 8-4 the Connectors view in Exchange and, in particular, how the SMTP connection to Domino has been established.
269
After you have run the Visual Basic script during installation and all modifications have taken place, a notes recipient looks similar to that shown in Figure 8-5.
270
Notes users in Exchange address book are configured to use an SMTP namespace. You can control the correct execution of the Visual Basic script in the event monitor. Look for events with the source Windows scripting host (WSH), such as that shown in Figure 8-6.
Finally, you can monitor verification of the correct function on the Domino side in the log.nsf. Example 8-1 shows how message processing should appear in the log file.
Example 8-1 Processing of an invitation from Outlook sent to Notes (from log.nsf)
06/29/2006 11:13:52 PM BTCal: Done checking for temporary messages. 06/29/2006 11:14:20 PM BTCal: Done checking for temporary messages. 06/29/2006 11:14:48 PM BTCal: Done checking for temporary messages. 06/29/2006 11:14:49 PM BTExchange: Message 0011D611 from "Feodor Engels" <fengels@itso2.us> with subject: "Invitation to the Breakfast meeting" has been stopped for processing. 06/29/2006 11:14:53 PM BTCal: sending message to processor 06/29/2006 11:14:54 PM iCalendar: Logging conversion of request from non-Notes source. Product ID: Microsoft CDO for Microsoft Exchange 06/29/2006 11:14:58 PM BTCal Processor 1: processing complete. 06/29/2006 11:15:21 PM BTCal: Done checking for temporary messages.
271
Example of BTCal process an e-mail containing a calendar attachment originated from Exchange. Note: The upcoming release of Lotus Notes/Domino 7.0.2 provides many improvements in iCalendar processing. Because this release was not yet available at the time of this writing, it would need further testing to determine the exact extent to which using BTCal provides improvements for calendar processing or if, alternatively, native Domino processing of iCAL now provides the same advantages. As shown in Example 8-2, BTCal server task stops the message that is intended for Exchange in the tempexchange.box. It then puts it in the server mail.box to be sent to Exchange using SMTP transfer.
Example 8-2 Processing of an e-mail from Notes designated to Exchange (from log.nsfI
06/29/2006 11:15:44 PM Router: Transferred 1 messages to MIGRATE2003B/ITSO/FR via Notes 06/29/2006 11:15:49 PM BTCal: Done checking for orphaned messages. 06/29/2006 11:15:50 PM BTCal: Transferred message 0011EB8E to the mail router database. 06/29/2006 11:15:50 PM BTCal: Done checking for temporary messages. 06/29/2006 11:15:50 PM Begin CD to MIME Conversion(Process: Router (00000F00:00000007), Database: C:\Program Files\Lotus\Domino\data\mail2.box, Note: 000009EE) 06/29/2006 11:15:50 PM End CD to MIME Conversion(Process: Router (00000F00:00000007), Database: C:\Program Files\Lotus\Domino\data\mail2.box, Note: 000009EE) 06/29/2006 11:15:50 PM Router: Transferred 1 messages to [9.33.85.123] (host 9.33.85.123) via SMTP 06/29/2006 11:16:18 PM BTCal: Message 0011EB8E has been removed from the router database. 06/29/2006 11:16:18 PM BTCal: Done checking for temporary messages.
272
Chapter 9.
273
For directory lookups, you have several choices. You can configure the clients for LDAP lookups (refer to Chapter 16, Directory coexistence using LDAP on page 495), or you can use the Exchange connectors Directory Synchronization (DirSync) with some simple modifications to the mapping tables and recipient policies. If you are using DirSync, then additional internal SMTP addresses are used. Note: For more information regarding addressing and directory lookups in a coexistence environment, refer to Chapter 16, Directory coexistence using LDAP on page 495 and Chapter 17, Integrating Active Directory on page 519.
Virtual Server SMTP Connector Windows Exchange SMTP Firewall SMTP Internet
External DNS
When SMTP is configured in Exchange, the SMTP schema is expanded and management of SMTP is moved from Internet Information Service (IIS) to the Exchange system manager. (If you have not yet installed SMTP, ensure that Pop mail is removed from the Windows IIS installed components.) We discuss the
274
components of the Windows and Exchange SMTP later, in 9.3.1, Microsoft Exchange SMTP overview on page 276. In this configuration, all SMTP and Internet mail is routed through the Exchange SMTP virtual server and connector using internal DNS and external DNS to resolve destination addresses and then routed directly to the Internet.
SMTP Virtual Server SMTP Connector Windows Exchange SMTP Connector SMTP Firewall SMTP
SMTP
Internet
External DNS
275
Note: For more information regarding addressing and directory lookups in a coexistence environment, refer to Chapter 16, Directory coexistence using LDAP on page 495 and Chapter 17, Integrating Active Directory on page 519. During coexistence, all inbound SMTP messages from the Internet are delivered directly to Exchange, through inbound relays if used, using the SMTP Connector. Messages for users in the assigned Domino local SMTP domains are redirected to Domino. Messages from Domino for all users not in the Domino directory are sent to the Exchange server for delivery to the Internet or to Exchange.
276
native routing protocol between Domino servers and multiple SMTP servers or even other Domino servers. Domino converts between Notes and MIME format automatically as required, which means that clients can send and receive mail with no concern about format. For example, if a Notes client sends a Notes-formatted message to an client, Domino converts the message to MIME format for the IMAP client.
277
278
279
3. Select First Routing Group Connectors (Figure 9-5). Note: You can rename First Administrative Groups and Routing Groups from these default names to the names used within your organization.
280
281
5. In the SMTP Connector Properties dialog box (Figure 9-7), enter a unique name and either the DNS name or IP address of the Domino Server. Note: If you enter an IP address, ensure that you enclose the name in square brackets ([ ]).
282
6. After you have entered the IP address of the Domino server, click the Address Space tab and select Add.
283
284
8. In the Properties dialog box, enter the domain name for the Domino server (Figure 9-10). In our lab, the domain name for all our users is domino.itso.fr.
285
9. Although we are not using a separate Bridgehead server, the Connector requires one. To create a Bridgehead server link, click the General Parameters tab, and click Add. Then, select the Bridgehead server, and click OK (Figure 9-11). Note: If you attempt to close the server without configuring a Bridgehead server, a error message (shown in Figure 9-13 on page 288) displays.
286
10.The completed Properties dialog box opens (Figure 9-12). Click OK.
287
288
Follow these steps: 1. Open the exchange system administrator and select Administrative Groups First Administration Group Servers (Figure 9-14).
2. Select the Exchange server where the Virtual Server resides and select Protocols SMTP (Figure 9-15).
289
3. Right-click the default SMTP Virtual Server and select Properties (Figure 9-16).
290
4. Select the Messages tab, and in the Forward all mail with unresolved recipients to host field, enter either the IP address (in square brackets to speed up address resolution) or the FQDN of the Domino server (Figure 9-17). In this figure, we entered the IP address.
5. Restart the Exchange server. You have completed the exchange SMTP configuration and are now ready to configure Domino SMTP services. From this point forward, all messages sent to user@itso1.eu if not found in the Exchange server are forwarded to the Domino server.
291
292
To establish SMTP message transfer, begin by customizing the Global Domain document: 1. From the Domino Administration client, click the Configuration Tab of your Domino server and select Domains (Figure 9-18).
293
2. Click Add Domain. The New Domain configuration window opens (Figure 9-19).
294
3. On the Basics tab: a. Click the pull-down list selector to choose the Domain type that you are creating. b. Select a Global Domain document, as shown in Figure 9-20, and click OK.
295
c. Enter a name for the Global Domain Document. In our case, we called ours GDD for Global Domain Document. d. Enter a role for your domain of a role type of R5/R6/R7 Internet Domains or R4.x SMTP MTA. You can select this from the Global domain role pull-down list, as shown in Figure 9-21.
296
e. Select Yes for Use as default Global Domain (for use with all Internet protocols except HTTP). Figure 9-22 shows the completed Basics tab.
4. On the Restrictions tab, accept the defaults. Note: In our testing, we did not find any reason to change the Restrictions tab. However, we advise that you revise the options in the top and configure appropriately for your site.
297
5. On the Conversions tab, you configure how Domino interprets inbound and generates outbound addresses. To ensure that Domino is configured correctly for address lookup and address generation, you need to make some changes from the defaults, as shown in Figure 9-23.
In the Conversions tab, you need to change the following fields: Local primary Internet domain Set to the Domino FQDN domain. In our example, this is itso.fr. Because we use multiple Internet addresses, we add these to the alias fields as well. Local part Formed From In the event of a user not having an Internet address, you need to specify how the Local part is formed. In our example, we set this field to FullName. When an address is formed this way, the address is appended with the Primary Internet domain that you entered earlier.
298
Domino Domain(s) included Set to none. Otherwise, in conjunction with the Domain separator. Internet Address Lookup Set this to enabled to ensure that Domino looks up the Internet address before trying to create one. 6. If appropriate, you can keep all other fields and tabs at the default values. For our connections to Exchange in our testing, we kept the default values for all other fields and tabs. 7. Click Save & Close. This completes the procedure to create and modify the Global Domain document.
299
300
2. Enter your host name as known to the DNS in the Fully Qualified Internet Host name field (Figure 9-25).
301
4. Select the drop-down box next to Routing tasks, and select SMTP Mail Routing, as shown in Figure 9-27.
You do not need to modify any other fields or options on the other tabs for the Server document. 5. Click Save & Close.
302
303
2. In the Configuration Settings basics tab, select Use these settings as the default settings for all servers (Figure 9-29). You can accept the default for all other fields.
Note: There can be only one default configuration document. If you are configuring an additional server in your organization, then add your server name to the Group or server name field.
304
4. On the Basics tab, complete the following fields: Number of mailboxes: 2 Tip: A good rule of thumb would be to specify two or more mailboxes, in order to better serve a production messaging volume. SMTP used when sending messages outside of the local Internet domain: Enabled SMTP allowed within the local internet domain: Disabled
305
Relay host for messages that leave the local Internet domain: specify either an IP address or an FQDN of your relay If you do not use a relay, leave this field blank. Note: During the coexistence period, you might not want to disrupt the current routing architecture. Thus, you might want to continue routing all inbound and outbound SMTP messages through the Exchange server. If this is the case, then the Exchange Bridgehead server will be the relay, and you need to ensure that the Bridgehead server is configured to allow inbound and outbound relaying to the FQDN of the Domino server. Local Internet domain smart host: (enter the exchange Bridgehead server) 5. For the remaining tabs (Restrictions and Controls, Message Tracking, and Advanced), we made no changes and accepted the defaults. 6. Click Save & Close. All the documents have been configured within the Domino 7 server to enable SMTP message transmission, and you are now able to start testing mail flow.
306
The flow for this scenario is: 1. User Cindy logs on to the Exchange server with her profile (Figure 9-31).
3. Cindy then creates a new mail message to send to Susan with a subject line concerning the announcement of Domino 7. However Cindy cannot remember Susans e-mail address. Because Susans account is in Domino, the e-mail address does not exist in the Exchange directory. Therefore, Cindy needs to do an alternative address book lookup (LDAP). 4. Cindy selects the alternative directory from the address book drop-down list and is able to enter any of attributes that she knows to find Susans e-mail
307
address (first name, last name, telephone number, and so forth). Cindy chooses to search by first name (Figure 9-33). However, LDAP can search any of the mapped fields and returns all entries that contain the word Susan. Note: Using LDAP for directory lookups and using customized connectors for Directory synchronization is covered in Chapter 16, Directory coexistence using LDAP on page 495.
5. Cindy selects Susans entry from the directory list, clicks To, and adds Susan as a recipient for the e-mail. Cindy then clicks OK.
308
6. Cindy continues to compose the e-mail and sends it to Susan when she is ready (Figure 9-34).
7. The Notes user, Susan, receives a new mail notification and opens the e-mail message that is sent through Exchange and delivered through SMTP (Figure 9-35).
Figure 9-35 Lotus Notes client displaying the Exchange SMTP-based message
309
8. Susan then replies to Cindy over the SMTP connection (Figure 9-36).
9. Cindy receives the reply in her Outlook inbox. After reading the reply, she decides to create a meeting notice and invites Susan to discuss the Domino 7 announcement (Figure 9-37).
Figure 9-37 Exchange user creates meeting notice and sends to Notes user
310
10.Susan receives the meeting notice intact because both systems support iCAL (Figure 9-38).
11.After Susan accepts the meeting notice, a calendar entry is created in Susans Diary and an acceptance is sent to Cindy (Figure 9-39).
311
12.Cindy receives a notification that Susan has accepted the meeting request. Figure 9-40 shows that the attendees have accepted.
312
313
314
10
Chapter 10.
315
Figure 10-1 Test matrix used to methodically test coexistence results between each system
316
Our approach was to send a carefully formatted and representative message between both the Domino and Exchange systems, while covering an extensive sample of messaging and calendaring formatting and functionality. To conduct the test, we created a richly formatted document that contained specific elements such as rich text, tables, sections, document links, and embedded graphics in order to verify how these elements would transfer between the two systems. Figure 10-2 shows the document that we used as the primary test message between systems.
317
318
Figure 10-3 illustrates how the Common Migration Tool (CMT) for Exchange and Domino Coexistence from Binary Tree preserved clickable document links, basic section formatting, and all other basic formatting within the document.
319
As shown in Figure 10-4, we also liked the basic message fidelity retention when using an SMTP routing solution. All basic formatting was retained, including an embedded clickable document link. However, section formatting was lost.
320
Figure 10-5 illustrates the basic result when using the Exchange Connector. We were surprised to see that basic formatting such as table formatting or embedded images was not retained. Attention: When using the Exchange 2003 connectors, we did see significant improvements in the retention of table formatting and embedded graphics. Figure 10-8 on page 324 illustrates the improved rendering when using the 2003 Exchange Connector.
With Exchange Connector - most basic formatting lost - no preservation of table formatting
Figure 10-5 An e-mail rendering from Notes to Exchange using Exchange Connectors
321
Figure 10-6 DNS name lookups and accessing the Exchange Directory
322
323
Section formatting not retained Figure 10-8 Example of how a note is sent from Notes to Exchange
324
Document Links
Figure 10-9 illustrates how document links are translated when sent from Domino to Exchange using the Exchange Connector. Document links are most frequently translated to a Notes specific URL.
Figure 10-10 Example of how message appeared when sent from Exchange to Notes
325
326
Figure 10-11 Overview of Message transferred using CMT for Exchange and Domino Coexistence Tool
327
328
Figure 10-13 shows the Notes Section of the test mail as a text line with a triangle showing down, mocking an expanded section. Beyond the appearance, which visually indicates where a section was placed, there is no Notes-centric section functionality. If you click the twisty image, nothing happens.
Figure 10-13 CMT Coexistence: Notes Section converted to a mock-up section in HTML
However, the big advantage over other approaches is, that the section heading and overall layout is retained. The Notes link (document link) has been converted into a Notes URL, similar to the messaging coexistence option, based on pure SMTP routing. However, instead of (Link) in the document, an icon has been included that resembles the Notes mail layout (Figure 10-14).
Figure 10-14 CMT Coexistence: Notes links with an icon in the mail body
329
330
331
332
Our third test was to send document links to Exchange. We found that the document links were received in tact, However, we were unable to take action with them because we did test delivery to a user that had not yet installed Lotus Notes. (This user was running Outlook as their client.) Accordingly, if a user had not yet installed Lotus Notes, when we clicked the document link, we received the error shown in Figure 10-19.
Subsequent testing revealed that after Notes was installed, the document link did launch correctly, and after the user was migrated all document links continued to work successfully.
333
Embedded HTML
We then sent an embedded HTML message and received the result shown in Figure 10-20.
334
We noted the following results from this test: Meeting notices where received intact in Outlook. Acceptance, changing, delegation, and declination all worked and the chair was notified in both directions. Note: Subsequent testing with different versions of Outlook produced differing results. Not all versions of Outlook fully support the iCAL standard. We recommend ensuring that you have the latest Windows Service pack installed. We also noted that Outlook 2000 not only required the latest Service Pack, but also a hotfix only available from Microsoft support.
335
336
Part 4
Part
337
338
11
Chapter 11.
339
340
Migration Workstation
Migration Workstation
Migration Workstation
Migration Workstation
LAN
Microsoft Exchange
Domino
Refer to Chapter 3, Migration project overview on page 47 for instructions about planning for your migration from Exchange to Domino.
341
After these prerequisites are meet, you need to complete the following steps: 1. Create Administrator profile in Outlook. 2. Install Exchange as a Foreign Directory Source. 3. Migrate users. 4. Convert Exchange Addresses to Notes Canonical form.
342
2. Select the Properties item, and the Mail General Tab displays (Figure 11-2).
3. Click Add and the New Profile dialog opens (Figure 11-3). In the Profile Name box, type the name of the Administrator profile for the Exchange server from which you are migrating data (for example, Administrator - Exchange Server). Click OK.
343
4. The E-mail Accounts dialog opens (Figure 11-4). Select Add a new e-mail account and click Next.
344
5. A dialog box opens that allows you to select the server type for the administrator profile (Figure 11-5). Select Microsoft Exchange Server and click Next.
345
6. The Exchange Server Settings dialog box opens. In this dialog box, complete the following items: a. In the box next to Microsoft Exchange Server, type the name of the Exchange server from which you are migrating users. b. In the box next to User Name, type the name of the Exchange Administrator. Click Check Name, and a dialog box displays requesting the password for the Exchange administrator. c. Type the password for the administrator, and click OK. The e-mail accounts dialog box displays with the name of the administrator underlined (Figure 11-6 on page 346). d. Click Next.
346
7. The Congratulation Screen displays, as shown in Figure 11-7 on page 347. Click Finish.
8. Click OK.
347
348
5. Enter the password of your Certifier ID, and click OK (Figure 11-11).
Note: If you have not set up a recovery ID process, a message displays to warns you that the Certifier does not contain recovery information. Click OK to continue, as shown in Figure 11-12.
349
6. The Register Person dialog box opens. Click Migrate People (Figure 11-13).
350
7. When the People and Groups Migration dialog box opens, select Microsoft Exchange Users from the Foreign directory source (Figure 11-14).
8. When prompted, select the profile of the administrator for the Exchange server from which you are migrating, and click OK (Figure 11-15).
351
9. In the Filter drop-down list, select All Users and Groups, and click GO! (Figure 11-16).
10.From the drop-down list of Exchange users, select all users to migrate and add to the People and Groups to Migrate list (Figure 11-17).
352
11.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
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 converts data from the mail file on the Exchange server to the new Domino mail file automatically. 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, for example if the specified mail server lacks sufficient disk space or if the user remains unregistered, 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
353
ID is removed from the ACL and is replaced with the name of the mail file owner. At this point, only the mail file owner can open the mail file.
Figure 11-19 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 has been 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 users existing Domino mail file. 12.Select Migrate (Figure 11-20).
354
13.A successfully queued message displays (Figure 11-21). Click OK. This returns you to the People and Groups to Migrate list, Figure 11-20 on page 354.
14.From within the People and Groups to Migrate list, click Done to go back to the Register Person dialog. 15.In the Register Person dialog box, select Advanced, and then click Password Options (Figure 11-22).
355
16.On the Password Option dialog box, select Set internet password and click OK (Figure 11-23).
17.On the Mail tab, from the Mail file template list, choose Domino Web Access (7), as shown in Figure 11-24.
356
Note: We chose Domino Web Access because it provides flexibility based on the client you that deploy within your organization. The Domino Web Access template provides the ability to roll out a Notes Client, Web Client, or DAMO Client without having to change the mail file template. 18.On the Address tab, you can control the creation of the SMTP address format (Figure 11-25).
357
19.On the ID tab, make sure that the location for storing the users ID file is set to in Domino Directory. Also verify the Certifier information to make sure it is the one that you selected earlier. Then, click the green check mark, as shown in Figure 11-26. Note: (Optional) You might want to store the users ID in a file. To do this, select the in file option. Then, set the path to the location where you want the ID file to be stored by clicking Set ID file.
20.Click Register to finish the registration process and complete the migration. Note: If you have multiple users in the registration queue, you can click Register All.
358
When you click Register, the following actions occur: Person Document is created. Notes user ID is created. Domino mail database is created. Data is migrated from Exchange mailbox to the newly created Domino Mail Database on the Domino Server.
359
For example, if you view a migrated users mail file prior to converting the Exchange addresses to Notes Canonical format, the address fields will contain a name followed by the string WTD, as shown in Figure 11-27.
Figure 11-27 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 that are contained in the migrated mail file, the WTD string indicates that the user was migrated from Exchange to Domino and that the Mail Convert tool needs to be run against the users migrated mail file.
360
Figure 11-28 shows an example of the 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 Chases 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 that contains his name in Lisa Chases migrated mail file. The WTD
361
string is removed from the Chair field and replaced with the appropriate server and domain information, forming a Notes Canonical address. Figure 11-29 demonstrates the Chair field that contains William Chases name resolved to Notes Canonical format.
Figure 11-29 Chair field containing William Chases name resolved to Notes Canonical format
362
Note: We tested mail routing without running the Mail convert tool, and mail routing worked as expected. The difference is from a users preceptive. If you do not convert e-mail addresses, prior e-mail messages will have an address such as: william chase/notesdev/ibm/com/WTD However, if you convert the address, they will appear as: william chase/ibm The key is that both values are in the Person document, so name resolution and lookup will work.
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 only] mail\*.nsf [-w specifies conversion of Exchange addresses
363
Note: After all users have been migrated you would run the convert.
11.3.6 Tip
After you have migrated a user from Exchange to Domino, this user is most likely now listed in three different address books: Domino Directory Exchange Directory (the directory you created during your coexistence stage which Directory synchronization populated) Active Directory We suggest that you hide the entry from users in the Active directory and Exchange directory. This way, when an users attempts to address a message to this new Domino user, only their new Domino address is listed as a choice.
364
12
Chapter 12.
365
366
Notes Upgrade Services, also referred to as the Upgrade Wizard, performs much of the same functionality as the Domino Migration Tool, with a few key differences: Because Notes Upgrade Services works only with a local PST file and creates a local .NSF file, no servers are accessed and no updates are made to the server's primary Domino directory. While Notes Upgrade Services is designed to migrate Microsoft Exchange data that resides locally in an Outlook PST file, Notes Upgrade Services never accesses the Exchange server. The Domino Migration Tool updates the Domino server directory and resolves all addresses in the Domino mail file to Notes Canonical format. However, Notes Upgrade Services does no address resolution. Addresses in the .NSF file resulting from the local migration are not resolved to Notes Canonical format. Messages, tasks, and calendar entries in the .NSF file resulting from the Notes Upgrade Services migration are not intended to be fully functional in the Domino mail clients. You use the .NSF file for reference purposes, and we do not recommend that users replicate the local .NSF file with their Domino server mail file. If users replicate the local .NSF file with their server mail file, they will be unable to reschedule meeting invites or respond to e-mail messages that originate in the locally migrated .NSF file.
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
367
368
2. Click the Mail icon to display the Mail Setup dialog box. Click Show Profiles (Figure 12-3).
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
369
3. The Mail dialog box displays with a list of all the Outlook profiles that exist for the Outlook client. Click Add (Figure 12-4).
4. In the New Profile dialog box, type a name for the new profile and click OK (Figure 12-5).
370
5. The E-mail Accounts window opens, as illustrated in Figure 12-6. Select View or change existing e-mail accounts and click Next.
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
371
6. In the E-mail Accounts dialog box, click New Outlook Data File (Figure 12-7).
7. In the New Outlook Data File dialog box, select the appropriate version for this PST file and click OK (Figure 12-8).
372
8. In the Create or Open Outlook Data File window, navigate to the PST file that you want to migrate and select OK (Figure 12-9).
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
373
10.The E-mail Accounts dialog box displays the New Outlook Data File field populated with the PST file that you have selected, as shown in Figure 12-11. Click Finish.
374
The Outlook profile is created with the Outlook PST file that you selected linked to it. The Mail dialog box illustrated in Figure 12-13 displays with the newly created profile in the Profiles list.
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
375
376
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
377
5. Select the Basics tab and select Convert local cc:Mail/MSMail/MSExchange data. This option displays the Software Notification and Mail Conversion tabs, shown in Figure 12-16. If you would like to be notified when each user completes their mail conversion, select Yes under this section.
Figure 12-16 Upgrade Notification: Basic, Software Distribution and Mail Conversion tabs
378
6. To select a user or group to send the upgrade notification, click Address at the top of the window to display the address book for the Domino server that you have selected. Select the user or group to whom you want to send an upgrade notification. For this example, we have selected a single user, as illustrated in Figure 12-17.
Figure 12-17 Select the user or group who will be sent an upgrade notification
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
379
7. Click OK and the To field in the Basics table is populated with the address or group that you selected, as shown in Figure 12-18.
380
8. Select the Mail Conversion tab. In the list box under the Mail Conversion Options section, you can choose the type of migration to automate by selecting the arrow next to the drop-down list. A list of options displays, as illustrated in Figure 12-19.
Figure 12-19 Mail Conversion Options tab: select the migration type
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
381
9. Because you are sending users an automated message to initiate the Notes Upgrade Services process, select MSExchange from the list box, then click OK. The Convert user from field is populated with MSExchange, as shown in Figure 12-20.
10.After you have configured all options for the upgrade notification, click Send to send an e-mail to the user that you selected, enabling the user to initiate Notes Upgrade Services to perform local conversion of an Outlook PST file (Figure 12-21).
382
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
383
2. Open the message, and notice the button titled Convert My Local Data to Notes (Figure 12-23).
384
3. To initiate Notes Upgrade Services, click Convert My Local Data to Notes. The window shown in Figure 12-24 displays. Follow the instructions in 12.4.1, Starting the migration on page 386, beginning with step 4, to migrate your local Outlook PST file using Notes Upgrade Services.
Figure 12-24 Starting Lotus Notes Upgrade Services from the Upgrade Notification
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
385
Outlook PST files. To access historical data from the Notes client, individual users must manually migrate data using Notes Upgrade Services. Due to the storage limitations of the Exchange server, users might have a number of local Outlook PST files that contain archived data. After their Exchange mail file data is migrated to Domino, they still need access to their archived data from the Notes client. A user might join a company that operates with a Notes and Domino IT infrastructure, but this user has a local Outlook PST file that he needs to access from his Notes client. This is a likely scenario in the case of a newly hired executive, who needs to access historical Outlook data, particularly contacts. In this case, the Domino Administrator will not institute an automated Notes Upgrade Services migration for the executive, but rather the executive or an assistance will need to perform the migration manually.
386
3. Press Enter and the Notes Upgrade Services displays, as shown in Figure 12-25. Click Next.
4. Select the Outlook profile that is associated with the Outlook PST file that you want to migrate using Notes Upgrade Services, and then click Next (Figure 12-26).
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
387
5. Select the appropriate upgrade method (Figure 12-27). The Express method migrates all e-mail, calendar, task, and contact elements from the Outlook PST file to a Notes .NSF file. The Custom method allows you to migrate either all elements in the Outlook .PST file or Personal Folder or to migrate only contacts. We recommend that you choose the Express method to migrate all data in the Outlook PST file. Click Next.
Figure 12-27 Notes Upgrade Services: Select the upgrade method, Express
388
6. Select the personal information items that you want to convert, and click Next (Figure 12-28).
7. Specify the conversion options for Notes Upgrade Services, and click Next (Figure 12-29).
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
389
8. As discussed in 12.2, Preparing the workstation for local migration on page 367, you must use the Extended Mail Template (Mail7ex.ntf) or iNotes Template (iNotes7.ntf) for all migrated .NSF files. In the Template name field, select one of these templates by clicking the button next to the Template Name field and navigating to the directory where it is located on the local workstation, as shown in Figure 12-30.
390
9. Select the location where you want to save the Notes .NSF file that results from the Notes Upgrade Services migration from the local Outlook PST file. Click the button next to the Folder field and navigate to the directory where you want to save the migrated filed, as shown in Figure 12-31.
The results of the Notes Upgrade Services migration are written to an .NSF file, a_PersonalFolders.nsf, in the location that you specified in Figure 12-31. Note that subsequent local migrations using Notes Upgrade Services are appended to this file unless you change the location where the migrated file is stored. If you are migrating several local Outlook .PST files, it might be useful to allow Notes Upgrade Services to append a_PersonalFolders.nsf so that all locally migrated Outlook data is located in the same .NSF file.
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
391
Figure 12-32 displays the Notes Upgrade Services dialog box populated with the template selection and personal folder location. Click Next. If you would like change your folder conversion options, click Previous to return to the previous dialog box.
Figure 12-32 The template name and folder have been selected
10.You are prompted to begin the upgrade. Click Finish to begin the migration using Notes Upgrade Services.
392
The dialog illustrated in Figure 12-34 displays, indicating that the migration process is in progress.
11.You are prompted, as illustrated in Figure 12-35, to enter the password that is associated with your Notes ID. Enter your Notes ID password, then click OK, and the migration process continues. Note: The Domino Administrator supplied you with a Notes .id file in preparation for installing the Notes Client. If you do not have a Notes .id file, see your Domino Administrator.
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
393
When the migration is finished, the dialog illustrated in Figure 12-36 displays.
You can open the results of the Notes Upgrade Service migration, which are located in the a_PersonalFolders.nsf file, from the Notes Client.
394
When warnings or errors are returned by Notes Upgrade Services, they are written to a log file, log.nsf, which is located in the data subdirectory of the Notes Client installation directory. A sample log.nsf file, shown in Figure 12-38, displays the messages that are returned by Notes Upgrade Services.
Figure 12-38 Notes Upgrade Services: Log entry in the log.nsf file
The entries in the Notes Upgrade Services log file provide information about what processes executed during the migration processing and any failures during the processing. These entries can help you determine whether the Outlook PST file contains faulty data that cannot be accessed during migration processing and can be particularly useful for the IBM Support teams if you report a problem with Notes Upgrade Services.
Chapter 12. Migrating local Outlook data using Notes Upgrade Services
395
In general, if Notes Upgrade Services returns a warning but the migrated data contained in the local .NSF file appears correct, there is no need to take action. However, if Notes Upgrade Services returns an error, we recommend the following actions: Attempt to repair the Outlook PST file by using a data repair tool to fix the problems that might exist with the Outlook data. If the Outlook data repair is successful, delete any existing .NSF file (a_PersonalFolders.nsf) that was created during the failed Notes Upgrade Services processing. If the Outlook data repair is not successful, contact your system administrator for assistance with troubleshooting the erroneous Outlook data file. Repeat the steps outlined in 12.4.1, Starting the migration on page 386.
396
13
Chapter 13.
Server Level migration process using Binary Tree Common Migration Tool
This chapter provides detailed instructions for setting up the Binary Tree Common Migration Tool and using it to migrate users from Microsoft Exchange to Lotus Domino from server to server. We explain in detail the setup, usage, and on-the-fly configuration, followed by some examples of the expected results that you can obtain when using the tool. The procedure to perform the client migration using the same tool is detailed in Chapter 14, Local data migration using the Binary Tree Common Migration Tool on page 437. Depending on your migration scenario, you might have to combine both procedures and set up the server and client migration parameters simultaneously.
397
398
13.2.1 Prerequisites
The following prerequisites must be in place to ensure that the migration process is as smooth as possible: A Lotus Domino server 7 or higher. A workstation with Lotus Notes 7 or higher. A Notes Client with an ID file that is a member of the administrators group and that has appropriate access to the Domino server. If the ID to be used is not the administrator, grant the ID editor access to the certification log database. Ensure the ID has been granted editor access, along with the group and the roles of GroupCreator, GroupModifier, UserCreator, and UserModifier to the Domino Directory for the organization. Add the ID to the Access Server field in the Domino Directory for all servers to which CMT will be migrating data. The ID should also sign all design elements of the CMT database through the Domino Administrator Client. For server-to-server migration: In the case of already created mail databases, the ID used for migration should have full Manager access to all target Lotus Notes mail databases. Ensure that a version of Outlook is installed on the workstation running CMT, with a profile that has Administration privileges to the Exchange servers from which data will be migrated.
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
399
3. Click Enter License Key and click Yes to accept the CMT agreement terms (Figure 13-1).
4. Enter the license key that is provided by Binary Tree and click OK (Figure 13-2).
400
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
401
You can move forward and backward through most of the windows by clicking the Next and Back buttons located at the bottom right-hand corner of the screens. There is also a Cancel button in that corner.
402
You begin with configuring the end-user settings: 1. Open the Database and click Configure EU Settings (Figure 13-3 on page 402). You are presented with the main source mail system selection window shown in Figure 13-4. By default, all supported mail systems are selected. You need to deselect the mail systems that are not required, leaving you with the mail systems from which you want to migrate.
When you have only the correct source mail systems selected click Next. Lotus Domino is selected as the target mail system by default. Note: Although no messaging client is selected in our example, you might decide to select the appropriate messaging clients from which to migrate. 2. You are required to enter information about the Domino mail system, such as the default directory server (using either the Notes Canonical format or the abbreviated hierarchical name), and the Domino directory file name (Figure 13-5). In addition, specify whether the mail database is to be migrated in the current mailbox on the server or locally into a separate mail database with the file name of your choice. Select the appropriate Mail Template Version to be used when creating the new mailboxes. Click Next to proceed. Note: If you choose to migrate to a new local copy, you need to create the local mail database before you start the migration. See Chapter 14, Local data migration using the Binary Tree Common Migration Tool on page 437.
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
403
3. The Outlook and Exchange Settings dialog box is where you provide information about the Outlook and Exchange systems, such as default migration contents (Figure 13-6).
404
The Settings dialog box provides the following options: Message types to migrate The CMT lets you select which message types are migrated. For example, you could choose to migrate mail messages but leave calendar entries untouched. As shown in Figure 13-6, we opted to migrate all data. However, you might decide that not all data is relevant for migration, so you can refine the selection. Message stores to migrate Migrate Exchange server data The user's mailbox and data are on the Exchange server. When you migrate Exchange server data, the user's mail and folder structure saved on the server is migrated. When you choose to migrate Exchange server data, you also have the option to migrate shared Exchange mailboxes. A shared Exchange mailbox is used by more than one user. To migrate shared Exchange mailboxes, select Migrate Shared Exchange Mail Boxes. Migrate personal folder data The data is local to the users machine or is stored on a network drive. It is in the form of a PST file. This data is not stored on the server. If there is more than one PST file, CMT migrates all of the files. Migrate personal address book data The data is local to the user's machine or is stored on a network drive. It is in the form of a PAB file. You might also decide that the only data that you want to migrate is calendar, messages, and contacts. Later, during the selection of users for migration, you can further refine the data selection by changing from the defaults and adding date ranges, so as not to migrate older data.
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
405
MAPI profile to use Unless you have created a single or default MAPI profile with administration access, you need to let users choose a specific profile with sufficient privileges for logging into Exchange. Migrate shared Exchange mailboxes Use the option to migrate shared mailboxes with caution because this data is used by more than one user and is only available if you have chosen to migrate Exchange server data. When this option is selected, the shared data displays in each users mailbox. It might be more appropriate to create a mail-in database into which to migrate the shared data and give the users that require this data access to it. Migrate to Notes systems folder Data from Exchange, by default, is migrated by the CMT into the top-level folder in Notes. The Exchange and Outlook folder structure is retained. All of the users' Exchange folders are placed under this top-level folder, and the relevant data and mail messages are stored within these folders. Thus, within the Notes users mail database, there are separate folders for Notes data and old Exchange data. By selecting Migrate to Notes system folders, data within the Exchange system folders (Inbox, Sent Items, Drafts, and Deleted Items) are migrated directly into the equivalent Notes system folders (Inbox, Sent, Drafts, and Trash). All other non-system Exchange folders are migrated to Notes. In other words, the folders appears under the Notes root-level folder structure and not under an Exchange top-level folder.
406
See the illustrations in Table 13-1 for a comparison of the option selections.
Table 13-1 Comparing the folder migration options
Folders migrated to Exchange Mail folders (default selection as shown in Figure 13-11 on page 411)
Migrate to Notes system folders option selected (Figure 13-11 on page 411)
Note: These figures illustrate where you can find the migrated folders and the corresponding content depending upon whether the Migrate to Notes system folders option is selected. (By default, the top-level folder name is Exchange Mail, but you can change this to suit your requirements as shown in Figure 13-11 on page 411.)
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
407
4. When you have completed your selections, click Next and you are presented with the next settings window (Figure 13-7). 5. The final settings dialog box allows you to provide information about top-level folders in the Exchange mail clients. If you did not select Migrate to Notes system folders (Figure 13-5 on page 404), all data that is migrated from Exchange is migrated under the top-level folder that is named. You also have the option to select which message classes to migrate. A message class is how a note is stored in Exchange. To specify which message classes to migrate, type in the message classes separated with a semicolon (;). A semicolon must also follow the last message class that you enter. To have all message classes and rich text migrated, use an asterisk (*) to reset message classes to default. The defaults are: IPM.Note.RFC822.MIME;IPM.Note.RFC822; Click Next and you are presented with the settings completion window.
6. Click Finish and you are returned to the CMT Database main view.
408
Note: It is possible to select pre-registered users from a Domino database. To add users into the CMT migration database: 1. Click Add Users and launch the corresponding wizard (Figure 13-8).
2. We opted to select our users for migration from Active Directory because our Exchange users are not registered to the Domino directory. Therefore, we selected Import from Foreign Directory Wizard (Figure 13-9). Click Run Wizard.
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
409
3. You are presented with a window where you select the source systems to import the users from (Figure 13-10).
We selected Exchange as the source system for directory information. The target Domino server and directory have been acquired automatically from the configuration information that we provided earlier. If the intended destination server is different, you can change it now. Select the mail template version 7.0. Click Next.
410
Here you have the option to specify the settings for the migration of users from the identified directory source and to override the default parameters set earlier. Select the type of data to migrate from the following choices: Mail items: All e-mail messages that a user has received. Calendar items: A user's calendar items. When re-occurring appointments in Outlook do not have a re-occurring end date, a re-occurring end date is created for them that is five years past the current year. For example, an appointment is on 01 August 2002 and reoccurs yearly but does not have a re-occurring end date. This date migrates to Notes as the same appointment but with a re-occurring end date of 01 August 2011 (with a migration performed on 01 August 2006). Journal: Journal entries made by a user. Task items: All tasks a user has entered. Contact items: Contacts in the user's address book. Note items: All notes a user has made.
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
411
CMT can migrate the folder structure from the source, as well as the data contained within. If you enter a top-level folder name here, all migrated data will be located in that folder structure, separate from the standard Notes folders. In our example, we used Exchange mail. We would, therefore, expect that the folder structure, and its contents from Outlook will be placed here in the migrated users mail file, unless we select Migrate to Notes system folders (see Migrate to Notes systems folder on page 406 and Table 13-1 on page 407). Select to use either the alias or name value when logging into Exchange: If you select Alias, CMT uses the unique ID for each user to access each users mail store. Using the alias is recommended because it is unique to each user. If you choose Name, CMT uses the users last name, first name, and middle initial to access the mail store. This option is not recommended because the incorrect mail store could be accessed when users have similar names.
If you want rich text format (RTF) data to be migrated, click Migrate Rich Text Format (RTF) when available. If you select Create Exchange distribution lists in Domino Directory at registration time, you are telling CMT that you want it to create the distribution lists in which the individuals being registered by CMT belong. (An additional dialog box appears during this preliminary phase. See Figure 13-28 on page 423.) Note: The groups are migrated only when the individuals are registered to the Domino directory with CMT. If individuals are not registered with CMT, the groups to which they belong are not created. If you select Attempt to resolve names, CMT attempts to resolve names in the contacts list and e-mail messages to the counterparts in the Domino directory. As per recommendation, we used the alias profile for logging into Exchange.
412
5. Click Next. The dialog box that is returned gives you the option of further limiting the amount of data that is migrated by specifying date ranges for several types of data (Figure 13-12 and Figure 13-13 on page 414). Also, you can define rules for a finer tuning (Figure 13-14 on page 415 through Figure 13-20 on page 418).
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
413
Specify start and end dates. Only the data within the specified range is migrated to Domino. 6. Make your data selections and click Next.
414
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
415
2. Select the appropriate options as required to match your server-to-server migration requirements (Figure 13-15). As an example, you can decide to migrate mails received from 01 January 2000 to 31 December 2005 into an archive, with all mails received from 01 January 2006 moved into the active mail file. Mails received before 01 January 2000 are not migrated. Additionally, all appointments within the same date ranges are migrated to the same databases accordingly.
416
4. Select your next set of mail parameters and click Insert Rule (Figure 13-17).
5. Select the appointment migration parameters (Figure 13-18 and Figure 13-19). After you are done with your set of rules, click OK.
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
417
6. Click Next to proceed with the Add Users configuration settings (Figure 13-20).
418
7. You are presented with the Exchange User Filter window (Figure 13-21). The options are: Select all users in GAL Select GAL users from list Select only users from one Exchange Home Server If you select a particular server that you are required to specify the name, and only users from this server are available for selection.
The other two options are to import the entire GAL or to select from currently imported users. If this is the first time that you are doing the migrations, you should opt for Select all users in GAL. Note: The purpose of import of users is to create CMT person documents in the CMT database that is used for registration and migration. This does not add users to the Domino Directory. Rather than import all the users and to show additional options, we opted to select users from the GAL. Click Next to proceed. Depending on the option that you choose, you are presented with either the Exchange User Selection window (Figure 13-22) or the Import Users window (Figure 13-29 on page 423). If you selected to import all users, go to step 15 on page 423.
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
419
9. You are requested to select a MAPI profile (Figure 13-23). Ensure that you have set up a MAPI profile as mentioned in 13.2.1, Prerequisites on page 399. If not, you have to cancel the process, build the profile, and start the Add Users wizard again. Ensure that the selected profile has administrator privileges. Otherwise, you will not be able to access either the Global address list or, during migration, the user data to migrate. Click OK to select the profile.
420
10.You are prompted for a password. If you are not logged in to the NT Domain, you are presented with a window asking for the logon credentials for the Domain. Enter the required information and click OK. Importing users batch starts. A status window displays while the import is running (Figure 13-24).
11.When the import has completed you are presented with a screen that informs you of the number of successfully imported users. Click OK.
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
421
12.You return to the select users window, similar to the one shown in Figure 13-22 on page 420. This time, click Select users from Exchange user list. You are be presented with a list of users (Figure 13-26).
Note: If you selected to import distribution lists (Figure 13-21 on page 419), the selection dialog box appears as shown on Figure 13-27.
Distribution list
422
13.Select the users to import and click OK. The users are added to the import list. 14.If you selected to import distribution lists (Figure 13-21 on page 419), the window shown in Figure 13-28 displays. Specify settings that are related to the importing of the distribution lists and click Next. (In our example, we are using the same database where the Exchange users are listed and the group names are identified with the EXC prefix.)
15.The final step is to import users into the CMT database. Click Import Users from Exchange (Figure 13-29).
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
423
16.When the import is complete, you are presented with a message box that informs you of how many users have been successfully imported (Figure 13-30). Click OK.
17.The import users window remains on your screen. Click Next. 18.A message displays that informs you that you have finished importing users. Click Finish, and you are returned to the database main view (Figure 13-31).
424
You can verify that the users you have just imported are ready for registration into the Domino directory from the Registration view or from the Server Migration view (Figure 13-32).
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
425
2. This time, select Register to Domino Directory Wizard in the Add Users dialog box. Click Run Wizard to start. (Figure 13-33).
426
4. Complete all the fields, following these guidelines: a. It is advisable to enter the servers IP address. b. In a single server environment the mail server, template server, and registration server are the same. This might or might not be the case in a multi-server scenario. Ensure that you enter the correct server names in the fields. c. The standard mail template file for Domino 7 is Mail7.ntf. d. We recommend that you select the unlimited file name format. Tip: The file name format setting controls the format of the short name. Specifying Unlimited uses the short name (which is unique) as the name of the user's mail file. Choosing 8.3 sets a mail file name that is eight characters long. If you choose 10.3, then the mail file name is 10 characters long. e. If it is required (mostly during the pilot project), add the mail administrators group in the administrators field. This adds the mail administrators group to the ACL of the mail databases. Remember to remove this group after you start your full deployment! f. In the Local Admins field, enter the names of the administrators or groups who need administrator access to the users person documents in the Name and Address Book (NAB) after they are registered. The format must be: administrator's name/mail server. Separate each administrator with a comma (,). The default is the localadmins group. g. You also have the option to generate a random password or use a default password. If you select default, be sure to enter a password in the default password box. Attention: Passwords are saved in the CMT person document. h. Set the complexity of the password that users must use when changing the password. Values range from 0 (weak) to 16 (complex). i. If you want to create an Internet password for the user, select Set internet password.
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
427
5. Click Next to proceed to the second registration settings screen (Figure 13-35). Enter the location of the certification ID, the certification log, select the relevant security type, and complete all other fields. You also have the option of adjusting the format of the Internet address that is created and the location to store the created ID file.
6. Click Next. You are prompted for the certifier ID password. 7. Enter the password and click OK. The Select People window opens.
428
8. Click Select Users. You are presented with a list of users who are flagged ready for registration from the CMT database (Figure 13-36). Select the users who you want to register.
9. When you have selected all the required users, click OK to close the dialog box, and then click Register Users (Figure 13-37). The selected users are now registered.
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
429
A status bar displays during registration (Figure 13-39), followed by the completion message (Figure 13-40). Take note of and follow up on any errors. For further assistance in case of errors, refer to 13.4, Troubleshooting the migration on page 434.
430
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
431
CMT provides an easy to use wizard for migration. As with a manual migration, the migration wizard only allows you to select users from the CMT database that are in the correct status. To migrate server data: 1. Click Server Migration and launch the corresponding wizard from the main database view (Figure 13-42).
2. You are presented with the list of users who are ready for migration. You have the option to migrate all users or select the users for migration. If you select all users, the wizard attempts to migrate all users who are in the relevant status noted previously, meaning it does not attempt to migrate all the Exchange users in the GAL.
432
3. Select all users who are listed or some of them, and click OK (Figure 13-44).
4. Select a MAPI profile and click OK (Figure 13-45). Note: Be sure that you have set one up as mentioned in the 13.2.1, Prerequisites on page 399. If not, you have to cancel the process, build the profile, and start the wizard again. The selected profile must have administrator privileges. Otherwise, you will not be able to access either the GAL or, during migration, the user data to migrate.
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
433
The migration begins and a status screen displays its progress (Figure 13-46). Depending on the amount of data and speed or bandwidth of the network, the migration can take a fair amount of time.
During the migration process, you have the option to suspend and resume the migration. This option is useful; however, our testing did not result in either a failed migration or migration with errors. The option is useful if you need to suspend the process due to resource constraints. The option to cancel is also available. 5. A completion notice displays when the migration is complete (Figure 13-47). Take note of and follow up on any errors. For further assistance in case of errors, refer to 13.4, Troubleshooting the migration on page 434. Click OK.
434
failure, open the CMT database and click Registration. A list of users and their status displays (Figure 13-48).
Select and open the failed users document, which is in the Failed registration category. A migration information section is at the bottom of the document. The cause of the error displays in this section (Figure 13-49).
Chapter 13. Server Level migration process using Binary Tree Common Migration Tool
435
436
14
Chapter 14.
Local data migration using the Binary Tree Common Migration Tool
This chapter provides the details for a client side migration using the Binary Tree Common Migration Tool (CMT). You can use these instructions along with the latest release documentation that is available from Binary Tree.
437
438
2. Select Outlook and click Next (Figure 14-2). You have the option to select multiple mail sources. In the case of most migrations (in which you are also migrating server side data), you would most likely select the server-based migration as well.
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
439
3. In the Domino Directory Settings window (Figure 14-3 on page 441), enter the following information for the destination mail system: Domino Directory Mail Server This is the name of your primary Domino server. Domino Directory Filename In all cases, this name is names.nsf. Personal Address Book In most cases, a personal address book is also called names.nsf. This database is the local contacts directory. Target mail database You have the option to import your data into either the current mail database, in which case the imported data is replicated to the Domino server, or a separate local database. If you select local database, you are prompted for the name of the database. Ensure that you have already created the database. TIP: To create a mail database for migration: 1. 2. 3. 4. 5. 6. Select File Database New. Select Server Local. Select Title My Exchange Mail (any unique name) Select filename myexchange-mail.nsf (any unique name) Select the extended mail template: mail7ex.ntf. Click OK.
Mail Template Version For migration to Domino 7, always use the 7.0 template.
440
7. Select the data to migrate (Figure 14-4 on page 443). The CMT gives you the option to be granular on the information that you migrate from the local PST file into your Domino mail file. In our example, we migrated all the data. You can choose from the following types of data to migrate: Message types to migrate The CMT lets you select which message types are migrated. For example, you could choose to migrate mail messages but leave calendar entries untouched. Message stores to migrate Migrate Exchange server data The user's mailbox and data are on the Exchange server. When you migrate Exchange server data, the user's mail and folder structure saved on the server are migrated. When you choose to migrate Exchange server data, you also have the option to migrate shared Exchange mailboxes. A shared Exchange mailbox is used by more than one user. To migrate shared Exchange mailboxes, select Migrate Shared Exchange Mail Boxes.
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
441
Migrate personal folder data The data is local to the users's machine or stored on a network drive. They are in the form of a PST file. This data is not stored on the server. If there is more than one PST file, CMT migrates all of them.
Migrate personal address book data The data is local to the user's machine or is stored on a network drive. It is in the form of a .PAB file. You might also decide that the only data that you want to migrate is calendar, messages, and contacts. Later, during the selection of users for migration step, you have the ability to further refine the data selection by changing from the defaults and adding date ranges, so as not to migrate older data.
MAPI profile to use Unless you have created a single or default MAPI profile with administration access, you should select Let users choose profile to ensure that a profile with sufficient privileges for logging into Exchange can be chosen. Migrate shared Exchange mailboxes Use the option to migrate shared mailboxes with caution because this data is used by more than one user and is only available if you have chosen to migrate Exchange server data. When you select this option, the shared data appears in each users mailbox. It might be more appropriate to create a mail-in database into which to migrate the shared data and give the users who require it access to it. Migrate to Notes systems folder Data from Exchange, by default, is migrated by the CMT into the top-level folder in Notes. The Exchange and Outlook folder structure is retained. All of the users' Exchange folders are placed under this top-level folder, and the relevant data and mail messages are stored within them. Thus, within the Notes users mail database, they will have separate folders for their Notes data and old Exchange data. By selecting Migrate to Notes system folders, data within the Exchange system folders (Inbox, Sent Items, Drafts, and Deleted Items) are migrated directly into the equivalent Notes system folders (Inbox, Sent, Drafts, and Trash). All other non-system Exchange folders are migrated to Notes. In other words, the folders appear under the Notes root-level folder structure and not under an Exchange top-level folder.
442
8. When you have completed your selections, click Next and you are presented with the settings screen shown in Figure 14-5. 9. Enter details about the messages to migrate and the location in the Domino mail file.
In the previous configuration step, you had the option to select whether migrated messages are stored in the Notes system folders. If you did not select this option, then these settings allow you to provide information about the top-level folder to which all data is migrated from Exchange.
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
443
You also have the option to select which message classes to migrate. A message class is how a note is stored in Exchange. The default is an asterisk (*) , which means that all messages are migrated. Tip: We recommend that the message class setting remains as the default. To specify which message classes to migrate, type in the message classes separated with a semicolon (;). A semicolon must also follow the last message class that you enter. Click Next. Step 1 is complete (Figure 14-6).
444
When you start the wizard, you first select your trigger method (Figure 14-8). You can trigger a migration either through an e-mail message or automatically on mail database open.
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
445
These two options give you additional configuration options. If you select to e-mail the migration button, you can use the standard e-mail, or you can select to create a customized e-mail. In both cases, the users are sent a button that launches the local migration wizard. If you select to automatically trigger migration on database open, this option launches a wizard that generates LotusScript code that needs to be added to the migrated users mailbox. The script checks for local data and adds the data automatically to the users mail database.
446
You can use tags to enter information from the CMT person form in your message (Figure 14-10).
You can open a selection box by clicking View Tag List (Figure 14-11).
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
447
Table 14-1 lists a detailed description of each of the field tags that are available.
Table 14-1 Description of field tags Tag <!-Subject-> <!-SendTo-> <!-MigrateTo-> Description Subject of the message Who to send the migration message to Migration Platform to migrate to The full name stored in the user's person document Target mail system, located on the General Settings tab of the Settings document The date the mail message was sent Defined on the CMT person document under the End User Migration info section Defined on the CMT person document under the End User Migration info section AllowedProducts corresponds to the Allowed Products on the User's person document Corresponds to the custom help text used in the standard migration document Remarks
<!-DeliveredDate-> <!-StartDate->
Date the migration message was sent to the user Start Date for the user to begin their migration (also the date range the 'Start Migration' button to trigger migration is valid) End Date for the user to finish their migration by (also the date range the 'Start Migration' button to trigger migration is valid) The products the users is allowed to migrate Person to contact if the migration encounters a problem
<!-EndDate->
<!-AllowedProducts->
<!-HelpContact->
448
2. Select Start trusting the signer to execute this action and click OK (Figure 14-13).
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
449
4. The Wizard launches. Select Next. 5. You are presented with a prompt screen to store the Created instructions and DLL file (Figure 14-15). To change the location, enter or browse for the location and file name for the generated script. After you locate the file, click Next.
Figure 14-15
6. A screen with the instructions and the code to enter into the Mail database template is presented (Figure 14-16). This is the piece of generated LotusScript that you must insert into the mail template. By default, the code is generated in the Windows temp directory. The custom code is written to a file and displayed in the wizard screen.
450
Click Next.
7. Click Finish.
After the custom script is generated, you need to start Lotus Notes Designer and Open the mail file template. Next, open the output file that is created by the CMT and follow the instructions to complete the mail template customization. (The instructions are included in a comment section of the generated LotusScript code, with the user specific %INCLUDE.)
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
451
Run the load design task to refresh the design of all user mail databases so that they contain this script. Finally, the migration is done automatically when a user opens a mailbox for the first time.
452
To add users, perform these steps: 1. If not already done so, open the CMT, and select Add Users (Figure 14-19).
2. You are presented with a screen for the users source directory (Figure 14-20). Because we want to migrate users local data from Outlook PST to Domino NSF, the users should already be in Domino, whether this be by migration or default registration. Therefore, the directory source for this migration is Domino Directory. So, select Import from Domino Directory Wizard and click Run Wizard.
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
453
3. Select All people in Address Book and click Next (Figure 14-21).
4. Click Import User from Domino NAB and click Next (Figure 14-22). Note: The size of your Domino directory determines the length of time this process takes. In our lab exercises, we maintained a small directory, and the process finished very quickly. Unfortunately, you do not get a finish indicator and have to wait for the cursor to be released.
454
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
455
456
2. When you click End User Migration, you are presented with a list of users who are registered in Domino and have Domino mailboxes. You can select multiple users by clicking next to their names. Selected users are represented with a checkmark.
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
457
3. Click Actions Send Selected People Migration Doc (Figure 14-26). Messages that contain the migration button are sent to the users.
458
4. By opening the person document (as shown in Figure 14-27) in CMT, you can review when the users were sent the message, which can also be used as an alternative method to send the migration message or even resend.
5. The user receives a message similar to that shown in Figure 14-28 in the Notes inbox.
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
459
6. Click Start Migration. The migration begins, and a status message displays as the migration progresses, as shown in Figure 14-29.
460
7. When the migration is complete, the user is presented with the migration complete message shown in Figure 14-30. Click OK in this message.
Migration document
The users migration document is updated in the CMT directory, and the administrator can check the status. Figure 14-31 shows a sample.
Various details about the user migration are recorded and can be very useful for both troubleshooting and planning of further deployments.
Chapter 14. Local data migration using the Binary Tree Common Migration Tool
461
Tip: We noticed during our testing, that if we selected in the end user setting of the configuration, the user migration migrates both local and server data if the server migration has not already completed. This function of the CMT can be useful in distributing the responsibility of the data migration to the user and restricting the window of opportunity for the period available to the user for migration, thus helping to plan the migration load.
462
15
Chapter 15.
Migration results
This chapter provides a review of the migration results of a users data. It provides an understanding of how a representative set of data will appear when migrated from Exchange to Domino. The format for the comparison is that the pre-migrated image comes first, the DUS migrated image second, and the CMT image is displayed third. The migration tools are configured and run with the suggested defaults to give an understanding of the capabilities of these tools. This chapter deals with the migration results that are obtained with the Domino Upgrade Services (DUS) and CMT from Binary Tree for the following items: Inbox folder migration Mail message conversions Calendar entries Contacts Tasks and To Do
463
15.1.1 Inbox
Figure 15-1 illustrates a message in the Outlook client, pre-migration from Exchange. The user is able to scroll messages and preview a message in the preview pane in the Outlook client.
464
As shown in Figure 15-2 and Figure 15-3, both DUS and CMT convert the inbox and its contents. The user has access to functionality similar to that available in the Notes client. Figure 15-2 illustrates the inbox view using the DUS migration tool. Similar to the Outlook feature, you can preview the body and contents of the message.
Figure 15-3 illustrates the Inbox view using the using the CMT migration tool.
465
HTML messages
The first object is an HTML message. It is quite likely that Outlook users have sent URLs to guide other users to Web pages. Alternatively, the messages sent might exist as HTML content or, typically, as newsletters for your company that go out to users as HTML pages. Figure 15-4 illustrates a message in HTML format, beginning with how it appears in Outlook, pre-migration.
466
Both tools (DUS and CMT) convert the HTML message fairly well and very similarly. The message retains its functionality; however, some of the formatting is lost during the migration. Figure 15-5 illustrates the migrated message, which contains HTML content, using the DUS migration tool.
467
Figure 15-6 illustrates the same message after it has been migrated using the CMT migration tool. Note: You might also want to refer to the test results discussed in Chapter 10, Coexistence test results: What to expect on page 315 to see the results of embedded HTML messages sent between the two environments.
468
469
DUS does not convert the embedded object at all, as shown in Figure 15-8.
470
CMT converts embedded objects into images in attachments and includes them as attachments to the message. After the migration, the Excel graph is not editable in Notes; however, you are able to view it in Notes, as shown in Figure 15-9.
If your users have created embedded objects and you need to bring them or maintain them in a fully functional state from Outlook to Notes, you might need to look into other solutions. (See Appendix A, Other migration tools on page 707) for possible other solutions. ) Alternatively, one technical solution would be to convert the objects into attachments before migration. This could be automated programmatically, for example, by writing a Visual Basic script to iterate through mail messages, creating attachments. There might also be third-party applications that will do this.
471
472
Again, similar to the results with the embedded graph, DUS does not convert the embedded object at all, as shown in Figure 15-11.
473
CMT converts embedded objects into images in attachments and includes them as attachments to the message (Figure 15-12). After the migration, the Excel worksheet is not editable in Notes; however, you are able to view it in Notes.
474
Both DUS and CMT converts the table correctly, maintaining the text inside the table as well as the formatting of the table.
475
Figure 15-14 illustrates how the table translates using the DUS Migration tool.
476
Figure 15-15 illustrates how the table translates using the CMT Migration tool.
477
Both DUS and CMT converted the URL properly and placed the attachment at the bottom of the message.
478
DUS loses the graphic from the signature, as shown in Figure 15-17.
479
CMT places the graphic from the signature as an attachment at the bottom of the message, as shown in Figure 15-18.
480
481
Figure 15-20 illustrates that the meeting migrated successfully using the DUS tool.
Figure 15-21 illustrates that the established meeting also migrated successfully using the CMT migration tool.
482
Calendar Entry
This section illustrates, in slightly greater detail, how a specific Calendar entry appears after migrated. Figure 15-22 illustrates the Outlook calendar entry, before migration.
483
Figure 15-23 illustrates that the Calendar Entry migrated successfully using the DUS tool. All data is maintained.
484
Finally, Figure 15-24 illustrates how the Calendar Entry appears in Notes when migrated using CMT. As with DUS, all data is maintained.
485
15.3 Contacts
This section shows the results of the migration of contact information from Outlook to Notes using both DUS and CMT. Although the contacts and the contacts view look a bit different in Notes than in Outlook, the data has been converted correctly and similar functionality is available for users in Notes. Figure 15-25 illustrates the view of Contacts from within the Outlook client.
486
For the DUS migration option, DUS migrates contacts as part of the users mail file into the ($users) view. To add the contacts to the local names.nsf, the user selects Actions Synchronize Address Book from the menu bar. Figure 15-26 shows the results of the Contacts view using DUS (($Users) View: DUS). This is the first step.
487
After the user then performs the action to add the contacts to the local names.nsf, (namely the user selects Actions Synchronize Address Book from the menu bar), the results appear similar to those shown in Figure 15-27.
488
CMT migrates contacts as a separate .ns4 file. The user who was migrated receives an e-mail with the subject Contacts from Exchange. This e-mail contains the .ns4 file and a button titled Insert Contacts. To add contacts to local names.nsf, click the button. Figure 15-28 illustrates an e-mail that contains the .ns4 file and the Insert Contacts button.
489
After the user clicks Insert Contacts, the local name and address book in Notes is populated, as shown in Figure 15-29.
490
491
Figure 15-31 shows the same set of tasks, now referred to as To Dos in Notes, after they have been migrated using the DUS tool.
Finally, Figure 15-32 illustrates the results of the migration of tasks, this time using CMT. The tasks were brought over successfully into Notes. You can view and manipulate them through the To Do list.
492
Part 5
Part
Directory considerations
493
494
16
Chapter 16.
495
496
some users are using a Domino mail client on the Domino server, while other users remain on the Exchange server using the Outlook client. Non-migration coexistence Exchange users are registered on the Domino server, but neither the users nor their data are migrated from Exchange to Domino. In order for users in these scenarios to find each other from their respective Domino or Exchange environments, the following components must be completed: The Exchange server directory must be LDAP enabled. The LDAP service must be enabled and configured on the Domino server directory. An LDAP account needs to be created in the users address book An additional address book needs to be added to the Outlook profile
497
can contain spaces and hyphens. The value of the attribute would be the person's telephone number. A directory entry describes some object. An object class is a general description, sometimes called a template, of an object, as opposed to the description of a particular object. For instance, the object class person has a surname attribute, while the object describing John Smith has a surname attribute with the value Smith. The object classes that a directory server can store and the attributes they contain are described by schema. Schema define what object classes are allowed where in the directory, what attributes they must contain, what attributes are optional, and the syntax of each attribute. For example, a schema could define a person object class. The person schema might require that a person have a surname attribute that is a character string, specify that a person entry can optionally have a officePhoneNumber attribute that is a string of numbers with spaces and hyphens, and so on.
498
LDAP defines operations for accessing and modifying directory entries such as: Binding and unbinding Searching for entries meeting user-specified criteria Adding an entry Deleting an entry Modifying an entry Modifying the distinguished name or relative distinguished name of an entry (move) Comparing an entry
499
The Lotus Domino Server window shown in Figure 16-1 opens, allowing you to choose whether to start Domino as a Windows application or a regular application.
Figure 16-1
If you choose to start Domino as a Windows service, the LDAP service is enabled by default. If you choose to start Domino as a regular application, you need to enable LDAP explicitly during the Domino setup process. 3. Proceed with the Domino setup, and configure your server settings as outlined in Appendix F, Installing Domino on page 801until you are presented with the Server setup dialog box that prompts you to select the Internet services for your Domino server. As mentioned in the previous step, if you elected to start Domino as a Windows service, LDAP is enabled by default. If you do not, select to enable LDAP (Figure 16-2 on page 501).
500
4. Finish the server installation, and the Domino server is configured for LDAP directory enablement.
501
502
503
9. Use the command tell adminp process interval to force processing of the Set Directory Assistance Field request, or wait until the Administration Process processes the request when it next processes interval requests. 10.Replicate the modified Domino Directory to the servers that will use the directory assistance database. 11.Restart the servers so that they detect the directory assistance database file names in their Server documents.
16.3.1 Entering the directory assistance database file name to a Server document manually
Follow these steps to enter the directory assistance database file name to a Server document manually: 1. Make sure that you: a. Created and replicated the directory assistance database. b. Have either Author access and the ServerModifier role, or Editor access in the ACL of the Domino Directory to which you will add the file names. 2. From the Domino Administrator, click the Configuration tab. 3. Next to "Use Directory on," select the server whose Domino Directory you want to modify. 4. In the left-hand pane, choose Server - All Server Document. 5. Select a specific Server document, and then click Edit Server. 6. In the Directory Assistance database name field in the Directory Info section on the Basics tab, enter the file name that you gave to the replica of the directory assistance database on this server (for example, DA.NSF). If the directory assistance database is in a subdirectory under the data directory, include the path relative to the data directory (for example, DIRECTORIES\DA.NSF). 7. Click Save & Close. 8. If the Domino Directory that you changed is not the replica of the server whose directory assistance database file name you specified, replicate the updated Domino Directory to the server. 9. Restart the server so that it detects the directory assistance database file name now in its Server document.
504
505
2. Select the Address Books tab and select New (Figure 16-4).
506
3. Select Internet Directory Service (LDAP), which is the default option, and click Next (Figure 16-5).
507
4. Enter the server name of the directory server. This name can be either the host name or the FQDN of the Domino server. Click More Settings. (Figure 16-6)
508
5. On the Connection tab, enter a Display Name for the address book, for example Notes users, as shown in Figure 16-7. We left ours as the server name.
Note: By default, the port value should be 389. Unless you have changed this in Domino, do not change this value.
509
6. On the Search tab, you can specify a search string (Figure 16-8). Domino has a default base, so there is no requirement for you to enter the Organization as a search base.
7. Click OK.
510
The LDAP address book has now been added to the Outlook profile, and the Domino database is now searchable from Outlook, as illustrated in Figure 16-8.
511
512
Searching an address book for certain attributes If you do not know the mail address of the person for whom you are searching, you can find an address in the Domino directory by searching an address book for certain attributes that you do know about that person (such as firstname). a. From Outlook, select Tools Select Address Book. b. Click the twisty in the Address Book tab and select the newly created address book (Figure 16-11).
513
Enter any of the attributes for the person for whom you are looking. In our example, we used the first name and returned one value (Figure 16-12). In the event of multiple attributes, all accounts with the value that you type in any field are displayed.
514
515
3. On the Basics tab: a. Enter a descriptive name for the account, for example Exchange or the server name. b. Enter the FQDN of the Active Directory Global domain controller in our lab this was the same as the Exchange server. c. If needed, enter a user ID and password for the bind. By default, this field is not required. d. Leave all other fields as the default.
4. On the Protocol Configuration tab, enter the Search base (Figure 16-16). In our example, the Active Directory Organization Forest for the Exchange users was ITSO1, so we entered DC=itso1. All other fields can remain as is.
516
5. On the Advanced tab, specify the port (Figure 16-17). In most organization the LDAP port (non SSL) is set at 389 by default.
6. Click Save & Close. 7. To test the configuration as with Outlook, open another directory from the address book by clicking Directories on the top selection bar (Figure 16-18).
517
8. Select the recently created directory and enter a search term. Here, we enter a first name (Figure 16-19).
Figure 16-20 shows the results that were returned. You can see additional details about the returned entry by clicking Details. Finally, Address book lookups are also possible when sending e-mail by clicking the To: button in the new memo.
518
17
Chapter 17.
519
520
During the coexistence of Domino and Exchange, with Active Directory as part of the IT infrastructure, without ADSync the IT Administrator would be required to maintain two separate directories. Figure 17-1 offers an illustration of the early coexistence scenario before the implementation of ADSync. Without ADSync to manage users in both the Domino directory and Active Directory, users on the respective directories must be managed separately.
Default Domino Installation Early stage of a migration
Authentication
Users
521
With the introduction of ADSync into the infrastructure, users and groups in the Domino directory and Active Directory are administrated centrally in Active Directory. Figure 17-2 illustrates the role ADSync plays in allowing central management of users in the Domino directory and Active Directory. In this illustration, the blue shaded area represents directory management where users exist in both Active Directory and the Domino directory, with all changes being made in Active Directory and replicated automatically to Domino.
With AD Sync AD Sync for user and group management
Active Directory
Domino Directory
MS Exchange
Authentication
Users
Figure 17-2 ADSync for users and groups in Active Directory and the Domino directory
Note: ADSync is included in the Domino installation, and the Microsoft Windows operation system is not a prerequisite for the Domino server. The following sections outline likely coexistence scenarios and illustrate how you can use ADSync in conjunction with LDAP enablement to manage users in both the Domino directory and Active Directory.
522
created. ADSync allows the IT administrator to manage users who still reside in Exchange as well as users who have migrated to Domino, from one central location.
Using LDAP for directory lookups
Active Directory
Domino Directory
MS Exchange
Authentication
Figure 17-3 Domino and Exchange coexistence, using LDAP for directory lookup
523
Domino Directory
MS Exchange
Authentication
Users
Figure 17-4 LDAP lookups for users in Active Directory but not in Domino Directory
524
Active Directory remains after coexistence and the removal of Exchange LDAP directory lookup
Active Directory
Domino Directory
MS Exchange
Authentication
Users
525
After installing the Domino Administration client, start a DOS command prompt window, and navigate to the directory where you installed the client. Type the following command and press Enter: $c:\Program Files\Lotus\Notes> regsvr32 nadsync.dll The command adds a container entry for Lotus Domino Options to the Active Directory Users and Computers management screen and returns the confirmation shown in Figure 17-7. You are now enabled to administer groups and users in Active Directory.
Figure 17-8 Active Directory Users and Computers: Lotus Domino Options
526
2. Double-click the entry for Domino Directory synchronization in the results panel to initialize the Lotus ADSync tool and to synchronize Active Directory with the Domino Directory. You are prompted to enter the Domino Administrator ID and the Domino Administrator ID password for the Domino server to synchronize with Active Directory, as illustrated in Figure 17-9.
3. You are prompted to select a Domino server for all Active Directory and Notes user synchronizations, as shown in Figure 17-10. Select the appropriate Domino server from the drop-down selection box.
4. Click OK. If the synchronization is successful, the success message that is shown in Figure 17-11 displays.
527
5. Double-click the Domino Directory synchronization entry to display the Lotus ADSync Options window (Figure 17-12).
From the Notes Synchronization Options tab, make the following selections: Enable or disable all synchronization operations Customize synchronization options with "Select synchronization operations to enable" Configure prompting options from the drop-down selection box Choose to use the CA process for user registration
528
6. Select the Notes Settings tab to display the notes settings for Lotus ADSync, as shown in Figure 17-13.
On the Notes Settings tab, specify: Registration server (which Domino server will be used for registration). Administration ID (which user ID has administrative privileges). User deletion options. From the drop-down selection box, you can choose which actions should take place when a user is deleted. Default certifier and policy. Group type mappings.
529
7. Select the Field Mappings tab (shown in Figure 17-14) to specify which Active Directory fields to map to Domino Directory fields. During ADSync tool initialization, the schemas from Active Directory and Domino are mapped based on default settings. If additional field mappings are needed, left-click in the right column under "In Domino Directory" and a drop-down selection box with Domino directory fields displays.
8. Select the Container Mappings tab, shown in Figure 17-15 on page 531, to map Active Directory containers to Notes Certifiers and Policies. Active Directory containers are a special class containing both a namespace and attributes. The container does not represent anything real or concrete, but rather holds one or more objects. Objects, on the other hand, are the underlying principle of everything in the Active Directory. Servers, workstations, printers, users, documents, and devices all represent objects. Each object has its own access control list (ACL) and attributes.
530
By design, the synchronization tool allows you to preserve the hierarchies in Active Directory and Domino using mapping. You can select a specific container to map to a certifier or a policy. You can restrict access to a directory structure (container, object, and so forth) with group policies in Active Directory just as you can use the extended access control list in Domino to issue restrictions. An extended ACL is an optional directory access control feature available for the Domino Directory, an Extended Directory Catalog, and the Administration Requests database.
531
While the Domino Directory and Active Directory are synchronized, a user can have certain rights in one directory and not the other. ADSync does not ensure that Active Directory group policies and Domino extended access control lists are synchronized. Therefore, the administrator is responsible for ensuring no security settings are bypassed in either directory. In this example, we selected the container root, the domain controllers, and the Users container. In addition to the container that you want to associate with a certifier, double-click in the Notes Certifier column to see your selection choices. Select the appropriate certifier and click OK to continue.
532
2. Select Register in Domino and the Choose Registration Options dialog shown in Figure 17-17 on page 534 displays.
533
3. Select the appropriate registration options for this user, then click Register Now. The dialog illustrated in Figure 17-18 displays, prompting you to select the Notes certifier and the Notes policy for this user. You must select a Notes policy from the drop-down list.
534
4. After you have specified a certifier and registration policy for the Active Directory user that you are registering in Domino, click OK to register the Active Directory user in the Domino Directory. The success window shown in Figure 17-19 displays, which indicates that the registration process has completed.
535
Figure 17-20 Active Directory Users and Computers: Actions: Add new user
536
2. The New Object - User dialog displays (Figure 17-21). Complete the user name fields, including the user logon name. Click Next.
schase
schase
3. The dialog box shown in Figure 17-22 displays. Enter the password for this new user, ensuring that it meets the security standards for your IT infrastructure. Also, select the password settings for this user. Click Next.
537
4. Because we are migrating to Domino, the check box next to Create an Exchange mailbox should not be selected (Figure 17-23). Click Next.
5. Register the new user in the Domino directory (Figure 17-24). We recommend that you select this check box, so that the new user exists and is accessible in both Active Directory and the Domino Directory. We also recommend that you select Use common password, because setting one password for Windows and Notes is most convenient for the user. Fill in the password fields and set an explicit policy for this user (a requirement for this dialog). Select Next.
Sarah
schase
schase
538
6. You are prompted to enter the Certifier ID and password for the Domino server on which this user is registered (Figure 17-25). Select OK.
Figure 17-25 Enter certifier ID and password for the Domino server
7. A confirmation window displays (Figure 17-26). Notice that the new user is added to the Domino directory as well as the Active Directory. Click Finish.
539
8. A Lotus ADSync dialog displays confirming that the new user has been registered in Notes (the Domino Directory). Click OK.
540
Figure 17-28 Select the user to delete, then select Delete from actions list
541
2. Delete the users mailboxes on Exchange or Domino (Figure 17-29). We recommend deleting the users mailboxes on either server where they are present to conserve disk space. Click Yes.
3. The message shown in Figure 17-30 displays, confirming that the user has been deleted from the Domino directory, as well as from Active Directory.
542
Sarah
Sarah Chase
543
2. On the General tab, add the required information to the users record and click OK. In this example, shown in Figure 17-32, we added a phone number for this user.
Sarah
Sarah Chase
3. Because the Domino Directory and Active Directory are synchronized, you have the option of updating the Domino Directory with the changes made to this user. Click Yes to update the users record in the Domino Directory (Figure 17-33).
544
If you open the Domino Directory that contains this user, you find that the users record has been updated with the changes that you made in Active Directory. Figure 17-34 illustrates the Domino Directory entry for Sarah Chase, updated with a phone number.
Sarah John
Figure 17-34 Domino Directory record, updated with the Active Directory changes
545
2. On the right-side of the screen, select Register Person. You are prompted to enter the Notes Certifier ID file, as illustrated in Figure 17-36 on page 547. Select the appropriate certifier file to be used, supply the certifier password and click OK.
546
3. When the Register Person dialog displays, complete the information for the new user, including any policy setting and password options. Figure 17-37 illustrates the Register Person dialog with all fields completed. Ensure that the password options for this user comply with your IT infrastructures security policy.
547
4. Select the Advanced check box to display the Advanced registration options. Complete the information appropriate for your organization in the Mail, Address, ID Info, Groups, and Roaming sections. The Mail settings options are shown in Figure 17-38.
548
5. Click the tab to display the Other section, then select the Windows User Options button to add this person to Windows 2000. The Add Person to Windows 2000 dialog displays, as illustrated in Figure 17-39. In this window, select the Active Directory container and Windows 2000 groups to add this person to, then click OK when finished.
549
6. In this example, illustrated in Figure 17-40, we placed the user in the Users container, although we could have placed the new user in any container appropriate for that user's security rights.
550
7. Select OK to return to the Register Person dialog. Select the check mark box circled in Figure 17-41 to confirm all information has been completed for the new person. The entry is added to the Registration Queue window at the bottom of the screen.
8. Click Register to initiate the registration process. After the registration process completes, this person will exist in both the Domino Directory and Active Directory.
551
In this section we outline the method for adding, deleting, and modifying users in Active Directory and propagating these changes to the Domino directory.
Figure 17-42 Active Directory Users and Computers: Actions: Add new user
552
2. The New Object - User dialog displays (Figure 17-43). Complete the user name fields, including the user logon name. Click Next.
Sarah Chase
schase
schase
3. Type the password for this new user, ensuring that it meets the security standards for your IT infrastructure, and select the password settings for this user (Figure 17-44). Click Next.
553
4. Because we are migrating to Domino, the check box next to Create an Exchange mailbox should not be selected (Figure 17-45). Click Next.
5. Register the new user in the Domino directory (Figure 17-46). We recommend that you select this check box, so that the new user exists and is accessible in both Active Directory and the Domino Directory. We also recommend that you select Use common password, because setting one password for Windows and Notes is most convenient for the user. Fill in the password fields and set an explicit policy for this user (a requirement for this dialog). Select Next.
554
Sarah
schase
schase
6. You are prompted to enter the Certifier ID and password for the Domino server on which this user will be registered (Figure 17-47). Select OK.
Figure 17-47 Enter certifier ID and password for the Domino server
555
7. A confirmation window displays (Figure 17-48). Notice that the new user is added to the Domino directory as well as Active Directory. Click Finish.
8. A Lotus ADSync dialog displays that confirms that the new user has been registered in Notes (the Domino Directory), as shown in Figure 17-49.
556
Figure 17-50 Select the user to delete, then select Delete from actions list
557
2. A confirmation dialog displays, prompting you to delete the users mailboxes on Exchange or Domino (Figure 17-51). We recommend deleting the users mailboxes on either server where they are present to conserve disk space. Click Yes.
3. A message displays confirming that the user has been deleted from the Domino directory, as well as from the Active Directory (Figure 17-52).
558
Sarah
Sarah Chase
559
2. On the General tab, add the required information to the users record, and click OK (Figure 17-54). In this example, we added a phone number for this user.
Sarah
Sarah Chase
3. Because the Domino Directory and Active Directory are synchronized, you have the option of updating the Domino Directory with the changes made to this user. Click Yes to update the users record in the Domino Directory (Figure 17-55).
560
If you open the Domino Directory that contains this user, you will find that the users record has been updated with the changes that you made in the Active Directory. Figure 17-56 illustrates the Domino Directory entry for Sarah Chase, updated with a phone number.
Sarah John
Figure 17-56 Domino Directory record, updated with the Active Directory changes
561
562
Part 6
Part
563
564
18
Chapter 18.
565
566
users. In many cases Migration tools are not able to migrate the access, and the Administrator is required to add access through ACLs to the migrated database. Additional information about permissions is given in the following section.
567
568
2. In the Public Folders Properties dialog box, select the Security tab (Figure 18-3). Assign or revoke public folder tree access and click OK.
In our default installation, the ability to create Public Folders in the root was restricted to the system administrators.
569
570
3. In the Client Permission dialog box, add the members of the public folders by selecting the client and clicking Add. Be sure to select Create subfolders. Click OK, and then click OK again.
571
572
3. In the Properties dialog box, enter a name and a description for the folder on the General tab. You can add control information about the Replication, Limits, and Detail tabs. For our testing, the default settings are adequate. Click OK.
Note: By default the root permissions are the default on this folder to allow different access (that is, to restrict or to allow the posting and reading of documents).
573
4. Select the newly created Public Folder, right-click to bring up a menu, and select Properties. 5. On the Permission tab, define access as per requirements, and click OK (Figure 18-8).
574
575
In both cases, you are presented with the Create New Folder dialog box. 3. Enter a name for the folder, select the content type to store, and then click OK (Figure 18-11).
576
Public folders in Exchange 2000 and 2003 can have moderators to check the content before it is published. To assign moderators and change the permissions of the folder, follow these steps: 1. Right-click the Public Folder and select Properties.
You can add a description or click the Home Page tab assign a Web page to make the Public Folder available from the Web browser.
577
2. In the Properties dialog box, select the Administration tab and click Moderated Folder (Figure 18-13).
578
3. In the Moderated Folder dialog box, add the required Moderators by clicking Add and entering the name (Figure 18-14). If desired, you can also add an autoforward for all content by entering a name in the Forward new items to field.
579
4. Click the Permissions tab. By default Author access is granted. Change the access as required to ensure that users have the required access, and click OK (Figure 18-15).
580
However before you migrate a Public Folder, consider the following questions: Is the data required in your new system? What access do you need to grant in the Domino database after migration? Is this a private folder or a Public Folder? Are folders used correctly in a new team room? If not, then Domino might be more appropriate. Have users cleaned up defunct entries in the folder before migration? Have you checked for complex folders and custom forms?
581
582
19
Chapter 19.
583
584
585
determine where you install ecKnowledge server. For example, if there is a lot of data transferred, it might make sense to install ecKnowledge on the same server computer as Exchange server or Domino server to reduce networks packets from going back and forth and to increase overall throughput of the system.
Figure 19-2 shows the Domino database before the data is migrated into Notes. We have created basic items, such as views, forms, actions, and navigators using Domino Designer.
586
587
To set up ecKnowledge, follow these steps from within the ecKnowledge installer: 1. The initial screens that you see during the installation process are the typical Windows and InstallShield setup routines and licensing agreements. In the Welcome window (Figure 19-3), click Continue.
588
3. Read the ecKnowledge License Agreement. If you agree to the license agreement, click Yes (Figure 19-5).
4. In the Product Registration window, accept the defaults and use the Key Manager later to get the proper keys from CASAHL (Figure 19-6). In the case of our testing, we used an evaluation copy. Click Next.
589
5. Modify the program location from the standard destination folder if you want and click Next (Figure 19-7).
6. You can select either a custom or typical setup (Figure 19-8). ecKnowledge has a wide variety of connectors for other products, such as Oracle, Microsofts SQL, SharePoint, and Groove, as well as SAP. Licensing is done per connector, so you might decide to use this product for things other than just Exchange and Domino migration and coexistence. For this example, we chose the Typical installation. Click Next.
590
7. You can create a program group for the icons if want, and then click Next. (Figure 19-9).
8. You are prompted for an account with which to associate a service (Figure 19-10). For this example, we used the Administrators account, but that is not what you would normally do in a production setting. You should create an account, which you will use with your Outlook profile as well, that has rights sufficient that it can act as a service. The service associated with this account initially is set to manual, which means it will not start automatically if the server requires a restart. After testing of the connector is complete, you need to consider setting the service to automatic.
591
9. Configure ecKnowledge to start with sample applications or a blank system catalog that you can use to create your own applications (Figure 19-11). If you opt for a blank catalog, a Microsoft Access database (MDB) is created for this purpose.
When you install ecKnowledge with the samples, you will find some additional services added to the mail profile that associated with the account that you used to install the program.
592
2. The first time you start the program, you might see the dialog box shown in Figure 19-14. Click OK.
Figure 19-14 Dialog box after starting Key Editor for the first time
593
3. Enter the Site and the Features key that you obtained from CASAHL (Figure 19-15). Note: The Key Editor generates a Site Code automatically based on the machine. If you move the program to another machine, you might need to contact CASAHL for a new Site Key and Features key.
594
Important: If you want to do coexistence for a period of time, to minimize disruptions, we would recommend creating Replication objects to perform ongoing synchronization. This chapter walks through creation of Import and Export objects, which we typically recommend if you want to do one shot migration. Replication objects provide functionality for two-way synchronization with conflict detection and so forth.
595
We found two approaches to creating this connection. You can either create the connections to Lotus Notes databases and Exchange folders first or as part of the Import and Export wizard. We selected to use the Wizard. To create the connection between Domino and Exchange using the Wizard, follow these steps: 1. Select Create Import/Export to start the wizard (Figure 19-18).
596
3. In the Connection dialog box, enter the information about the new connection (Figure 19-20 on page 598). You need to be very specific when completing this information. For example, be careful if the machine that you are using has multiple profiles. Make sure that you spell the profile correctly with the proper credentials to the Public Folders with which you want to migrate or coexist. After you complete the information, click the button next to the Folder field to choose the source Public Folder.
597
4. Choose the folder for migration or coexistence and click OK. Confirm the folder selection and click OK (Figure 19-21).
598
5. You are returned to the Source dialog (Figure 19-22). Here things get a bit tricky. ecKnowledge reads information from the Organizational Forms Library and the Public Folder. You need to know what form and fields that you want to use for the migration before you get started. We know that for this example the IPM.Contact.HR form has the fields that we want and is associated with the public folder Employees. Choose the form and click Next to proceed to the Destination dialog box.
6. The next step is setting up the Domino side. Click Create New Connection to create one.
599
7. When you create the Domino connection you need to specify the Domino data path and the NSF file that you want to use (Figure 19-23). The path can vary from machine to machine. Our Domino database has a form, although if it did not, ecKnowledge would create one.
8. After you click OK to confirm the Connection properties, you are returned to the Target dialog box (Figure 19-24). Select the correct form and click Next to proceed.
600
9. The next step is to map fields (Figure 19-25). You can elect to let ecKnowledge map fields for you automatically (Figure 19-26), but you still need to verify the mapping (Figure 19-27). Click Next to proceed.
10.The next option asks if you want to match columns based on names, which we accepted.
Note: In some cases, you might need to massage data when converting from Exchange to Domino (for example, when Domino designers created the application a little differently). To take care of such issues, ecKnowledge includes data transformation feature which allows conversion of data using simple table values, Visual Basic script, JavaScript, or Notes formula. The data transformations can be associated during column mapping.
601
11.Figure 19-28 shows the field matches that ecKnowledge can find and shows fields that it could not. One necessary step is the selection of a key field or fields. If this selection is not made, you see a warning message.
602
12.Select your key field. We chose the company name field as the key field (Figure 19-29). Click OK.
603
13.You have the option of setting up filtering for the Import/Export Connector.
You can set up filtering by field (Figure 19-31) or keyword (Figure 19-32). You can use Visual Basic script or Dominos formula language to set parameters.
604
14.You can also decide what you want to do with the source data and how to handle errors (Figure 19-33). We selected Update existing records in Target with same keys.
15.The step shown in Figure 19-34 provides execution, error control, and job handling.
605
16.Figure 19-35 through Figure 19-38 show the different scheduling options. You need to take into account the expectations of your users and your long-term goals as you make these choices.
606
607
17.If you want an e-mail notification to occur based on a condition, you can select a user to send it to (Figure 19-39). Click Next.
608
18.Click Finish. Note: In many cases, we found that the Exchange hierarchy contains multiple similar folders. To take care of such cases, ecKnowledge provides an XML API. This API allows you to define the replication or import and export mappings in Composer, and then run in the context of different folders.
609
Figure 19-42 shows the data populated as a result of the job that we created. If we select an entry, we can see how the data appears in Notes (Figure 19-42) and compare it to the same record in Outlook (Figure 19-44).
610
611
John Doe
Doe, John
612
2. If you need to modify any job, you can go into Composer and examine its properties. Figure 19-45 shows the options that are presented.
613
Figure 19-46 The request view of the Service Request Public Folder
614
The steps involved with migrating the data are almost the same as in the previous example. The only difference occurs when you are setting up the Domino side of the connector. Remember that you are starting with a blank database with only the default view. In Figure 19-24 on page 600, you selected from the available Domino forms. Because you have no forms, at this point in the process, you type in the name of the form that you want ecKnowledge to create.
615
616
The view, however, only shows document numbers, and to someone unaware of Domino view capabilities, it would look broken (Figure 19-49).
To give users what they had in Outlook, we need to modify the Notes view to show the contents of the Request Date, Request Number, Requested By, and Service Description fields. We do that with the Domino Designer program.
617
Figure 19-50 The default view of the Domino Service Request Database
3. Each column in a Domino view has its own set of properties that control attributes such as appearance, sort order, and data format. You can reach the column properties by right-clicking the column in designer. You can also access them by the menu selections Design Column Properties). You change the contents of a column at the bottom of designer. There you can place the content of a field, or multiple fields if you want. You can add logic and simple functions as well. 4. Let us change the value of the first column. With the first column selected, at the bottom of the screen select the field radio button (Figure 19-51) and then select the reqdate (requested date) field.
618
5. You can then go to the properties box for the column and change things such as the title and format of data. Clicking the check box saves your changes.
619
6. You might as well change the name of the view and save it. In the Domino Designer select Design Properties.
7. You can insert or append to add additional columns. Inserting adds a column to the left of the selected column and appending adds a column to the right of the last existing column. If you make a mistake, you can drag and drop a column to the right place later. Figure 19-54 shows that we are inserting a new column.
620
8. You can add any field you want to be shown in a view except for a field of type Rich Text.
621
9. Add the fields you want to each column, and make whatever changes to the column properties you might need, based on the types of data. 10.When you are done, your users see something that is similar to what they had in Outlook, as illustrated in Figure 19-56 on page 623. If you need more information about how to further customize views for your users, see the Domino Designer 7 Help database, read the IBM Redbook Domino Designer 6: A Developer's Handbook, SG24-6854, contact a Business Partner, attend a Domino Developers training class, or search the Lotus Developer Domain at http://www.lotus.com/ldd for additional resources.
622
623
624
20
Chapter 20.
625
626
2. On the General Settings tab (Figure 20-2 on page 628), you need to: Enter the name of the Domino server where the Domino address book (Domino Directory) is located. Enter the name of the Domino address book file name. The address book on the Domino server is used to compare and to resolve the names found in the Exchange permissions to get a Notes Canonical name that coincides with the Exchange distinguished name. This process is covered in 20.4, Name resolution, security, and migrated permissions on page 634. Select the level of logging for the migration tool. Only use verbose logging for debugging purposes because it generates very large logs that are attached to the Public Folder document. Select the Public Folder template. The CMT for Exchange Public Folder Migration Tool comes with a modified mail template that is used for creating the Notes databases. The main modification is the ability to store contact lists in the folder list in Notes. CMT also keeps shared calendars and shared contact lists separate in the folder list. The template design is open for further modifications.
627
Important: Modify the default Access Control List (ACL) entries of the template to suit your access requirements. The Custom code flags and Rules options are advanced options. Note: You can create rules to further refine your migration process. The procedure and features provided are similar to those described in Chapter 13, Server Level migration process using Binary Tree Common Migration Tool on page 397, and more specifically in Defining migration rules on page 415.
628
3. On the Exchange Public Folder tab (Figure 20-3 on page 630 and Figure 20-4 on page 631), you need to select different parameters. You might need to set the Exchange Public Folder Root to have nothing in it, depending on what you want to import. The root is top-level Public Folder that you want to migrate. This root becomes a Notes database and all of the sub-folders under this root become internal folders in this database. If you migrate multiple top-level folders, you will have multiple Notes databases. We left the Exchange Public Folder Root blank, so that we could take all of the Exchange Public Folder. You specify the names of the Domino server and the directory where the new Notes databases are created. The default directory name is All Public Folders. Make sure that you have all of the message types selected that you want to migrate. If you leave the wildcard asterisk symbol (*), CMT migrates all of the message classes as well as rich text. You might also want to specify a profile to use for the migration of Public Folders to prevent being asked each time a database is created. The MAPI profile used for the migration has to have Owner access in the Exchange permissions.
629
Figure 20-3 The Exchange Public Folder configuration page (top half)
The security options are found under the Exchange Public Folders Migration Settings (Figure 20-4 on page 631). CMT can bring over Database security, Folder security and Document security. These settings determine what rights are migrated along with the data. Make the appropriate selections according to your security requirements and policies. Database security: The database security settings remains intact and applies to the public folders that are migrated to Notes. Folder security: The security surrounding each folder (who can access which folders) applies to the migrated folders in Notes. Document security: The security surrounding each document (who can access which documents) applies to the migrated documents in Notes. Ignore ALC entries whose permissions exactly match the Default entry: The ACL has the names of users who can access a specific database and documents in Notes. Each database has an ACL. In Exchange, security is at the folder level. For users security to stay the same after the migration, CMT must manipulate the document and database security. Each ACL has a default entry. You can have users who
630
either match or do not match the ACL entry that is added to the ACL. Click the check box to have users whose security does match the default not added to the ACL. Deselect the check box to have users whose security does match the default added to the ACL.
Figure 20-4 The Exchange Public Folder configuration page (bottom half)
The Import All Public Folders Actions section relates to the Import All Public Folders button found in the Public Folders views. Merge database at top level: The same database name is used for the top-level folder and all of the sub-folders found in the Exchange folder structure. Use Aggregate Names: The Exchange display name is used for the Notes database name. The Custom fields section is used for migrating custom MAPI properties that are found in the Exchange Public Folders. You have three options: Ignore custom fields. Use mapping file. Bring across all custom fields. If you select this option, you need to go into the design of the Notes database and make all of the new fields viewable in Notes (see Dealing with customized Public Folder forms on page 645). 4. After your selections are completed, click Save & Close. You are ready to import and migrate the Exchange Public Folders.
631
Figure 20-5 Bringing the Public Folder list into the CMT database
3. As the process begins you are asked for the Public Folder root (Figure 20-6). We went with the default of All Public Folders.
632
4. The next question concerns which MAPI profile that you want to use. If multiple profiles exist on the workstation, choose the one with owner rights to the Public Folders that you want to import (Figure 20-7). Click OK.
5. Finally, once the import of the Public Folders is complete, you will see them listed as shown in Figure 20-8.
633
Figure 20-9 Successful mapping of users from Exchange to the Domino Directory
You can find more information in the ACL Settings section in the Public Folder document (see Figure 20-14 on page 638). With the ability to do ACL matching, CMT for Public Folders translates Exchange permissions into Domino permissions. The equivalent permissions are shown in Table 20-1.
634
Table 20-1 Permission levels in Exchange and Domino Exchange permission None Contributor Reviewer Author Editor Owner Domino permission No Access Depositor Reader Author Editor Manager
Figure 20-10 is an example of a security document that shows the display name for Anais Bourgeois has been resolved. The Exchange Permissions are mapped to Notes security during the migration. When CMT finds the Exchange Distinguished Name, it replaces the Distinguished name with the Notes Canonical Name in Notes security.
635
To ensure that security is brought over, you need to make sure all users have an Exchange Distinguished name with a matching Notes Canonical name. After you have resolved the names found in the list, you are ready to proceed with migrating the Public Folders.
636
The Migration Settings section shows the folder name, the Domino server, the Notes database path, and the Notes URL for the public folder. You can edit any value as required.
637
The Workflow Management section provides useful information about the status of the migration (Figure 20-13). The ACL Settings section gives insight on the roles and permissions granted (Figure 20-14).
If you are satisfied with your settings, close the document. 2. Select the folders you want to import from the list and click Migrate Selected to start the job (Figure 20-15).
638
3. You might be prompted to accept or reject the overwriting of Domino databases and might need to confirm the MAPI profile used during the migration (Figure 20-16). (You have the ability to predefine these options in the Exchange Public Folders configuration page, see Figure 20-4 on page 631.)
639
You see different progress bars while migrating, as shown in Figure 20-17 and Figure 20-18.
Figure 20-18 Progress bar indicating the status for a given Public Folder
When the migration is finished, a green check mark appears next to the name of the folder, indicating successful migration (Figure 20-19).
Figure 20-19 Status report showing a batch of successfully migrated Public Folders
640
Attention: We did see mixed results when looking at the various documents and noticed that not all data is migrated without problems. CMT for Exchange Public Folders tool uses the same engine for converting documents as CMT for Notes, and we have documented the migration results of the individual message types in Chapter 15, Migration results on page 463. We advise that you carefully examine the data types that might exist in your Public Folders and consider the consequences that the possible loss of any data fidelity might present. Figure 20-20 shows the Domino database after the Public folder information has been migrated to it.
641
CMT was successful in bringing in standard type of Public Folder data. The following figures show a series of documents in both Outlook and Notes that illustrate different types of Public Folder data. Figure 20-21 and Figure 20-22 illustrate one of the more difficult items a contact formfirst shown in Outlook and then in Notes. The users experience will be somewhat similar with data fidelity maintained.
642
643
The view of Contacts, Figure 20-23, also has a similar look and feel to its Outlook counterpart (Figure 20-24). The same contact shows up multiple times because of multiple categorization.
644
645
Figure 20-27 shows the default Domino database to where we migrated the Public Folder.
Figure 20-27 Domino database after migrating non standard forms into it
646
6. To see that the fields actually are part of the document, open the properties for a document (Edit Properties) and go to the second tab (the Fields tab). Scroll down the list of fields to see the custom fields. RequestNumber field in Figure 20-28 is an example of a custom field. On the right-hand side of the dialog box, you can see that it has the value 1001.
7. If you open the document, you notice that none of those fields are actually shown as part of the document. 8. The document contains a file attachment. When opened, it looks similar to Figure 20-29. Each row lists a custom field name and the value of the field in the document. You can use this as a guide when designing the form to show the document.
647
9. Use Domino Designer to create a form to show those fields to the user. Going through all the necessary steps to create a form and views to show all these fields is beyond the scope of this Redbook. For detailed information about designing Domino applications, see the Domino Designer 7 Help database, read the IBM Redbook Domino Designer 6: A Developer's Handbook, SG24-6854, contact a Business Partner, attend a Domino Developers training class, or search the Lotus Developer Domain at http://www.lotus.com/ldd for additional resources.
648
10.Figure 20-30 shows the design of a form in Domino Designer that we created to show the desired end result of the migration. The form is an example of what an application might create to mimic the look and feel of a customized form in a Public Folder.
649
11.Figure 20-31 shows the document in the Public Folder and migrated into the Notes client. The document is viewed with the form that we created.
Figure 20-31 The migrated document in Notes shown with a custom form
650
21
Chapter 21.
651
652
To migrate data manually using DUS, follow these steps: 1. Create an Exchange mailbox. Ensure that the account that you use for the migration has full access rights to the mailbox. 2. Connect the mailbox to your Outlook Profile. 3. Copy the Public Folder information into the new empty mailbox. 4. Check the quality of the data. 5. Migrate the mailbox using DUS. 6. Review and manage the migrated data in the new database. These steps are discussed in detail in 21.4, Migrating the contacts Public Folder on page 660.
653
7. Open the new folder and export the data to Excel. a. Select File Import and Export (Figure 21-1).
654
d. Select the new folder as the export source and click Next (Figure 21-4).
655
e. Enter a file name and location and click Next (Figure 21-5).
f. The next dialog box defines the field mapping. Click Map Custom Fields to define field mapping.
656
g. The current field maps should be a one to one, However there might be fields that you do not want to map or want to map to similar fields that defined in your Domino database forms. In the Map Custom Fields dialog box, drag the values from the source file on the left to the appropriate destination field on the right. When you are finished, click OK.
h. Click Next and then click Finish. The folder has now been successfully migrated to a Domino database 8. Review the spreadsheet and remove any unwanted fields, rows, columns, and so forth and, if required, add additional information. 9. Insert a top row in the spreadsheet and ensure that each row matches the corresponding field in your Lotus Notes database. Ensure that the cells in this row are left justified and are formatted as text. 10.Save the file as a Lotus 123 (.wk1). (You might want to save the file as an Excel spreadsheet first in case you have issues later.) 11.Exit Excel, and open Lotus Notes.
657
12.Open the database that you created earlier, and select File Import (Figure 21-8).
13.Select the file type as Lotus 123, and select the 123 workbook that you created earlier, and click Import (Figure 21-9).
658
14.In the import dialog box, select Main Document and select the form that you created earlier. Under Column Format, select Defined by the view, and click OK (Figure 21-10).
659
The data is migrated. We created a Public Folder with two fields: body and billing information (Figure 21-11). This database took two minutes to create a single form with two fields and a single view.
Note: There is a hard limit of 8192 rows for this type of import (wk1 limit). You need to use alternative methods of migration or you need to create multiple wk1 files manually for larger files. Remember that Domino can use Lotus 123 data. Lotus 123 does not need to be installed on the system. (We also noted the beta2 version of Excel 2007 does not have the ability to save files in the Lotus format.)
660
Another method that you can use is to send the contacts as vCards across the coexistence solution or to save them to a shared network and drive and then import them to Lotus Notes using the following procedure: 1. Open Outlook and select the Contacts public folder. 2. Press Ctrl+A (to select all), as shown in Figure 21-12.
661
4. The message is received in the Domino mailbox (Figure 21-14). Open the received mail item.
662
5. Select all the vCards (select Edit Select All or press Ctrl+A). 6. Select Save and place the files in a holding directory. 7. Create a new Personal address book (Figure 21-15): Select File Database New. Select to save the file on the server. Enter a meaningful title. Enter a unique file name. Select the personal address book template (pernames.ntf).
663
8. Right-click inside the open database: Select Manage ACL. Add all users who need access to the Database with defined permissions. Select File Import. Select the files to be saved. Click Import.
9. For each vCard, a prompt box opens (Figure 21-17). Click Save for each vCard.
664
665
require an Exchange 5.5 server and recreating permissions. A PST (personal storage file) is a much more convenient way of sending data. Tip: You can also use a PST in a migration to store old mail messages of a critical nature. In the future, an Outlook client is all that would be required to recover a single document, which could be printed or e-mailed to the new system later.
Attention: The larger you make the PST, the more likely it is to get corrupted. There is a 2 gigabyte limit on PST files. You would be better served by creating several smaller PST files instead of one big one. Creating a PST from a Public Folder is simple: 1. Select the Public Folder and select File Import/Export. 2. This action invokes a wizard that walks you through the steps that get the job done. When the wizard begins, select Export to a File (Figure 21-19).
666
4. You can select one or a set of nested folders if you want (Figure 21-21).
667
6. It is usually a good idea to give the Public Folder a different title than the default of Personal Folder, just in case the developer has multiple personal folders with which to work (Figure 21-23).
7. You can put a password on the PST. Be aware that if you lose the password you will need to re-create the file. After you create the PST, you can send it to anyone you choose, by any means, including electronic delivery. Just remember that if you burn the file onto a CD, you need to copy it to disk and remove the read-only attributes before you use it.
668
22
Chapter 22.
669
Post-migration:
670
requests. You can share a folder for multiple access for a limited group of users when you do not have rights to share the same data in a public folder.
Sharing a folder
To share an e-mail folder, you need to grant permission at the top-level folder. For example, if you create a folder called Projects and then under that folder create a subfolder called 2006, to grant access to 2006, you first need to grant at least read access to Projects. You can use the following procedures to share a folder in Outlook and Exchange: 1. Open Outlook with your desired folder and click a folder. (The items in the folder show in the viewing pane.) 2. Right-click the folder to share and select sharing, as shown in Figure 22-1.
671
3. On the Permissions tab, click Add and select a user from the GAL. Then, click OK (Figure 22-2).
672
4. Assign permissions that can be granted from being able to see the folder to being a able to create subfolders and edit and delete items and then click OK. For example, we assigned the user Christopher the rights to read and edit items and to create subfolders (Figure 22-3).
673
2. Enter the details of the users account and folder to which you want to connect. You can use the Name button, which opens the GAl for you to select the name. A selection box shows the available folders (Figure 22-5).
674
Note: When you select this option when a users migration is initiated, all shared folders are migrated along with the users other local data. Thus, multiple copies of the same data will exist in multiple migrated mailboxes.
675
Overview
If we copy all shared data into an intermediary mailbox folder, we can migrate using the DUS. Thus, our objective then becomes getting the data into a mailbox to migrate and gathering information about the shared folder permissions. Note: This process is a manually intensive process and needs to be done on a user-by-user basis. You need to plan for this process the planning phase. For a large-scale migration, either get users to move shared folders into Public Folders or use CMT and look at using TeamRooms to provide managed share repositories. The migration itself follows some simple steps 1. Gather information about shared folders, permissions accounts, and so forth. 2. Create an Exchange mailbox. Ensure that the account that you use for the migration has full access rights to the mailbox. 3. Connect the mailbox to your Outlook Profile. 4. Copy the shared data information into the new empty mailbox. 5. Check the quality of the data. 6. Migrate the mailbox using DUS. 7. Review and manage the migrated data in the new database.
676
677
2. In the Migration Mailbox Properties dialog box, go to the Exchange Advanced tab and select Mailbox Rights (Figure 22-8). Tip: To see Exchange advanced properties, select View Advanced Features.
678
4. Enter the migration mailbox user name and click Check Names (Figure 22-10).
679
5. Select the rights of the mailbox user. The user needs full mailbox access. Click OK. (Figure 22-11)
680
681
2. Copy the selected contents to the clipboard (either Ctrl+C or Edit Copy), as shown in Figure 22-13.
3. Create a new folder in the migration mailbox: a. b. c. d. Select File New Folder. Give it a meaningful name (for example, Graemes contacts) Select the location under the mailbox tree. Click OK.
682
4. Copy the contents of the clipboard into the newly created folder, as shown in Figure 22-5.
We can now use DUS to bring the data into Domino. Tip: Contacts are created as a subfolder in contacts and, when migrated, are migrated as contacts and thus are not visible as a folder in the new mailbox. An additional step has been added to describe what to do with contacts. After the migration is complete, the Domino Administrator needs to change the access to the ACL to give access to all the users: 1. Open Domino administrator and select the registration Domino server. 2. Create a new mailbox. 3. Select the People & Groups tab.
683
4. From the right-hand tool bar, select People Register. Tip: You might want to reuse the same account for multiple shared migrations, which might also be the case for shared mailboxes. The following option (step 5) should be used if this is the case. 5. Click Options, and in the Advanced Person Registration Options dialog box (Figure 22-15), select the following options: Allow registration of previously registered people. Select Dont prompt for duplicate person and select the Update the existing address book entry option Select Dont prompt for duplicate mail file and select Replace the existing mail file option 6. Click OK.
684
8. Select Exchange as the foreign directory source. Use a profile that has full access to the Exchange migration mailbox that you created earlier. 9. Click GO! 10.Select the migration mailbox and click Add. 11.Click Options. Deselect all options and select Convert mail ONLY (Figure 22-16). Click OK.
12.Click Migrate. Note: You will get an error that the user migrated with errors, but you can ignore this error. 13.Click Done. 14.Enter a password that meets your password requirements, and select an explicit policy.
685
16.Click Register to migrate the account data. 17.Click OK. 18.If there are any errors, review and rectify them. The error messages are normally descriptive enough to help determine the issue. 19.Click Done.
686
687
b. Enter the details for the new copy, keep in the server, but give the file a descriptive title and unique file name (Figure 22-19). Leave all other details as default and click OK.
3. Select the new mailbox, right-click the mailbox, and select Access Control Manage (Figure 22-20).
688
4. Add the users as required for sharing. User can be selected from the address book by selecting the person icon.
You now have the data shared in Domino and shared among the users. For data using custom forms, additional work on the Domino views and forms might be required. For more information, see other IBM Redbooks about cover design and development of Domino databases, which are accessible from: http://www.ibm.com/redbooks
689
To synchronize these contacts: 1. Log in to the migration account on Domino and open the mail file. 2. Select Actions Synchronize Address Book (Figure 22-22).
3. The contact data in the address book is synchronized with the personal address book on the local machine (names.nsf). Click OK in the confirmation message.
You can copy the personal address book to the Domino server and assign relevant permissions as discussed earlier in , Configuring the data for sharing on page 687.
690
Note: if you intend to reuse the same databases, be sure to delete and re-create the databases before each migration. Otherwise, you will mix your data.
691
692
23
Chapter 23.
693
694
Look for these articles: Knowledge Base article 189286 covers deleting a server from a site. Knowledge Base article 152959 covers deleting the first server in a site. This may or may not be the same as the previous item. If you accidently erased the Organizational Forms Library, Knowledge Base article 239760 can help you recover the lost forms. If you need to recover a single mailbox from a deleted server without causing problems with your remaining Exchange organization, see Knowledge Base article 163713.
Chapter 23. Migration project wrap up: Removing the Microsoft Exchange environment
695
23.2.1 Considerations
Being extremely cautious, let us imagine some of the things that could be on that server: A mailbox that you chose not to migrate, such as an archival mailbox that held information from the mailboxes of other users. Public Folders that do not have replicas elsewhere. Connectors, or it could be a key management server. The server could be a bridgehead or a replication hub. Public Folders might be stored on it. Maybe you started to deploy Active Directory and the server has the Active Directory connector on it. The server is used to expand a distribution list. These items, in and of themselves, are not a reason to necessarily keep a server up indefinitely. However, they may represent issues that need to be mitigated prior to decommissioning any Exchange Server. What follows are some suggestions on how to deal with such conditions. Mailboxes not migrated If a mailbox contains messages but was not migrated, there are two alternatives. Either place the mail in a PSTthe details on how to do this are the same as for a Public Folderor confirm you have a good backup, and recover messages as required on an Exchange server that is not really part of the network. For details on this, see Microsoft Knowledge Base article 163713. If you put the mail in a PST and store it optically, you will need to return it to disk and change the permissions from read only. If you are relying on tape, be aware that recovering an Exchange server can take several hours from start to finish. The server has connectors The impact of removing a server that has a connector could be profound to the other remaining users of Exchange. Be sure to create alternate
696
connectors with a lower cost than the connector being removed. Also, allow for any changes you make to your topology to propagate through the rest of your Exchange environment. If the connector on the one server in the one site is the Internet connector, make sure that you have a way to send mail to the Internet, as well as the appropriate Mail Exchange (MX) records to point to the connector. Allow sufficient time for the MX records to replicate on DNS servers throughout the world. If someone else is hosting DMS services for you, make sure the provider makes the changes correctly. It is a key management server This server manages keys used to sign and encrypt mail. If this server was unavailable and a users certificate expired, they might not be able to open some messages. See the Microsoft documentation about how to move this functionality elsewhere. Bridgehead server While not very likely, a server might act as a hub for one or more functions. If the single server is acting as a bridgehead, make sure you adjust your topology accordingly.
Chapter 23. Migration project wrap up: Removing the Microsoft Exchange environment
697
Public Folder home server If you have a Public Folder that was created on the Exchange Public server you want to decommission, then the Public Folder will need to be re-homed in order to ensure that proper permissions are maintained. To re-home a folder, first create a replica on another server, and then go to the advanced properties of the folder resetting the home server (Figure 23-1).
698
Public Folder permissions can be reset when a consistency check is done on the information store. Orphaned Public Folders get new permissions when the original server can no longer be found in the directory. The consistency checker is manually run when you delete a number of objects and want to clean things up. The Consistency Adjuster is on the Advanced tab of the Property page of the server (Figure 23-2).
An Active Directory connector is on the server The Active Directory Connector is used to synchronize data between the Exchange 2000 and 2003 world and Active Directory. Loss of the connector means there would no longer be updates between Exchange 2000 and 2003 and perhaps Exchange 2000 servers that might have been part of a cancelled deployment. Your alternatives are to break the connector and let no further changes replicate or place the connector elsewhere. Server is specified to expand distribution lists A distribution list can be parsed locally or on a specified server. Verify that distribution list expansion is not on a targeted server.
Chapter 23. Migration project wrap up: Removing the Microsoft Exchange environment
699
700
3. If you have the rights, you next have the option of removing the connector at the remote site (Figure 23-5). If you do not have permissions, the deletion will fail. Click Yes to confirm the deletion.
4. A message warns of the consequences of using the Consistency Adjuster before you have verified that the Public Folders have been re-homed properly (Figure 23-6). You should have done this as part of your pre-contraction checklist.
Chapter 23. Migration project wrap up: Removing the Microsoft Exchange environment
701
Important: In addition to Site Connectors, you can find either X.400 or SMTP connectors that would need to be removed as well. 6. You are asked to confirm this action. Click Yes.
Force replication
In the site or sites that remain, force replication from servers that connected to the site about to be removed to other sites.
702
Recalculate routing
Run the routing calculation on the routing calculation page of the site addressing tab (Figure 23-8).
Chapter 23. Migration project wrap up: Removing the Microsoft Exchange environment
703
Your servers global address routing table will no longer show a way to get to the Branch Office (Figure 23-9).
704
So, if you have a choice, you would delete the first server last under most circumstances. Knowledge Base Article 152960 deals with moving first server functionality. Best Exchange practices have you move those functions before decommissioning the first server. Otherwise, removing other Exchange servers from a site follows the same pattern as a single server, single site. The steps are as follows: 1. Verify everything on the single server, single site list. 2. Make sure the server is not the first server. 3. Run the Exchange setup from the server you are decommissioning and make sure to remove all connectors. Not doing this might result in your being unable to remove the server. 4. Using the Exchange Administrator on a remaining server, remove the object that represents the deleted server. 5. Force replication to other sites. If you need to keep users on Exchange in a site but need the server, either migrate the users or use the Exchange Administrator to move them to another Exchange server in the same site.
Chapter 23. Migration project wrap up: Removing the Microsoft Exchange environment
705
706
Appendix A.
707
Note: IBM does not necessarily endorse the tools listed in this appendix over other available tools to be used in a migration. While there might be many additional tools in the market, the scope required for discussing each of them exceeds what is possible in this book. Instead, we focus on those tools with which members of the IBM Redbook team had experience.
A.1 CoexLinks
CoexLinks is a coexistence solution which maintains the fidelity of embedded Notes document links (Document Links). It complements the Microsoft Exchange connector or the pure SMTP routing solution by adding message fidelity while sending mail messages from Notes to Outlook which contain embedded notes document links. For more information about these solutions, see: Chapter 5, Using the Microsoft Exchange Connector for coexistence (Exchange 2000) on page 113 Chapter 6, Using the Microsoft Exchange Connector for coexistence (Exchange 2003) on page 175 Chapter 9, Using SMTP routing for coexistence on page 273 As we highlight in Chapter 10, Coexistence test results: What to expect on page 315, specifically in the section Document Links on page 325, the fidelity of document links is normally lost when sending messages between a Domino and Exchange Domain. Rather than the document link remaining in the Notes document, it appears within the message received on the Exchange side as a long URL. CoexLinks addresses this issue.
A.1.1 Overview
CoexLinks is a Tool manufactured by Genii Software: http://www.geniisoft.com It watches the outgoing Notes mail messages for notes document links (doclinks) and converts these to a format that can be handled by non-notes clients, including Microsoft Outlook. It offers: Seamless conversion of doclinks, view links and anchor links, as well as link hotspots. Customized disclaimer on modified messages. Converts links to choice of NDL attachments, Notes URL links, or Web HTTP links.
708
Selective conversion to HTTP links by database allows non-Notes users to use Notes databases over the Web. Optional formatting URLs allows calls to agents or servlets to process links. Plug-in architecture requires no scripting, coding or design changes.
709
Figure A-1 A sample message, how it is sent from a Notes-based workflow application
Figure A-2 illustrates the same message converted by CoexLinks. Notes links are replaced to .ndl files in this example but could be replaced to http:// links as well where appropriate.
710
711
You change it after the installation to: extmgr_addins=toool1, tool2, COEX 3. Restart the Domino Server.
COEXDocLinkType
This setting determines the form that the converted doclinks take. If set to zero (0), doclinks are not converted at all, and all other CoexLinks processing is suspended. Effectively, this is a way to temporarily disable CoexLinks. The most common choices are 2 for NDL attachments, which works well with all versions of Outlook, and 8 for URL hotspots.
Table 23-1 Overview of the COEXDocLinkType notes.ini setting Notes.ini value COEXDocLinkType=0 COEXDocLinkType=2 COEXDocLinkType=4 COEXDocLinkType=8 COEXDocLinkType=16 COEXDocLinkType=32 Meaning Disable CoexLinks - no processing took place Convert to NDL file attachments, leave text in place Convert to text URLs Convert to URL hotspots, default Notes:// Convert to NDL file attachments, no text left in place Convert to URL hotspots, default http://
COEXLimitToDB[n]
This setting limits processing of messages to specific databases, which are usually specific mailboxes. For example, you can limit processing of messages to those which flow through the exchange.box if you want to use CoexLinks in conjunction with the Microsoft Exchange Connector. This ensures that only messages destined for the Exchange Connector are converted, and other e-mail messages which can be routed to Notes client users are not.
712
Table 23-2 Overview of the COEXLimitToDB notes.ini setting Notes.ini value COEXLimitToDB1=exchange.box Meaning Process only messages sent through the Microsoft Exchange Connector and not affect any messages set directly over SMTP (through mail.box)
COEXPrependDocLink
This setting enables a disclaimer to be prefaced every message that has been changed by the conversion process, as shown in Example A-1.
Example: A-1 Enable a disclaimer
COEXPrependDocLink=1 COEXPrependDocLinkText1=********************************************** COEXPrependDocLinkText2=Lotus Notes doclinks have been converted to COEXPrependDocLinkText3=URL links. Launch the hotspots to COEXPrependDocLinkText4=access the linked document in web browser. COEXPrependDocLinkText5=**********************************************
A.2.1 Overview
Client Genie (http://www.clientgenie.com) is manufactured by ICODEX and was originally marketed under the name INTEGRATE!People. It is a highly configurable solution for controlling, managing and monitoring Notes Clients from a centrally administered Notes database. The key features Client Genie provides include: Enhanced Lotus Notes Login Screen with easy Location- and User-ID-Selection Central Administration of the Lotus Notes Workspace, Replicator pages, Personal Names, notes.ini, Welcome page (Homepage bookmark), the Bookmarkstore, and Toolbars
713
Stores desktop, bookmark and various other data as XML for enhanced roaming and rollback Viewing Notes desktops with a Web browser just like in Notes, without needing physical or network access to the respective users computer Automatic building of maintenance-free portals that mix centrally controlled notes-, Web- and file links with user individual Notes links all from a single point of administration into a single point of information access portal for every user to just about any information.
714
Here some example scenarios depicting how Client Genie could be used in a Microsoft Exchange to Lotus Domino migration project: By using the ability to run agents in a Lotus Client, you could install a migration tool on the users systems and run the agent with a help of LotusScript, or through Windows Scripting Host (WSH). For example, you could run the Domino Migration Services local data migration process (that is, nupgrade.exe) (see Chapter 12, Migrating local Outlook data using Notes Upgrade Services on page 365) and automatically fill the dialog boxes that the user then completes. Additionally, as a preventative measure, you could also ensure that the local data migration process could not be run a second time (accidentally allowing a user to migrate all the data a second time with the result of creating duplicate data). Alternatively, you could use Client Genie to deploy TransSend Mail Migrator (see A.3, Transend Migrator on page 721) and run it in batch mode (visible or invisible). By defining a corporate standard for Lotus Notes Client desktop, you could give a newly migrated user give a ready to use, fully "furnished" desktop surface with all desktop icons, bookmarks, local replicas, replicator page settings, and toolbars in place. This allows users to use the new platform in the most productive way, reducing the time required for training and learning the new environment. Note: To some degree, the ability to deploy and create a standardized desktop can also be accomplished by using the built-in setup policies in the Domino directory. This, however, is mostly limited to initial setup only and does not cover the entire life cycle of a Notes client. For additional information about this topic, see the Domino Administrator Help: http://www-12.lotus.com/ldd/doc/domino_notes/7.0/help7_admin.nsf/ f4b82fbb75e942a6852566ac0037f284/74996b4926fa94378525706f0065b175 ?OpenDocument By creating a custom skin for the login dialog and the Notes workspace, you could implement your companys Corporate Design, to drive user acceptance of your project. When you have a migration project as a result of an enterprise merger or acquisition, and you are integrating new users into an existing Domino infrastructure you could use Client Genie to support the consolidation of your Domino Servers by redirecting the bookmark links and workspace tiles on the users desktop to reflect database moves across servers. Furthermore, Client Genie can help in the renaming of servers or whole domains, without any interaction required from users. This contributes toward minimizing the load at
715
your help desk that usually accompanies large scale changes in your organization. By using the log database of Client Genie you could analyze how Notes Clients are set up "out there," and how your users utilize Lotus Notes. Namely, this can help to identify what databases users have links to on their desktop and in their bookmarks, which screen resolution are they running and even latency times as to identify network bottlenecks from a client-side perspective.
716
Figure A-3 illustrates what the Client Genie looks like for the user. Users log in to Lotus Notes. The ICODEX Client Genie Login Screen displays (naturally not with Single Sign On). You can freely customize the login screen; all ID and security handling is still done by Notes - the ICODEX Client Genie Login dialog only ensures that new changes can be downloaded from the server and immediately applied to the local client configuration before Notes locks it (such as deskop*.ndk, bookmark.nsf, and so forth).
Figure A-3 Client Genie replaces the Notes login dialog with a customized version
After successful password entry, users see a short progress bar, indicating that something is happening but that does not allow the user to choose whether the something happens (and without being dependent on the user as with e-mail or button-based administration).
Figure A-4 After the login dialog the user sees progress bars
After synchronization is finished, Lotus Notes starts as usual. Except for the managed content, such as the position of a database tile, bookmark, or replicator page entry, and the server to which they point, all of which is fully controlled through the administration documents in the Central database.
717
Finally, Figure A-5 illustrates how Client Genie can provide a customized skin to the Notes Desktop to provide a compliance with corporate design and identity.
Figure A-5 Client Genie can provide a customized skin to the Notes Desktop to provide a compliance with corporate design and identity
718
719
All the settings are made by creating appropriate Notes documents that are arranged hierarchically as parent documents (that is, multiple Database Icon documents can be attached to a Workspace Page document). All documents have fine tunable access control entries of readers and authors fields.
720
A.3.1 Overview
Transend Migrator is manufactured by Transend Corporation.: http://www.transend.com/ It is a client-based utility for converting data to and from a number of e-mail programs including a migration from Outlook and Exchange to Lotus Notes and vice versa. It covers: Messages/Folders Local Archives Address Books Calendars Tasks Notes versions 4 to 7 are supported. All versions of Outlook and Exchange are supported. Both the Notes and Outlook clients need to be installed on the PC running Transend Migrator, which can be installed on a network drive or the user's PC. Transend Migrator typically is run from the user's system but can also be run for multiple users from a central location (see below: Running Transend Migrator from a Central Location). Transend Migrator includes both a graphical Windows interface with easy to follow wizard-like instructions as well as a powerful command line batch mode processor. The users Exchange mailbox and Outlook personal folders (PST file) can be converted to the Notes server or local .nsf file. Transend Migrator provides a report of the completed migration and generates a detailed log file.
721
Here are some highlights: Runs on the client machine either in a GUI or directly using a command line. Attachments are converted and maintained with the converted messages or can be detached from the message and copied to a specified directory. Addresses can be converted to a format that can be replied to through Notes based on a specified name conversion rule. Outlook Contacts or Personal Address Book are converted to the users local names.nsf, including personal addresses and distribution lists. You may optionally specify an e-mail address conversion rule, so that the converted addresses would work in the new environment. (that is, convert Exchange addresses to SMTP or to Notes hierarchical name) All data from the Outlook address book is converted, including: name, e-mail address, comments, location, department, manager, company name, title, suffix, job title, spouse, children, assistant, pager, office phone, office fax, home phone number, home fax, cell phone, birthday, office address, home address. (Domino Upgrade Services does not migrate some fields, like birthday) The user's Outlook calendar is converted to the Notes calendar. Transend Migrator gets all Outlook appointment types: anniversary, all day, meeting, and reminder. It also converts the Tasks list. Reoccurring entries are supported, but expanded to multiple entries in Notes. Data fields retrieved are Subject, Location, Room, StartDateTime, EndDateTime, Importance, DueDate, AppointmentType, SentTo, RequiredAttendees, OptionalAttendees, comments, and attachments. Can be installed on a network drive. There are some limitations: It runs on a client system and needs both a MAPI (that is, Outlook) and Notes installed side by side. You have to create the Lotus Notes user accounts in advance. There is no management interface were you would track the status of the migration of multiple users. When running in the GUI mode a user required to do a lot of interaction with the dialog boxes, being asked for quite obscure technical information and settings. It does not migrate all Outlook data in one step. The user need to start it multiple times to migrate mails, than calendar and then address books.
722
723
724
From the same dialog box, you have the access to the program options dialogs. Below are the figures for the Outlook and Notes settings screens.
725
As shown in Figure A-9, users can select specific Notes options to refine the migration procedure.
Next, you are asked what systems you want to migrate to and from.
726
In order to access Exchange or Outlook to extract the data, you must have already installed the Exchange or Outlook client on your machine. In most cases Outlook is accessed through a profile. If you are using a profile, enter the name of the profile here. As an alternative to using predefined profiles, you can tell Transend Migrator to extract data from a PST file that you specify. If you are converting address book data, this screen includes the field Contact Folder, where you can enter an alternate name of the folder that contains your Outlook contacts if you are not using the standard default.
727
The logon screen for Lotus Notes asks you to enter values for the Notes user name, mail database, and password. Default values for both the user name and mail database should appear in these fields. This screen also includes a check box for Shared Folders, which you need to check if you intend to convert to a shared Notes database.
728
The folder selection screen presents a list of all existing Outlook and Exchange folders (from which you are converting). Folders in a multi-level hierarchy (folders within folders) are separated from higher levels by a slash. You can select single or multiple folders for conversion.
Prior to running the conversion, the following options can be set from the Miscellaneous Options screen (Figure A-14 on page 730): Convert only those: To convert only those messages that contain the given string. Leave this field blank to convert all messages. Max Attachment Size: This field allows you to limit the size of attachments that are converted. If you want all attachments to pass, enter all nine's (9) in this field. There is a command line switch that allows you to specify that deleted attachments will be copied to a directory. See Command Line Options. Max Distribution List: Use this field to cut off a distribution list (to's and cc's) at a given number. Oldest Message Date: This option allows you to convert only those messages that were created more recently than the given date. To convert all messages, enter a very old date (such as 1 Jan 1980, the default). Message Store: This field appears only if you are converting to a system that supports multiple message stores, such as Exchange or Outlook. In that case, you may select the message store from the drop down list.
729
Name Conversion: For many conversions, the original e-mail address of people on the distribution list will not make any sense in the new system. This field allows you to create an Internet style address based on a display name.
In the example in the Figure A-14, the address conversion rule converts the sender Gregory Engels to GEngels@itso.de.
730
A.4.1 Overview
GMI Infopath_2_Notes is manufactured by Smartix Gmbh: http://www.smartix.de GMI InfoPath_2_Notes provides a set of rule-based transformations to migrate any Microsoft InfoPath form in a Notes database. This transformation includes four different steps: 1. Saving the Microsoft InfoPath form as resource-files. 2. Selecting a target location on your Domino server or local Notes client. 3. Migrating the user interface of the selected form according to the specified translation filter. 4. Migrating the code of the form based on configurable translation filter and highlight the migrated elements in the new created Notes application.
731
Fast and error-free status quo on the new platform due to exclusion of human error-sources Consistent solution across all existing Microsoft InfoPath forms (and views)
732
2. Select the form on your computer by opening a form in design mode (Figure A-16).
Figure A-16 The dialog box to select a form template (.xsn file)
3. For data attributes within the form and overall database properties, you can define specific behavior and how data migration is handled.
733
734
4. Save the resource-files for this form. The menu command is File Extract Form Files (Figure A-18).
735
736
737
GMI InfoPath_2_Notes reads the XML-stream of all these files and combines them into a valid DXL-stream. This DXL-stream is then imported to an empty Notes-database and creates forms and included Code within this empty database.
738
For the transformation of the user interface information such as tables, fields, and action-buttons, GMI InfoPath_2_Notes uses the GMI framework to translate the Microsoft InfoPath structure in the GMI-XML-pattern (Figure A-22).
739
In the next step, the GMI-representation of the Microsoft InfoPath form is transformed in a Notes-application using the "GMI Lotus Notes" set of filter (Figure A-23).
For the transformation of code-elements such as JavaScript, Visual Basic script, or special elements such as @Formulas, a set of code-translation-filter are used (Figure A-24).
So, in this case the expression normalize-space(.) is replaced by @Trim(FIELDNAME). The result of these transformations is pasted in the corresponding location in the DXL-tree. So, a Default-value remains a default-value, and a Input-validation becomes a input-validation.
740
Here you have to enter the licence-key provided on your invoice (Figure A-26).
Figure A-26 The license key is the one setting that is mandatory
741
A.6.1 Overview
The Domino on UNIX/Linux Start Script is written by Daniel Nashed from Nash!Com and is available free of charge upon request from Nash!Com, homepage: http://www.nashcom.de/nshweb/pages/startscript.htm The Domino cross platform start, stop, and diagnostic script has been written to unify and simplify running Domino on Linux and UNIX. The start script is designed to be one-stop shopping for all kind of operations done at the UNIX prompt. The script can start and stop the server, provides an interactive console and run NSD in different flavors. The script ensures that the environment is always set up correctly and supports multiple partitions.
742
Script commands
You can invoke the script with a number of command line commands: start Starts the Domino server and archives the last OS-level Domino output-file. The output-file is renamed with a time stamp and compressed using the configured compression tool. Compressing the log file is invoked in background to avoid slowing down the server start when compressing large
743
log-files. The start operation does clear the console input file and logs information about the UNIX user environment and the security limits of the UNIX user. stop Stops the Domino server through server -q and waits a given grace period (configurable through DOMINO_SHUTDOWN_TIMEOUTdefault 10 minutes). After this time the Domino server is killed through NSD if it cannot be shutdown and processes are still ruining after this time (see kill command below) The Java controller remains active if configured. stopjc In case you configured to use the Java controller (USE_JAVA_CONTROLLER) this command shuts down the controller component. When starting the server and the controller is running it will be shutdown before starting the server. There is currently no way to restart Domino with a running Java Controller from the Domino console. The work-around is to stop and restart the controller. restart Stops the Domino server and restarts it using stop and start command with all implications and specially the time-out values for stop. status Checks if the Domino server is running and prints a message. Return code of the script: 0 = server is not running 3 = server is running
monitor
Attaches to the output and the input files of a running Domino server and allows a kind of live console from a telnet/ssh session using the input and output files. Ctrl+c terminates the live console. archivelog Archives the current server text log-file. The file is copied, compressed and the current log file is set to an empty file without losing the current file-handles of the server process. There might be a very short log file interruption between copying the file and setting it to an empty file. The new log file contains a log-line showing the archived log file name. info Generates a sysinfo style NSD (nsd -info). nsd Generates a NSD without memcheck (nsd -nomemcheck).
744
fullnsd Generates a full NSD, including call-stacks and memcheck. kill Terminates the Domino server (nsd -kill). setenv Sets the Domino server environment. You need to invoke the script in a way that the environment variables are inherited into the current shell.
default value
/opt/ibm/lotus /local/notesdata
4. For AIX and Solaris change first line of the scripts from #!/bin/sh to #!/bin/ksh. Domino on Linux used sh instead of ksh. The implementation of the shells differs in some ways on different platforms.
745
A.7.1 Overview
Domino uses functionality provided by the operating system it resides on to perform tasks such as a listing of a directory or finding a database by its filename. So, if the operating platform is case sensitive for filenames, Domino also behaves that way. Windows is a case insensitive platform, so a file named MigrationTeamroom.nsf and migrationteamroom.nsf as well as MIGRATIONteamroom.NSF is considered the same file. This is not so on UNIX based operating systems such as Solaris or Linux. When moving Domino Servers from Windows to UNIX one might run into huge problems with databases whos filenames consist of mixed case spelling (for example MigrationTeamroom.nsf). Most problems occur in the following areas Agents try to open databases Server replication Mail delivery (when the person document contains wrong casing) Opening mail-files (when the location document contains wrong casing) Opening databases from the workspace (when the icon has been added with different casing when the database was already in the cache) When opened through HTTP The main problem is that this behavior is not controllable or supportable in day to day operation. You cannot be 100% sure that you find all places to correct the casing and specially migrating from another platform where casing is ignored. And in some cases you also run external or third-party applications which you cannot control at all. For some customers this might not be an issue, especially if you do not have a large number of databases, but for some can became a major problem when facing migration of a Domino Server to other platforms. In addition the behavior of two databases with different casing would be still inconsistent because after one of the databases has been opened, further
746
requests (also for the database with other casing) would hit the open database in cache and ignore casing. So you could never open both databases.
747
NshExtLo: DBOpen: (adminp) : '/local/notesdata/names.nsf' OPT:0x0 ST:0 USER: 'Gregory Engels/ITSO/DE nshextloOptions=2 Same as Option 1 but log all databases not just databases with error codes. nshextloOptions=4 Translate Upper case to Lower case file names. The translation is logged on the console/ in log.nsf.
748
nshextloOptions=8 Enables verbose logging. In most cases verbose logging is not needed and could cause a high number of additional log messages.
Example: A-3 Log File with nshextloOptions=8
749
750
Appendix B.
751
752
Alternatively, if you are using the CMT, select ADD users Registration register. 4. Register users in Domino, If you are using Domino migration tools, deselect the option to convert mail and select Add Admin to ACL (this is necessary to be able to add migrated mail documents later). 5. Install the mail client for the user that is being migrated (Outlook Connector or Full Notes clients). As an option, you can also enable Sametime for instant messaging. 6. Set an autoforward on the Exchange account. Note: This is an important step for a successful migration. If non-migrated users still in Exchange reply to mail or select a recipient from local contacts, the reply to address will be the old Exchange address. Setting an autoforward ensures that all mail is received in his new mailbox on Domino. a. If a directory synchronization solution has been installed, then run a synchronization to put the Domino account into Exchange.
753
b. Add a Contact to Exchange by opening the Active Directory Users and Computers and right-clicking the Organization. Select New Organizational Unit (Figure B-2).
754
d. Select the newly created Organizational Unit folder, right-click, and select New Contact (Figure B-4).
755
e. Enter details of the person who you are migrating and give a meaningful display name and click Next (Figure B-5).
f. Ensure that Create an Exchange e-mail address is selected and click Modify g. Click SMTP Address and click OK (Figure B-6).
756
h. Enter the secondary Domino SMTP address (that is, localpart+@+domino server FQDN ). In our example, this is cryan1@migrate2ka.itso1.eu (Figure B-7). There is no need to modify anything on the Advanced tab. Click OK.
i. Click Next and then click Finish. 7. To add the autoforward, in Active Directory Users and Computers, select View Advances Features (Figure B-8).
757
9. Right-click Properties, select the Exchange General tab, and select Delivery Options (Figure B-9).
758
759
11.Select the forwarding account, which is the name domain/OU. In our example, it is cindy ryan itso1.ey/mytest (Figure B-11). Select OK.
12.Click OK again.
760
From now on, all e-mail for the user is forwarded to the Domino account. You can migrate the user any time from this point forward.
761
762
2. If you are using Exchange connectors for directory synchronization, run a synchronize now and replicate directory between Exchange servers. 3. Provide users with desktop support (through Sametime). 4. In some migrations, you might be required to remove the account after a successful migration has been acknowledged. Refer to Chapter 4, Overview of the migration procedures on page 99.
763
764
Appendix C.
765
766
To install the plug-ins, follow these steps: 1. Create the following directories on the Windows Sharepoint server: C:\WebSphere\AppServer\bin C:\WebSphere\AppServer\config C:\WebSphere\AppServer\etc C:\WebSphere\AppServer\logs 2. Copy the following the files: Copy iisWASplugin_http.dll to C:\Websphere\AppServer\bin Copy plugin_common.dll to C:\Websphere\AppServer\bin Copy \Lotus\Domino\Data\domino\plugins\plugin-cfg.xml to c:\WebSphere\AppServer\config
767
3. Configure the Plugin-cfg.xml: a. Open the following file in a text editor such a WordPad: c:\WebSphere\Appserver\config\plugin-cfg.xml b. Change Hostname to the host name of the Domino server. c. Add the following after <UniGroup Name=default_host_URIs>: <Uri <Uri <Uri <Uri Name="/*.nsf*"/> Name="*.NSF*"/> Name="*/icons/*"/> Name="*/domjava/*"/>
768
4. Update the registry (Regedit). Add the following entries to the registry under _HKEY_LOCAL_MACHINE: > SOFTWARE > IBM If IBM does not exist, right-click IBM, then click New Key (Figure C-5).
769
5. Enter WebSphere Application Server, right-click WebSphere Application Server, and then click New Key (Figure C-6).
6. Enter 5.0. The version number might change depending on the version of WebSphere installed (for example, 5.1.0.1). You need to add the following string values: BinPath with a value of C:\websphere\AppServer\bin InstallLocation with a value of C:\websphere\AppServer LibPath with a value of C:\websphere\AppServer\lib MajorVersion with value of 5 (again dependant on the release) Plug-in Config with a value of C:\websphere\AppServer\config\plugin-cfg.xml
To add a string, right-click the version number that you created, then select New String Value (Figure C-7).
770
7. Enter the string name (for example, BinPath). 8. Right-click the string (BinPath) and select Modify (Figure C-8).
10.Do the same for each of the strings mentioned above. The registry should look like Figure C-10.
771
12.Navigate to the Default Web site and right-click the default Web Site. Select New Virtual Directory (Figure C-12).
772
13.You are presented with the Virtual directory creation wizard as shown in Figure C-13. Click Next.
773
15.Enter the path for Web site contents path. This path is Default Web C:\Websphere\AppServer\Bin. Click Next (Figure C-15).
16.Select Read, Run Scripts, and Execute, as shown in Figure C-16. Click Next.
774
775
19.Select Properties and click the ISAPI Filters tab (Figure C-18). Click Add.
20.Enter iisWASPlugins for the filter name and enter C:\websphere\AppServer\bin\iisWASPlugin_http.dll for the executable. Note: You can use browse to search for the file if you want.
776
777
22.Add a WebExtension: a. From IIS manager select Web Service Extensions, right-click, and select Add new Web service extension (Figure C-20).
b. Call the extension iisWASPlugins. c. Add the following Dlls to the required files: C:\websphere\AppServer\bin\iisWasPlugin_http.dll C:\websphere\AppServer\bin\plugin_common.dll d. Click Set extension services to Allow.
778
e. Click OK. Note: Do not do the following step if you are configuring IIS on the same physical machine as the Sharepoint server. Otherwise, Sharepoint will fail to load.
779
f. Right-click Web Sites, and select the Services Tab. Select Run WWW services in IIS 5.0 isolation mode.
780
23.Add the path extensions for the Domino Web Access. a. Start the Sharepoint central Administration tool. Select Start Programs Administration Tools Sharepoint Central Administration (Figure C-23).
781
b. Select Configure Virtual Server Settings under Virtual server configuration (Figure C-24).
782
c. Select the Virtual server to configure. In our Web site, this was <sharepoint Web site> (Figure C-25).
783
d. Under <Virtual Server Management>, select Define managed path (Figure C-26).
784
e. Under Add a new path, enter http://<server name:port>/mail (for example, http://sps1-lab-1:89/mail), and click Exclude Path. Click OK. (Figure C-27)
f. Repeat for the following: /inotes and /domjava The command line to do this is as follows:stsadm -o addpath -url http://localhost/mail -type exclusion stsadm -o addpath -url http://localhost/inotes -type exclusion stsadm -o addpath -url http://localhost/domjava -type exclusion 24.Add users credentials to the person document. You need to add the Domain login credentials to the user accounts. If you use the ADSYNCH to add users from Active Directory they are automatically added. a. Open the person document.
785
25.Set up Web redirection. As we pass the credentials to Domino, Domino can now match to a user record. Domino therefore knows the mail file for the user. It would be a tedious task to configure a unique mail Web part for each user containing the location of the mail file. Fortunately, Domino comes with a Web redirector that we can use to automatically open a persons mail file based on passed credentials. The current one shipped with Domino has limited capability. Unlike an earlier release, it does not allow the administrator to define the mail component that should be open (for example, inbox, calendar, address book, and so forth). However the version 641 available at: http://www-10.lotus.com/ldd/sandbox.nsf/140e61e7f55c607685256ead0064 d6c4?OpenForm&ParentUNID=F4B19C0C3327DF5385256A8F0063BDF4 Unzip and copy the WebMailRedirect641.ntf to the Domino server data directory. a. Create the Inbox redirector database from the Domino administration client, select File Database New. b. Select the server for the database (for example, migrate2003b/itso/fr). c. Give the database a name (for example, mail redirector). d. Give the database a file name (for example, redirmail.nsf). e. Select the server to where you copied the template. f. Select WebMailRedirect641.ntf as the template.
786
g. Click OK. h. Configure the database. Click Setup. i. Click Server Settings and select Dynamic if you have multiple servers and Fixed if you have a single server. j. If Fixed enter the Domino server name.
787
k. Click UI setup. Set the time out to zero (0) and disable personal profiles. l. Click the twisty next to Disable for Global profiles and select iNotes inbox portal.
788
m. Click Application setup and select Auto Set ACL settings. n. Click Save and Exit. o. Create new redirector database for Calendar. p. Optionally create additional redirect databases for ToDos and Notes.
789
Tip: For a full inotes view leave the UI setup as defaults. 26.Add Web part to Sharepoint. Add additional Web parts to your Sharepoint site for Mail and Calendar. a. Launch your browser b. Enter the URL of your site. (In our example , we created a new site. Thus, our URL was http://sps-lab-1:89/sites/mail/newsite.) c. Click Modify Shared Page.
d. Under modify shared page, click Search. e. Enter Page Viewer in the search box.
790
f. Select Page Viewer Web part and click Add (Figure C-34).
g. Click OK. h. Exit the modify page (click the little x). i. Select open the tool pane form the new Web part.
j. Enter the full FQDN of the Domino server followed by /<redircordb.nsf>. In our example, this would be http://migrate2003b.cam.itso.ibm.com/redir.nsf.
791
k. Adjust the size to your site preferences. l. Click OK. The Web part should resolve to the new URL m. Clear all cache from the Web browser, and when prompted log in as a valid Domino user. In our example, this was spovall.
792
The redirector message is displayed in the Web part window while the mail file is accessed and the view built.
After a short while the mail file will be open in the Web part.
793
794
Appendix D.
795
796
issues If the Domino Migration Tool fails while users are in the process of being migrated
Solution 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.
797
798
Appendix E.
799
800
Appendix F.
Installing Domino
This appendix serves as a quick reference for optionally installing Domino. In the case that you are migrating from Exchange and are not familiar with installing Domino Servers, you can use this appendix as a quick reference guide. Important: This appendix is simply a quick reference for optionally installing Domino. Refer to the product documentation available at the IBM Web site for comprehensive instructions: http://www.lotus.com/ldd/notesua.nsf/0b345eb9d127270b8525665d006bc35 5/8313e8d10f025dee8525698100541f6d?OpenDocument
801
3. Read the license agreement and click Yes to accept the license terms (Figure F-2).
802
4. Enter your Name and Company and then click Next (Figure F-3).
803
6. Select Domino Enterprise Server (Figure F-5). If needed, you can customize services by clicking Customize. Click Next.
7. The installation is complete, as shown in Figure F-6. Click Finish and then start Domino server to begin the setup.
804
8. The window changes to show Welcome to Domino Server Setup, as shown in Figure F-7. Click Next.
805
9. In the First or additional server window, select Set up the first server or a stand-alone server (Figure F-8). Click Next.
806
10.In the Provide a server name and title window, enter your values (you can leave the title blank because it is not a required field), as shown in Figure F-9. Click Next.
807
11.In the Choose your organization name window, enter your values (in this example, ibm) and provide a suitable password for the Organization Certifier, as shown in Figure F-10. Keep this password somewhere safe, because you will need it later. Click Next.
808
12.Enter the Domino domain name and click Next, as shown in Figure F-11.
809
13.In the Specify an Administrator name and password window, enter the name Domino Admin with a suitable password, as shown in Figure F-12. As before, keep this password somewhere safe.
810
14.When choosing which Internet services Domino should run, select all three options, as shown in Figure F-13, and click Next.
811
15.The Domino network settings window shows that all available ports have been enabled and that setup has determined what the fully qualified domain name of the server should be (Figure F-14).
812
16.In the Secure your Domino Server window, select Prohibit Anonymous access to all databases and templates and Add LocalDomainAdmins group to all databases and templates, as shown in Figure F-15. Click Next.
813
17.The final window asks you to review and confirm the setup options (Figure F-16). Click Setup.
When setup finishes, start the Domino server. For Windows environments, we recommend that you start the Domino server as a Windows service the first time you are prompted.
814
Complete the following steps: 1. From the Notes Client install CD, select Notes Administration client and run setup.exe. Click Next in the Welcome window, as shown in Figure F-17.
2. Read and accept the license agreement and click Next. 3. Select a directory and click Next, as shown in Figure F-18.
815
4. Select the client to install and click Next, as shown in Figure F-19.
5. When prompted for a user name, enter the name of the Domino Administrator you created (in this example, Domino Admin) and the host name for the Domino server, as shown in Figure F-20. Click Next.
816
6. Clear the Setup instant messaging option and click Next, as shown in Figure F-21.
7. On the Additional Services window, clear all options and click Finish (Figure F-22).
817
8. The Notes Client will now connect to the server and perform some local setup activities. Note that this will take a couple of minutes to complete before displaying the window shown in Figure F-23.
9. Set the field values, as shown in Figure F-23, and click Save & Close.
818
Related publications
We consider the publications that we list in this section particularly suitable for a more detailed discussion of the topics that we cover in this IBM Redbook.
IBM Redbooks
For information about ordering these publications, see How to get IBM Redbooks on page 820. Note that some of the documents that we reference here might be available in softcopy only. Migrating from Microsoft Exchange 5.5 to Lotus Notes and Domino 6, SG24-6955 Migrate Exchange 5.5 to Domino on Linux, REDP-3777 Exchange Your Exchange: Migrating from Microsoft Exchange 5.5 to Lotus Domino 6, REDP-3694 Active Directory Synchronization with Lotus ADSync, REDP-0605
Online resources
These Web sites and URLs are also relevant as further information sources: Lotus Developer Domain http://www.lotus.com/ldd Trade up to Lotus Software - Move to Lotus campaign http://www-142.ibm.com/software/sw-lotus/lotus/offering1.nsf/wdocs/m ove2lotus
819
820
Index
A
Access Control List (ACL) 117, 181, 191, 353354, 427, 504, 530, 585, 628, 630, 670, 675 acquiring the necessary information for migration 90 Active Directory 14, 60, 96, 157, 172, 211212, 329, 364, 409, 495496, 503, 519, 626, 652, 696, 699 group policies 531 lookup addresses 515 managing users 524, 526 propagate account changes 14 remains the corporate directory 520 user 519, 526 users 535, 551 add a local replica 246 add users 452 add users from foreign directory source 408 additional resources 694 Address book 307308 address book 33, 37, 76, 78, 132, 193194, 330, 359360, 379, 405, 411, 440, 442, 487488, 496497, 627, 663, 684, 689, 721722 display name 509 LDAP name 308 successfully lookup names 330 address conversion 359, 361, 363, 796 address field 291, 360 Address Space tab 283 address space 159, 161, 215 administration and support infrastructure 65 ADSync 522 advanced office workstation 31 Advantages of Domino Server over Exchange Server 12 Advantages of migrating from Exchange to Domino 10 advantages of the product 265 application design 586 archiving or sending Public Folder data elsewhere 665 assembling the project team 52 autoforward 104, 579, 751, 753 automated application synchronization 84 automated directory synchronization 83 automated e-mail message Notes Upgrade Services 375 Automatic Deployment Toolkit (ADT) 96 automating a message to initiate Notes Upgrade Services 376 Automating Notes Upgrade Services 375
B
backup and disaster recovery 96 basic office workstation 31 Basics tab 131, 198, 297, 377, 380, 504, 516, 547 before you begin removing Exchange 695 benefits of proof of concept deployment 86 benefits of this approach 86 Binary Tree 104, 106, 262, 264, 318319, 398, 437, 463, 625626, 761 CMT 463, 492, 626 Domino Coexistence 318319 release memos 437 business requirements 55
C
Calendar Connector 114, 176, 230, 241242, 263264 Exchange 2000 247 calendar data 262, 264, 385 Calendar entry 311 calendar entry 359, 366367, 405, 438, 441, 463, 483, 523524, 566, 665 calendar migration results 481 CERT.id 118, 120, 181, 183 certifier ID 118, 120, 181, 183, 341, 349, 539, 546 Clear Roadmap 12, 24 Client Genie 713714 Central database 716, 720 Clientside installation 719 database 716 log database 716 client offering 28, 32 full range 28
821
client selection 73 available options 74 cost considerations 79 decision points 81 Linux 79 Macintosh 79 offline usage 79 performance 80 platform 79 requirements 74 security 80 TCO 79 user training requirements 78 Clients 73 CMT 8990, 398, 402, 441, 462, 464, 471, 481, 625626 add users from Domino 408 add users from foreign directory source 408 choosing items to migrate 411 configuring input parameters 411 configuring settings 402 distribution lists 412 end date 414 end-user migration 460 Exchange User Selection 419 groups 412 image 463464 MAPI profile 406, 442 migrating calendar 411 migrating distribution lists 423 migrating mail 411 migrating server data 431 migrating shared mailboxes 406, 442 migration details 432 migration document 461 migration e-mail 456 migration process 401 migration steps 401 Outlook and Exchange settings 404 prerequisites 399 registering users 429 registration settings 428 Reset Message Classes to Default 408 running the migration 433 running the user import 421 selecting users for migration 425 selecting users to import 419 setting up licenses 399 Source mail system selection 403
specifying details for the migration 427 specifying range of dates 413 start date 414 starting the migration 431 target mail system selection 403 Top level folder settings 408 troubleshooting the migration 431 CMT for Exchange and Domino Coexistence 326 CMT for Public Folders a migrated Public Folder 642 contacts 642 custom fields 645, 647 custom form in Domino 649 customized Public Folder forms 645 described 626 Domino configuration 629 Domino database, after migration 642 importing Public Folder names 632 Importing Public Folders 636 importing standard forms 636 migrate permissions 634 migrated document 650 migration results 641 migration settings document 627 specifying types of messages for migration 629 CoBIT 4.0 22 coexistence 87 application access 84 application synchronization 84 calendaring and scheduling support 83 directory synchronization 82 messaging 82 public folders 583 strategy 82 coexistence scenario, using the PIM portlet approach 41 coexistence solution 315, 318 co-existence strategy 4 coexistence strategy 82, 101, 315 coexistence with Exchange Connector 322 coexistence, key steps 48 collaborative application 8, 32 IBM Lotus Domino 8 Com Trace 746 common directory requirements for coexistence 496 Common Migration Tool (CMT) 8990, 103104, 261, 318319, 326, 397398, 437438, 753, 761 Common PIM Portlet 38
822
Common PIM Portlets Mail Portlet 40 Communication plan creating 58 topics 58 Communications 57 complete the mail template (CMT) 261262, 438439, 625626 composite application 6, 12 Conceptual Overview of how it works 114, 176 configuring Calendar Connector 249 configuring CMT and import users for migration 439 configuring CMT settings 402 configuring Exchange Connector for Lotus Notes 154 Configuring Lotus Domino 7 for SMTP message transmission 292 Configuring Microsoft Exchange SMTP 277 configuring the Binary tree tool for Outlook migration 438 configuring the import of Public Folders tool 627 connecting to an Exchange server 342 connecting to another users shared folder 674 Connector mailbox 117, 127, 181, 188 considerations 696 considerations for Public Folder Migration 580 converting Exchange addresses to Notes Canonical format 359 copy contents from shared folder to migration Folder 681 corporate infrastructure 366, 520 Active Directory 520 cost consideration 74, 79 creating a communication plan 57 creating a Microsoft Outlook Profile 368 creating a migration mailbox 677 creating a PST from a Public Folder 666 creating a Public Folder 567, 571 creating a risk management plan 69 creating a training plan 66 creating and configuring a shared Mailbox 670 creating and LDAP account in Notes 515 creating and setting up Exchange Connector Mailboxes 127 creating Exchange User Directory 132 creating Foreign Domain Document 130 creating LDAP address book in Outlook 505 creating Public Folders and administering them 567 creating the Administrator profile in Outlook 342
creating the connection between Domino and Exchange 595 cross-platform Calendar 83 custom application 17 customized mail message e-mail trigger 446 customized to migrate this (CMT) 626
D
dat file 723 Data importance 86 Data migration 84 Data migration using Notes Upgrade Services 366 Data retention 86 Defining the project scope 54 Deploying the coexistence and migration strategy 94 Deployment approaches - Proof of concept deployment 86 Deskless Workforce 30 Determining the characteristics of the servers needed 70 Developing a coexistence and migration strategy 82 Developing the training plan 66 DHTML application 34, 76 Directory Assistance 109, 117, 134136, 181, 195197, 495, 503504 basic tab 137 database 135136, 195196, 503504 database name 504 Information 503 Directory assistance 132, 193 Directory Information Tree (DIT) 497 Directory Lookups 322, 329 Directory service 12, 60, 114, 177, 694, 702 Directory synchronization 226 customized connectors 308 directory synchronization 8283, 105, 114, 117, 176177, 242, 262263, 274, 308, 364, 753, 763 Exchange Connectors 105 Microsoft Exchange Server directory 242 disable LDAP 502 Disaster recovery policy 65 disk I/O 22 disk i/o heavily used system 22 distinguished name (DN) 497, 499
Index
823
Distributing client software 95 distribution list 61, 91, 104, 412, 422, 696, 699, 722, 761 dll file 450, 716 DNS Name lookup 322, 329 resolution 322 document link 155, 210, 317, 708 Documenting the business requirements 54 Documenting the current messaging environment 59, 799 Documenting the Exchange environment 59 Documenting the hardware profile 64 Documenting the Microsoft Exchange environment 59 Documenting the network infrastructure 64 Domain Name System 277 Domino amount of servers needed 72 choosing the platform 73 CPU scalability 71 memory utilization 72 scalability 71 Server Configuration Document 305 server types 72 sizing 70 SMTP mail traffic 292 topology 70 Transaction logging 71 Domino 7 3, 15, 2728, 47, 52, 89, 175, 201, 261, 264, 315, 340, 398, 440 Domino Access 10, 18, 3638, 74, 77, 366 Domino Access for Microsoft Outlook 73 Domino Access for Microsoft Outlook (DAMO) 78, 366 Domino Address Book 360361 Domino address book Person Document 360 Domino Administrator 53, 89, 118, 180181, 300, 340341, 375, 499, 502, 525, 527, 565, 683, 687, 715716, 814, 816 client 348 directory synchronization 229 Id 353 Server pane 376 Domino administrator normal user registration process 90 Domino client 27, 523
Domino considerations 585 Domino database 17, 242, 398, 409, 511, 583584, 626, 641, 651653 free/busy time calendar information 242 Lotus 123 spreadsheet data 653 new Web service 17 pre-registered users 409 Domino Designer 17, 28, 586, 617, 620, 648649, 653, 737 7 Help database 622 changing the name of a view 620 client 16 creating a form 648 modifying a view 617 modifying columns 619 Service Request Database 617 Domino Directory 9, 117, 124, 181, 242, 276, 358359, 399, 403, 440, 453, 496, 519, 627, 634, 715 Access Server field 399 Active Directory 527 Active Directory user 535 administration server 503 Exchange distribution lists 412 ID file 205 new Domino users 545 new user 538, 554 Domino directory manually re-create entries 9 setup policies 715 Domino environment 36, 59, 67, 77, 519, 713 Domino Server 12, 14, 276277, 282283, 285 new release 18 Domino server 32, 35, 70, 72, 117, 181, 242, 244, 251, 263, 265, 348, 353354, 363, 366, 376, 398399, 441, 496497, 520, 522523, 585586, 626627, 651, 683, 690, 710711, 715, 743, 796, 801802 address book 379 configuration part 745 Connector mailbox 127 corresponding mail file 366 DAMO client 524 Domino executable directory 256 Domino mail client 497 EXCALCON add-in task 255 Exchange users 366 existing Domino mail file 796 host name 816
824
IP address 282283 message queues 232 migrated mail files 796 migrated user 796 newly created Domino Mail Database 359 Notes client 585 Notes data directory 398 Notes.ini file 711, 748 password ID 527 security advantages 36, 77 SMTP domain name 285 Domino Upgrade Service 89, 339, 366, 625, 652 Domino Upgrade Services Overview 339 Domino Web Access 73 only option 91 Domino Web Access (DWA) 10, 18, 28, 34, 74, 76, 341, 356, 366 DUS 89, 683 adding administrator to ACLs of mail files 353 connecting to an Exchange server 342 converting mail 353 mail files 353 migration option 487 migration preparations 340 migration setup 340 migration tool 465, 467 passwords 353 starting 340 dynamic HTML 34, 76
E
ecKnowledge 583 admnistrators account 592 automatic mapping of fields 603 column mapping 601 Composer 595 connecting to the Exchange server 585 connection between systems 595 creating the connections 596 creating the Domino connection 600 customizing the Domino database 617 data comparison 610 designing the Domino application 586 Domino considerations 585 Domino database, after migration 613 Domino database, before migration 587 Exchange considerations 584
execution control 605 filtering fields 604 getting data from Exchange 584 installing on a Domino server 585 key manager 589 manual mapping of fields 603 migration results using a blank database 616 Oracle 590 post-installation tasks 594 product keys 593 profile 584 profiles 585 running as a service 594 running the coexistence 610 samples 592 SAP 590 scheduling 606 setting up 587 setup type 590 source data in Outlook 586 source Public folder 598 specifying the form and fields 599 SQL 590 starting the Composer 610 ecKnowledge product 583, 585 ecKnowledge service 584, 594 e-mail 11, 28, 30, 49, 55, 76, 104, 108, 272, 307308, 320, 329, 366367, 372, 374, 489, 709, 717, 756, 761 average size 62 e-mail account 344 e-mail address 165167, 220, 222, 265, 756 e-mail message 114, 176, 306, 309, 359, 375376, 411, 446, 670 e-mail metric 72 Enable Lotus Domino Proxy Addresses 165 Enabling Client LDAP lookups 505 Enabling Directory Assistance for LDAP authentication 503 Enabling Domino Routing and the SMTP Listener Task 299 Enabling LDAP during Domino server installation 499 Encrypted documents 63 end user migration tool 715 typical categories 29 very low customer satisfaction 58 end user (EU) 23, 29, 56, 58, 106, 363364, 439,
Index
825
445, 487489, 566, 586, 645, 648, 715716 End user migration overview 438 Entering the directory assistance database file name to a Server document manually 504 Entering the product keys 593 enterprise directory 14 Event viewer 702, 704 Exchange Administration procedures 66 antivirus 63 applications 63 backup software 63 calendaring and scheduling 61 contacts 85 creating a mailbox 677 e-mail 62 instant messaging 63 Personal address books 85 Personal folders 85 Public folders 62, 85 Service Level Agreements 66 User Directory 62 Exchange 2000 3, 38, 113, 175176, 243244, 275276, 315 Exchange 2003 18, 22, 113, 175, 181, 267268 Exchange Connector 237 modified default recipient policy 267 second modified recipient policy 268 Exchange Administrator 53, 346, 366, 499, 617, 700, 705 Exchange administrators 53 Exchange client topology 60 Exchange Connector 113, 175177, 249, 262, 264, 273, 318, 321, 708, 712, 763, 799800 as a service 225 Conceptual overview 178179 gathering information about Domino 180 gathering information about Exchange 180 ID file 181 Lotus Notes User ID 118 multiple Exchange servers 220 Notes client 202 Notes configuration utility 202 operating 226 Person document 184 preparing for the installation 116, 179 starting 225 user ID 190, 194 verifying directory synchronization 227, 229
Exchange Connector installation installing Notes 200 registering connector with Notes 181 Exchange considerations 584 Exchange Directory 62, 307, 322, 364 Exchange Public Folder 584, 586, 613, 626627, 629630, 660, 665 Exchange Server Lotus Notes client 138 Notes Client 147, 150, 203 Exchange server 12, 43, 5960, 63, 105, 108109, 138139, 147, 176, 180181, 200, 203, 242, 264, 266, 276, 342343, 365366, 399, 405406, 408, 441, 481, 496497, 522523, 584585, 626, 694695, 763 Administrator mail profile 342 Administrator profile 343 data 405, 441 data store 366 directory 496 functionality 694 mail file 353354 Migrating users 346, 348 name 180, 800 Notes Client 200, 202 Organizational Forms library 584 Outlook client 496 storage limitations 386 x client 201 exchange server domain name 277 inbound and outbound SMTP messages 306 Exchange server topology 59 Exchange services 61 Exchange System Manager 154, 166, 209, 226, 246, 249, 274, 276, 568, 571, 677 Manager dialog box 156, 158, 211, 213 Manager window 221 Exchange user 65, 82, 114116, 178, 187, 242, 259, 264, 306, 310, 341, 409, 423, 497, 516, 524 Active Directory Organization Forest 516 drop-down list 352 Exchange Connector ID 187 free/busy time 230 person document 229 specific training guide/program 65 exchange.box database 233 exchangenames.nsf 193, 218
826
Exchconn.ini file 238 Executive overview of results 318 External DNS 275
F
file name 189, 192 Final phase 51 Closure 97 Finding an address in the Domino Directory from Outlook 512 first in, first out (FIFO) 164, 219 Flexibility in Features and Offerings 29 foreign directory source 408 FQDN 291, 298, 508, 516 free/busy time calendar information 242 lookup 262 search 242 Further requirements 56
G
General setup information 180 Global Access List (GAL) 91 global domain Document (GDD) 266, 292, 295 GMI Infopath_2_Notes 731
H
Hardware inventory 64 Help Desk 65 How the migration process works 340 How to share data in a mailbox 670 HTML content 466467
Install and Setup Notes Client 138 Install Calendar Connector 244 Install Calendar Connector Add-In for Lotus Domino 255 Install Exchange Connector for Lotus Notes 150 Installation 398 Installing and setting up the Exchange Connector 181 Installing Exchange as a Foreign Directory Source 348 Installing Lotus ADSync 525 Installing the Calendar Connector 244 Installing the Exchange Connector 117 Installing the Exchange Migration Component for Lotus Notes 368 InstallPump 96 Instantaneous rollout 95 Interaction between the LDAP enabled server and client 498 internal folder 629 Internet address 298299, 428 Internet Mail Service (IMS) 276 Internet protocol 23, 297 Internet standard 37, 55, 78 Improved interoperability 55 Native support 37 Introduction 4 IP address 148, 252, 276, 282, 427, 498 IPM.Post.Account form 599 ISO 17799 22
J
Java controller 744 JavaScript 740
I
IBM Tivoli Configuration Manager 96 iCAL support 263264, 273, 665 iCalendar attachment 272 ICODEX Client Genie Login dialog box 717 Login Screen display 717 ID file 80, 117, 126, 181, 358, 393, 399, 428 Implement Directory Assistance 134 Import/Export wizard 596 Importing Public Folder names 632 Inbox 28, 40, 383, 463464, 670 Initiating Notes Upgrade Services from an automated message 383
K
Key Manager for ecKnowledge 589 key step 48 Key steps involved in the Proof of Concept / Pilot deployment 87 Key steps that are involved in the proof of concept deployment 87 Knowledge Workforce 31
L
LDAP account 497, 515 LDAP architecture overview 497
Index
827
LDAP directory enablement 501 store 497 LDAP Directory Configuration 496 LDAP enablement 499, 522 Domino server 499 LDAP implementation in Domino and Exchange 499 LDAP service 497, 499 left-hand pane 532, 536 appropriate container 532, 536 Levels of coexistence 82 Lightweight Directory Access Protocol (LDAP) 495, 497 Linux 79 local Outlook 365366 Notes Upgrade Services migration 391 local replica 246 Lookup Results 259 lotus 113114, 175176 Lotus ADSync 524 dialog box 540 Notes Settings 529 Options window 528 tool 527 Lotus Domino 3, 28, 32, 67, 72, 115, 117, 176177, 242, 244, 261262, 397, 399, 715 coexistence scenario 41 integrated collaborative environment 16 Name Space 264 Lotus Domino 7 SMTP environment 276 Lotus Domino Administrator 7 Help 183, 199 permissions 118, 127, 187, 189, 256 Lotus Note 10, 13, 2728, 52, 69, 113, 175, 242243, 398399, 438, 451, 515, 713714 default format 220 Exchange Connector 176, 179 Exchange connector 113114 key original differentiators 16 Message flow 232 message flow 232 Microsoft Exchange Connector 220, 238 Lotus Notes Configure Exchange Connector 127 configure Exchange Connector 188 Connector 155, 169, 209, 226 Exchange Connector 176177 Exchange connector 175
Exchange Migration Component 368 Exchange Server 2003 Connector 205 Installed and configured Microsoft Connector 243 Microsoft Exchange Connector 180, 184 next release 24 right-click Microsoft Exchange Connector 169 Lotus Notes Client 14, 16, 28, 32, 75, 138, 232, 714715 Lotus Notes/Domino 14, 18 7.0.2 272 collaborative application access 21 executable directory 585 Lotus software 24
M
mail APIs 62 mail database 399, 406, 427, 440, 728 mail file 85, 102104, 342, 353354, 412, 427, 487, 523, 752, 796 mail flow change 761 mail message 14, 55, 307, 405406, 441442, 445446, 466, 469, 496, 523524, 626, 666, 708 specific delivery time 55 Mail message migration results 466 Mail Migration Results 464 Mail Portlet 38 Mail rules 61 mailfile 33, 76, 690 mailflow change 105 Managing users with Active Directory 535, 551 Manual application synchronization 84 Manual directory synchronization 83 Manual Migration 385386, 432, 580, 651, 724, 726 Manual migration using Notes Upgrade Services 385 MAPI profile 406, 420, 433, 442, 626, 629, 633 menu bar 132, 193, 256, 487488, 536, 552 message class 408, 444, 629, 636 message sent (MS) 309 Messaging - Exchange to Notes 325, 329 Messaging - Notes to Exchange 324, 326, 330 messaging system 22, 5051, 230, 273, 276 Methodology used for testing 316 Microsoft Domino Connector for Exchange 83 Microsoft Excel 653 Microsoft Exchange 3, 8, 38, 41, 47, 49, 175,
828
241242, 261262, 275, 340, 342, 397, 693, 708, 712 2000 Server 237 5.5 18 automated directory synchronization 263264 Calendar Connector 241, 254 calendar data exchange 263 Challenge 7 client topology 60 Connectivity Controller 168, 237 Connectivity Controller service 225 Connector 113, 117, 123, 151, 175, 180, 322, 713 Connectors 318 data 367 data migration aspect 747 directory 264 Domino Server 12 DUS 90 environment 59, 88 Exchconn.ini file 238 free/busy lookup 262, 264 free/busy schedule lookup 263 highly functional, stable and reliable connection 262 IBM Lotus Domino 3 Messaging 151, 206 Microsoft CDO 271 migration path 90 migration tool 90 MTA Stacks service 235236 Notes Connector 262, 264 organization 13 popular and functional connectivity solution 262 Public Folder 264 Server 89, 199, 237, 242, 264, 276, 345346, 670 Server directory 242 Server release 200x 264 server user 348 standard Notes Connector 264 such migrations 8 system 59 System Manager 276 user 8, 264, 351 Microsoft Exchange Connectivity Controller 225 Microsoft Exchange Connector for Lotus Notes 225 Microsoft Exchange Internet Mail Service 277 Microsoft Exchange SMTP overview 276
Microsoft Office centric desktops 14 Outlook 10 Outlook dialog box 374 software 24 System server middleware 14 Microsoft Outlook 9, 18, 28, 3638, 77, 323, 366367, 652, 708 Domino Access 28, 36 export data 652 Lotus Domino Access 3637 Microsoft SMS 96 Migrate local user data 445 Migrate server data 431 Migrated Domino mail file address fields 361 valid Notes Canonical addresses 363 Migrated mail file address conversion 363 address fields 361 migrated mail file address conversion 364 address fields 361 Migrating Contacts Public Folder 660 Migrating Exchange users and their data to Domino 341 Migrating Public Folders 636 Migrating shared Calendars Public Folder 665 Migrating shared Data 675 Migrating shared mailboxes. 670 Migrating users from the Exchange server to Domino 348 Migration 340 abandoning old data 85 calendaring data 85 deciding on data to be migrated 85 messaging data 85 public folders 583, 625 strategy 82 user data 85 Migration Procedure 99, 752 Specific technical details 102 Migration process 401 coexistence process 89 existing Domino user 359 overview 88 single step 88 migration process 82, 84, 88, 104, 340, 393, 398, 628, 715, 731, 761, 796797
Index
829
existing Domino user 359 Migration project acquiring the necessary information 90 administration procedures 66 backup and disaster recovery 96 basic requirements for the new system 55 categorizing the requirements 56 client selection 73 closure 97 commitment 51 communication plan 57 creating a schedule 54 current environment 56, 59 deciding on the coexistence level 82 designing the new environment 69 documenting the business requirements 54 documenting the expectations 58 expectations 94 high-level goals 52 initial kickoff meeting 52 Instantaneous rollout 95 key steps 48 management support 51 managing risk 68 network 64 new environment 56 planning the servers 70 requirements 55 roles 53 schedule 54 scope 54 setting boundaries 54 setting the expectations 58 sponsor 51 Staged rollout 94 support structure 65 team 52 team members 53 training plan 66 vision 52 migration project 4748, 100101, 707 adequate communication 49 adverse effect 82 business reasons 55 challenging aspect 101 Migration project overview 47 Migration Result chapter deals 463
migration result 89, 463464, 641 Migration results All day event 483 calendar data 481 Calendar View 481 CMT 465, 468, 470, 472, 475, 482, 484, 492 Contacts 486 DUS 465, 467, 470, 472, 475, 482, 484, 492 HTML messages 466 mail messages 466 Tasks 491 URLs 478 Migration results using a blank database 616 Migration steps 100 Migration strategy 82 migration strategy 50, 82 Migration tool 9 migration tool 61, 82, 86, 8990, 103, 106, 339340, 368, 397398, 441, 463, 481, 660, 714715 CMT 8990 DUS 89 Exchange migration component 368 mixed environment 87 mobile device 5, 10, 61 Modify/Create the Global Domain document 292 Monitor and Troubleshoot the Connector 230 Moving data from public folders 652 Multiple Exchange servers 220 multiple user 37, 78, 358, 721723
N
Name and Address Book (NAB) 363, 427 Name resolution, Security and Migrated permissions 634 NDL attachment 708, 712 ndl file 710 Network infrastructure 64 new user 535536 Non-migration coexistence 524 Notes 73 client installation 200 ID files 80 security 80 user information 204 Notes Canonical format 359363, 367, 403, 627, 635 Notes Client 9, 18, 67, 74, 76, 106, 117, 181, 200,
830
202, 259, 277, 309, 348, 357, 368, 383, 465, 505, 583, 627, 650, 708709, 713, 814, 818 entire life cycle 715 Notes client 348 data subdirectory 395 historical data 386 multiple releases 18 same number 80 Notes Connector 261262 Directory Synchronization component 265 Directory Synchronization portion 264 main purposes 264 Notes database public folder contents 626 notes database 264, 585, 626627, 709, 731, 736 MS InfoPath form 731 Notes desktop 118, 181, 713714 Notes inbox 459 Notes installation directory 815 Notes Upgrade Service conversion options 389 Notes Upgrade Services 366 executable file 386 Notes user 228, 237, 242, 255, 265, 271, 306, 309, 340, 406, 442, 509, 626, 709 name 728 reply 306 notes.ini 155, 202, 209, 266, 502, 711712 NOTES.INI file ServerTasks line 502 Notes.ini file 253, 258, 502, 711712 noteslinks 709710 nsf file 365, 367, 385, 388, 391, 600, 721, 723 NT domain 180, 421
directory names 497 single version 71 Organization and certifier password 808 Other considerations 585 Outlook client 37, 74, 84, 236, 259, 341, 366367, 464, 472, 496, 522523, 584585, 652, 666, 721, 727 Domino Access 74 icon 342 Overall calendar view 481 preview pane 464 Outlook Contact Information 660 Outlook profile 369370, 497, 511, 591, 653, 676677 Outlook user 237238, 366, 466, 523524, 669670, 709 e-mail message 237 Overview of Domino Upgrade Services (DUS) 340 overview of Notes Upgrade Services 366 Overview of the Calendar Connector 242 Overview of the Client Offerings 32 Overview of the Exchange Connector 114, 176 Overview of the migration process 88 Overview of the product 262 Overview of the SMTP environment 275
P
PAB 61 Password protecting a PST 668 Performance consideration 74, 80 permissions 567568, 584, 626, 676, 696, 698 Person document 122, 126, 184, 229, 353, 359, 419, 427, 448, 459, 746 User name field 353 Personal Information Management (PIM) 3839 personal storage (PST) 61, 666, 668 personalized data 18 place upgrade 18 Plan, design, and document the new environment 69 Platform support 73, 79 Post-installation tasks 594 Potential benefits 263 Preparation 116, 179 Preparing for the migration process 340 Preparing the workstation for local migration 367 Pre-requisites 652 Prerequisites 243
O
Office Workforce 31 Offline use 79 On 629 on-disk structure (ODS) 71 opened Exchconn.ini file following text 238 opening mail-files 746 Operate the Connector 226 Operating and monitoring the Exchange Connector Services 225 operating system 6, 20, 70, 497, 502, 743, 746 different variations 9, 14
Index
831
Prerequisites for performing the migration 341 341 Preserving Exchange data for use in DAMO or Notes 340 Prevent Exchange Connector ID Synchronization (optional) 126 procedures/applications 62 Product setup and considerations 584 Project manager 53 Project schedule 54 project team 4748, 52 initial meetings 58 right personnel 53 Pros and cons of migrating 84 PST 61, 665 PST file 61, 108, 368, 376, 385, 388, 405, 441442, 666, 721 Public Folder 6263, 246, 398, 503, 565567, 583584, 625626, 651652, 671, 676, 694695 blank Lotus Notes databases 585 customized form 649 Home server 698 manual migration 651 migration settings 637 Notes URL 637 properties pages 584 workflow settings 638 Public folder permissions ability 571 replication interval drop-down list 247 server 60 tree hierarchy 571 public folder same data 671 shared folders 676 Public Folder Overview 566 Public Folder Security 566 Public Folder structure 566 Public folders administering 567 archiving 665 basics 565 CMT 625 coexistence 583 copying content 682 creating 567, 571 creating a PST 666 explained 565 migrating Public Folder data in a mailbox 652,
676 migration 583, 625 permissions 567568 PST 665 sending Contacts as vCards 663 structure 566 subfolders 567568
Q
Quotas 86
R
real simple syndication (RSS) 5 Realigning the expectations 94 Reasons for leaving things alone 694 Reasons to remove Exchange carefully 694 Recovery planning 96 Redbooks Web site 820 Contact us xix Register a Lotus Notes User ID for Exchange Connector 118 Registering existing users in Domino from Active Directory 532 Registering new Domino users in Active Directory 545 relevant profile 103, 752 Removing a server from a multi-server site 704 Removing Exchange considerations 694, 696 multi-server site 704 overview 694 planning 695 public folders 699 removing connectors 700 removing the server 700 single server, single site 696 removing Exchange 695 Removing Exchange servers 694 Removing the Microsoft Exchange environment 693 Removing the server 700 Replicator page 713, 716 replicator page entry 717 setting 715 Required permissions 567568 Requirements 55 return on investment (ROI) 17
832
rich text 104, 262, 317, 330, 408, 412, 621, 629, 761 high fidelity MIME encoding 262 Risk 68 Risk management 69 roadmap 12, 24, 99 Roles 53 rollout 86, 94, 102 Routable domain 164, 219 RTF attachment 155, 210 running Domino server input files 744 Running the coexistence 610
S
Schedule 54 scroll box 128129, 189, 193 Sealing 63 Security 63 Security consideration 74, 80 select File 654, 658, 674 Select users for migration 425 Selecting the client 73 Sending Contacts as vCards 663 Sending mail between Exchange and Domino via SMTP 306 Sending the migration e-mail 456 server data 19, 401, 405 Server Document Directory Assistance 134 Server document 134, 195196, 288, 292, 299, 503504 Directory Assistance 195 SMTP routing 292 Server drop-down list 128129, 189, 192 Server level spam control 23 server name 60, 104, 118, 131, 180, 257, 304, 427, 503, 508, 761, 796, 807 server start-up 226 Services Oriented Architecture (SOA) 5, 12 Set up CMT and migrate users 402 Set up the licenses 399 Setting the expectations 58 Setting up CMT 626 Setting up ecKnowledge 587 Setup and Configuration 266 shared data 406, 442, 563, 580, 669
Shared Folder 660, 675676, 728 Show Xdir 138, 199 Signing 63 Simple Mail Transfer Protocol (SMTP) 273 Single server, single site 696 Single step migration 88 process 88 SMTP address 265, 277, 326 SMTP Coexistence configuring Domino SMTP 292 Establishing SMTP message routing 303 SMTP coexistence configuring Exchange Internet Mail Service 277 configuring IMS 278 Domino SMTP 276 Exchange 276 Global domain document 292 pre-configuration 277 prerequisites 277 scenario 275 sending mail via SMTP 306 SMTP coexistence scenario 275 SMTP connection 262263, 292, 310 SMTP connector 264, 276, 702 SMTP Listener 299, 302 SMTP Listener Task 300, 303 Server document 300 SMTP message queue 236 transfer 293 transmission 277, 292, 306 SMTP namespace 265266 SMTP protocol 263264 SMTP Routing 329 SMTP routing 114, 261, 265, 273, 288, 318, 320, 708 redundant alternative messaging paths 265 SMTP Scenario 274 SMTP service 236, 276277 SMTP task 299, 306 SMTP transfer 272, 326 Specifying an Exchange Administrator mail profile 342 Sponsor 51 SSL 81 Staged rollout 95 Start Calendar Connector 254 Start Connector Add-In (EXCALCON) 257
Index
833
Start Directory Synchronization 169 Start Exchange Connector Services 168 Start the Connector 225 Starting the Exchange Connector 225 Starting the Migration 386 Steps to convert addresses to Notes Canonical format 363 Stop the Connector 237 string WTD 359360 Sub Folder 571 Support 65 Supported Environment 117, 180 Synchronizing with the Domino Directory 526 system expertise 30
Training plan 66 gathering requirements 67 planning for delivery 67 Training resources 68 Transactional workstation 30 Transend Migrator 721 Troubleshooting Notes Upgrade Services 394 Troubleshooting the migration 434
U
Understanding the role of Active Directory 520 un-interrupted access 20 UNIX user environment 744 Update Foreign Domain Document 256 Upgrade Notification 377 URL 117, 133, 180, 194, 478479, 708 URL link 330, 708, 713 URL shortcut 155, 210 Use SMTP 292 User and data migration coexistence 522 user credential 14 user ID 118, 124, 186, 190, 348, 359, 376, 529 User information window 816 user mailbox 102, 752 physical migration 752 User migration coexistence 523 user name 80, 169, 226, 346, 353, 359, 498, 728, 745, 816 Default values 728 Using a spreadsheet as an Intermediary 653 Using a spreadsheet to massage data 653, 691 Using CMT to Migrate Shared Data 675 Using Domino Designer to modify the view 617 Using DUS to Migrate Public Folders 652 Using DUS to Migrate Shared data 676 Using Lotus ADSync for long term user management 524 Using the Automated Migration 449 Using the Microsoft Exchange Connector for coexistence (Exchange 2003) 175 Using the product- step by step 267 Using the send e-mail Button 446
T
Tasks 491 Tasks/To Do entries 491 Team members 52 Technical overview of the product 263 Technical workstation 31 text file 364, 408 TFS Gateway 83 The basic requirements 55 The communication plan 57 The Exchange Public Folder 614 The five steps to migration with CMT 401 The project team 52 The project vision 52 The schedule 54 The scope 54 The sponsor 51 Think Outside the Inbox 28 third party application 471 product 20, 22 software 22 x 23 Tip 364 Tips and suggestions 237 To create and set up the Exchange Connector mailbox 189 To create the connector mailbox for bad mail 191 To Do entries 491 Tools used to create public folders 568 total cost 6, 39, 55, 73 total cost of ownership (TCO) 39, 55
V
vCard 662 Verify the synchronization 227
834
Visual Basic script 265, 267, 270, 604, 652, 740 correct execution 271 Voting 61
W
Web browser 10, 12, 74, 577, 713714 open nature 78 web browser linked document 713 Notes desktops 714 Web browser authentication 81 Web conferencing 32, 75 Web Service Definition Language 17 Web Site 48, 64, 73, 208, 583, 626, 652, 766, 772, 775, 783, 801 Web Site Voice 65 WebSphere Portal 5.1 38 Server environment 21 What has been improved in the Exchange Connector 2003 176 What is Common Migration Tool 398 What to migrate 85 Why local data migration is important 366 Why migrate? 8 Windows contact 157, 212 Windows Scripting Host (WSH) 715 workflow application 709710 Working with a blank database 613 WTD string 360361
X
X.509 certificates 81
Z
ZenWorks 96
Index
835
836
Back cover
BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL 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.