Symantec endpoint protection manager 12 1 not updating
So, the only solution was to reinstall version 10, which is once again working perfectly.
We may try again when our server is upgraded in a few months ...
Does that mean they ae managed rather than unmanaged?
I then reinstalled, following the Symantec "Best Practice" for SBS 2003 Servers.
The Clients appear in the client list and I can send instructions such as "Disable Network Threat Protection" to the client from the server and it works.
The issue has been documented on both Windows 2003 and Windows 2008 servers.
When you launch the SEPM console locally on the server, you are prompted to enter administrator credentials.
This is a known issue, and is documented on the Symantec site as first occurring in deployments of version 12.1 of the SEPM application.
The most recent report was posted in January of 2014.
As far as I understand it, the folder C:\Program Files\Symantec\Endpoint Protection Manager\Inetpub\content is where clients get updates from ... Live Update put's it's stuff in C:\Documents and Settings\All Users\Application Data\Symantec\Live Update\D After 2 days of trying and 2.5 hours on the phone to Symantec support, it was not possible to get Endpoint Protection working on our server (we only have one server).
It worked perfectly on my laptop but that's not a suitable location for it.
) are looking for them somewhere else, hence there never being any new updates!?
The reason I wanted you to try live update on the client computer is so we can identify if the client is being managed or not. Since you can send instructions to the clients, obviously the clients are being managed.
Run the following command at the prompt: dbsrv11 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5After the log file is regenerated, force-start the SEMP service using the tool.Tags: Adult Dating, affair dating, sex dating