lastlogontimestamp

[ditto]

I am being told that from out corporate data center that Lansweeper is using "lastlogin" instead of "lastlogontimestamp" when the active searching query goes out to the domain. All our systems are 2003 or highter is there anyway to change this in the software to use only lastlogontimestamp?

--Dave

[Hemoco]

That is correct, that's why it's gathered on all DC's to make sure that the value is up to date.

[ditto]

This is what I see. I removed my acual domain names and replaced them with Domain_Name in this example.

Client:
10.15.63.8
Starting node:
dc=Domain_name,dc=Domain_name,dc=com
Filter:
( & (objectCategory=CN=Computer,CN=Schema,CN=Configuration,DC=Domain_name,DC=com) (lastLogon>=129290318340585404) ( ! (userAccountControl&2) ) )
Search scope:
subtree
Attribute selection:
lastLogon,cn,operatingSystem
Server controls:

--Dave

[ditto]

My understanding is that the lastlogon is not a replicated attribute, while lastlogontimestamp is. Lastlogintimestamp would seem to provide better information than lastlogin. Am I way off base with this?

--Dave

[Hemoco]

No.

Lansweeper query's all dc's for the lastlogon timestamp so you will have the correct one.