지금 지원 담당자와 채팅
지원 담당자와 채팅

Coexistence Manager for Notes 3.9.2 - User Guide

About the CMN Documentation Suite Introduction CMN Directory Connector
Directory Connector overview Installation and configuration DC Management Console Connector Creation Wizard Connector Advanced Settings Starting and stopping the Directory Connector service
CMN Mail Connector
Mail Connector features overview Coexistence mail routing basics Deployment of CMN Mail Connector Installation Configuration Mail Connector Management Console
CMN Free/Busy Connector The Log Viewer Appendix A: Known limitations Appendix B: Troubleshooting Appendix C: CMN Logs

Directory Connector issues

•
The CMN Directory Connector cannot read a Notes Directory Catalog for a Notes-to-Exchange directory update.
•
A Domino-to-Exchange Connector will not update Active Directory with a contact for a Domino group with no internet mail address. Domino may insert a mail attribute for a group when the internet address field is empty, in which case the group will be copied into Active Directory, although the internet address field will remain empty in Domino.
•
When a CMN Exchange-to-Notes Connector updates Domino with a contact that contains no SN attribute in Active Directory, the object's CN attribute is copied into the SN attribute field in the Domino contact.
•
The name of the source container for an Exchange-to-Notes connector cannot begin with the letters CMN. If the source container name begins with CMN the connector will generate an "Empty Recipient List" error.
•
When provisioning or updating a user with no last name in the AD source, an E-to-N connector will sync the user to Domino with the first name in both the first name and last name fields.
•
The Add and Delete Verification values in the General tab of DC Advanced Settings do not reset to zero if the corresponding checkboxes are unmarked.

Mail Connector issues

