haircut / detectx-jamf Goto Github PK

Since we purchased DetectX Swift this summer, I had noticed that a number of machines that were running our DetectX search policy were producing policy log failures, while most were running the policy just fine.

While the policy itself is throwing failures for this subset of machines ...

... from what I can tell, the script is running fine and successfully writing to our results.json file. Below is the contents of results.json for the machine that produced the policy error above (notice the timestamps on the email and the DetectX searchdate).

cat /Library/Application\ Support/JAMF/Addons/DetectX/results.json 
{
	"product" : "DetectX Swift",
	"registered" : true,
	"version" : "1.082",
	"searchdate" : "2019-01-04T08:06:37-0500",
	"duration" : 118.47,
	"spotlightindexing" : true,
	"issues" : [

	],
	"infections" : [

	]

This is happening both on the current DetectX version - 1.082 - and the previous version we were deploying.

When I run sudo /Applications/Utilities/DetectX\ Swift.app/Contents/MacOS/DetectX\ Swift search -aj /Library/Application\ Support/JAMF/Addons/DetectX/results.json manually on a couple of the machines in question, I can confirm that the exit code of the command is 0 and that data of the results.json file gets updated. This leads me to believe it's something with the error logic of the DetectX-Search script.

The majority of our machines are on 10.13.6 and running DetectX 1.082.

If there's any additional information you need from me to troubleshoot further, please let me know.