1 of 1 people found this helpful
I will suggest you to use either SDAT file from the McAfee website which will have both DAT/engine or copy/burn Engine folder from the machine which is updated.
I had previously thought that you had to package SDAT files yourself, but have found KB66694 that led me to http://www.mcafee.com/apps/downloads/security-
updates/security-updates.aspx. From the SuperDAT tab, I downloaded SDAT6607.exe, and ran it on my test server.
Before SDAT6607.exe was run, the DAT version showed as 1111.0000 (creation date Feb 2, 2010), and the scan engine version showed as 5400.1158. Buffer overflow
and access protection DAT version was 567.
The install runs through smoothly, until it gets to the window 'please wait while the 64-bit anti-virus files are being copied into installation directory'. This
window gets to the stage 'Removing temporary files.' and an error message pops up in another window advising 'error: product already running latest engine files'.
Clicking OK on this error window closes both windows. On checking VSE, the DAT version now shows as 6607.0000, the engine version as 5400.1158 (may well be the
latest, I will need to confirm), and Buffer Overflow and Access Protection DAT Version shows as 567. A window in the background advised that SuperDAT2.5.0 had
After a browse around, I stumbled across KB59164 - 'How to Perform a forced installation of a SuperDAT file'. Out of curiosity (and the fact I never like getting
error messages...), I reverted the state of my test machine (to DAT1111.0000 and all), and followed this article through. Everything happened the same as before,
with the only exception being the lack of error message regarding the latest engine files. DAT = 6607.0000, engine version 5400.1158 and Buffer Overflow and
Access Protection DAT version 567. All looks ok. There is no explanation in this KB as to what situation you would need to run a forced install in, however,
which makes me curious...
Anyhoo, that appears to have done the trick, so I am happy for now. Still going to raise a query regarding the lack of explanation on the forced install, but will do that in another discussion. Similar issue seen in KB52858 for 8.5i, and that suggests running the install in silent mode with /s! Seems to imply that there isnt a problem and the error is meant be informational?
With regard to the suggestion on the Engine folder, given the fact that a manual copy would run into issues with Access Protection stopping the copy of files, my concerns over file locks (not sure what processes the SDAT exe stops in order copy files etc), and the fact that license files and config.dat files look to be in there - I am stepping away from that one for now just in case I run into unexpected issues. That and that fact that the operator would need to run an integrity check on every file copied across!