Quick Connect for Lotus Notes is an option of Quest ActiveRoles Quick Connect (hereafter Quick Connect). The Quick Connect environment comprises the core module - Quick Connect Sync Engine, and connectors to different types of connected data systems.

With Quick Connect for Lotus Notes, you can synchronize the identity information between Active Directory and Lotus Domino for the following pairs of the object classes (Active Directory class< -> Lotus Domino class): Users <-> Persons; Groups <-> Groups; Organizational Units <-> Certifier objects.

TF00106373
Fixed: Quick Connect For Lotus Notes may incorrectly update group membership in Lotus Notes.

TF00106582
Fixed: If your Lotus Domino scope includes a significant number of groups to synchronize, an attempt to synchronize group membership for all groups may fail due to an operation timeout.

TF00107727
Fixed: When synchronizing the group membership for significant number of groups (2000 groups or more), you may experience slow performance.

TF00110974
Fixed: Incorrect synchronization of the group membership for nested groups: when synchronizing from ActiveRoles Server to Lotus Notes, the nested groups have invalid names.

TF00062863
When provisioning a user object from ActiveRoles Server to Lotus Domino, you may encounter the following issue: the Last Name ('sn’) attribute value is always generated by the object name generation rules. The initial attribute population rules configured for the 'sn' attribute are ignored.

WORKAROUND
To specify the 'sn' attribute value, use the object name generation rules.

TF00062867
Incorrect behavior of the application: the Initial Attribute Population rules do not apply to some of the dominoPerson attributes.

WORKAROUND
To populate values of those attributes, create an update step and configure the Attribute Update Rules on the "Configure rules for the update task" page provided by the Add Synchronization Step wizard.

Note: The list of attributes that can be configured with the Initial Attribute Population Rules is specified in the "Attributes Used for Provisioning Person Objects" section in ActiveRoles Quick Connect - Administrator Guide.

TF00091760
When provisioning Person objects, you may encounter the following issue: the provisioning operation fails returning the "Notes error: You are not authorized to access the specified directory" error message.

This error is observed if several provisioned Person objects have the same short names. If two Person objects have the same short name, only one new object will be created.

WORKAROUND
Using Initial Attribute Population rules, set the LNEnforceUniqueShortName attribute of Person object to "false," or configure a rule that generates a more complicated unique value for the ShortName attribute. By default, the Person short name is generated as <first letter of the 'FirstName'><'LastName'>.

TF00091775
When using the Lotus Domino connector, you may encounter the following issue: if you run a mapping or synchronization operation immediately after you provision objects to Lotus Domino, Quick Connect cannot read the newly provisioned objects as if they were not created at all.

This issue is observed because of some latency period in Lotus Domino server.

WORKAROUND
After you perform a provisioning step, wait for several minutes before running a next synchronization step. This latency period will allow the application to properly retrieve data on newly created objects from Lotus Domino server.

TF00094627
When provisioning Domino objects, you may encounter the following issue: the newly created Domino objects reside within a container that differs from the Organizational Unit specified when configuring the provisioning step.

This problem is observed if you have specified an invalid Certifier ID file for the target Organizational Unit when configuring connection to Lotus Domino server.

WORKAROUND
When configuring connection to the Lotus Domino server with the Add Connected System wizard, on the 'Specify Organizational Units' page, ensure that you specify valid Certifier ID files for each selected Organizational Units.

TF00094732
Incorrect behavior of the application: when provisioning Person objects to Lotus Domino, if the LNPolicyName attribute is set to name of a policy containing Registration settings, the newly created Person objects do not receive these settings.

This issue applies only to Registration settings within the policy; other setting types such as Mail, Setup, Desktop, etc., work as expected.

WORKAROUND
To populate the Person object attributes belonging to Registration settings, configure appropriate Initial Attribute Population rules for those attributes .

TF00094770
When provisioning new Person objects without creation of the ID files (i.e. if the LNNoIDFile attribute is set to TRUE), the operation may fail with the "Required registration argument not provided" error message.

WORKAROUND
If the LNNoIDFile attrubute is set to TRUE, using Initial Attribute Population Rules, set the following values to these attributes:
LNCertifierName= <the name of the appropriate certifier, such as "/MyCompany")>
LNStoreIDInAddressBook= "FALSE"

