I support several Windows Small Business Servers (2003 and 2008). After upgrading them to SEP 11 RU7 MP2, at least 3 of them are dedicating an entire CPU core to running SemSvc.exe. For example, on a quad-core server, this means 25% CPU is dedicated to SemSvc.exe - on a dual-core, 50%.
On all of these servers, entering the SEP Management Console results in a myriad of errors. Sometimes, I am able to login, other times I get a message "Failed to connect to the server". Restarting the Symantec Embedded Database and Symantec Endpoint Protection Management services seems to get things running again (for a while). Even when I am able to login to the management console, after a few minutes, the CPU spike occurs and I am eventually returned to the management console login screen where I am unable to login without getting the aforementioned error message. It appears that SEP clients are unable to connect to the SEP server with the SEP server in this state (although other network traffic appears to be OK) - SEP client updates don't get pushed out, etc.
I've read several online posts about Data Execution Prevention, but all of the posts I've seen refer to SEP 12.1. Is there something I should add to the DEP exclusions on these servers to get SEP 11.x running reliably again? Are there other things I should consider?
Any help is much appreciated - thanks in advance.