Capture Client PPPC, System Extensions, & Content Filter via MDM
russell_feagley
Newbie ✭
Hey All,
I know as part of the Capture Client install the end user is prompted to approve PPPC permissions, System Extensions, and the Web Content Filter. I'm really hoping to pre-approve these via MDM, however I cannot find any documentation on the system extension that needs approval, or the app for the web content filter. Once I can deploy these via MDM, then I can silently deploy Capture Client without the end user having to approve any prompts. Our environment is full of Mac standard users.
Thank you,
Russell
Category: Capture Security Center
Tagged:
0
Answers
@russell_feagley - have you seen this KB article? Please let us know if you see any missing info:
Suroop:
There is (still) missing/incorrect information. Going back to a separate thread "Capture Client 3.6 - Release Status and Availability"
you said back on May 25 that the KB article that you cited above would be fixed, but it does not seem to be fixed.
Is there a corrected KB article?
@Syzygy - sorry about that. Not sure why that KB hasnt been updated yet. We'll get that fixed that.
But while we do that - what info are you looking for? We'll try to grab that as well from Engg to add to this KB.
@SuroopMC When capture client is installed it prompts you to approve system extensions and a web content filter.
System Extension Information Needed:
Web Content Filter Requirements:
Pre-deploying these along with the Sentinel PPPC prompts will stop the need of the user having to manually approve the PPPC, System Extension, and Web Content Filter settings.
Russell
@Syzygy
So I think I've come a little closer to completely getting this working. Here are some of the things you will need to do for your MDM configs:
Hopefully this helps you. I'm still getting one prompt, I'm testing out Kernel extensions right now to see if I can get this completely silent
Well I found out that the last prompt that I'm still getting is due to a legacy system extension that Capture Client still uses, and the last prompt is inevitable currently, until Sonicwall updates their software. I haven't pinpoint what kernel extension it is, but I'm assuming it's the CFDriver.kext file that I found. Sending a kext config doesn't fix this. If you're working with non-admin users, you can enforce the legacy system extension to install by: