Irregular Jamf Inventory update

Are you referring to the Jamf 15minute "heartbeat" or do you have a policy that doing a full recon (inventory scan) every 15 minutes?

I have a policy which runs full recon.

Running full recon every 15 minutes isn't recommended. First, the recon probably isn't finishing before it gets triggered again. That's why it appears to never update for you. Also, doing recon so often puts unnecessary load on your machines and the server. Your machines aren't changing that often to need a recon with that kind of frequency. Realistically, once or twice a day is more than enough. It's customary to set a recon after software installs or other pushes to help you know when changes are occuring, you can set that as part of the installation or script execution, as appropriate.

I think you are confusing for check-in and inventory update. 

100% This! "Check-in" every 15 minutes is ok. It's the default. Inventory is usually advised to be run only once a day. In our case, the basic inventory policy is set to execute once a day, on the recurring check-in (which is set to every 15 min). So the machine is checking with the server every 15 minutes, but only submits an inventory once. 

Further, we used to add a recon line to the end of installation policies to update inventory and associated smart groups. Even that could cause quite the strain on various systems and make the policy take MUCH longer to execute. Jamf found a less heavy-handed way of handling that, too!

In the "Maintenance" section of a computer policy, there's a checkbox labeled "Update Inventory". The cool part about this is that it is at least a little aware of other processes happening and won't step over/on them, waiting until all running processes are complete, further reducing conflicts between processes and cutting down on inventory. AND since the inventory process is handled separately in this case, it does not reflect in the execution time of the policy, so everything looks and feels much faster to the end user. 

I guess your referring to Check-in not happening in every 15 mins, check the jamf logs of the device where checkin is not happening, check if there is any other jamf policy is still running the background, check the jamf process 

ps aux | grep jamf, Kill the process and try the check-in works. 

Recommended Actions:

• Verify and renew MDM profiles if necessary.

• Encourage regular device restarts.

• Disable "Collect available software updates" in inventory settings.

• Use the sudo jamf recon --verbose command to identify specific issues.

For persistent problems, consider redeploying the Jamf binary via APNs or re-enrolling the device.

In some of our systems, I have done an OS & User clear cache function and had the user restart and then the inventory picked up again...

@ScottEKendall Yes, that tweak sometimes works locally on Mac.