I am developing a script to report on users who have not logged in to the domain for 6 months. I'm using lastLogonTimestamp as within 14 days is precise enough for my purposes, and I don't want to have to query each DC.. The problem is, when I run the script, the lastLogonTimestamp comes back blank for nearly 600 users. It is my understanding that lastlogondate is some sort of powershell alias that converts the 'lastlogontimestamp' user attribute value from a large integer into a readable date. I had success with this query in the past and again it works fine for some users. I went into ADSIedit and found that all users have a value in lastlogontimestamp. To say it's "a PowerShell problem" would be akin to saying that any fault in a C# app is "a .NET problem." I wasn't able to reproduce what you saw, but I didn't check every system on my network (not an admin) and our setups are almost certainly different, so there's a lot of wiggle room there. In Windows 2003 Active Directory, Microsoft introduced another user attribute named lastLogonTimestamp. This attribute is replicated to other DCs, but only after two weeks (minus a random percentage of 5 days), so it is suitable to locate inactive accounts which did not logon to the domain for a long time. AD LastLogonTimeStamp not working as it's supposed to ? I've been doing some querying in AD (with Powershell) and retrieved the LastLogon, LastLogonDate and LastLogonTimeStamp for Misses X. Taking this into consideration, using the lastlogontimestamp to find stale user accounts is still What AD attribute should be used pwdlastset or Lastlogontimestamp to determine if a computer object is stale? I like this guidance "One-Liner: My Take On Finding Stale User and Computer Accounts". Ian recommends using both attributes as a way to determine when an object is stale. What is the difference between lastLogon vs lastLogonTimestamp atributes in Active Directory? These attributes contain slightly different values - pls see an example below. I am trying to determine when was the last time that this user has logged in to see if this is a stale user or active user. Description: In this article, I am going to explain the difference between LastLogon vs LastLogonTimeStamp in Active Directory and how to find the True Last Logon value of an user from these two attributes. Summary: Both are Active Directory Schema attributes which are used to hold an user's Last Logon Time in two different ways. Windows PowerShell Step by Step Your hands-on guide to Windows PowerShell scripting fundamentals Expand your expertise—and teach yourself the fundamentals of Windows PowerShell scripting, including features available in Windows PowerShell 5. If you are an IT professional, power user, Active Directory Cleaner - User Guide 1 Active Directory Cleaner User Guide. Active Directory Cleaner - User Guide 2 Reports can be exported to PDF, CSV and Excel formats. PowerShell command for each of the report category. The Active Directory attribute lastLogonTimestamp shows the exact timestamp of the user's last successful domain authentication. In contrast to the lastLogon attribute th lastLogonTimestamp is replicated between all domain controllers in the domain - but only if the value is older than 14 days (minus a random percentage of 5 days). Powershell script to extract all users and last logon timestamp from a domain This simple powershell scrip