We have a Patch Management policies that updates Jamf Connect to the latest version.
When applied the numbers go up pretty fast, but then it stops.
Machines don't get any update.
When is an updated triggered on a device (check-in?)
and what to do to update the clients again?
Are you only seeing this in Jamf Connect or other apps as well? I know I felt a little dumb when I figured out I had the old package assigned the definition for the new versions of an application when I first started using patch management. So I pretty much created loop of detecting the app was out of date, installing the package, inventory update finds app is still out of date and it continues.
I only use the patch management for JC and only since the release of 2.9.1
Before using patch management i was using a smart group to check for outdated versions, but it had the same issue as patch management.
Initial installs go very quick, and then sudednly it halts.
Machine check-in every 15 minutes but stick to the old version.