C Users Marg AppData Local Temp Plugtmp-8 Plugin-CMN 20 UserGuide

2.0Coexistence Managerfor Notes

User Guide

Quest Coexistence Manager for Notes

Quest Coexistence Manager for Notes User GuideUpdated - April 2010 (Doc ID 103)Software Version - 2.0

© 2010 Quest Software, Inc.ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc.

If you have any questions regarding your potential use of this material, contact:

Quest Software World HeadquartersLEGAL Dept5 Polaris WayAliso Viejo, CA 92656 USAwww.quest.comemail: [email protected]

Refer to our Web site for regional and international office information.

TRADEMARKS

Quest, Quest Software, the Quest Software logo, AccessManager, ActiveRoles, Aelita, Akonix, Benchmark Factory, Big Brother, BridgeAccess, BridgeAutoEscalate, BridgeSearch, BridgeTrak, BusinessInsight, ChangeAuditor, CI Discovery, Defender, DeployDirector, Desktop Authority, Directory Analyzer, Directory Troubleshooter, DS Analyzer, DS Expert, Foglight, GPOADmin, Help Desk Authority, Imceda, IntelliProfile, InTrust, Invirtus, iToken, JClass, JProbe, LeccoTech, LiteSpeed, LiveReorg, LogADmin, MessageStats, Monosphere, NBSpool, NetBase, NetControl, Npulse, NetPro, PassGo, PerformaSure, Point, Click, Done!, Quest vToolkit, Quest vWorkSpace, ReportADmin, RestoreADmin, ScriptLogic,

SelfServiceADmin, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Storage Horizon, Tag and Follow, Toad, T.O.A.D., Toad World, vAutomator, vConverter, vEcoShell, VESI,vFoglight, vPackager, vRanger, vSpotlight, vStream, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vEssentials, Vizioncore vWorkflow, WebDefender, Webthority, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks are property of their respective owners.

DISCLAIMER

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

http://www.quest.com/

mailto:[email protected]

CONTENTS

ABOUT THIS GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .V

OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VI

DOCUMENTATION CONVENTIONS . . . . . . . . . . . . . . . . . . . . . . VI

THE CMN DOCUMENTATION SUITE . . . . . . . . . . . . . . . . . . . .VII

CHAPTER 1INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

WELCOME TO COEXISTENCE MANAGER FOR NOTES (CMN) . . . . . .10MAIL CONNECTOR. . . . . . . . . . . . . . . . . . . . . . . . . . . .10

FREE/BUSY CONNECTOR . . . . . . . . . . . . . . . . . . . . . . . .11

COEXISTENCE MAIL ROUTING BASICS. . . . . . . . . . . . . . . . . . .11EMAIL COEXISTENCE BEFORE AND AFTER CMN . . . . . . . . . .13

DEPLOYMENT OF CMN MAIL CONNECTOR. . . . . . . . . . . . . . . . .14SIMPLE CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . . . .14

REDUNDANT CMN MAIL CONNECTORS . . . . . . . . . . . . . . .15

PROCESS SUMMARY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16SYSTEM REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . .17ABOUT QUEST LICENSE KEYS. . . . . . . . . . . . . . . . . . . . . . . .18

CHAPTER 2CONFIGURATION AND ACTIVATION . . . . . . . . . . . . . . . . . . . . . .19

PREPARE THE CMN CONFIGURATION . . . . . . . . . . . . . . . . . . .20CONFIGURATION EDITOR MENUS. . . . . . . . . . . . . . . . . . .21

CONFIGURATION EDITOR SCREENS . . . . . . . . . . . . . . . . .21

REVIEW AND UPDATE (IF NECESSARY)OTHER CONFIGURATION OPTIONS . . . . . . . . . . . . . . . . . . . . .24

CONFIGURE CMN LOGGING. . . . . . . . . . . . . . . . . . . . . .24

CONFIGURE DNS MX RESOLUTION . . . . . . . . . . . . . . . . .28

CONFIGURE SOCKET CHANNELS . . . . . . . . . . . . . . . . . . .29

CONFIGURING EXCHANGE-TO-NOTESMEETING INVITATIONS AND CHANGES. . . . . . . . . . . . . . . .30

iii


RUN THE MAIL CONNECTOR . . . . . . . . . . . . . . . . . . . . . . . . .32OPTIONAL "PASS-THROUGH" MODE . . . . . . . . . . . . . . . . .32

STARTING THE MAIL CONNECTOR . . . . . . . . . . . . . . . . . .32

STOPPING THE MAIL CONNECTOR . . . . . . . . . . . . . . . . . .33

MAIL SERVER CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . . .33CONFIGURE THE DOMINO SERVER FOR CMN . . . . . . . . . . .34

CONFIGURE THE EXCHANGE SERVER FOR CMN . . . . . . . . . .34

CONFIGURE THE DNS SERVER FOR CMN . . . . . . . . . . . . .34

APPENDIX A:KNOWN LIMITATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

APPENDIX B:TROUBLESHOOTING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

CMN DOES NOT APPEAR TO START . . . . . . . . . . . . . . . . .41

SERVER DISALLOWS MESSAGE . . . . . . . . . . . . . . . . . . . .41

OTHER ISSUES . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

APPENDIX C:CONFIGURATION PARAMETERS . . . . . . . . . . . . . . . . . . . . . . . . .43

GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

ABOUT QUEST SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

ABOUT QUEST SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . .50CONTACTING QUEST SOFTWARE . . . . . . . . . . . . . . . . . . . . . .50QUEST SUPPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50VISIT OUR ONLINE COMMUNITY . . . . . . . . . . . . . . . . . . . . . .51

iv

About This Guide

• Overview

• Documentation Conventions

• The CMN Documentation Suite


OverviewThis document has been prepared to explain the intended uses and operating instructions for Quest Software’s Coexistence Manager for Notes, and to explain how the product’s features are most typically used.

This document is intended for network administrators, consultants, analysts, and any other IT professionals who will install the product, use its features, or contribute to coexistence project planning.

Documentation ConventionsIn order to help you get the most out of this guide, we have used specific formatting conventions. These conventions apply to procedures, icons, keystrokes and cross-references.

ELEMENT CONVENTION

Select This word refers to actions such as choosing or highlighting various interface elements, such as files and radio buttons.

Bolded text Interface elements that appear in Quest® products, such as menus and commands.

Italic text Used for comments.

Bold Italic text Used for emphasis.

Blue text Indicates a cross-reference. When viewed in Adobe® Reader®, this format can be used as a hyperlink.

Used to highlight additional information pertinent to the process being described.

Used to provide Best Practice information. A best practice details the recommended course of action for the best result.

Used to highlight processes that should be performed with care.

Ctrl+C A plus sign between two keystrokes means that you must press them at the same time.

Edit | Copy A pipe sign between elements means that you must select the elements in that particular sequence.

vi

The CMN Documentation SuiteThe documentation for Quest Coexistence Manager for Notes includes:

• Release Notes (HTML): Describes the current CMN release—any new and enhanced features, resolved issues, and known issues. Also documents minimum installation requirements, and provides Quest contact information.

• Quick-Start Guide (printable PDF): An orientation to the product's basic purposes and features, and a brief case study showing how it is most commonly used within a typical coexistence scenario. Also documents System Requirements, and explains how to download and install the software.

• Coexistence Manager for Notes User Guide (printable PDF): Process instructions and application notes for configuring and launching CMN, and configuring the Domino, Exchange and Active Directory servers it will serve.

• Online Help (compiled Windows Help file): Context-sensitive instructions and application notes for the various screens and features of CMN’s Configuration Editor utility.

• CMN Free/Busy Connector Release Notes (HTML): Documents system requirements for the current release of the Free/Busy Connector (only), and any new and enhanced features, resolved issues, and known issues pertaining to that component.

• CMN Free/Busy Connector User Guide (printable PDF): Orientation to the Free/Busy Connector component of CMN, and process instructions and application notes for configuring and launching the component.

• CMN Free/Busy Connector PowerShell Administration Guide (printable PDF): Instructions for launching and using Microsoft Transporter (required for the Free/Busy Connector), using Windows PowerShell cmdlets.

All CMN documentation is intended for network administrators, consultants, analysts, and any other IT professionals who will install or use the product components, or who may help plan for their use in a coexistence scenario. All of these documents, including the online Help, are bundled and installed with the product, and all except the Help file are available separately at Quest’s SupportLink for Coexistence Manager for Notes: https://support.quest.com/SUPPORT/index?page=productInformation

