Published: 2011-04-19
Updated: –
Version: 1.0

Since this is included with Coexistence Manager for Notes from version 3.0 and above it was released very late last year (2010).
The version I’m using in the lab is 3.0.2 and is currently the latest version when this blog post is released.

Below are some known issues that are fixed in version 3.0.2.

Known Issues in the CMN Directory Connector:

#140661 SMTP addresses that contain a space within a quoted string, such as “Wilbur Jones”@domain.com, are not supported in this release of the Directory Connector.
The addresses must be corrected (remove the space).
#139586 The Directory Connector Configurator creates a folder for each defined Connector (under …\Directory Connector\Tools\Connections) to store Connector-specific
information. The Remove feature does not remove this corresponding Connector folder.

 

More information about Coexistence Manager for Notes can be found here.
I don’t deal with license questions, these can be handled directly by Quest, just send them an email on: info@quest.com.

When downloading the trial version of the product there are some PDF’s with valuable information included, make sure you read
through them if you’re going to use the product(s). There are also some videos about DirSync included

  • Configuring LDAP
  • Domino to Exchange DirSync
  • Exchange to Domino DirSync

If you’re reading this post I suppose you already know what CMN DirSync provides, this post is based on basic knowledge of the product.

Any form of feedback on the article would be nice, good as bad.

Infrastructure Setup

 

This is an overview of my Infrastructure in this setup.

Installation

 

Prerequisites

  • Microsoft .NET Framework 4.0
  • An account for synchronization that have access for creating objects in each directory’s

 

Configuration

 

The first thing to do is to install the license; it’s done by starting “Quest Coexistence Manager for Notes Configurator”. Go to Common -> Licenses and browse for the license file.

Directory Synchronization (Domino -> Exchange)

 

For creating a DirSync connector, go to “Connector Settings” and pressing Add.

Start with typing in a friendly name for the Connector.
Mine is called “Domino to Exchange” and Direction: Notes to Exchange.
Press Next.

Typing in the credentials for Source server:

Server: domino
Username: system/target
Password: ****
Port: 389

Typing in credentials for Target directory (Active Directory)

Target Server: server02 (DC)
Username: Administrator
Password: ****
Port: 389

I want to synchronize “Users & Contacts” from O=taget (Organization).

Select a Target OU for the objects to be placed into, also specify the Exchange part of the sub-domain,
in my case it’s domino.target.local and the check “Notes Migrator for Exchange compatibility mode” so the objects not get duplicated.

Facts from Quest PDF:

Notes Migrator for Exchange compatibility mode: If this checkbox is marked, the Connector will merge any processed object from the source
that matches (by proxyaddresses) an existing object in the target. For each processed object from the source, the Connector will search the
entire target directory (all containers) for any merged object with the same proxyaddress. If this checkbox is not marked,
the Note: The values you enter for Notes Calendar domain, Notes Domain and Server Running QCALCON are merged with the AD source data
that is pushed into Notes. There are no comparable fields for this data in Active Directory. If you later change the value of any of these fields,
it will appear that the source data has changed, although nothing has actually changed in AD.

Quest Coexistence Manager for Notes 3.0 Directory Connector will compare its source objects to the target objects, and will copy only new
source objects into the target. Note: This feature is intended to find and eliminate duplicate objects (same proxyaddresses), and thereby
help prevent directory looping—which proliferates duplicate objects by copying them back and forth.

Quest therefore recommends that you enable this feature (mark the checkbox) unless you have a particular strategic reason not to.
If you experience Connector errors that appear due to duplicate objects, or if you just want to learn more about duplicate objects,
see Connector Errors Due to Duplicate Objects in the Troubleshooting Appendix of this User Guide.
This checkbox must be marked if you will use Quest’s CMN Free/Busy Connector.

Note Also: When using NME compatibility mode with a Notes-to-Exchange Connector (only), some admins report that Domino updates
sometimes do not arrive in Active Directory. This is actually a system latency issue rather than a CMN process bug. In some environments
the Domino changes simply take a few seconds to propagate to the Notes LDAP service, and therefore may be missed if the Connector is
run too soon after the updates are entered in Domino. The Connector will succeed, however, if you wait a minute or two after the last of the
Domino updates before running the Connector.


Since there is no existing connector, it cannot be selected.

Scheduling settings, I choose to synchronize Daily at 1 AM. Press Add.

These users below are located in Domino as mail-users and will be synchronized into Active Directory.

Right clicking the connector and make sure it runs and then validate if any objects have been created.
In my case they are located under DirSync OU and looks like the picture below.

The first impressive tells me that it haven’t synchronized everything since 2 objects are missing.
BUT, they already have a mailbox with that proxyaddress so we have now validated the function for Notes Migrator for Exchange compatibility mode.

Directory Synchronization (AD/Exchange -> Domino)

 

For creating a DirSync connector, go to “Connector Settings” and pressing Add.

Start with typing in a friendly name for the Connector.
Mine is called “Exchange to Domino” and Direction: Exchange to Notes.
Press Next.

Typing in credentials for Source directory (Active Directory)

Target Server: server02 (DC)
Username: target\administrator
Password: ****
Port: 3268

Typing in the credentials for Source server:

Server: domino
Username: system/target
Password: ****
Port: 389

I want to synchronize “Users & Contacts” from OU=Migrated..

Domino target information

Exchange Internal Routing Domain: exch.target.local
Notes Calendar domain: Exchange
Notes Domain: target
Server running QCALCON: domino

And check the NME compatibility mode

I choose to not make any kind of order management setting on my DirSync connectors.

Scheduling settings, I choose to synchronize Daily at 2 AM. Press Add.
Then the DirSync in the other direction is finished and up-to-date.

Domino configuration

 

In case of objects should be synchronized from Exchange into Domino, Domino must be LDAP configured.

This is done by using Domino Administrator, select Configuration tab and Directory, LDAP and Settings.
Allow LDAP users write access: Yes

Then select, Save and Close and restart the Domino server.

Quest recommends that DirSync resides on a separate server.

For setting up CMN from Quest, it’s recommended to use a PSO (certified consultant)!

Feel free to give feedback on the article!