Is Last_Logon_Timestamp0 the best way to get the last logged on time?

My9to5 261 Reputation points
2020-12-21T13:47:31+00:00

I am in charge of writing an inventory report the management can use to locate machines. I was very excited when we turned on AD discovery because I was after the Last_logon_timestamp0 field to integrate into reports. Come to find out, that field is pretty useless for me because the dates are very off compared to the AD field "LastLogonDate". Is there a better option? Is there anyway I can force SCCM to grab the "LastLogonDate" from AD?

Microsoft Security | Intune | Configuration Manager | Other
{count} votes

Accepted answer
  1. Garth Jones 2,076 Reputation points
    2020-12-21T14:32:28.44+00:00

    The problem is with AD, the field is update every 14 days in AD across all DCs, and updated with the last update on the DC that this the authentication. Therefore it is not reliable when inventory by CM as it will depend on which DC CM inventory.

    What exactly is your end goal? How often is Hw inventory?


1 additional answer

Sort by: Most helpful
  1. Youssef Saad 3,416 Reputation points
    2020-12-21T14:37:25.467+00:00

    Hi @My9to5 ,

    Have you tried to add the attribute on Administration > Discovery Methods > Active Directory System Discovery settings? You can check the following article, it may help you.

    In addition, below an article to understand the difference between LastLogon and LastLogonTimestamp:

    I agree with @Garth Jones , you have to check the same attribute on Active Directory, ConfigMgr just discover the attribute based on what is recorded in AD.

    Regards,


    Youssef Saad | New blog: https://youssef-saad.blogspot.com
    Please remember to ** “Accept answer” ** for useful answers, thank you!


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.