vii

https://support.quest.com/SUPPORT/index?page=productInformation


viii

1

Introduction

• Welcome to Coexistence Manager for Notes (CMN)

• Coexistence Mail Routing Basics

• Deployment of CMN Mail Connector

• Process Summary

• System Requirements

• About Quest License Keys


Welcome to Coexistence Manager for Notes (CMN)Quest Coexistence Manager for Notes (CMN) provides rich email and calendar coexistence features between Lotus Notes and Microsoft Exchange 2007 or 2010. Quest CMN can be deployed either for a finite transition period, as when an organization is migrating from Notes to Exchange, or for indefinite or even permanent coexistence.

The Notes/Domino and Outlook/Exchange environments offer most of the same email and calendar capabilities, but the two brands implement many of these features differently. Outlook therefore cannot make sense of certain message types that originate in Notes, and vice versa. Often the recipient application can display the pertinent information correctly, but cannot then perform the calendar updates that would have been automatic if the recipient and sender were using the same email/calendar client. Or sometimes the receiving client can perform automatic calendar updates, but introduces errors—missing dates, or extrane-ous meetings, etc.—and will not detect or report the errors. Meanwhile, since the two environments also implement their calendar free/busy queries differently, each side is virtually blind to the availability status of the other side’s users.

Quest Coexistence Manager for Notes consists of two basic components: a Mail Connector for email remediation, and a Free/Busy Connector. The two com-ponents are separate entities, configured and run independently, although they are designed to work together.

For coexistence between Notes and Exchange 2007 (only), the directory synchronization features of Microsoft’s Transporter Suite can be configured to work with CMN for a more complete coexistence solution than can be achieved with CMN or the Transporter alone. The Microsoft Transporter does not support Exchange 2010, so a complete coexistence to that environment would require some other method or tool for directory synchronizations.

Mail ConnectorThe CMN Mail Connector is a Windows service that sits between the Domino and Exchange mail servers to monitor SMTP message traffic, and intercept and fix the incompatabilities inherent to certain message types and message contents and attachments. This email remediation service detects and converts in-transit messages as necessary, on the fly, to facilitate (for example):

• Invitations to recurring meetings.• Requests to reschedule meetings, or series of recurring meetings.• Cancellations of single meetings, or entire series of recurring meetings.• Notes links and Domino applications.• Attachments to single meetings or series of recurring meetings.

10

Introduction

The Mail Connector functions as a passive SMTP interface between the Domino and Exchange mail servers. That is, CMN does not establish a connection of its own to the server on either side, and does not store its output of processed messages. CMN catches and converts only messages containing calendar data and DocLinks, while all other messages simply pass through to the destination server untouched.

Free/Busy ConnectorCMN’s Free/Busy Connector lets Exchange and Domino query the calendar availability of each other's users. This sharing of free/busy data between Notes and Exchange makes possible automatic calendar updates for accepted meeting invitations, or when a user proposes a different day/time, or cancels, or so forth.

The Free/Busy Connector features and configuration are documented in the separate Free/Busy Connector User Guide and Free/Busy PowerShell Administration Guide that are included in this product kit.

Coexistence Mail Routing BasicsThese diagrams illustrate how email is routed in a single-namespace mail coexistence between Notes and Exchange—without CMN. This is native functionality and does not involve any Quest product.

via SMTP. (Notes is unaware of the native mailbox in Exchange.)

4. The msg is delivered to the Exchange user.

Internet Message Routing(MX Pointing to Notes)

1. Msg arrives from the Internet.

2. A msg for a native Notes user is delivered locally.

3a. A msg for a user familiar to Notes, but who has a mailbox in Exchange, is sent through the Smart Host to Exchange via SMTP. (A contact document exists in Notes for an Exchange mailbox, most likely when the Notes user has been previously migrated.)

3b. A msg for a native Exchange mailbox that is unknown to Notes beyond the domain name, is sent through Smart Host to Exchange

11


dress in the contact document (mail system is also set to "Other Internet Mail") and sends message to Smart Host. In either case, Notes cannot find a mail file for the recipient. Once the message reaches Exchange, a recipient lookup permits its delivery to the appropriate mailbox.

change finds a forwarding address in the contact ("targetaddress" attribute in AD) and sends the msg via the Send Connector to Notes, where it is delivered to the appropriate mail file. In the second case, the msg is still routed to Notes via the Send Connector, but is delivered in Notes only if the appropriate mail file exists.

Notes Message Routing

1. Message sent from one native Notes user to another. Delivered locally: Domino recog-nizes there is a valid mail file internally for the msg and does not send it to the Smart Host.

2. Message sent from native Notes user to Exchange user. Two possibilities: The Exchange user either is represented in Notes by a contact document (has been migrated), or is un-known to Notes. In the first case, Notes finds the forwarding ad-

Exchange Message Routing

1. Msg sent from one native Exchange user to another. Delivered locally: Exchange rec-ognizes there is a valid mailbox internally for the msg, so doesn’t send it to the Send Connector for external delivery.

2. Msg sent from native Ex-change user to Notes user. Two possibilities: The Notes user either is represented in Exchange by an external contact (created by Transporter), or is unknown to Exchange. In the first case, Ex-

12

Introduction

Email Coexistence Before and After CMN

These diagrams illustrate how Quest's Coexistence Manager for Notes (CMN) integrates into a single-namespace coexistence (using Smart Hosts) between Notes and Exchange. CMN uses round-robin traffic distribution for load balancing and redundancy among multiple CMN servers.

Smart Host Coexistence Without CMN

Smart Host Coexistence With CMN

1. The MX for external inbound messages is pointing to Notes:

1. The MX for external inbound messages is pointing to Notes.

2. Smart Host routes mail to Exchange for users without a native Notes mail file—typically represented in Notes by Trans-porter/Connector-created con-tact documents.

3. Send Connector routes mail back to Notes for users without a native Exchange mailbox—typi-cally represented in Exchange by Transporter/ Connector-created external contacts.

13


2. When CMN’s Mail Connector is installed and configured, the previously configured Smart Host in Notes must now point to the CMN server. Within CMN, the SMTP IN and OUT queues are also configured to accept mail from Notes and deliver mail to the receiving Exchange server. Effectively, the CMN server(s) sit between the original Smart Host.

3. Similarly, the Exchange Send Connector must now point to the CMN server(s), effectively splitting the connector. The SMTP IN queue receives mail from Exchange, and the SMTP OUT queue delivers messages to the qualified Notes server.

4. Multiple CMN servers can be deployed for load balancing and redundancy. Since Smart Hosts are being used in this scenario, MX priority cannot be used for redundancy. Instead, CMN will rotate through all available Exchange or Domino servers in the configuration.

Any of CMN’s defined outbound servers may in turn point to a load balancer that uses DNS round robin—in which case multiple DNS host records can be created, each for a different IP address, but the same host name. For example, three cmn.company.com records are created, each with a different IP. See this Microsoft article for more information about DNS round robin.

Deployment of CMN Mail Connector

Simple ConfigurationsA single instance of CMN’s Mail Connector may be used for coexistence between a single Notes server and a single Exchange server, or between multiple redundant mail servers on either or both sides of the CMN server.

14

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

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

Introduction

Regardless of the number of servers or your preferred routing schema, all mail servers on both sides must be defined in the CMN configuration file. Inbound and outbound servers may be specified to CMN by their DNS names, IP addresses, or MX-record notations. When a CMN server will distribute messages to multiple redundant servers, the destination servers can be priority-ranked in the MX record for load balancing.

For receipt of external inbound messages (from the Internet), CMN distributes the traffic among multiple mail servers on either side in a round-robin array.

Redundant CMN Mail Connectors

Multiple instances of CMN’s Mail Connector can be deployed for load balancing, and to provide redundant mail paths. As shown in the accompanying illustration, any CMN server can receive messages from any mail server defined in the con-figuration file, and likewise can relay messages to any of the defined destination servers. In multiple-CMN schemes, the CMN servers are load-balanced by MX-record priority designations used by the source mail system.

15


Process SummaryThe process of configuring and activating CMN consists of these general steps, all of which are explained in more detail in Chapter 2 (Configuration and Activation) of this Guide, and in the accompanying Free/Busy Connector documentation. This process begins with the assumption that your Notes and Exchange environments are already up and running.

