[OT] How to handle machines that don't check in

[jwojda]

How do y'all handle machines that don't check in? In a large company like ours, we have constant turn over - user's/manager putting former employees machines in their desk drawers until a new employee is hired, lost, stolen, damaged, "borrowed to use at home", or just plain DB glitches - where the machine is here but not talking to the JSS, etc. Most are machines that were deployed prior to our DMZ setup, so they have the internal only JSS setup on them.

I know about Rich's CasperCheck which helps for going forward, but not the backfill.

[Sanders]

I've setup a Smart Group that keeps track of all computers that haven't checked in for over a day. Since our network is segmented by building, we can generally figure out where the computer is located and the go look at it. Not a perfect system, but it helps keep track of most of the problem computers.

[SeanA]

It is taken care of as part of an asset management process.

If an asset does not check in 30 minutes, an email is sent to the user asking about the status of machine (you still have it and use it, you have it and don't use it and it can be picked up, you don't have it, etc). In the email, if they have it, they are asked to click on a link to update our asset management database. For Macs, they click on a link that opens up a Self Service policy which runs 'jam manage', 'jamf recon', and also updates our asset management database (See open Self Service via email link for details on email link).

If email does not resolve the issue, a ticket is created and a tech is sent to the desk.