Endpoint Protection

Need some help,

I have just installed SEPM MR3 with 10 managed clients, some of them are displayed with the correct defitions, but about 3 machines are displayed with  wrong information. I go physically on that clients and they are with updated definitions. I have allready checked communication between clients and the server and all seems to be correct.

Does anybody have the same issue????

Regards,

NTC

I have this issue and have a long running call open with Symantec support.  We have tried a variety of potential solutions with no success.

The last thing suggested was to upgrade to MR4 MP1a but this has not worked.  I'm currently waiting for the next suggestion.

It'll be upgrade to MR$ MP2 =P

What happens if you run the cleanwipe utility and re-install ?

I had this problem too for several months now.  In the security status/ more details page was showing me a lot of definition failures but on the clients, nothing was wrong.  I ended up having to uninstall/reinstall all SEPM servers and creating a new embedded database and finally things look good.  This was a LOT of work just to get the database fixed.  Please note that I have one primary and two replicated servers and my servers are running MR4 MP1 and clients are MR4.

You can try deleting the clients from the SEPM and they will re-appear on the next heartbeat.  If that doesn't fix the problem, you should open a case with tech support.  You can reference my case (as an extreme measure): 312 084 585

Hi!!

Im getting crazy... I upgraded SEPM and clients to MR4 MP1a and still having the same problem. I open a case with techn support and dont have any answer that explains this behaviour. I have reinstall SEPM in different boxes whith  the same results. help help help!!! I tested chanching clients to another SEPM (Virtual Mahcine)  with a "new" slylink file and have the same symptom-- "client not reporting status".  I think that the source problem is the SEP client.. but dont know exactly what it is. Looking in SEPM System- Client Activity and everything seem to be correct:

My issue with this problem is now resolved.

The reason that my SEPM was not showing the correct definition dates was that the symantec endpoint protection service on the clients was set to start automatically by group policy.

SEP needs to be in full control of the service and having it controlled by group policy caused the reporting to fail.

Removing the group policy setting and a restart of the SEP service is all I needed to do.  Within a couple of hours, all clients were showing as being up to date.

Can you explain that a little more please?

What setting in the GPO controlled the startup type for the service?

Removing the GPO in SEP services made it work. It took me too much time to find out what was going on. But i still dont understand why this GPO is affecting SEP .. any idea???

Regards,

NTC