1. Run the CMN Configuration Editor

Quest CMN includes a Configuration Editor utility to let you configure the Mail Connector service for your environment, and for your circumstances and preferences. Since these configuration options control CMN’s functions and scope, and designate valid mail servers, the Configuration Editor must be run before the service can be started.

2. Review and Update (If Necessary) Other Configuration Options

Other CMN and related configuration options may be set in the .xml configuration file, and elsewhere, although all of these are conditional:

• Configure CMN Logging: The log4net utility can generate log files of CMN system activity to document and elaborate on runtime errors, warnings and other significant processing events. This information is critical to diagnosing any runtime problems or performance issues that may arise.

• Configure DNS MX Resolution: One setting in CMN’s configuration file lets you enable/disable this feature, while another lets you specify the feature’s cache-update interval.

• Configure Socket Channels: By default, CMN waits up to 5 seconds for an available socket channel before opening a new one (if none are then avail-able). This is a "throttling" feature to enforce a time interval for CMN to conclude its communications protocol with a channel before opening another. The actual delay, in seconds, is a "delay factor" (5 by default) x the ratio of the number of open channels to the maximum allowed number of channels. If you want to change the delay factor to some other value, you can manually edit the settng in CMN’s active configuration file.

• Configure Exchange-to-Notes Changes to Accepted Meetings: A set-ting in CMN’s configuration file lets you specify which of two methods CMN should use when processing a Notes user’s receipt of an Exchange user’s change to either a single meeting in a recurring series, or an entire recurring series. Differences in how Notes implements calendar features in different client versions require that you choose which algorithm CMN should use when processing these sorts of messages.

3. Run Quest CMN Mail Connector

The CMN Mail Connector is typically run as a Windows service, but can also be run as a console application for shorter-term use, as in testing and diagnostics. In either case, once started, the application simply runs with no further input until it is stopped.

16

Introduction

4. Switch the Mail Servers to Work with CMN

Quest Coexistence Manager for Notes runs in conjunction with one or more Lotus Domino and Microsoft Exchange mail servers, and perhaps also with the Microsoft Transporter Suite coexistence application (only with Exchange 2007). As such, the Domino, Exchange and AD servers must be configured to recognize and route mail via CMN.

5. Configure and Run CMN Free/Busy Connector (Optional)

The Free/Busy Connector features and configuration are documented separately, in the Free/Busy Connector User Guide and Free/Busy PowerShell Administration Guide that are included in this product kit.

System RequirementsDomino Server(s):

• Lotus Domino version 6.5.1–6.5.6, or 7.0.0–7.0.3, or 8.0.0–8.0.2.

Exchange Server(s):

• Exchange 2010, 2007, or 2007 SP1 or SP2.

CMN Workstation (hosting the CMN service):

• Must be a separate machine from the Exchange and Notes servers: • Minimum required: 4-Core 3+GHz processor, 4GB memory. • Recommended: 8-Core 3+GHz processor, 8-16GB memory.

• Workstation operating system must be any of:

• Windows Server 2008 or 2008 R2, 64-bit only.• Windows 2003 Server (32-bit only), SP1 or higher.

• .Net Framework 3.5 must be installed. (The CMN Installer will install .Net 3.5 if it is not already installed.)

• SMTP service must be installed but not running.

• For Windows Server 2003 (only): POP3 service must be installed but not running.

End-User Workstations:

• Outlook client version 2003 or 2007, or Outlook Web Access 2007.– OR –

• Notes client version 6.5.1–6.5.6, or 7.0.0–7.0.3, or 8.0.0–8.0.2.

Important: These server reconfigurations should occur only after the CMN service is started (in the preceding step). Reconfiguring the mail servers before starting CMN would at least briefly send mail to a nonexistent destination.

17


About Quest License KeysCoexistence Manager for Notes is a metered-use product that will run only with the application of a valid license key. Quest Software sells CMN license keys by numbers of users served.

You can obtain your first or a subsequent license key by contacting your Quest Sales representative, or by email at [email protected]. When you obtain a license key, you must install it for it to take effect and enable the product. A license key is installed in the CMN Configuration Editor utility, in the About screen, which is opened from the Help menu. See the Help Menu section of Configuration Editor Menus in chapter 2 for complete instructions.

18


2
Configuration and Activation
• Prepare the CMN Configuration• Configuration Editor Menus• Configuration Editor Screens

• Review and Update (If Necessary) Other Configuration Options• Configure CMN Logging• Configure DNS MX Resolution• Configure Socket Channels• Configuring Exchange-to-Notes Meeting

Invitations and Changes

• Run the Mail Connector• Optional "Pass-Through" Mode• Starting the Mail Connector• Stopping the Mail Connector

• Mail Server Configurations• Configure the Domino Server for CMN• Configure the Exchange Server for CMN• Configure the DNS Server for CMN


Prepare the CMN ConfigurationCMN includes a Configuration Editor utility for you to configure the Mail Connec-tor in your environment. CMN configuration settings are saved in a file, which may be opened, modified and re-saved as needed by the Configuration Editor. The last-saved configuration file becomes the active configuration for the CMN Mail Connector. The configuration file controls only the CMN Mail Connector, not the Free/Busy Connector.

To start the CMN Configuration Editor:

• From the Start menu: Select Quest Software | Quest Coexistence Manager for Notes | Quest Coexistence Manager for Notes Configuration Editor

The Configuration Editor runs in a window with a navigation sidebar down the left side of the window. The sidebar is a list of all the screens in the program. A single "configuration" is the set of all settings on all screens in the Configuration Editor. Each screen name in the sidebar list is a clickable link that instantly opens the associated screen. The order of the screens in the sidebar list is irrelevant. An admin typically works through the list top to bottom, but you may visit the screens and edit their contents independently in any order you like.

The status bar at the bottom of the Configuration Editor window reports the current status of the CMN Mail Connector: Running or Stopped.

20


Configuration Editor Menus

File Menu

The File menu lets you open a previously saved configuration file, or save your entries and changes in an already open file:

• Open Configuration File: Lets you open a previously saved CMN configuration file—to edit and/or activate its settings. This option presents a generic Windows Open dialog box, set to the CMN default installation folder. When you open a configuration file, the Configuration Editor draws all of its data into the pertinent fields in all of the screens.

• Save Configuration File: Lets you save the current settings in the Configuration Editor (in all of its screens)—either under an existing name, or under a new name. The menu option presents a generic Windows Save As dialog box.

Help Menu

The Help Menu offers direct access to the on-line Help file for the CMN Configuration Editor, and also offers an About option that identifies the specific release of the software, and declares Quest’s intellectual property rights for the software and its documentation.

The About screen also lets you install a Quest license to enable CMN. CMN is a metered-use product that will run only with the application of a valid license key. Quest Software sells license keys by numbers of users served. When you obtain a license key, you must install it in CMN to enable the product.

You can obtain your first or a subsequent license key from your Quest Sales representative, or by email at [email protected].

To install a Quest license key for CMN on this Help|About screen:

1. Use the Browse button to locate and specify the License File.

2. Click Update License to install the license key.

Configuration Editor ScreensAll configuration settings that appear in the CMN Configuration Editor screens correspond to parameters that are stored and may be manually edited in the CMN .xml configuration file, as described later in this chapter. Appendix C: Configuration Parameters of this User Guide provides a table that shows how the fields in the Configuration Editor correspond to the .xml file parameters.

Note: Saving a configuration file makes it the active configuration for the CMN service.

21



Servers / Inbound

This screen defines the valid Domino and Exchange mail servers whose message traffic the Mail Connector will monitor—the servers from which CMN will accept incoming connections (to receive messages). The server name for an inbound server may be designated as the DNS name of the physical box, or by the IP address associated with the server, or by its Mail eXchanger (MX) record notation, which can rank physical server names by a priority usage preference.

Each row in the table defines a single server. Specify at least one server for each of Exchange and Domino. You may specify two or more for either or both. Click Add to define a new server in the table, or select an existing server and click Edit to change its configuration, or click Remove to delete it from the table.

Each server is defined by values in these columns:

• System Type: Select Microsoft Exchange or Lotus Domino.

• Server Name / IP Address: The server name for an inbound server, which may be designated as the DNS name of the physical box, or by the IP address associated with the server, or by its MX record notation.

Servers / Outbound

