Coexistence Manager for Notes 3.9.2 - User Guide

•

Release Notes (printable PDF): 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, features and capabilities, with a case study showing how its primary components are most commonly used within a typical coexistence scenario. Also explains how to download and install the software.

•

CMN User Guide (printable PDF): Comprehensive documentation of CMN's three primary components: Directory Connector, Mail Connector and Free/Busy Connector. Describes component capabilities, deployment considerations, configuration instructions and tips, and application notes and screen-by-screen field notes for CMN's Management Console software tools.

•

FBC Scenarios Guide (printable PDF): Provides process instructions and application notes for installing and configuring CMN’s Free/Busy Connector (FBC) in a variety of Exchange-side scenarios.

•

CMN Program Parameters Reference (printable PDF): Listing of all CMN program parameters that are not associated with UI fields in CMN’s Management Console, with descriptions and default values and usage/application notes. (Parameters associated with UI fields do appear in the Configuration.xml files, but should not be edited manually.)

•

Management Console Online Help (three compiled Windows Help files, one for each CMN component): Field notes and application notes for the screens and features of CMN’s Management Console.

•

•

•

•

Directory coexistence: Most organizations routinely experience staff additions, departures and transfers. These staff changes introduce data inconsistencies between the two environments’ directories. A directory update reconciles these differences by updating the contents of one directory to match the contents of another. A bidirectional update ensures that both directories contain all of the organization’s users, resources and groups.

•

Mail coexistence: Simple, direct SMTP mail routing is easy to configure, but does not preserve or compensate for substantial cross-platform losses in the fidelity of message contents: attributes, attachments, calendar data, and so forth. Notes and Exchange environments offer similar email and calendar capabilities, but implement many features differently. Outlook therefore does not handle certain message types that originate in Notes, and vice versa. Often the recipient client can display the pertinent information correctly, but cannot perform the calendar updates that would have been automatic if the recipient and sender were using the same email system. Or sometimes the receiving client can perform automatic calendar updates, but introduces errors— incorrect times, missing dates, or extraneous meetings, etc.

•

Free/Busy coexistence: The Notes and Exchange environments implement calendar free/busy queries differently, making each side blind to the availability status of users on the other systems. The calendar applications on both sides need some mechanism to determine the free/busy status of users within the other environment.