Manual Update Not Working - No Error

[jbcook]

We have Virusscan Enterprise 8 and EPO 3.5. The scheduled EPO task to update the clients works great. However, when you try to do a manual update from the client machine, it does not pull the new dats from the EPO server. It checks the repository, downloads, verifies, and extracts catalog.z, loads Catalog.xml, then "Update is finished." No error, but it does not update either. The local dats are older than the dats in the repository. I know the EPO repository updates because I can do that manually and it goes through all the steps. Any ideas? Thanks!

 

[billybarty]

How old is your engine on the client? Download the superdat to update both the engine and the dat and then try it again

 

[jbcook]

That's what I thought at first too, but it didn't help. The strange thing is, this has worked for a long time. The only thing that has changed is that we updated the VirusScan client on the EPO server. It was at 7, now its at version 8.

 

[Bendeguz]

I have the same problem with my epo server. My virusscan client version is 7.1 (I didn1t change it). The last thing what i change is that i install epo 3.5 patch 4 (version 3.5.0.649). But i don't know how i reroll the server to the state witout the patch?

 

[jbcook]

I called McAfee tech support, they had a corrupted dat and engine in their repository. After you download the corrupted one, it corrupts anything new that you pull in. So, to fix this, go to your EPO repository, using the EPO console, and delete anything that says SCMDat or SCMEngine. Then delete any other dat and engine. After that, do the Pull Now and you will be able to update your machines.

The fun part is, if you have replicated respositories, you will need to do the same thing at each one. Our system is up and running like a champ now.