This screen defines the valid Exchange and Domino mail servers to which the Mail Connector will try to route outgoing mail. Each outbound server is designated here by the DNS name of the physical box, or by the IP address associated with the server, or by its Mail eXchanger (MX) record notation—which can rank physical server names by a priority usage preference.

Each row in the table defines a single server or MX record, and you must specify at least one server or MX record for each of Exchange and Domino. You may specify two or more servers for either or both sides—in which case CMN will distribute the outbound traffic among all of the servers defined for any single side (Exchange or Domino) in round-robin fashion.

Click Add to define a new server in the table, or select an existing server and click Edit to change its configuration, or click Remove to delete it from the table.

Each server is defined by values in these columns:

• System Type: Specify Microsoft Exchange or Lotus Domino.

• Server Name / IP Address: The server name for an outbound server, which may be designated as the DNS name of the physical box, or by the IP address associated with the server, or by its MX record notation.

22


Notes Doc Links

This screen lets you specify how you want CMN’s Mail Connector to handle Notes DocLinks. Select one of the radio-button options. If you select either of the first two, you must also specify a Site Address.

• HTML Links to your Domino webserver: A DocLink converted to an HTML link will not require the Notes client on the user’s desktop, and will instead open into a web browser if iNotes is enabled.

• Site Address: The URL for the Domino web server.

• HTML links to your SharePoint server (requires Notes Migrator for SharePoint): A SharePoint server link will point to a document on a separate SharePoint server. This option requires that you have Notes Migrator for SharePoint (formerly known as Proposion Portal format). If you select this SharePoint option, you must also specify:• Site Address: The URL for the SharePoint server.

• Notes NDL links (requires Notes client on Outlook users’ workstations to use): This standard DocLink format will work only if the Notes client is installed and running on the user’s desktop.

Network Settings

The settings on this screen tell CMN how to process message traffic, and how to maximize network and processing performance:

• Port Number to Listen On: The SMTP port that CMN will monitor. The default is 25, but you may specify any port from 1–65535.

• Performance Tuning: • Maximum Connections: Number of simultaneous open channels CMN will

allow. Default=600.• Maximum Processing Threads: Maximum number of threads CMN will use

to process message bodies. Default=16. In most environments this setting is best set to 4x the number of CPU cores.

Advanced Message Settings

Advanced Message Settings include SMTP port-configuration settings, and additional performance-tuning features.

SMTP Port Configuration

CMN’s Mail Connector is configured by default to send an SMTP NOOP every 30 seconds, to keep the server from timing out when processing larger messages. You can disable and re-enable this feature, and/or set the time interval to some other value, by these settings:

23


• Send Keep-Alives During Processing: Determines whether CMN will send NOOPS to a destination socket to keep the socket open in the event message processing is slow or otherwise delayed. This feature is on (checkbox is marked) by default.• Send Keep-Alive Message Every ___ Seconds: Number of seconds CMN

will wait before sending the first NOOP and each successive NOOP (if Send Keep-Alives is enabled). Default=30.

Performance Tuning

• Maximum Allowable Message Size: Maximum message size, in bytes, that CMN will process. Default=31457280 (30MB = 30 x 1024 x 1024).

• Maximum Message Process Time: Maximum time, in seconds, that CMN will spend processing a message before giving up and reporting a failure. Default=240 (4 mins x 60 secs/min).

Sub-Domain Settings

The setting on this screen is necessary for proper handling of accept/decline response messages, but only if you are using mutli-domain differentiation for mail routing. The value is optional if you are using smart hosts to route mail in a single-domain environment.

• Mail System SMTP Root Domain (optional): The SMTP domain name that will route mail from Notes to your Exchange server.

Review and Update (If Necessary) Other Configuration Options

Configure CMN LoggingBy default, CMN is installed with the log4net utility to generate log files of CMN Mail Connector system activity: to document runtime errors, warnings and other significant processing events. This information is critical to diagnosing any run-time problems that may arise. CMN log entries look like this:

2009-09-18 16:20:43,851 INFO CMN.logging - Connection from 127.0.0.1:200452009-09-18 16:20:43,866 INFO CMN.logging - [1] Established channel from

Domino(127.0.0.1:20045) to Exchange(10.4.160.17:25). Total Channels: 22009-09-18 16:20:48,804 INFO CMN.logging - [1] Message Sent From: , To: , Message Number:

(1) Message ID: () Size: (5) Proc Time: (188)msec Routed From Domino(127.0.0.1:20045) to Exchange(10.4.160.17:25)

2009-09-18 16:20:49,788 INFO CMN.logging - [1] Router closed. Open Sockets: 0

24


2009-09-18 16:24:54,446 ERROR CMN.logging - [2] Message Failed 552 CMN was unable to process the message. ICal Error: The recurring series spans over 1000 days, and Exchange can not display it. From: [email protected], To: [email protected], Message Number: (2) Message ID: () Size: (244159) Proc Time: (2828)msec Routed From Domino(127.0.0.1:20056) to Exchange(10.4.160.17:25)

2009-09-18 16:29:02,224 INFO CMN.logging - [152] Message Sent From: [email protected], To: [email protected], Message Number: (340) Message ID: () Size: (2) Proc Time: (0)msec Routed From Domino(127.0.0.1:27483) to Exchange(127.0.0.1:25) iCal:(no) iCal Was:(none)

CMN logging is enabled by default, but you may want to change the location of the log file, and/or change the scope and level of detail that will appear in the logs. Configuration options are set in a log4net configuration file, as described below. Level of detail is specified by one of these single words:

OFF FATAL ERROR WARN INFO DEBUG ALL

The values are listed here in ascending order of detail (left to right), and the log will contain items at and above (to the left of) the specified value. For example, the WARN level includes WARN, ERROR and FATAL events in the log file.

The CMN Mail Connector actually generates as many as three log files, so you can track different types and levels of program activity/event notices for differ-ent purposes:

• CMN.log: Captures a continuous stream of activity/event notices at a configurable level of detail. This general logging feature is on by default, and can be configured as described separately below. The CMN.log file is helpful for routine, general inquiries into CMN performance and processing.

• CMN_ERROR.log: Captures the 100 activity/event notices that preceded an error, but captures all notices at and above the INFO level of detail. (If this feature captured one level of detail deeper, to include the DEBUG level, the added level would impose a dramatic hit in performance, typically on the order of 5-10x slower.) This feature is on by default, and can be configured as described separately below.

• SMTP.log: Captures only SMTP commands, at and above the INFO level of detail. The SMTP logging feature is disabled by default, but may be enabled and configured as described separately below.

The CMN_Error.log and SMTP.log files are valuable diagnostic tools in the event of a system error. All three log files are generated as plain text.

The following subsections explain how some operational details can be config-ured by changing default parameter values in the log4net.config file in the CMN

Note: If you are upgrading from an earlier version of CMN, and log4net logging was turned off in that earlier version, you must manually edit the active CMN .xml configuration file to re-enable log4net. See the Getting Started / Upgrade Considerations section of the CMN Quick-Start Guide for the procedure.

25


installation directory. The log4net.config file is an XML file that can be opened and edited with an XML editor.

For more detailed information about the log4net utility and how its log files can be configured, see the log4net Config Examples at the Apache.org web site.

Configuring the CMN.log File

By default, the CMN.log file is named CMN.log, and is generated in the program’s executable directory, and the log track will roll over to a new file (close the ex-isting log file and create a new one) when its contents reach 10 MB in size. Also the log4net utility will create up to 25 sequential log files before deleting the old-est to make room for the newest. But these defaults can be changed in the log4net.config configuration file. To change any of these defaults:

1. Open the file log4net.config (in the CMN installation directory) with an XML editor.

2. Find the section <appender name="LogFileAppender" ...>, which contains the parameters for the CMN.log file.

3. Make any changes you care to make to these parameter values. Values must be enclosed in double quotation marks and followed by a trailing space and slash character as shown here:• <file value="[PathAndFilename]" />: Location and name of the log file

that log4net will generate. By default this value is set to ".\log4net\CMN.log".The path specification can be absolute (e.g., "C:\log4net\CMN.log") or relative to the installation directory (e.g., ".\log4net\CMN.log").

• <threshhold value="INFO" />: Scope and level of detail to appear in the logs. A valid value is any of these single words:

OFF FATAL ERROR WARN INFO DEBUG ALLThe values are listed here in ascending order of detail, left to right, and the log will contain items at and above (to the left of) the specified value. For example, <threshhold value="WARN" /> tells log4net to include WARN, ERROR and FATAL events in the log file. The level is set to INFO by default.

