It appears composer is no longer able to package the CB_install.pkg and unattended .sh file. Our previous install involved packaging the .sh file and pkg from a temp location and dumping that on to a client machine then running a script file that pointed to the .sh and pkg location with company code and policy name.
Does anyone have and updated method for this or a different way to deliver CB defense? I have an open ticket with support but so far they're stumped.
Jamf wants to hear your feedback around Peripherals and Jamf Connect settings configuration