dating by site chile - Symantec endpoint protection update policy not updating

I have Symantec Endpoint Protection Manager installed on a Windows Server 2008 R2 machine and I've attempted to push the SEP client out to Windows 7 workstations on my domain.

Remote installation of the client is successful, but the clients are, from that moment forward, unable to connect to the SEP Management software.

Recently I had a client using System Center Endpoint Protection (SCEP) who was having issues with Definitions not being updated across their enterprise.

symantec endpoint protection update policy not updating-21

It appears to be just the Anti Virus/etc definitions that are not being updated - and it "seems" like they are not being put in the right place by Live Update or something else. Hi ascendinternet, If you click "Download Live Update Content" above "Show Live Update Satatus" does anything happen? Do any of the clients have up to date deffinitions?

If you click start then run and type on one of the clients will the client download the definitions?

We did some checking on custom client policies and they had policies that where deployed to these servers with the software updates selection not checked.

The client has changed that customer client policies for their servers and now the servers are all getting definitions.

Updating the antimalware definitions in FEP/SCEP fails with error 0x80248014.

Clicking the Update button in the System Center 2012 Endpoint Protection client user interface fails with error 0x8024402c.Error 0x8024402c happens when the Windows update client can’t connect and download the proper definitions. Our client decided to change their Config Mgr Antimalware settings to disable the user from manually updating the definitions.In this clients case, they have a policy set that doesn’t allow the Windows Update clients to go to Microsoft Updates. Which brings us to the third issue we had to resolve.We did the basic trouble shooting, viewing logs, checking the distribution point health, the health of the distributed package, client health, etc.What we found was that a majority of their servers had their software update component disabled.To resolve this issue manually change this setting.

Tags: , ,