Using Autoupgrade

[tekkid]

Hi,

I'm attempting to setup Autoupgrade to download and open the latest superdats every month across the netowork to each machine. Is there an expert out there that can help me by explaing what i need to do.. I went in and setup the file and pointed the download to a directory on my server where I have the superdat file. But it is saying that the file doesnt exist.. I used the browse button so i Know that its there.


Please help walk me through setting this up if ya can.


Thanks in advance!

kidd

 

[ChrisHirst]

You actually need to configure the Autoupdate to keep the dats up to date. The superdat.exe is not used in the general update procedure, what you need are the .INI files, .UPD files and the DATnnnn.zip. The best way to update is to configure a ftp server on your network and setup a DNS entry to point to it.

This thread38-208680 is for the batch file and ftp script I use for downloading the update files from NAI.

You can configure the client update to look to a UNC path for the files but you will have to give the AV Sync Mgr(4.5.x) or AV Task Mgr(4.0.x) a logon name and password with Domain Admin rights if you are running NT4.0 or Win2k otherwise the update will fail.

My updating system is to check the NAI site on a weekly basis (scheduled batch file) every Wednesday at 06:00 (GMT) (New DAT's are uploaded on Wed at NAI) and the Workstations update every day at startup, with servers updating daily at fixed times (we run Win2k and NT4 only). I also have subscribed to e-mail warnings and advisory info from Sophos, NAI, Trend, AVERT & SARC. Every morning I will check for dat updates at NAI and check overnight virus activity at Trend and if anything looks like it may need extra attention or alteration to blocking\scanning requirements gets attended to first (often before making a coffee). If any new dat's have been uploaded at NAI and the risk appears high enough I will start a manual download and and set in motion steps to update every client ASAP (120+). The measures I use may seem OTT but in the 4 years I have been maintaining the AV measures nothing has got past the initial point of entry.

Chris.

 

[AVChap]

You have to rename SDATxxxx.EXE to SETUP.EXE in order for this to work. AutoUpgrade looks for SETUP.EXE, not SDATxxxx.EXE. You can probably extend Chris' advise on the batch file to rename the file automatically.

Hope this helps.

AVChap

 

[FatesWebb]

just a note on all this..

Since you can use autoupdate to monitor the scan engine along with the dat files, I see really no reason to do this as it is harder. there is a checkbox for autoupdate to check for a newer scan engine.

However if you still wish to do it.

youll rename, (as avchap said) the sdat file to setup.exe and also you will need these files in that directory..

http://a64.g.akamai.net/7/64/2015/2...s/licensed/superdat/english/tools/autoupg.zip

unzip that and get the ones from the mcafee directory and also put them in the share..

3 files you will have

setup.exe
pkgdesc.ini
setup.iss

then just point the autoupgrade to this spot.

NOTE if you replace setup.exe with say a service pack (renamed as setup.exe) you will be able to deploy that also.

But like I said I would just use autoupdate to achieve the same results. js error; 67 on line; 36 of signature.class