Meeting invitations sent from Notes to Exchange recipients
•
When an Exchange invitee accepts a meeting invitation from a Notes organizer, the acceptance notification appears in some versions of Notes with an "i" icon. This is a known consequence of the way some Notes versions process SMTP calendar messages, and in any case is only a harmless cosmetic artifact.
•
When an invitation originating in Notes is sent to an Exchange recipient, any inline image in the original invitation (including any DocLink icon) does not appear in Outlook. This appears to be an Outlook issue rather than a CMN issue.
•
Multi-line subjects and locations in Notes 6.5.x meeting invitations appear in Outlook truncated at the end of the first line, because Notes transmits only the first line.
•
If an invitation originating in Notes is sent to an Exchange recipient and requires that the recipient open an .ics file to accept the invitation, when the .ics file is opened and accepted by some other party with delegated access (e.g., the recipient's secretary), the appointment is added to the other party's mailbox and not in the recipient's mailbox.
•
When a Notes user organizes a meeting series, then reschedules a single instance of the series, and then invites an Exchange user to all instances, the Exchange invitee receives separate invitations for different portions of the recurring series. For example, if the Notes originator reschedules the time of a Wednesday instance (only) of an every-day recurring meeting, the Exchange invitee would receive one invitation for the Mon-Tues meetings, another invitation for the Wed meetings, and a third invitation for the Thurs-Fri meetings. The invitee can simply accept all of the invitations, but the tracking information associated with such acceptances may appear to the Notes originator as "no response" unless the forcereplyremediation config option is set.
•
Notes does not recognize the delegation of an Exchange user's invitation by his/her forwarding the original invitation to another Exchange user. In this scenario, if the delegated user accepts the forwarded invitation, the Notes originator receives the acceptance, but the tracking shows "no response" from the original invitee, while the delegated user appears as an "unknown" user who accepted. Thereafter, any reschedule notice is sent to the original invitee (who delegated the invitation), but not to the "unknown" delegate invitee. This is a known limitation of Notes that CMN cannot remediate.
•
When a Notes user with delegate access to another Notes user's calendar sends a recurring meeting invitation (on behalf of the other Notes user) to an Outlook user, then updates a single instance to change the date, and then adds another Outlook invitee:
•
The first Outlook invitee gets the date update but receives no indication of the new participant.
•
The new invitee is notified that he/she "may need to accept from calendar" (rather than accepting via the email invitation).
•
The delegate chair receives a message that "acceptances cannot be processed, error that they are not in mailfile."
•
Meeting requests originating in Notes and sent to Exchange users may be off by one hour for meetings scheduled in the period between the second Sunday in March (when daylight savings time begins) and the first Sunday in April (when DST used to begin). This is not a CMN defect, but rather an apparent issue in the way Windows processes time zone data. Microsoft offers a free time-zone update utility (downloadable from http://support.microsoft.com/kb/2443685) that will likely correct this problem. Apply the update to the Windows OS on both the Domino server and the CMN admin server hosting the Mail Connector software.
•
A meeting invitation from a Notes organizer to a Notes invitee, but then forwarded to an Exchange user, arrives in Outlook as an email, but not as a functional invitation that can be accepted/declined or added to the user's calendar. This appears to be an issue with how Notes/Domino forwards an invitation rather than any limitation of CMN, since the same behavior is observed when a Notes invitee forwards the invitation to another Notes user (where the invitation never passes through CMN).
•
The original Comments entered with a Notes-sourced recurring online meeting request may be lost in an attendee's invitation and calendar if additional Comments are appended to the original Comments when rescheduling a single instance of the series. This is a problem with some versions of Notes/Domino rather than with CMN.
Custom meeting invitations
•
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. Therefore, CMN converts custom meetings to an appropriate series (with exceptions) for Exchange and 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 in the message body, alerting the invitee and listing the true meeting dates and times.
•
Exchange rooms and resources cannot properly process custom recurring meetings, regardless of the source. An Exchange room or resource does not respond to a request for a custom recurring meeting, with dates/times for multiple instances, and sends the request to its Deleted Items folder.
•
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.
Other meeting/appointment features
•
Exchange cannot process the case of a Notes resource being available for only a part of a meeting series organized by an Outlook user. In this case, the resource account in Notes generates two accept/decline replies for the same meeting: one listing the date(s) for which it accepts, and the other listing the date(s) for which it declines. Exchange, however, does not support partial acceptance of a series, and cannot correlate these separate accept/decline notices to its original meeting record. The Tracking tab therefore incorrectly shows all instances as accepted, even though some were actually declined. CMN does explain this limitation to the Outlook organizer, and suggests: Leave your calendar as it is, and simply note to yourself the date(s) that the resource has accepted and declined; or cancel the entire meeting series and create a new invitation rescheduled to accommodate the resource.
•
Notes does not correctly display (in the calendar) a meeting that spans two or more date boundaries—for example, a meeting that begins Monday and ends Wednesday. CMN detects such meetings and inserts a note explaining that the calendar may show only the first day, but the meeting can be opened to see the full duration.
•
When an Exchange user reschedules an entire recurring meeting, the reschedule notification appears in Notes 6.5 as a cancellation, and the change is not processed by the Notes calendar. Therefore, CMN inserts a notice to the user explaining that he/she should "manually reschedule the meeting with the following dates...." This only occurs with Notes 6.5. In Notes 7.0.0 and higher, the reschedule notification appears in Notes in the form of an invitation to a new meeting, so CMN inserts the string "Rescheduled: " to prepend the invitation title (which matches the original invitation title), and the Notes calendar is correctly updated despite the possibly confusing message format.
•
When a meeting with an online meeting place is rescheduled by a Notes user, the meeting URL does not appear in the Location field in the rescheduling notice in Outlook. Notes does not transmit the URL as it does when the meeting is originally scheduled, so CMN cannot insert the URL, and in Outlook the meeting appears to have a modified location and does not show the URL.
•
A meeting time counterproposal from a Domino attendee to an Exchange meeting organizer often shows an incorrect "Current" meeting time in Outlook. The calendar processes the counterproposal correctly, and CMN inserts an explanatory note in the message, but incompatibilities between Notes and Exchange prevent CMN from determining the correct time for display in Outlook.
•
Rescheduling a single instance of a recurring meeting to a date/time before the 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 behavior occurs between Notes and Exchange, with or without Quest Coexistence Manager for Notes.
•
Rescheduling a single instance of a recurring series that has previously been rescheduled may, in certain specific circumstances, 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 part of the series. This behavior occurs between Notes and Exchange, with or without Quest Coexistence Manager for Notes.
•
When a single instance of a recurring series is rescheduled, and then an Exchange user changes the location of the entire series, the old and new locations both appear in Outlook, and CMN in turn passes this to any Notes invitee(s), where the same calendar error occurs. This is a known Exchange limitation.
•
When a meeting request from an Exchange user (with Microsoft Rollup 5, 6 or 7 only) is accepted in Notes, the Notes user's response mistakenly appears in Outlook as "tentatively accepted."
•
When an Exchange user declines a meeting invitation from a Notes 6.5 user, Notes reports a mail template error when attempting to remove the Exchange invitee. This is a limitation of Notes, and occurs only with Notes version 6.5.
•
A Notes user who sends a meeting invitation to an Exchange user, and later removes the Exchange user, cannot then re-add the Exchange user. This is a known limitation of Notes.
•
When an Outlook user invites a Notes user to a single-instance meeting, and the Notes user then delegates the invitation to the Exchange user, the notice back to the Outlook organizer does not identify the delegate and Outlook cannot automatically process the reply. Delegation to another Notes user does work, however.
•
CMN is unable to completely reconcile an incompatibility between Notes and Exchange when a Notes user schedules a recurring meeting, and then reschedules a single instance, and then reschedules the entire series. For example:
1
Notes user schedules an every-day, Monday through Friday meeting recurring at 10am.
2
Notes user then changes the Wednesday instance (only) to 11am.
3
Notes user then changes the series as a whole to start at noon.
Notes processes the second change (in step 3) to preserve the one-hour difference on Wednesday, so that the Wednesday instance is rescheduled to 1pm. But Exchange cannot process this sequence. As a result, CMN sends a notification to any Exchange invitee, warning that only the first change has been processed, and listing the subsequent proposed changes to the other instances with a suggestion that the invitee make those calendar changes manually.
•
The owner of a Domino resource is unable to approve a meeting request from an Exchange organizer when Owner Approval settings are in force for Domino resources. This is a bug in the Notes client (not in CMN), and IBM may resolve the problem in a future Notes release.
•
An Exchange user cannot schedule a recurring series of meetings with a Domino 6.5.x resource because Domino does not support this scenario over SMTP. (This is a limitation of Domino, not of CMN.) CMN will not relay any such attempt, and will send a brief explanatory notice back to the Outlook user.
•
An Exchange user cannot reschedule an entire recurring meeting to which a Notes resource has been invited. CMN will not relay any such attempt, and will send a brief explanatory note back to the Outlook user.
•
A Notes user who declines a meeting request from an Exchange user, and who unchecks the Keep me informed of updates checkbox in the Notes reply, still receives update notifications if the Exchange organizer reschedules the meeting.
•
When an inline image occurs in a calendar message sent from an Exchange user to a Domino user, CMN converts the inline image to an attachment. This is necessary to accommodate Notes' requirement for "content-disposition: attachment."
•
CMN does not support a scenario in which an Exchange user schedules a recurring meeting, invites a Notes resource, and then reschedules all instances of the recurring meeting. In that case, CMN prevents the delivery of the reschedule notice to Notes invitees, and sends a courtesy message to the Exchange originator explaining that he/she must delete the meeting series altogether and then recreate it at the new time.
Certain attributes, embedded elements and other features
•
Exchange, and thus CMN, does not prevent delivery of a Notes-encrypted message to an Exchange recipient when TLS is disabled in Exchange and active mail processing is disabled in CMN. The message arrives in Outlook unencrypted. If active mail processing is enabled, however, the message remains encrypted in Outlook.
•
An attachment to an encrypted Notes-to-Exchange message cannot be seen when opened from Outlook, if the source Domino Mail Router Server version is earlier than 8.5.3.
•
An OLE object embedded as active content in a Notes message sent to another user—whether in Notes or in Exchange—arrives in the recipient's mailbox as a read-only document. This is not a limitation of CMN, but appears to be the way Notes handles an OLE object within active content. CMN simply relays the object in that state when it passes the message to Exchange. The recipient cannot alter the document and then return or forward it, as with other forms of active content.
•
An NSF attachment may be un-openable by an Exchange recipient if the attachment name contains Japanese, Russian or Arabic characters. To prevent this issue, always use English-language attachment filenames.
•
Relative font-size specifications in Notes' HTML message outputs (e.g., where sizes are specified as 1, 2, 3, etc.) can cause mismatched font sizes in Outlook. This appears to be caused by the two-step conversion process: First the point sizes of the Notes original are mapped to the 1-2-3 sizes in the HTML output, and then Outlook interprets the HTML to re-map the 1-2-3 sizes back to point sizes, but according to its own (apparently different) mapping methods.
•
Read receipts and delivery receipts do not function between Notes and Exchange, in either direction. A Notes user requesting a delivery receipt from an Exchange recipient is notified that the server does not support delivery status notifications. An Exchange user requesting a delivery receipt from a Notes recipient is notified that the message was relayed, but that Notes sent no delivery notification. Senders requesting read receipts are not notified that the feature is not supported.
•
A meeting invitation originating in Notes and sent to an Exchange 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.
•
Notes priority designations (Low, Normal, High) assigned to calendar invitations are not retained for an Exchange recipient, although priority designations are preserved for non-calendar emails.
•
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 Exchange to Notes.
•
A moodstamp in a message originating in Notes is not preserved when 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.
•
Calendar items sent as attachments to messages originating in Outlook do not open in Notes.
•
As of October 31, 2018, Microsoft Office 365 will remove support for TLS 1.0 and 1.1. This means that all client-server and browser-server combinations must use TLS version 1.2 or later. In this scenario, a connection needs to be secured but fails when mail is sent from Office 365 to a Domino server that does not support TLS 1.2. (i.e., Domino version is lower than 9.0.1 FP3 IF2).
Notes DocLinks
•
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. This is a Notes limitation.
•
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.
•
In some environments, when you choose to Convert to NDL Attachment (in the Mail Connector Management Console, Notes Doc Links screen), an Outlook recipient can successfully open an .ndl attachment only if the required Notes client on the user's workstation is not already running. If the Notes client is already running, the user sees an error message: Invalid directory name or device not ready. In that case, the attachment should open if the user dismisses the error message, exits from the Notes client, and re-clicks on the attachment.
Resources
•
If you are using Quest's Migrator for Notes to Exchange (MNE) to migrate from Notes to Exchange: The current version of MNE cannot set visibility on resources. This can be done manually, or the resources could be removed/disabled after they are migrated.
•
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.
•
A contact object representing a room can be added to the Exchange 2010 Room Finder Distribution List only if it is an actual room with an associated mailbox—that is, only after the resource has been migrated and brought live in Exchange.
•
A Notes user requesting a Notes resource no longer appears in the From field of the booking-request message to the resource owner after the owner has migrated to Exchange. The requestor's name does appear in the body of the message, but only in addr-spec format (the left-hand side of his/her email address). This is a known Domino issue; Domino does not send the name except within the message body.
Active mail
•
Active Mail attachments cannot be opened from a Web Access connection to an Exchange Inbox. The Web Access Inbox shows that a message with an Active Mail attachment has been received, but the attachment cannot be opened without the Notes client installed on the local machine, and Web Access permits only a download of the attachment.
.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.

Free/Busy Connector issues

•
Notes queries for free/busy information from meetings with any external users can take longer and in some cases fail to return data for internal users. This is a known issue with Notes/Domino, which places such requests in the LWPSCHEDGATEWAY queue instead of the configured queue preferred by CMN (in most cases called MAIL.BOX or MAIL1.BOX).
•
The Get-CmnExchangeWebServicesUrl command does not work in a single-namespace environment.

Appendix B: Troubleshooting

This Appendix describes the most common problems encountered when installing and using Quest Coexistence Manager for Notes, and provides suggestions and procedures that are most likely to resolve them. Virtually all of these issues are unique to particular CMN components—the Directory Connector vs. Mail Connector vs. Free/Busy Connector. Such component-specific issues are listed and discussed separately, grouped by CMN component, following the more general introductory notes and comments below.

Many issues can be resolved quickly by reviewing this short list of preliminary checks before calling Quest Support:

•
Review the component log file(s). You can find valuable information about component errors and warnings in the components’ respective log files. If you call Quest Support and a support engineer can't immediately identify the problem, typically he/she will ask for copies of your log files.
•
Verify system requirements. CMN problems are often traced back to inconsistences between the product’s system requirements and the host network’s hardware or software specifications. You may therefore save yourself some time and trouble by simply comparing your local system to the CMN system requirements. System requirements are documented in the RTM Release Notes.
•
Always ask yourself:
•
Is this a known limitation or known issue? 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.
•
What has changed since the last server restart? Configuration values are normally updated only when a service is restarted. This can hide a pending problem for weeks or longer until an administrator restarts the services and the changes are applied.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택