Cause:
This can be due to several scenarios, ie: moving users between Exchange Servers, OU's, AD name changes, etc.
If the user has been moved from one Exchange Server to another, the SynchInMigrationMode key should be in place before making changes to users in Active Directory. See Technote 284956 under Related Documents below. When not used, the information is not updated properly in SQL, thus causing the errors. The key can be added after the move but it is recommended to add the key prior to the move.
A Dtrace of AgentClientBroker process will show the following line:
"CFilterHelper::StampVaultIDEx - error 0x8004010F"
Solution:
1. Run the following Query to gather the EV information regarding the user:
USE EnterpriseVaultDirectory
SELECT * FROM ExchangeMailboxEntry WHERE MbxAlias = 'alias name of user'
2. Examine the columns labeled LegacyMbxDn and ADMbxDN in the Query results. In most situations, the information in either or both of these columns is incorrect. Compare this to the user’s Active Directory Properties. Please follow the next steps if the information does not match.
3. Run the following Query to remove the user’s information from EV (the user will be re-added to EV in the next step):
USE EnterpriseVaultDirectory
DELETE FROM ExchangeMailboxEntry WHERE MbxAlias = 'alias name of user'
4. From the EV Administration Console, run the Provisioning Task. When it has completed, run the same query from Step 1 above and compare the columns again. They should now match up. At this point, the user can now be Enabled and Synchronized.
