I've also hit this issue - Thankfully we don't actually make use of
Content Control which got me wondering why the hell it was showing as a
loaded module even though it's disabled! I did a reconfigure on the
client and it's now not showing the Conten...
Just a small update on my side as I'd been testing this script on some
new M1 based machines.Initially, I was a little confused as it
"appeared" to work according to Jamf policy logs in the web portal but I
wasn't see Chrome appear in the apps folder...