The lastLogonTimestamp attribute in System Center 2012 Configuration Manager may not be accurate

Article ID: 2679653 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario in Microsoft System Center 2012 Configuration Manager:
  • Active Directory User Discovery is enabled in a Microsoft System Center 2012 Configuration Manager environment.
  • You use the lastLogonTimestamp attribute to determine the last logon for a user.

In this scenario, the exact time at which a particular user last logged on may not be accurate.
Back to the top | Give Feedback

CAUSE

This behavior occurs because the design and default configuration of Active Directory may result in the value of the lastLogonTimestamp attribute being updated only when the current value in Active Directory is 9 to 14 days older than the time of logon.
Back to the top | Give Feedback

REFERENCES

For more information about the lastLogonTimestamp attribute, visit the following Microsoft websites:
Last-Logon-Timestamp attribute
(http://msdn.microsoft.com/en-us/library/windows/desktop/ms676824(v=vs.85).aspx)


"The LastLogonTimeStamp Attribute" – "What it was designed for and how it works"
(http://blogs.technet.com/b/askds/archive/2009/04/15/the-lastlogontimestamp-attribute-what-it-was-designed-for-and-how-it-works.aspx)



Back to the top | Give Feedback

Properties

Article ID: 2679653 - Last Review: July 9, 2012 - Revision: 3.0
APPLIES TO
  • Microsoft System Center 2012 Configuration Manager
Keywords: 
kbtshoot kbprb kbexpertiseinter kbsurveynew KB2679653
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top