TF00095101
When updating the Lotus Domino objects, you may encounter the following issue: the update step fails with the "Notes error: A required certifier entry was not found in the Name and  Address Book." error message.

This error is observed if you have configured the Object Location Rule for this update step.

WORKAROUND
When configuring an update step, on the 'Configure rules for the update step' page of the Add Synchronization Step wizard, do not configure the Object Location Rule, because  the 'Move' operation is not supported in this release for all types of objects.

TF00095108
After you perform the update or derprovisioning synchronization step, you may encounter the following issue: Quick Connect did not rename Lotus Domino objects even though you have properly configured the Object Name Generation Rules.

This issue is observed because of some latency period in Lotus Domino server.

WORKAROUND
After performing a synchronization step that involves the object rename operations, wait for several minutes before running a next synchronization step. This latency period will allow the application to properly retrieve data from Lotus Domino server.

TF00095385
Incorrect behavior of the application: if you delete members of a Domino group, and then run a synchronization step from Active Directory to Lotus Domino, the application considers that deleted objects are still members of the Domino group.

This issue is observed because of some latency period in Lotus Domino server.

WORKAROUND
After you delete members of a Domino group, wait for several minutes before running any group memberships synchronization operation. This latency period will allow the application to properly retrieve the group memberships information from Lotus Domino server.

TF00096253
Incorrect behavior of the application: the resulting mail file for a newly provisioned Person object does not contain the ACL entry specified in the LNMailACLManager attribute with the use of Initial Attribute Population rules. Moreover, even users with the Domino Manager rights cannot access the mail file.

WORKAROUND
When configuring provisioning step, do not specify the Initial Attributes Populations rules for the  LNMailACLManager attribute. Add the desired Manager ACL entry to the ACL of the mail template on the Lotus Domino server instead.

TF00097052
When provisioning a Person object with the LNCreateMailDb attribute set to TRUE, the created mail database file is inaccessible. An attempt to access the mail database in the security context of the Domino Administrator causes the "You are not authorized to access that database" or "You are not authorized to perform that operation" error message.

WORKAROUND
Using the Initial Attribute Population Rules, set the LNMailTemplateName attribute of a provisioned Person object to the mail template file name.

TF00097534
When provisioning user objects from ActiveRoles Server to Lotus Domino, you may encounter the following issue: user objects that have the same First Name and Last Name attributes are mapped to the same Person object in Lotus Domino.

This issue is observed if the Object Name Generation rule does not ensure that provisioned objects have unique names.

WORKAROUND
Use more complicated Object Name Generation rule, which ensures that all provisioned objects have unique names.

TF00107747
When provisioning User objects to Lotus Domino, you may encounter the following issue: the provisioning operation fails if the Name Generation Rule uses values of attributes that contain space characters. For example, the provision operation will fail, if the Name Generation Rule uses the "givenname" attribute of the user "Anna Maria Victoria"

WORKAROUND
To workaround this issue, rename such objects or redefine the Name Generation Rule.

TF00107961
When performing any synchronization step from ActiveRoles Server to Lotus Domino or vice versa, you may encounter the 'Cannot read the attribute list from the "$VIMGroups" view' error message.

This error is observed if you deleted or renamed the following groups on Lotus Domino server: LocalDomainServers, LocalDomainAdmins, OtherDomainServers.

WORKAROUND
On Lotus Domino server, create a group with any of these names: LocalDomainServers, LocalDomainAdmins or OtherDomainServers.

TF00108000
When updating the group membership for groups with a significant number of members (2000 or more), you may encounter the following issue: the update operation fails returning the "An attempt to update the 'Members' attribute of the object <object name> failed with an unexpected error." error message.

This error is observed if the text field sizes exceed the maximum limit (32 K) defined in Lotus Notes.

TF00108341
When synchronizing between Active Directory and Lotus Domino groups, you may encounter the following issue: the Lotus Domino connector returns an incomplete list of mapped groups.

This issue is observed because of some latency period in Lotus Domino server.

