Using Composer I packaged it in the following directory: /Library/Application Support/Symantec/Uninstaller and changed the permissions so that only root and the admin group can read, write, and execute it. This way the removal script will always be included with the rest of the Symantec software. command file so we can include it in the. command file in the /Library/Application Support/Symantec/Uninstaller folder where it is inaccessible to my end users, but available to JAMF tools, and since the script is smart enough to know if it’s being run as sudo (and therefore requires no interaction), Casper Remote can simply call the. command file into the larger Symantec Endpoint Protection.mpkg installer. With this information in mind I set out to incorporate the. It can be automated to an extent when using Apple Remote Desktop, but one is still required to specify to run the command as ‘root.’ If the uninstall is part of a larger workflow or the company simply does not employ ARD for Mac management, this solution can become unwieldy at best.Ī quick look at Symantec’s removal script quickly reveals that it will not be easy or fast to rewrite, and cannot be simply imported into JAMF’s Casper Suite as it requires user interaction and will just continually fail when run through Remote (and would likely do so with other Mac management tools). However, this removal script was not built for unattended removals and still requires some user interaction to elevate privileges – fine for a small business, but not a global enterprise. Luckily Symantec HAS provided a nice convenient removal script to completely uninstall SEP 12.1 from Mac OS X. Symantec has always had a reputation for being difficult to completely remove from a computer once it’s been installed, on both PCs and Macs. How to uninstall SEP 12.1 using Symantec’s own script

Symantec uninstaller mac