We pushed a flavor of this with group policy as a startup script with a reboot, and it did most of our work. So my question is: How can I force the SEPM to send down a policy that disables (unchecks) the Tamper Protect box? I know that I can switch to server control mode for a couple hours and the setting will be sent down to all online clients.but that seems like a kludgy way to do things and only gets the online clients. If you have tamper protection, or password protected uninstall, you need to use SEPM to remove those options FIRST. The problem is this, we run in 'Mixed Mode' and every time a new client comes out (MP2 in this case) and is pushed down from our SEPM, Tamper Protect gets re-enabled or if it's a new install, tamper protect is enable by default. It protects the clients services and registry keys from being.

Tamper Protect seems to conflict with our two factor authentication software and unfortunately.upgrading the two factor software is not an option. Tamper Protection is one of the most important features of Symantec Endpoint Protection. In the section Boot options, enable Safe boot. Boot into safe mode Click on Windows Start and search for msconfig.

We have an issue with SEP (and SAV for that matter) assisting in a BSOD with a stop 50 error if 'Tamper Protect' is enabled when a machine is rebooted. Find out how to disable Symantec Endpoint Protection through the next steps.

Tamper protection symantec