Hdiutil attach -nobrowse /tmp/wsamacsme.dmgĬp -R '/Volumes/Webroot SecureAnywhere/Webroot SecureAnywhere.app' /Applications/ĭiskutil unmount '/Volumes/Webroot SecureAnywhere'

Sudo rm -rf '/Applications/Webroot SecureAnywhere.app' Sudo rm -rf /System/Library/Extensions/SecureAnywhere.kext Rm -rf '/Applications/Webroot SecureAnywhere.app' Rm -rf /System/Library/Extensions/SecureAnywhere.kext Sudo launchctl unload /Library/LaunchDaemons/.plist Launchctl unload /Library/LaunchDaemons/.plist I want to cover all of my bases, thus my script tries a few things in an effort to remove the old and install the new. Actually, it might be more complicated than that! My users are not local administrators, so I am not entirely sure if their WebRoot is running as them or as sudo. My script is designed to blow out the entire config and start fresh using a silent install. My deployments have already been using WebRoot and my goal is not just to install on new systems, I want to fix all the old systems that are not reporting. All I do is write a short BASH script to download and install Webroot. I use Ansible and SaltStack to run automation on macOS devices, so this is easy.

Knowing that MDM KEXT features are relatively new, this is a good time to add exceptions for common used tools like TeamViewer, ScreenConnect, etc.Īutomate WebRoot silent installation using BASH… Once I have values, I build and ship the Kernel Extension Policy Control using my Mobile Device Management solution. Why is this necessary? Apple’s macOS checks the authenticity of each application by verifying a digital signature.ĭistribute Kernel Policy Extension Control… Although I can open the plist or check the signature my favorite option is the community assembled spreadsheet. Here is how this works in practice: Collect KEXT info…įirst, I collect the “ Bundle ID” and “ Team ID” for WebRoot. The bridge to allowing this is the Kernel Extension Policy Control which allows remote administrators – through systems such as Mobile Device Management (MDM) – to grant permission to an application and deploy it.

Meanwhile, macOS does everything possible to limit their power in an effort to keep users safe. The reason they are complicated is quite simple: these applications expect lots of access to do their jobs. This spells trouble for applications that need a lot of access, such as antivirus. Apple’s macOS Sierra introduced new security features that simplify apps from the App Store, but complicate everything else. The Apple macOS security and privacy features make remote management tough.

Install webroot on mac