#48232 winsync lastlogon attribute not syncing between DS and AD.
Closed: Fixed None Opened 3 years ago by nhosoi.

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.)


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 0db2978

Pushed to 389-ds-base-1.3.4:
bff0dba..b81adb0 389-ds-base-1.3.4 -> 389-ds-base-1.3.4
commit b81adb0

Pushed to 389-ds-base-1.3.3:
1cde230..a3af235 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit a3af235

Pushed to 389-ds-base-1.2.11:
f5552bf..e94bf22 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit e94bf22

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.4.4

2 years ago

Login to comment on this ticket.

Metadata