mega_stream

Quick question..(Is it Jack thats the resident McAffe expert)

We use Sophos a/v at the mo' all works well with the central install pusing ide updates out when a PC is connected to the LAN.
Problem is when laptop users dial in if theres been a monthly update on the central server they have a 8-9mb file to download to update their install not good on a 56k link

I know I can get them to select don't update at this time but I don't want to do that.

How does McAffe handle this? Whats the average size of a dat file? and how often are the actual engines released?

Any help would be, well, helpful

Cheers
John

IanW

Jacks the man you want!

We use NAI internally, we get new Dats every week, and the update including the engine is only about 4Mb ish! (from the last time i looked)

TiggerWRX

We use McAfee. Its pushed by epolicy orchestrator agent (epo).

Even on dial up, new dat files are pushed down the wire. Average dat sizes are 1.5M. If a new engine is being sent, then a sdat is sent which is about 4.5M.

mega_stream

Yup I was going to look at the epo, seems a no brainer though if its a large file that needs to be pushed out on update...I can handle small files going out file ide or signature files, users are gonna moan like maryhell if they have to wait for a multi-meg file to come down...

Hows everyone else handle a/v on remote users dialing in?

David_Wallis

Actually a dat update is about 45k as it is incremental, it only uses the bigger zip if It cant update with the incrementals or if it needs an engine update...

David

blp

I agree with David. I use McAfee, and the update files are tiny, espeically if you do them once a week...like good boys and girls do.