Last Check-in reporting issue

powellbc
Contributor II

I have discovered that when creating a smart computer group that returns last check-in, all computers list a time. However, for many of these computer record, when going to the individual record, no last check-in time is listed. If I query the database directly using MySQL, the check-in time is reported as expected.

Is this a bug or is there a reason for this?

9 REPLIES 9

dwandro92
Contributor III

Did you ever find a solution for this? I am experiencing the same problem and currently have a case open with JAMF.

CAJensen01
Contributor

It's definitely a bug. Have seen it as well on 9.81/9.82. Not sure on the status, though.

bpavlov
Honored Contributor

If this is a bug and you have defect info, can you share and submit it here:
To submit bugs:
http://goo.gl/forms/tEvpXJrZaj

To view defects peruse through here:
https://goo.gl/zTdvwT

More info:
https://jamfnation.jamfsoftware.com/featureRequest.html?id=1699#responseChild14176

CAJensen01
Contributor

D-008311 Is the bug I have that was supposedly linked to this behavior.

bpavlov
Honored Contributor

Do you have an description from JAMF on that defect?

CAJensen01
Contributor

I do not, my support rep just noted that was the bug ID they were tracking the behavior under, and the workaround is to use an advanced search.

bpavlov
Honored Contributor

I went ahead and added it based on the info. Hopefully it's fixed at some point for those effected. Thanks for contributing. :)

dwandro92
Contributor III

I did some digging into the issue and I believe that I found the cause of the problem. I sent this info off to the support engineer working on my case.

If you're experiencing the problem now, check your log flushing settings for "Computer Usage logs". If you compare this time frame with the last check-in time of the records that are experiencing the problem, you'll likely find a correlation. (e.g. if your flushing period is set to "1 week", you'll probably see that computers which haven't checked in for 8 days are affected).

KSchroeder
Contributor

We are encountering something similar in 9.92...which led to about 50 of our developer's Macs being locked down with a boot lock PIN (trying to keep things secured, don't you know). I'm going to investigate one of them tomorrow, but anyone have any ideas what could do this, short of removing the MDM profile and/or the JAMF agent? Also, is this field controlled by the JAMF agent, or a MDM "heartbeat" functionality inherent in the OS?