This is due to the whenChanged attribute itself, which is not replicated across DCs.
It is likely the DC that is being selected to collect the information during discoveries is not the same as the one you cross-reference with in active directory.
This value can be different on every DC, and is only changed per DC when a user change is initiated on that DC.
The best way to work around this is to set the preferred DC in the discovery scopes setting.
This will give you consistent values during discoveries and reporting, but can still be incorrect if the user was not modified on this DC.
It is recommended to not report on this attribute, due to the likely inconsistencies you will face.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center