Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Im using LastLogon attribute to check when a user account last was used, but i see the value seems to be updated on each DC when a user logs in via that DC. And its NOT synced across the different domain controlers.

So my question is: Is this how this attribute should work? Or is it something wrong in our domain?

share|improve this question
up vote 2 down vote accepted

The lastLogonTimeStamp attribute is automatically replicated across all domain DCs only if the domain is (at least) at Windows Server 2003 functional level.

Also, beware of differences between lastLogonTimeStamp and lastLogon (the latter one is obsolete and never replicated).

share|improve this answer

The LastLogon attribute is not replicated. When the domain functional level is "Windows Server 2003" there is a new attribute "lastLogonTimeStamp" which is replicated.

share|improve this answer
He wrote "LastLogon", but actually linked "lastLogonTimeStamp". – Massimo Apr 19 '10 at 9:04
He is correct also. I was actualy checking both, but assumed the LastLogon was correct one to use ( And used lastLogonTimeStamp as a fallback). – EKS Apr 20 '10 at 10:41

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.