If the distinguished name of an object in Lotus Domino contains a comma or another special character, an error occurs in the Domino Connector. For example, you cannot import an object that uses "CN=Example,WA,US,NAB=names.nsf" as the distinguished name.
Issue 2
If a Domino secondary address book is not located in the same folder as the Names.nsf file, the address book is not detected.Issue 3
A dependency on the SHORTNAME value for provisioned objects causes intermittent errors during an export process.Issue 4
FIM 2010 Lotus Domino Connector does not use the ID vault as expected.
After you apply this update, you can set the _MMS_IDStoreType field to Null. In this situation, FIM 2010 Lotus Domino Connector creates the user's ID file in the ID vault instead of in the Address Book file or in a local file.Issue 5
A mailbox must be provisioned on the same server to which Domino Connector exports.
After you apply this update, you can set the MailServer attribute to create the mailbox on an alternative server.Issue 6
When you add custom attributes to Domino, some attributes are not visible in Domino Connector.
After you apply this update, you can see attributes that were created by using an extensible object class and an auxiliary class in the Domino Connector.Issue 7
Domino Connector does not work with Forefront Identity Manager 2010 R2 Service Pack 1 (SP1). This issue is caused by some changes to the platform.Issue 8
The MailServer attributes for people and the list names for a group are converted to reference attributes during the export process.
After you apply this update, the MailServer attributes are set to strings and are not converted. Issue 9
If you try to clear the existing value in an attribute in the connector space, the value is not deleted in Lotus Domino.Issue 10
When you run a delta import process on a server that uses a non-US date and time format, an error occurs. This issue occurs on specific dates.Issue 11
You experience a "stopped-extension-dll-updated-version" error in Domino Connector. This issue occurs because the ID file is generated in the extension folder.
After you apply this update, the ID file is generated in the Temp folder.