Hi,

Yesterday was the first day of production here in the Philippines. After 2 days rest, most of the workstation are started to open early in the morning yesterday. Upon opening of their workstations, they will report directly to the SEPM to check and get the latest virus definition file. As per checking on the SEPM, it says that the latest on the manager is 03/22/2015. After lunch, I noticed that most of the workstations are still on 03/19/2015 virus definition. Their GUPs didn't get the latest from manager. Until the end of the day yesterday the clients are still stucked on 03/19/2015 virus definition.

Today, I checked the status of the SEPM servers. The latest from manager is 03/23/2015 but as per checking on C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Inetpub\content\{535CB6A4-441F-4e8a-A897-804CD859100E}\150319035, the latest definition is still 03/19/2015.

Appreciate your help. Thank you.

How many system having problem ?

Corrupt definitions prevent Endpoint Protection clients from receiving updates

Hi James,

We have 4 SEPMs here. 2 SEPM with 1 sql database on headoffice site and 2 SEPM with 1 sql database on branch site and scheduled replication of logs is set every 12:00mn. Currently, the headoffice site is updated and the definitions of 03/20/2015, 03/21/2015 and 03/22/2015 apperas on the definition folder.

As per my last checking, almost 6000 workstations are still on 03/19/2015 virus definition file. Even their GUPs are stucked on that definition. I also noticed that only the workstations with 64bit operating system gets the latest update. Thank you.

Hello,

I would request you to restart the SEPM machines and GUP client servers machines.

Secondly, Navigate through the following path to check most recent downloaded of liveupdate content.

SEPM >> Admin >> Servers >> Localsite >> Show liveupdate downloads 

Here you may find more info about release history - 

http://www.symantec.com/security_response/definitions.jsp?pid=sep1213

Hope that helps!!!

Enable syling debugging for an affected client, let it run through a couple heartbeats and post the log here for review if needed.