• <rollingStyle value="Size" />: Determines what will trigger log4net’s closing of a current log file and opening of a new one: either a change in calendar date, or a log file reaching a particular size. Parameter value is set to "Size" by default, or change to "Date" for the alternative.

• <maximumFileSize value="10MB" />: Maximum log file size—the size at which log4net will close the current log file and open a new one (applies only if <rollingStyle value="Size" />.

• <maxSizeRollBackups value="25" />: Maximum number of log files to keep—after which log4net deletes the oldest log file to create a new one.

4. Close and Save the configuration file under the same log4net.config filename.

Note: Any changes to the log4net.config file are immediately applied by the CMN service when the configuration file is saved.

26

https://svn.apache.org/repos/asf/logging/site/trunk/docs/log4net/release/config-examples.html


Configuring the CMN_ERROR.log File

By default, the CMN_ERROR.log file is named CMN_ERROR.log, and is generated in the program’s executable directory, and the log track will roll over to a new file (close the existing log file and create a new one) when its contents reach 10 MB in size. Also the log4net utility will create up to 25 sequential log files before deleting the oldest to make room for the newest. But these defaults can be changed in the log4net.config configuration file. To change any of the defaults:


2. Find the section <appender name="ErrorLogFileAppender" ...>, which contains the parameters for the CMN_ERROR.log file.


that log4net will generate. By default this value is set to ".\log4net\CMN.log".The path specification can be absolute (e.g., "C:\log4net\CMN.log") or relative to the installation directory (e.g., ".\log4net\CMN.log").




4. If you want to exclude SMTP logging from the CMN_ERROR.log file: Find the section <logger name="CMN.SmtpProtocol.logging" ...>, and set the <level value= /> parameter value to:

<level value="OFF" />


Configuring the SMTP.log File

The SMTP logging feature is disabled by default, but may be enabled and con-figured as described here. By default (if enabled), the SMTP.log file is named SMTP.log, and is generated in the program’s executable directory, and the log track will roll over to a new file (close the existing SMTP.log file and create a new one) when its contents reach 10 MB in size. Also the log4net utility will create up to 25 sequential SMTP.log files before deleting the oldest to make room for the newest. But these defaults can be changed in the log4net.config configura-tion file. To enable or disable the feature, and/or change any of its defaults:

27

2. To enable or disable the feature, find the section <logger name="CMN.SmtpProtocol.logging" ...>, and then:• To enable SMTP logging:

• Set the <level value="INFO" /> parameter value to INFO.• Uncomment the line:

• To disable SMTP logging:

• Set the <level value="OFF" /> parameter value to OFF.• Restore the comment enclosures to the line:

<appender-ref ref="SmtpFileAppender" />

3. Find the section <appender name="SmtpFileAppender" ...>, which contains the parameters for the SMTP.log file.


that log4net will generate. By default this is set to ".\log4net\SMTP.log".The path specification can be absolute (e.g., "C:\log4net\SMTP.log") or relative to the installation directory (e.g., ".\log4net\SMTP.log").





Configure DNS MX ResolutionDNS MX Resolution may be enabled and configured, or disabled, by manually editing the Mail Connector’s active .xml configuration file. The feature is off by default. To turn it on and/or to set its cache-update interval:

1. Use an XML editor to open the active configuration file. (Remember that the active configuration file for the Mail Connector is the last-saved configuration file in the CMN Configuration Editor.)

2. To enable DNS MX Resolution:

28


a) Find the <resolvemx> parameter, in the <root> node. If the <resolvemx> parameter does not already exist, create it as shown in the next step below.

b) Set the <resolvemx> parameter value to true:<resolvemx>true</resolvemx>

If the tags are omitted from the file, the feature is disabled.

If the tags appear in the file but are left empty (no value), the feature is enabled.

3. To set the cache-update interval for the DNS MX Resolution feature:

a) Find the <mxcacheupdateinterval> parameter, in the <root> node. If the <mxcacheupdateinterval> parameter does not already exist, create it as shown in the next step below.

b) Set the <mxcacheupdateinterval> parameter value to the number of seconds you want MX lookups to be cached:<mxcacheupdateinterval>600</mxcacheupdateinterval>

The default (if unspecified) is 300 seconds (5 minutes). You may want to increase the value to reduce the load on the DNS server and/or the network. You may want to decrease the value if you want change to take effect faster, and/or to allow for round-robin resolution.

This feature is applied separately per host, so (for example) if server A is looked up at 12:00PM, it will be cached until 12:05, while if server B is looked up at at 12:01PM, it will be cached until 12:06, and so forth. There is no setting that causes all hosts to expire/lookup at the same time.

4. Close and Save the configuration file under the same filename.

The new settings will take effect the next time the CMN service is restarted.

Configure Socket ChannelsBy default, the Mail Connector waits up to 5 seconds for an available socket channel before opening a new one (if none are then available). This is a "throttling" feature to enforce a time interval for CMN to conclude its communications protocol with a channel before opening another. The actual delay, in seconds, is a "delay factor" (5 by default) x the ratio of the number of open channels to the maximum allowed number of channels. If you want to change the delay factor to some other value, you can manually edit the setting in CMN’s active configuration file:

1. Use an XML editor to open the active configuration file. (Remember that the active configuration file for the CMN service is the last-saved configuration file in the CMN Configuration Editor.)

29


2. Find the <routerwaitsecs> parameter in the root level of the CMN Configuration file, and update its value to suit your circumstances. The value specified here (default=5) is the "delay factor" as defined above.

3. Close and Save the configuration file under the same filename.

The new settings will take effect the next time the CMN service is restarted.

Configuring Exchange-to-Notes Meeting Invitations and ChangesDifferences in how Notes implements calendar features in different client versions require different accommodations for end users with different Notes versions. The <notesclientversion> parameter (in the root level of the CMN Configuration file) tells the Mail Connector how to process Exchange-to-Notes meeting invitations and Exchange-to-Notes changes to existing meetings.

If your end users are running different versions of the Notes client, then you must choose which group will get the benefit of these conversions. Some admins simply choose the setting for whichever group of users is largest, but many admins feel that the issues encountered by Notes 6.5.6 users are more problematic than the issues associated with other versions, and therefore choose the 6.5.6 setting even if those users make up a minority of their overall users.

The <notesclientversion> parameter value defaults to "all" (for the default behavior of CMN before these alternate methods became available) if the parameter does not appear in the Configuration file when CMN is started. If the parameter or its value is missing from the Configuration file when the CMN Configuration Editor is started, the Configuration Editor automatically adds it with its default value of "all."

• For Notes 6.5.5 and 6.5.6 users: A Notes user's calendar can be correctly updated when the user accepts a proposed reschedule request for a single meeting that the Notes user had previously accepted at the invitation of an Outlook user. (See also the 6.5.1–6.5.6 option below, which resolves a similar issue for series of meetings.) To enable this fix, add this line to the root level of the CMN Configuration file:

<notesclientversion>v6_5_6</notesclientversion>

You can set the parameter to either v6_5_5 or v6_5_6; the same fix is activated by either value. For Notes 6.5.5 and 6.5.6 users, CMN automatically removes the old meeting from the calendar, but Notes–Outlook incompatabilities prevent CMN from adding the new (rescheduled) meeting to the calendar. Instead, CMN replaces the reschedule-notification message with a cancellation message that provides the details of the new meeting, and suggests that the user manually add it to his/her calendar.

30


The v6_5_6 setting also enables a similar fix for series of meetings that apply to client versions 6.5.1 through 6.5.6, as documented separately in the 6.5.1–6.5.6 option below.

• For Notes 6.5.1 – 6.5.6 users: A Notes user's calendar can be correctly updated when the user accepts a proposed reschedule request for a series of meetings that the Notes user had previously accepted at the invitation of an Outlook user. (See also the 6.5.5–6.5.6 option above, which resolves a similar issue for single meetings.) To enable this fix, add this line to the root level of the CMN Configuration file:


You can set the parameter to any value from v6_5_1 through v6_5_6; the same fix is activated by any value in that range. For Notes 6.5.1 – 6.5.6 users, CMN automatically removes the old meetings from the calendar, but Notes–Outlook incompatabilities prevent CMN from adding the new (rescheduled) meetings to the calendar. Instead, CMN replaces the reschedule-notification message with a cancellation message that provides the details of the new meetings, and suggests the user manually add them to his/her calendar.

