Endpoint Protection Small Business Edition

Hello. I've been doing some minior changes to our Symantec install in regards to the policy. I made one small change on the primary policy, disabling the Outlook detection, and it then promtped a few users to update Symantec....almost like they were receiving a version upgrade.

Some folks went through this but they are getting errors in Windows that "Symantec Endpoint Protection reports that it is turned off". I also see the attached screen show in the management console for things showing as NOT being installed. 

Has anyone seen this before? And is there anyway I can resolve it remotely without having to uninstall and re-instlal the clients manually??

can you run the symhelp logs and verify if the SEP module is working fine as expected.

Can you uninstall Windows defender.

What version is this for? Exact version..

12.1.2 RU2 Windows 7 (x64)

Out of curiosity can you try to run a repair on one affected client?

Also, I seem to remember a similar with this version...any chance you can try 12.1 RU4 (latest version)?

Looks like the repair is working on one of the clients so far. It makes it look like it's installing Symantec for the first time and is running the live update. I will confirm soon if this resolves it.

Is there any way I can run this repair remotely for the affected users? Or will they have to do that manually. 

Yea, I've seen running a repair as a "workaround", not ideal but it seems to work.

I believe you can do it with a powershell script. No way from the SEPM though.

I see, any thoughts as to why it would break Symantec like that??

Ok great no problem. Also, would you happen to know if there's a way I can run a repair from a CMD line? That way I can at least create a batch file and speed the process along a bit. 

I'm not really sure if it's SEP or WIndows. I saw a fix before in a previous version and it was fixed in a new release of SEP. Support could probably shed some light on it.

To my knowledge, not from a cmd line. But I've seen it done with either powershell or wscript. I'll see if I can dig up and old forum post about it.

Ok great keep me posted. Also, my user ran the repair but they're seeing this now. Thoughts?

What happens after a reboot?

This error came up after the reboot. 

After contacting Symantec support they were no help and suggested I run cleanwipe and re-install Symantec. All requiring manual work.