ODMAD: specific users are not being read by the workflow (4377633)

After workflow has finished, there are some missing users that weren't created in the target. These users are also missing in the source environment, Details, expand Users. These users are in scope, which means that they are in the same OU as working users and LDAP filter is applicable for them as well.

How it's possible to force ODMAD to read those users?

PS: Same may apply to the cloud tenant users

Users' usnChanged value is outside of Read LDAP read boundaries, shown in the workflow log.

When ODMAD is reading AD objects, it's using the following algorithm:

• initially, it extracts usnChanged value from DC and runs LDAP read objects with usnChanged>=0 and usnChanged<=<current_DC_value>
• this <current_DC_value> becomes the LastPushUsn
• next time workflow is performing a Read, the LDAP will read objects with usnChanged>=LastPushUsn and usnChanged<=<current_DC_value>
• <current_DC_value> becomes the LastPushUsn again
• etc

If some object was not read and the rest of LDAP filter parameters are applicable, then it means that AD object's usnChanged value is outside of boundaries in the LDAP read command.

To resolve the issue, please modify the affected AD object in any way, by changing any of its unused attributes, for example. This will modify its usnChanged value and it will be included during the next Read cycle.

It's also possible to perform a Read refresh on all objects in the scope by going to menu, Environments, select environment, Settings. Select "Reset USN/delta timestamp" checkbox.