WORKAROUND
Wait for several minutes, and then restart the synchronization step again.

TF00110960
When viewing the membership list of a Lotus Notes group using the "Operation details" dialog box, you may encounter the following issue: the membership list does not display the nested groups.

WORKAROUND
To view nested groups that are members of a Lotus Notes group, use the Lotus Notes client User Interface.

TF00111144
When synchronizing between Organizational Units (Active Directory) and Certifier objects (Lotus Domino) you may encounter the following issue: when viewing the mapped object pairs, the application displays invalid parent path for Certifier objects.

TF00111156
When synchronizing the group membership for Active Directory and Lotus Notes groups, you may encounter the following issue: Quick Connect fails to delete nested groups on Lotus Domino server whose counterparts in Active Directory have been deleted.

WORKAROUND
To workaround this problem, on Lotus Domino server, manually remove nested groups whose counterparts in Active Directory have been deleted.

TF00111179
When provisioning groups or certifier objects from Lotus Domino Server to Active Directory or vice versa, you may encounter the following issue: Quick Connect cannot find objects to provision, even though the synchronization scope contains such objects.

This issue is observed if in the synchronization step settings, you have specified the target or source container that differs from the root container (names.nsf).

WORKAROUND
When configuring synchronization steps, do not specify the target or source container. Use the default container (names.nsf).

The table below outlines the hardware and software requirements for installing and running Quick Connect for Lotus Notes.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

Licensing

To use Quick Connect for Lotus Notes, you need to obtain a license from Quest Software. The license specifies the maximum number of enabled user accounts in all domains managed by ActiveRoles Server. When installing Quick Connect for Lotus Notes, you will be prompted to install the license key file purchased from Quest Software.

Important: You can install Quick Connect for Lotus Notes only on a computer running Quick Connect Sync Engine.

Preparing for Installation

You need to complete a number of steps to prepare for a successful installation and configuring Quick Connect for Lotus Notes.

1. On your local computer, install Lotus Notes 6.5.x.
2. Save all Organizational Unit certifier ID files you want to use on your local computer, in a secure location.

Installation Instructions

Use the following steps to install Quick Connect for Lotus Notes :

1. Run the delivered QuickConnectForLotusNotes.msi file.
   The Quest ActiveRoles Quick Connect for Lotus Notes Installation wizard starts.
2. On the Welcome page, click Next.
3. On the License Agreement page, select the I accept the license agreement option and click Next.
4. On the User Information page, specify your personal information, and then click Licenses.
   The License Status dialog box opens.
5. In the License Status dialog box, click Browse License, using the Open dialog box locate and open the license key file obtained from Quest Software, and then click Close.
6. On the User Information page, click Next to proceed with the installation process.
7. On the Ready to Install the Application page, review the installation settings you are going to use. To proceed with the installation process, click Next.
8. On the Completion page, click Finish to close the wizard.

For information on how to use Quick Connect for Lotus Notes, see "Configuring Connection to Lotus Domino Server" in Quick Connect - Administrator Guide.

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

Contact Customer Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.

Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com 

From SupportLink, you can do the following:

• Quickly find thousands of solutions (Knowledgebase articles/documents).
• Download patches and upgrades.
• Seek help from a Support engineer.
• Log and update your case, and check its status.

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

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.

© 2010 Quest Software, Inc. ALL RIGHTS RESERVED.

Quest, Quest Software, the Quest Software logo, Aelita, Akonix, Akonix, AppAssure, Benchmark Factory, Big Brother, ChangeAuditor, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, GPOAdmin, I/Watch, Imceda, InLook, IntelliProfile, InTrust, Invertus, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, MessageStats, NBSpool, NetBase, Npulse, NetPro, PassGo, PerformaSure, Quest Central, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, vAnalyzer, vAutomator, vControl, vConverter, vEssentials, vFoglight, vMigrator, vOptimizer Pro, vPackager, vRanger, vRanger Pro, vReplicator, vSpotlight, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vEssentials, 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 used in this guide are property of their respective owners.

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

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656

Web:    http://www.quest.com
e-mail:  legal@quest.com

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.