Computers falling out of management

Is the jamf framework being removed from the computer or is the device listed by the JSS as "unmanaged" in the computer record?

Going forward until JAMF implements incorporating a self heal function I recommend using CasperCheck to help:

https://github.com/rtrouton/CasperCheck

That must be unnerving, so I can understand your frustration.
Have you been able to pull a jamf log off one of the Macs affected by this to see what the log is showing? I'd be curious to see if an errant policy is being run as the last item before it became unmanaged. Is there perhaps a policy removing the management account from them, or changing the password on the management account?
I've never heard of that many devices going unmanaged in such a short time, so something must be causing it.

While things like CasperCheck are great and can help, they don't replace troubleshooting to find the root cause of what's causing this.

Hello All,

Thanks for replying @nkoval and @Cornoir. The binary is still present on the client Macs. In fact, I was able to go back to the client object in the JSS and "re-check" the box for allowing the JSS to manage the Mac. This resolved the management piece.

@mm2270 is right, troubleshooting is critical. I still don't have an answer why these Macs dropped their management component in the JSS. My next worry is, there are a large number of our Macs that are not updating their inventory in the JSS. They are all checking in still, but the updating of the inventory for each computer isn't working. I don't know why. I don't have a sense as to why either.

I have asked our JAMF support team to chime in based on the logs they sent me.

If it helps, I was having the same issue with computers randomly becoming "unmanaged." Since I know our management account username/ password, I was able to create a script that finds all unmanaged computers that were formally managed and "re-manage" them. It can be set up as a cron job or run manually through Self Service (with some setup).

API_UnmanagedComputerFix.sh

I was able to find the issue as my bad implementation of @rtrouton CasperCheck that would cause all computers to reinstall a quick add package every startup irrespective of the checks in the script. I'm still in the process of fixing the issue. But I have a workaround to keep computers managed in the interim.