skip to content »

Updating vdefhub zip

Download the virus definition file from the Symantec FTP site: Check the currently applied pattern file version and date by double click the Symantec shield icon in the system tray.

Open C:\Program Files\Common Files\Symantec Shared\Virus Defs\temp\with Notepad At the bottom of this file is a section like so: Copy the value of Date Close Rename the ..\temp\ directory to the value of Date copied from the [verinfo] section Example: Rename: C:\Program Files\Common Files\Symantec Shared\Virus Defs\temp\ To: C:\Program Files\Common Files\Symantec Shared\Virus Defs140528.003\ Navigate to the directory: C:\Program Files\Common Files\Symantec Shared\Virus Defs\ Make backup copies of and Edit with Notepad Update the version number in the square brackets [] to be the value of Date (captured above from ..\temp\catalog.dat) Example From: Start “Symantec Settings Manger” first as it is a dependency for the other Symantec services Wait five (5) to ten (10) minutes after starting the services for the update to take effect. Check if the pattern file has updated by double clicking the Symantec Antivirus system tray application In this example the version has been updated to 28/05/2014 rev 3 There you have it. Symantec Version : Symantec Anti Virus 10 Corporate Edition Operating System : Windows XP Professional Culture : Australian (Just so the our US brothers and sisters are not confused by any dates in screenshots 🙂 ) Note: Windows XP is now out of support by Microsoft as of April 2014.This is not to say this process will not work on other operating systems or for other Symantec versions, just that this is the only system I have used this process on.We check to make sure that no one’s logged in before we run this (by checking for a registry key that only exists when a user’s logged in) because this removal process can take some serious time.I use (from Symantec’s nonav) and (from Sysinternals) to hopefully kill the various processes.If there is a version, I don’t install, (because I want to remove SAV first) otherwise I force run a silent MSI install. Final thoughts: We also had to push a reghack (prior to the install) to keep a daily quick-scan from grinding our machines to a halt.

Caveat here is it won’t install on a locked down workstation. (Note, this scan doesn’t show up in scheduled scans. Reghack follows: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Intel\LANDesk\Virus Protect6\Current Version\Custom Tasks] "Created User Quick Scan"=dword:00000001 "Copied Default Scan Options"=dword:00000001 I hope this info is helpful to somebody.

Now this scan can be anything but “Quick” so you will want to remove it. I didn’t discover this issue until we had deployed it out to most of our workstations so I made a ZENworks app to push the registry changes out to fix the problem. Using ZENworks for Desktops to push it out is pretty easy. We obviously use ZENworks for Desktops to push out SAV.

Even with these issues I really like having the real time spyware and adware protection, we’ve cleaned up a lot of workstations on our network since deploying SAV 10. We have been running the 10 installer right over top 8.0 or 9.0 clients. DAT file from the server you want the client to attach to, and drop the file in: C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Anti Virus Corporate Edition\7.5 for Win XP clients. We have had nothing but troubles with SAV until this version which appears to be leaps and bounds better.

Symantec has zero (yes, zero) articles regarding the deployment procedure of SAV CE (=for clients) 10.0 .

Maybe Cool Solutions will soon have more info about this issue than Symantec does.

I still need to figure out what reg keys it needs rights to. Well, because we have lots of different versions out there. We have spent many hours trying different ways and have found this to be the best for us.