#Set up netwin surgemail manual

That is, for a date that’s more than 14 days ago, that was the last time the user logged on at any DC in the domain. You can use LastLogonTimestamp (which is replicated to all DCs) to find a last logon time that’s accurate to within 14 days (I don’t know why it’s this interval). If you query the user information on another DC, it can be completely different (and generally *is* different). The LastLogon time attribute is not replicated between domain controllers, and it only applies to the DC where you’re reading the value from. “LastLogon” queried in this way is only accurate for a domain where there is one domain controller. This advice seems very old fashioned and amateur (not “pro”), and I have no idea how this page is so high in Google rank. Let me know by leaving a comment below right now. Was this post helpful or do you have questions? I have just shown you three very simple and quick methods for finding when a user last logged on to the domain. It would be very time consuming and difficult to return the real last logon time without this tool.

#Set up netwin surgemail manual

The AD last logon Reporter eliminates all the manual work of checking the lastlogon attribute for all users across all domain controllers. Here is a screenshot of the report exported to CSV You will be prompted for a location to save the file, once saved the file will automatically open. To export the results just click on the export button, select your format and click export all rows. You can click on any column to sort the results in ascending or descending order. You can see in the screenshot below the tool returns the users name, account name, domain controller name, and the last logon date. It only takes 3 simple steps to run this tool. You can try this tool for free, download your copy here. The built-in Microsoft tools do not provide an easy way to report the last logon time for all users that’s why I created the AD Last Logon Reporter Tool.