Posted on 09-22-2022 07:46 AM
I get many error messages on all computers under Management commands. We do not have nor did we ever have Jamf Protect. I searched just about everywhere in Configuration Profiles & Settings to no avail. We have a cloud server, not on prem. I thought I would reach out before opening a ticket. Any way to stop these messages from happening? As far as I know it isn't affecting anything, so is low priority.
Remove Jamf Protect PPPC and System Extension | Profile with identifier 'com.jamf.protect.daemon.pppc' not found. <MDMClientError:89> |
Solved! Go to Solution.
Posted on 02-13-2023 11:37 AM
Jamf Pro 10.43.1 now available
Jamf Pro 10.43.1 fixes the following product issue:
[PI110938] Jamf Pro no longer sends looping InstallProfile MDM commands to computers in the scope of automated deployments for Jamf Protect.
Posted on 09-22-2022 10:32 AM
Do you have anything listed/enabled under Settings -> Jamf Applications -> Jamf Protect?
Posted on 09-22-2022 10:42 AM
Nothing, Just a Begin Registration button.
Jamf Protect Registration
Begin registration
Posted on 09-22-2022 10:54 AM
Hmm, only other thing I found was this:
Posted on 09-22-2022 10:58 AM
I did look there, I'm not even offered that Jamf Protect option. Thanks!
Posted on 09-22-2022 10:59 AM
Sorry, actually it's there and unchecked... I was looking at Notifications settings..
Posted on 09-22-2022 11:16 AM
Sorry to say but I don't know what else could be causing it :(
09-22-2022 06:40 PM - edited 09-22-2022 06:41 PM
I have this exact same issue. i've seen this for the better part of 6 months as well. I 100% have never enabled this profile in Jamf settings, as I don't have the product, yet have failed profile removals across my environment. I've submitted a few tickets about this and yet to get a resolution. I'm working through a ticket currently with Jamf on this. The last recommendation I got was to enable the PPPC profile in Jamf settings and let it go to to all (or as many machines as possible), and then uncheck the profile in the Jamf settings. I'm letting it go out for ~2 weeks before unchecking.
I'm assuming this is actually some kind of product issue though. Why would Jamf try to remove a PPPC profile that was never enabled/pushed out.
Posted on 12-01-2022 01:10 PM
@dennisnardi Did you get to enable as Jamf said or resolve this annoying issue? Thanks in advance.
Posted on 12-01-2022 01:46 PM
I never got a resolution. I ended up just deploying the Jamf Protect PPPC profile via settings, and leaving it on. It doesn't hurt anything in my enviorment, and I didn't seem to be making any headroom with Jamf support.
Posted on 09-23-2022 05:42 AM
@dennisnardi Thank you for the information. I did have a ticket open over a year ago and didn't get any results either. Please let us know if enabling has any impact on those computers and your experience. Much appreciate your input!
Posted on 02-13-2023 07:38 AM
Chiming in to say we're seeing this exact same thing. We've never, tested, configured, or even looked at Jamf Protect, and many computers have the following failed command:
Remove Jamf Protect PPPC and System Extension | Profile with identifier 'com.jamf.protect.daemon.pppc' not found. <MDMClientError:89> |
Posted on 02-13-2023 11:37 AM
Jamf Pro 10.43.1 now available
Jamf Pro 10.43.1 fixes the following product issue:
[PI110938] Jamf Pro no longer sends looping InstallProfile MDM commands to computers in the scope of automated deployments for Jamf Protect.
Posted on 02-13-2023 12:07 PM
Interesting! Supposedly 10.43.1 was installed by 2/4 looking at the last cloud upgrade schedule. Last pushes I'm seeing were from 2/8.
Posted on 02-20-2023 12:00 PM
Haven't seen any errors since new version came out. Marking it as solution.
Posted on 06-01-2023 12:56 PM
Hi - we are on version 10.46.1-t1683911857 and am seeing the issue noted here. We do not and never had Jamf Protect. What has been the solution to prevent from this appearing on our macOS devices under the Failed commands?
Posted on 06-01-2023 01:02 PM
There are leftover failed messages on some machines, but it seems Jamf Pro 10.43.1 fixed our issue. Maybe open a ticket.
Posted on 06-01-2023 01:05 PM
Thanks. I'll open a Jamf case and reference this post to see if this was resolved in version 10.46.1