LastLogon change on AD is not synchronized to DS by itself.
This is a note from Microsoft forum:
The DirSync control taps into the replication stream to get the necessary changes. Since lastLogon is not replicated, it isn't available via the DirSync control.
Additional notes:
The lastLogon attribute is not replicated. In contrast the lastLogontimeStamp attribute is replicated.
So, most likely, we have to replace lastLogon with lastLogonTimeStamp. (so is lastLogoff/lastLogofftimestamp.)
git patch file (master) 0001-Ticket-48232-winsync-lastlogon-attribute-not-syncing.patch
Ack
Does that use the same format as lastLogon? If not, there may be syntax and console changes required.
Replying to [comment:3 rmeggins]:
Ack Does that use the same format as lastLogon? If not, there may be syntax and console changes required.
Thank you, Rich! Luckily, the format looks identical. {{{ dn: CN=ou0_user1,OU=OU0,DC=test,DC=example,DC=com lastLogon: 130826658763641736 lastLogonTimestamp: 130826658763641736 }}}
Reviewed by Rich (Thank you!!)
Pushed to master: c6b211f..0db2978 master -> master commit 0db29788e6c1b17f944fcafa368b66580e1e90d5
Pushed to 389-ds-base-1.3.4: bff0dba..b81adb0 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 commit b81adb0bc8ad97fec50fba30454e94858476bad5
Pushed to 389-ds-base-1.3.3: 1cde230..a3af235 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 commit a3af2351bb1fb3782c9f79209043ddc36e0e06d1
Pushed to 389-ds-base-1.2.11: f5552bf..e94bf22 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 commit e94bf22c252197c85e7f7562d3ba93f5a0f2215e
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1248738
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.4.4
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1563
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)