This script enables you stop and start Symantec Endpoint Protection on OS X
sudo curl https://gist.githubusercontent.com/steve-jansen/61a189b6ab961a517f68/raw/sep -o /usr/local/bin/sep
sudo chmod 755 /usr/local/bin/sep
sudo chown root:staff /usr/local/bin/sep
If your user account is not a member of the admin
group (i.e., not an OS X Administrator),
you need to add the following line to /etc/sudoers
using sudo visudo
tool:
myusername ALL= NOPASSWD: /usr/local/bin/sep
me:~$ sep stop
/usr/local/bin/sep: relaunching as sudo /usr/local/bin/sep
/usr/local/bin/sep: unloading Symantec Endpoint Protection daemon
/usr/local/bin/sep: unloading Symantec Endpoint Protection shared settings daemon
/usr/local/bin/sep: closing Symantec Endpoint Protection UI widget
me:~$ sudo /usr/local/bin/sep start
/usr/local/bin/sep: relaunching as sudo /usr/local/bin/sep
/usr/local/bin/sep: loading Symantec Endpoint Protection daemon
/usr/local/bin/sep: unloading Symantec Endpoint Protection shared settings daemon
/usr/local/bin/sep: launching Symantec Endpoint Protection UI widget
Stopping SEP on OS 10.15 (Catalina)
OS 10.15 has started using
systemextensionsctl
to manage extensions, and Symantec is one of the first companies to use this.Steps:
sep
tool as described above under Installation.systemextensionsctl
on OS 10.15, you need to disable System Integrity Protection. This requirement may be removed in future OS X releases, and it only needs to be done once.terminal
from the Utilities menu.csrutil disable
.sep stop
as an admin user.systemextensionsctl list
:systemextensionsctl uninstall 9PTGMPNXZ2 com.symantec.mes.systemextension
. (The team ID may be different for you. Please send feedback whether or not your installation of SEP has the sameteamID
.) Note that this command must be run by an admin user while logged into the OS X GUI. This is necessary because thesystemextensionsctl
command requests a password via dialog box.