I just discovered that i have a lot of macs with the red marks on jamf protect. This means that they did not connect to jamf protect since one month.
This is strange because those computers regularly check in with jamf pro and jamf protect is pushed automatically from jamf pro.
What can be the problem and how can i solve it?
@Phileinif they are still checking in via Jamf Pro, you can run this command / add this in a shell script to a Jamf Policy set for recurring check-in once a day & see how that goes, this will force a jamf protect check-in
sudo protectctl checkin
The Jamf Protect agent includes the protectctl tool, which allows you to execute some simple commands on computers. The following commands are available:CommandDescription
Finds and repairs issues that may occur during installation of the Jamf Protect agent
Prints the Jamf Protect agent version installed on computers
Prints the following information about computers, including the following:
You can also use the following flags:
Forces a Jamf Protect agent check-in on computers. You can also use the --insights flag to force an insights check-in.
Prints help information about protectctl commands
Re-Deploy the Configuration Profile (Un-scope / Scope) - for Jamf Protect. Re-Deploy the Jamf Protect Package. Clearly something is wrong with the Configuration Profile, that's where i'd start.