I'm having trouble with the Absolute system we use in my company to track and freeze laptops. I've set a policy to freeze devices that have been inactive for over 60 days, but it seems like Absolute is incorrectly freezing active devices, claiming they've been inactive longer than they really have. Has anyone else faced this issue? If so, what solutions did you find? Thanks for your help!
2 Answers
It sounds frustrating! I haven’t used Absolute myself, but I'm curious about how it tracks inactivity. Sometimes, issues can stem from Active Directory attributes that might not sync correctly. I used to rely on lastLogonDate, but I've found it can be misleading because the updates from different domain controllers aren’t always in sync. Now, I check the computer account password reset date instead—if it hasn't reset in over 60 days, that machine isn’t logging in for sure. Could this approach help you?
Have you checked when the last check-in dates appeared for those devices? That could provide some insight into what’s going wrong. Sometimes, it shows a check-in date, but it might not reflect actual activity.
Yeah, I did check that. The last check-in is showing October 26th for some of the devices, which is confusing since they're being flagged as inactive.
That's a good point! I've had similar experiences with lastLogonDate. It really can be a hassle to track down accurate data, but using password resets is definitely a more reliable method.