Skip to main content

Hi

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

 

 

 

https://docs.jamf.com/jamf-protect/documentation/Core_Components.html

 

protectctl Command-Line Tool

The Jamf Protect agent includes the protectctl tool, which allows you to execute some simple commands on computers. The following commands are available:

CommandDescription

repair

Finds and repairs issues that may occur during installation of the Jamf Protect agent

version

Prints the Jamf Protect agent version installed on computers

info

Prints the following information about computers, including the following:

  • Agent uptime and version

  • Install Type (system extension or launch daemon)

  • Agent status (e.g., Protected, Enrolling, Missing Plan)
  • Plan ID
  • Plan hash
  • The date and time of the last agent check-in
  • The date and time of the last insights check-in

You can also use the following flags:

  • The -v flag prints verbose information about the agent, such as agent connection information (state, protocol, and identifier) and Threat Prevention information (current version and event and match count per sensor).
  • The --json flag prints the information in JSON format.
  • The --plist flag prints the information in PLIST format.

checkin

Forces a Jamf Protect agent check-in on computers. You can also use the --insights flag to force an insights check-in.

help

Prints help information about protectctl commands

@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

 

 

 

https://docs.jamf.com/jamf-protect/documentation/Core_Components.html

 

protectctl Command-Line Tool

The Jamf Protect agent includes the protectctl tool, which allows you to execute some simple commands on computers. The following commands are available:

CommandDescription

repair

Finds and repairs issues that may occur during installation of the Jamf Protect agent

version

Prints the Jamf Protect agent version installed on computers

info

Prints the following information about computers, including the following:

  • Agent uptime and version

  • Install Type (system extension or launch daemon)

  • Agent status (e.g., Protected, Enrolling, Missing Plan)
  • Plan ID
  • Plan hash
  • The date and time of the last agent check-in
  • The date and time of the last insights check-in

You can also use the following flags:

  • The -v flag prints verbose information about the agent, such as agent connection information (state, protocol, and identifier) and Threat Prevention information (current version and event and match count per sensor).
  • The --json flag prints the information in JSON format.
  • The --plist flag prints the information in PLIST format.

checkin

Forces a Jamf Protect agent check-in on computers. You can also use the --insights flag to force an insights check-in.

help

Prints help information about protectctl commands


Thanks. This is the result of the command:

 

Request timed out while trying to perform info sync

Thanks. This is the result of the command:

 

Request timed out while trying to perform info sync


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.

I solved 2 of them. The users had not rebooted the system for over a months. After a reboot, the issues were gone. 

Terms & ConditionsCookie settingsAccessibility statement