A setting of 6.5.5 or 6.5.6 (but not 6.5.1–4) also enables a similar fix for single meetings, as documented separately in the 6.5.5–6.5.6 option above.

• For Notes 8.0.2 users: A Notes 8.0.2 calendar can almost always be correctly updated when the user accepts an invitation from an Outlook user to a recurring series of monthly meetings. This fix will correctly update the Notes calendar for meeting series scheduled for calendar dates 1 through 28, and for meeting series scheduled for the 31st day of the month (or the last day of each month with fewer than 31 days). But for meetings scheduled for the 29th or 30th of each month in a series span that includes February, the invitation message body will contain a warning that the February meeting is unscheduled, and that an extra meeting has been scheduled beyond the original series range. (Users should therefore add the February instance manually, and manually delete any extraneous instances at the end of the series.) To enable this fix, add this line to the root level of the CMN Configuration file:


31


Run the Mail Connector

Optional "Pass-Through" ModeCMN offers an optional "pass-through" mode that disengages CMN’s message-processing features while CMN continues to run and pass mail between the servers. This feature is off by default, but can be enabled by setting the <DisableProcessing> boolean parameter value to true in the CMN configuration XML file. The parameter can be set only manually, with an XML editor.

If left undefined, the pass-through feature defaults to false (the pass-through mode is disabled, so CMN processes messages normally).

To enable or disable the CMN pass-through mode:

1. Use an XML editor to open your active CMN configuration file.

Remember that your active CMN configuration file is the file that was most recently saved by the CMN Configuration Editor. If you are unsure of the name of the active file, you can look it up in the Windows Registry:

• Key name: HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Quest Coexistence Manager for Notes

• Value: ConfigurationFileName

2. In the configuration file, add this line, or change its true/false value:<DisableProcessing>false</DisableProcessing>

... where the value between the bracketed parameter names is either true or false.

3. Save the configuration file.

Starting the Mail ConnectorBe sure to prepare the CMN configuration and verify your settings for CMN logging (optional) before starting the CMN Mail COnnector. If necessary, see the preceding sections of this chapter for instructions.

The CMN Mail Connector is typically run as a Windows service, for long-term, continuous operation, but can also be run as a console application—usually for shorter-term uses, as in testing and diagnostics. In the event of a system reboot, the Mail Connector running as a Windows service would automatically restart. But if running as a console app it would require a manual restart.

IMPORTANT:Be sure to stop Microsoft’s SMTP service before starting CMN.

32


To start the Mail Connector as a Windows service:

• Use the Windows Service Control Manager.

To start the Mail Connector as a console application:

• Use Windows Explorer or a command prompt to find and run CMNConsoleApp.exe.

Multiple instances of CMN’s Mail Connector cannot run concurrently on a single workstation, because they would both try to use the same port.

Stopping the Mail ConnectorTo stop the Mail Connector as a Windows service:

• Use the Windows Service Control Manager.

To stop the Mail Connector as a console application:

• Press Esc from the console window.

Mail Server ConfigurationsThe CMN Mail Connector runs in conjunction with one or more Lotus Domino and Microsoft Exchange mail servers, and can be configured (for Exchange 2007) to complement the Microsoft Transporter Suite coexistence application. As such, the Domino, Exchange and Active Directory servers all must be configured to recognize and route messages via CMN.

If you will be using the Mail Connector with the Microsoft Transporter: The instructions below assume you have already configured the Transporter with your environment to facilitate directory synchronizations, and for email routing via an SMTP addressing schema. The Transporter does not handle mail routing, but its dirsync features can configure Notes person documents and AD object records for a mail coexistence.

The CMN Installer configures Windows to automatically start the Mail Connector Windows service upon Windows start-up.

Important: These server reconfigurations should occur only after the CMN service is started. Reconfiguring the mail servers before starting CMN would at least briefly send mail to a nonexistent destination.

33


Configure the Domino Server for CMNIn the Domino Administrator | Configuration tab | Messaging section | Domains document | Foreign SMTP Domain: Change the destination server to the IP for CMN. Use MX priority designations for load balancing.

Configure the Exchange Server for CMNIn the Organization Configuration | Hub Transport | Send Connector tab | Domino Send Connector Properties | Network tab: Add the IP or the FQDN for CMN as a "smart host" through which to route mail. Use MX priority designations for load balancing.

Configure the DNS Server for CMNAdd MX records for both the Domino and Exchange servers, to specify the mail servers responsible for handling emails for those domain names. More than one MX record can be entered for a single domain name using more than one mail server, so the MX records can be prioritized with numbers to indicate the order in which the mail servers should be used. For example:

34

Appendix A:Known Limitations

The known limitations of any coexistence method are usually due to feature inconsistencies between the two environments. That is, features that are available in one environment simply cannot be converted for an alternate environment that does not offer the same or comparable features. Other limitations are due to feature incompatabilities, where similar features are available in both environments, but their implementations are so different that remediation would be prohibitively impractical.

The known limitations listed here are issues that appear to be inherent to the process, and as such we do not expect to resolve these any time soon. Other known issues that we do expect to resolve in upcoming releases are itemized in the CMN Release Notes, under Known Issues.

Issues with Meeting/Appointment Invitations Originating in Notes, Sent to Exchange Recipients

• When an invitation originating in Notes is sent to an Outlook recipient, any inline image in the original invitation (including any DocLink icon) does not appear in Outlook. This appears to be an issue in Outlook rather than in CMN.

• When a custom meeting invitation is sent from a Notes organizer to an Exchange invitee using an older release of Outlook 2007 (only), the attendee may mistakenly appear as the meeting organizer. This is a known Microsoft problem in Outlook 2007, which may be corrected by applying either Microsoft's Hotfix 941275, or SP2 of Office 2007.

