Bug 1248738

Summary: winsync lastlogon attribute not syncing between DS and AD.
Product: Red Hat Enterprise Linux 6 Reporter: Noriko Hosoi <nhosoi>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED DUPLICATE QA Contact: Viktor Ashirov <vashirov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0CC: jgalipea, nkinder, rmeggins
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-31 22:52:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Noriko Hosoi 2015-07-30 17:57:27 UTC 
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.)
Comment 1 Noriko Hosoi 2015-08-31 22:52:25 UTC 

*** This bug has been marked as a duplicate of bug 1245237 ***