Error Message

YYYY-MM-DD HH:MM:SS,214 INFO  [directory.ads.ADSIndexer] (ADIndexer:) CaseName:[]  UserName:[superuser] Email address Leeroy.Jenkins@edp.lab shared between CN=Leeroy Jenkins,OU=Moved,DC=eDP,DC=lab and CN=Jenkins, Leeroy\ ,OU=TestUsers,DC=eDP,DC=lab. Skipping...

Notes

The esa property esa.adsindexer.resourceDomain allows enterprises, which employ a master domain model to simplify resource management by separating the administration of resources from the administration of user accounts, to perform eDiscovery Exchange mailbox collections when the user accounts are separated from email resources.  However, with this property enabled, an Active Directory Participant Synchronization is unable to determine the correct DN and email server based soley upon a user's SMTP email address and therefore skips updating the DN and mail server entries for such a participant.

WORKAROUND:

If the esa property esa.adsindexer.resourceDomain is set to true and the \logs\server.YYYY-MM-YY.log shows participant entries being skipped similar to the error above, perform the following steps:

1.  Set the esa property to false.
   1. Navigate to System > Support Features > Property Browser
   2. In Name of Property to change, enter: esa.adsindexer.resourceDomain
   3. In New value (leave blank to remove), enter: false
   4. Check the box next to Confirm change. Are you sure? 
   5. Click Submit.
2. Run an Active Directory Participant Synchronization
   1. Navigate to System > Support Features > Directories and Servers > Active Directory
   2. Click Start Discovery button at the bottom left of the page.
   3. Wait for the Active Directory discovery window to show Participant Synchronization Status: Idle - Discovery completed. 
3. Set the esa property to true.
   1. Navigate to System > Support Features > Property Browser
   2. In Name of Property to change, enter: esa.adsindexer.resourceDomain
   3. In New value (leave blank to remove), enter: true
   4. Check the box next to Confirm change. Are you sure? 
   5. Click Submit.

Enterprise Vault Technologies LLC has acknowledged that the abovementioned issue is present in the current version(s) listed under the Product(s) Section of this Article. Enterprise Vault Technologies LLC is committed to product quality and satisfied customers.

There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Enterprise Vault Sales representative or the Enterprise Vault Sales group to discuss these concerns. For information on how to contact Enterprise Vault Sales, please see  https://www.enterprisevault.com/

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

When running an Active Directory Participant Synchronization, participants whose Distinguished Name (DN) has changed since the last synchronization will not be updated with their new DN, if the esa property esa.adsindexer.resourceDomain is set to true. If the participant's DN and their mail server have both been updated since the last synchronization, the mail server entry will not be updated and therefore, not be available for an Exchange Collection.