When it comes to managing AV Dat updates, the fixlet for managing client AV tries to download a 13- 14 MB dat file whereas native mcafee epo only downloads the incremental updates. Any specific reason?
I know this post is old - but I have the same inquiry. Accept now the file size is over 21MB. I know from looking at McAfee’s website that this is most likely the superdat which includes the engine. Is there any way to change the payload to be just the .dat update and not a superdat? This task takes a toll on the WAN links and the on the local workstations when installing.
The definition update fixlets for McAfee VirusScan use the normal DAT packages available for public download from McAfee’s security updates site. They are not the superDAT packages that include the scan engine - which is still only ~1 MB larger than the normal DAT. McAfee ePO, is possibly managing incremental updates through its own infrastructure using micro-definitions that are not available for manual update.
Unfortunately, until McAfee releases more size-efficient definition packages (e.g. base and delta definition updates), the fixlets will implement the manual update process prescribed by McAfee using the DATs provided.
Ahh great - another EPO McAfee “gotcha”. So then, if I use McAfee AV without EPO - the client still has a different “smaller” mechanism for direct client to McAfee website updates? I run some plan McAfee agents - and they don’t appear to be download 20+MB dats.
We’re looking at dumping McAfee to go with the Big Fix offereing - because EPO has been a huge disappointment for us. We always have 1/3-1/2 of our systems out of compliance with dat updates (which is why we need to use BF to get updates out). And that is after McAfee has on numerous occasions verified that our installation is correct. It really comes down to their agents. EPO agents are just not written as well as Big Fix agents.
We already use the BF Antipest (and love it) - so why not the AV. Thanks for the info.