• When an invitation originating in Notes and sent to an Outlook recipient requires that the recipient open an .ics file to accept the invitation, and the .ics file is opened and accepted by some other party with delegated access (e.g., the recipient's secretary), the appointment is stored in the other party's mailbox and not in the recipient's mailbox.

• The Notes originator of an invitation accepted by an Exchange recipient in Exchange 2007, with any Microsoft update Rollup 3-7, is unable to remove the Exchange recipient from the list of attendees. The attempt in Notes has no apparent effect on the Notes object.

• When the Notes originator of an invitation accepted by an Exchange invitee (residing in Exchange 2007 SP0 or SP1, with no Microsoft update Rollup, or Rollup 1 or 2) later removes the Exchange attendee, the cancellation notice never arrives in the Exchange user's mailbox.

35

Coexistence Manager for Notes

• For an Exchange recipient in Exchange 2007 SP0 or SP1, with any Microsoft update Rollup 3–7: An update to an already-accepted meeting invitation, originating in Notes and accepted in Exchange, and with a changed Subject, arrives in Exchange with only the Subject change, but no other update information (no changes to day, time, place, etc.).

• For an Exchange recipient in Exchange 2007 SP1, with Microsoft update Rollup 5, 6 or 7: A meeting invitation originating in Notes arrives in Exchange with the false message "not supported calendar message.ics" in the invitation Description. (But the calendar features actually are supported.)

• For an Exchange recipient in Exchange 2007 SP0 or SP1, with any Microsoft update Rollup 3–7: A meeting invitation originating in Notes arrives in Exchange with the string "Invitation: " prepended to the original Subject, so accepted Calendar entries appear with the event title "Invitation: [original subject]." (Once an invitation is accepted, it is no longer an "invitation.")

Issues with Custom Meeting Invitations

• When a custom meeting invitation is sent from a Notes organizer to an Exchange 2010 invitee using an Outlook 2007 12.0.4518.1014 (RTM version) client, the CMN-attached .ics file arrives in Outlook with a blank message body. This is a known Microsoft problem that has been found only in the particular combination of Exchange 2010 with the above-cited Outlook 2007 release. The problem may be corrected by applying either Microsoft's Hotfix 939596, or SP1 of Office 2007.

• The conversion of a custom-meeting invitation from Notes to Exchange introduces meeting date/time errors. The invitation in Outlook, if accepted, does not correctly add the meetings to the recipient's Calendar, and the When field contents are inaccurate. CMN therefore attaches an .ics file that, when opened, will correctly add the series of recurring meetings to the recipient's Calendar. CMN also appends a notice to the message body, alerting the invitee to the problem in the When field and the need to open the .ics file, and listing the true meeting dates and times.

• An image in the message body of a custom meeting invitation originating in Notes, but received in Exchange, does not appear on the item in the Outlook Calendar after one of the .ics files is opened and accepted.

• Some custom meeting invitations (recurring events but irregularly scheduled) originating in some combinations of a Notes 6.5.5 client with a 6.5.3 Domino server are not transmitted out of the Notes/Domino environment. This appears to be a Notes/Domino issue rather than a CMN issue.

36

Other Meeting/Appointment Issues

• When a meeting request from an Outlook user (with Microsoft update Rollup 5, 6 or 7 only) is accepted in Notes, the Notes user's response mistakenly appears in Outlook as "tentatively accepted."

• Rescheduling a single instance of a recurring meeting to a date/time before the original first instance of the series, or after the last instance, will create a duplicate instance if the rescheduled instance is not already the first or last of the series, respectively. The original, unchanged instance will remain in the calendar, as a part of the series, and the duplicate will appear at the rescheduled date/time but not as a part of the series. This phenomenon occurs between Notes and Exchange, with or without Quest Coexistence Manager for Notes.

• Rescheduling a single instance of a recurring meeting that has previous-ly been rescheduled will create a duplicate instance. The instance will remain in the calendar at its previously scheduled date/time, as a part of the series, and the duplicate will appear at the rescheduled date/time but not as a part of the series. This phenomenon occurs between Notes and Exchange, with or without Quest Coexistence Manager for Notes.

• When a Notes user reschedules a meeting that was previously declined by an Exchange invitee, the Notes user cannot re-add the Exchange user to the meeting.

• A Notes user who sends a meeting invitation to an Exchange user, and then later removes the Exchange user, cannot then re-add the Exchange user at a later date.

• When a Notes user invites an Exchange user to a meeting but CMN cannot process the invitation, and the Notes user then cancels the meeting, the Exchange user will get a cancellation notice even though he/she never received the original invitation.

Issues with Certain Attributes,Embedded Elements and Other Features

• Message encryption does not work for a message originating in Notes and sent to an Exchange recipient, unless the recipient has a certificate registered in the Domino directory. The sender is notified that the message will not be encrypted for the Exchange recipient. Encryption does work, however, for messages originating in Exchange and sent to Notes recipients.

• Read receipts and delivery receipts do not work for messages sent between Notes and Exchange, in either direction. A Notes user who requests a delivery receipt from an Exchange recipient is notified that the server does not support delivery status notifications. An Exchange user who requests a delivery receipt from a Notes recipient is notified

37


that the message was relayed, but no delivery notification was sent from the destination. Senders requesting read receipts are not notified that the feature is not supported.

• A meeting invitation originating in Notes and sent to an Exchange/Out-look user, and containing an embedded (pasted) picture, appears in Outlook with an empty rectangle in place of the picture.

• An email or calendar item designated by an Exchange originator as "low" importance, and sent to a Notes recipient, loses that designation in the Notes environment. A "high" importance designation, however, is retained in Notes.

• An Expires After value in a message originating in Exchange is lost when the message is delivered to a Notes recipient. Both Notes and Exchange permit setting an expiration date for a message, after which it is safe to delete or archive the message. That value is preserved for messages originating in Notes and delivered to an Exchange recipient, but is lost in the other direction.

• The Outlook voting-buttons feature is not preserved in messages sent from Outlook to Notes. The buttons don't appear in messages in Notes.

• A moodstamp in a message originating in Notes is not preserved if the message is sent to an Exchange recipient.

• An attendee added as optional in Notes appears as a required attendee in Exchange. This is a Notes issue that CMN cannot detect and fix, but can be resolved by moving the attendee from the Required field to the Optional field.

Issues with .ics Files

• A table within an .ics file is rendered correctly within the body of a message, but loses its table formatting within the .ics file.

Notes DocLink Issues

• Notes DocLinks are sometimes lost in messages forwarded from Notes to Exchange recipients, because the Domino SMTP gateway occasionally fails to include the DocLinks in such messages.

• When a message containing a Notes DocLink is created in Notes by selecting Copy into New Memo after opening a message containing a DocLink, the DocLink is lost upon receipt of the message in Exchange.

38

Issues with Resources

• CMN’s Mail Connector does not remediate any resource reservation requests in either direction.

• If you are using Quest's Notes Migrator for Exchange (NME) to migrate from Notes to Exchange: Since the current version of NME cannot set visibility on resources, you will have to delete resources from Domino after they are migrated, and then use the Transporter's dirsync feature to re-sync resources back to Domino from Exchange.

• When Microsoft Transporter's dirsync is used to sync Exchange resources to Domino, the resources may not appear correctly in the Notes client, or may appear to the user but be invisible to Notes when you try to select them. These issues occur only in particular environmen-tal combinations of server and client versions, but appear to be issues in Domino and/or the Transporter rather than in CMN.

• When a Notes user adds a room resource to a previously scheduled and accepted meeting, the added room appears in Exchange meeting forms as an attendee but not as the meeting Location.

39


40

Appendix B:Troubleshooting

CMN Does Not Appear to Start

Verify that all system requirements have been met (see System Requirements in chapter 1). In particular, make sure that the CMN workstation has SMTP services installed, but not running at the same time CMN is running.

Verify that you have a valid Quest License Key installed. For more information, see About Quest License Keys in chapter 1.

Server Disallows Message

CMN processing may marginally increase or decrease the size of a message, so may rarely push a message over a receiving server’s maximum allowable size even though the original message was smaller than the server’s configured limit. For example, a message that was originally 9.99 MB may become 10.01 MB after CMN processing, and the server will refuse the message if it is configured to disallow messages > 10 MB.

Other Issues

Check Appendix A: Known Limitations in this User Guide, and the Known Issues section of the current CMN Release Notes, to see whether the problem might simply be a known limitation of the process.

Look through your CMN log files for clues to help diagnose and resolve the problem. If necessary, see Configure CMN Logging in chapter 2 of this User Guide for instructions to configure the feature to suit your needs.

41


42

Appendix C:Configuration Parameters
All configuration settings that appear in the CMN Configuration Editor screens correspond to parameters that are stored and may be edited in the CMN .xml configuration file. This table shows how the two correspond. All parameters in the .xml configuration file reside between the <root> and </root> tags.
Configuration Editor GUI Element Parameter in .xml Configuration File

Servers / Inbound:System Type

Identified by tag within <inbound>:<servers>

<inbound><exchange>xxxxxx</exchange><domino>xxxxxx</domino>

Servers / Inbound:Server Name / IP Address / MX Record

Specified within System Type tag:<exchange>ServerName</exchange><domino>ServerName</domino>

Servers / Outbound:System Type

Identified by tag within <outbound>:<servers>

<outbound><exchange>xxxxxx</exchange><domino>xxxxxx</domino>

Servers / Outbound:Server Name / IP Address / MX Record

Specified within System Type tag:<exchange>ServerName</exchange><domino>ServerName</domino>

Notes Doc Links:[method radio buttons]

<doclinks><doclinkconversiontype>

Valid method keywords are:• Http• SharePoint• NotesDocLink

Notes Doc Links:Site Address

Same parameter regardless of method:<doclinks>

<doclinkserveraddress>Network Settings:

Port Number to Listen On <smtpport>Network Settings / Performance Tuning:

Maximum ConnectionsMaximum Processing Threads

<maxrouters><maxmessagethreads>

Advanced Message Settings:Send Keep-Alives During ProcessingSend Keep-Alive Message Every ___

<sendnoops><noopintervalsec>

Adv Msg Settings / Performance Tuning:Maximum Allowable Message Size (MB)Maximum Message Process Time (mins)

<maxbodysize> (in bytes)<messagebodyproctimesec> (in secs)

Sub-Domain Settings:Mail System SMTP Root Domain <foreignsmtpdomain>

43


44

Glossary

CNSee Common name.

CoexistenceThe state of two independent mail or directory servers when both are serving the same organization at the same time. This is a common temporary condition during the transition period of a migration, when some users have already been migrated to a new server while other users remain on the old server, awaiting migration.

Common name (CN)The identifying name assigned to a directory object, typically a container. A common name must be unique within a context. (Compare to Distinguished name.)

ContactAn Active Directory object that represents a user outside the Exchange organization. For example, a contact may represent a not-yet-migrated user who still receives and sends email via the source server, or someone in another company with whom an Exchange user corresponds—a customer or a vendor, for example. A contact is associated only with an address, and has no Active Directory account.

Distinguished name (DN)A name that uniquely identifies a directory object, typically a user, by a series of attribute=value pairs, separated by commas and in a particular order, to define the entire path between the object and the directory root. (Compare to Common name.) The DN contains one attribute=value pair (called a Relative distinguished name, or RDN) for each level of the directory hierarchy, as in these examples:

cn=Susannah McCorkle,ou=marketing,o=My Company,c=UScn=Tony Bennett,ou=marketing,o=My Company,c=UScn=Sarah Vaughan,ou=engineering,o=My Company,c=US

Distribution group, Distribution listA set of directory objects—users and/or resources— collectively defined as a group of message recipients. A single message can be "broadcast" to all members of a distribution group by specifying the single group as the recipient.

45


DNSee Distinguished name.

DNSSee Domain Name System.

Domain Name System (DNS)A hierarchical, distributed database that maps domain names to various types of data, including IP addresses. Every node on the Internet is identified by a unique, numerical IP address of the form 255.255.255.255, although any particular IP address may be associated with 0, 1 or more domain names. The DNS defines the associations of domain names to their corresponding IP addresses.

FQDNSee Fully qualified domain name.

Fully qualified domain name (FQDN)The complete domain name for a particular computer (host) on the Internet, specified by a notation whose dot-delimited elements identify all levels of the hierarchy from the top-level domain to the root domain. For example: ParticularHost.XYZCorp.com.

MX recordShort for Mail eXchanger record, an entry in a domain name database that identifies the mail server responsible for handling emails for that domain name. More than one MX record can be entered for a single domain name using more than one mail server, so the MX records can be prioritized with numbers to indicate the order in which the mail servers should be used. (Lower numbers are higher priority.) This makes possible the designation of primary and backup mail servers.

ProvisioningPopulating a directory with objects (users, resources, and so forth), and the information that characterizes objects.

Relative distinguished name (RDN)One element or component of a Distinguished name (DN), in the form of an attribute=value pair (e.g., ou=marketing, or cn=Melvin Montgomery) that uniquely identifies the component among the children of its parent. (See Distinguished name.)

RDNSee Relative distinguished name.

46

Simple Mail Transfer Protocol (SMTP)The standard TCP/IP protocol that governs message transmission over the Internet, by addresses in the form [email protected]. SMTP is the default transport protocol for Microsoft Exchange.

SMTPSee Simple Mail Transfer Protocol.

SynchronizationProcess of updating the contents of one directory to match the contents of another, comparable directory. If, for example, the source and target server directories of a migration will coexist for more than a day or two, most organizations will want to regularly synchronize the two.

UNC PathA notation (UNC=Universal Naming Convention) to specify the absolute location of a resource (such as a directory or file), in this syntax: \\server\volume\dir\dir\...\file.

47


48

About Quest Software

• About Quest Software

• Contacting Quest Software

• Quest Support

• Visit Our Online Community


About Quest SoftwareNow more than ever, organizations need to work smart and improve efficiency. Quest Software creates and supports smart systems management products—helping our customers solve everyday IT challenges faster and easier. Visit www.quest.com for more information.

Contacting Quest SoftwarePhone 949.754.8000 (United States and Canada)

Email [email protected]

Mail Quest Software, Inc.5 Polaris WayAliso Viejo, CA 92656USA

Web site www.quest.com

Please refer to our Web site for regional and international office information.

Quest SupportQuest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to SupportLink, our self-service portal. Visit SupportLink at http://support.quest.com.

From SupportLink, you can do the following:

• Retrieve thousands of solutions from our online Knowledgebase

• Download the latest releases and service packs

• Create, update and review Support cases

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies and procedures. The guide is available at: http://support.quest.com.

50

http://www.quest.com


http://www.quest.com

http://support.quest.com


http://questsupportlink.quest.com/



Visit Our Online CommunityThe Quest Inside Migration community is an online interactive community dedicated to issues pertaining to:

• Migration of email, identity and applications to the Windows Exchange platform—including migration from Exchange, GroupWise, and Notes.

• Active Directory migrations. • Migrations from Notes application and Exchange public folders to Sharepoint. • Coexistence strategies and tools.

System administrators like you join together with Quest developers, architects, QA staff, support staff and tech writers to make the Inside Migration community a place where you can:

• Learn about product releases and betas before anyone else. • Get access to Quest product leaders and subject matter experts on migration

and coexistence. • Participate in discussion forums, share insights and ideas, and get common

questions answered.

You can log in, or register to join the Quest Inside Migration community at: http://migration.inside.quest.com/index.jspa.

51

http://migration.inside.quest.com/index.jspa


52

INDEX

AAccess Control List 45Advanced Message Settings screen in

Configuration Editor 23attachments 10

Ccache-update interval for MX

Resolution 16, 29CMN Configuration Editor 16, 20CMN license keys 18, 21CMN service status 20CMN workstation requirements 17CMN, starting 32CMN, stopping 33Coexistence Manager for Notes license

keys 18, 21Coexistence Manager for Notes

workstation requirements 17Coexistence Manager for Notes,

starting 32Coexistence Manager for Notes,

stopping 33coexistence of directories during

transition 45common name (CN), defined 45Configuration Editor 16, 20Configuration Editor status bar 20configuration of servers to work with

CMN 17, 33configuring SMTP port of CMN

workstation 23configuring socket channels 16, 29console application, running CMN as 16,

32Contact (in AD), defined 45custom-meeting invitation, conversion

from Notes to Exchange 36

Ddelivery receipts 37detail level, logging 25, 26DisableProcessing parameter 32distinguished name (DN), defined 45distribution group (or list), defined 45DNS MX Resolution 16, 28DNS name 22doclinkconversiontype parameter 43DocLinks 23, 38doclinkserveraddress parameter 43domain name system (DNS), defined 46Domino server requirements 17

Eemail remediation 10encryption 37end user workstation requirements 17Exchange server requirements 17

expiration date (for a message) 38Expires After value 38

Fforeignsmtpdomain parameter 43Free/Busy Connector 11free/busy lookups 11Fully qualified domain name (FQDN),

defined 46

Hhardware requirements for CMN

workstation 17

Iics file 35, 36, 38inbound servers, defining 22IP address 22

Llevel of detail, logging 25, 26license keys 18, 21load balancing by MX record 15, 22log4net utility 16, 24logging level of detail 25, 26

MMail Connector component 10maxbodysize parameter 43maxmessagethreads parameter 43maxrouters parameter 43message encryption 37message processing time, maximum 24message size, maximum 24messagebodyproctimesec parameter 43Microsoft Transporter 10, 33multiple redundant CMN servers 15multiple redundant mail servers 15MX record 15, 22, 46MX Resolution 16, 28mxcacheupdateinterval parameter 29

NNet Framework 3.5 17Network Settings screen in Configuration

Editor 23noopintervalsec parameter 43Notes Doc Links screen in Configuration

Editor 23Notes DocLinks 38

Ooutbound servers, defining 22

53


Ppass-through mode 32POP3 services 17priority ranking in MX record 15, 22

Rread receipts 37recurring meeting issues 37recurring meeting requests 10redundant CMN servers 15redundant mail servers 15Relative distinguished name (RDN),

defined 46rescheduling single instance of recurring

meeting 37resolvemx parameter 29resource visibility 39room resource, adding to accepted

meeting 39routerwaitsecs parameter 30

Ssendnoops parameter 43server configurations to work with

CMN 17, 33Servers / Inbound screen in Configuration

Editor 22Servers / Outbound screen in

Configuration Editor 22Simple Mail Transfer Protocol (SMTP),

defined 47SMTP port of CMN workstation,

configuring 23SMTP services 17SMTP sub-domain setting 24smtpport parameter 43socket channels, configuring 16, 29status bar in Configuration Editor 20status of CMN service 20Sub-Domain Settings screen in

Configuration Editor 24synchronization of directories 47system requirements 17

UUNC path, defined 47

Vverbose logging 25, 26visibility of resources 39

WWindows service, running CMN as 16, 32

54

C Users Marg AppData Local Temp Plugtmp-8 Plugin-CMN 20 UserGuide

Documents

Transcript of C Users Marg AppData Local Temp Plugtmp-8 Plugin-CMN 20 UserGuide