Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Needs Review
Workspace Domino
Categories Administration
Created by Guest
Created on Feb 16, 2026

AD Group-Based Sync and Sub-OU Handling in Domino DirSync

AD users that should be synchronized with Domino must be members of the defined Active Directory group G_DominoADSync.

This group contains multiple assigned users, and each of these users has a corresponding Domino account.

Currently, it appears that Directory Synchronization (DirSync) only searches one level below the defined base, which in our case is the Sub-OU HDH2.0, and only identifies person objects directly within that branch.

However, our understanding is that if a user (for example, CN=John Doe/OU=HDH/OU=ACME) is a member of a group located within the subtree (e.g., */OU=HDH2.0/OU=ACME), that user should also be returned during the LDAP search — even if the user object itself resides in a different OU branch.

From our perspective, Domino DirSync should honor and process all available sub-OUs starting from the defined root of the directory tree, ensuring that all eligible group members are properly discovered and synchronized.

  • Attach files
  • Guest
    Feb 16, 2026

    Btw. the members of a group have their on structural OU-Path in AD.

    So DirSync should honor the path for each indivual member not only of groups own hierarchy.