topic Re: JAMF Upgrade broke HIP report in GlobalProtect Discussions

JAMF Upgrade broke HIP report

JasonBTR — Sat, 14 Aug 2021 21:17:39 GMT

Greeting All.

JAMF Cloud did an upgrade this morning. This update caused the jamf client binary to be updated on my computers.

After the jamf client upgrade GlobalProtect no longer shows JAMF (Casper) in the hip report.

Tested GP version 5.2.5 & 6.

Has anyone else experienced this issue?

Re: JAMF Upgrade broke HIP report

taylorel — Sat, 14 Aug 2021 23:21:32 GMT

We started seeing issues today with macbook clients either not showing jamf in the hip logs, or showing version 10.31.1 as not enabled, and so failing to connect with their GlobalProtect client. Other macbook clients with jamf 10.30.3 appear to be connecting with their gp client OK

Re: JAMF Upgrade broke HIP report

JasonBTR — Mon, 16 Aug 2021 18:49:30 GMT

I found the jamf release notes. It look like jamfAgent was removed as part of the upgrade.

Not yet sure if the hip object it looking for the specific file or service running.

Release 10.31.0:

The legacy jamf agent utility (/usr/local/jamf/bin/jamfAgent)

The legacy jamf agent utility has been removed. This does not affect existing workflows using the jamf binary. Jamf.app contains the previous functionality of the jamf agent utility.

Re: JAMF Upgrade broke HIP report

RDuggal1 — Fri, 20 Aug 2021 13:00:06 GMT

Hi JasonBTR,

Do you know if fix is now available?

Re: JAMF Upgrade broke HIP report

JasonBTR — Fri, 20 Aug 2021 17:57:05 GMT

Happy Friday!
I've been informed that the fix for the jamf detection issue will be included in the next globalprotect client release (5.2.9 I think).

I haven't heard a timeline yet.

Once I get a GPC # for the issue I will share it.

Re: JAMF Upgrade broke HIP report

JasonBTR — Wed, 01 Dec 2021 22:14:03 GMT

GlobalProtect 5.2.9 has been released and is detecteting JAMF again for use in HIP Checks