[Vadikan]

Just read the first post on page seven from tbe beginning, and you'll find out how to get rid of the message.

Quote

what about using that CD few months later?

You'll need the recent virus defs anyway, correct?
You don't have to repack the whole package in order to update definitions. If 10 mb of space is not an issue, you can get an intelligent updater and open it in WinRar and change one line in the comment from

Setup=wrap32.exe

to

Setup=updater.exe /q

Or you can just unpack the SFX, extract updater.exe and run it with /q.

[pivot the blue]

Hi Guys,

I guess this topis is a bit old now, however i do hope someone can help me.
I created 7Zip Symantec corp. install. It works like a charm, however if I try to install it via RunonceEx It fails to install.

It's unzipping and when startx should have run msi, msg box with following text appears: StartX, No parameters spcified.

For a complete description of the command line parameters StartX accepts, click "Help"

Can you see the problem? The package works when it's run inside windows and RunonceEx does start it however there is some wierd problem that it does not wan't to install.

[jstone63]

Be careful using the suggestion of grabbing the VIRSCAN.ZIP file from the Symantec Intelligent Updaters and just renaming them the VDefHub.zip to place in the install packages. This can result in duplicate or missing definitions the next time the system runs LiveUpdate. The VDefHub file is also utilized to populate the BinHub folder. The BinHub is used to merge LiveUpdate packages to create the new set of definitions when using LiveUpdate. The method used when a parent server pushes definitions to a client is completely different and does not utilize the BinHub folder. When using LiveUpdate the BinHub set has to be from a known point in order for the merge to provide a correct set of definitions and in most cases the VIRSCAN.ZIP file you use will not be one of these known points specified by Symantec.

Instead what you should do is take a system that is always updating definitions using LiveUpdate (not getting them from a parent server), zip up the contents in the BinHub folder, and name that VDefHub.zip. This will mean that the system might not start out with the absolute latest definition file set but they will be within the last couple weeks and this way you don't end up with possibly non-functional definitions down the road.

[DonDamm]

@coucou, I have the same problem as I'm buildingan install for a friend who may not install it for a few weeks or even a couple of months. HIs dsl won't be setup until after install, so the "old virus def" box is sure to pop up.

I solved this in the following way. I use one cmd file called GetCurrentDate.cmd and first grab the current date and put it into a text file. Then it changes the system date during the installation to 1 May 2005 (a date with in 30 days of the build). After installation I run RestoreCurrentDate.cmd which take the date from the previously created file.

GetCurrentDate.cmd

cmdow @ /HID
@echo off

for /f "tokens=2 delims=/ " %%x in ('date /t') do for /f "tokens=3 delims=/ " %%y in ('date /t') do for /f "tokens=4 delims=/ " %%z in ('date /t') do echo %%x-%%y-%%z > "%tmp%\CurrentDate.txt"


date 05-01-2005

exit

RestoreCurrentDate.cmd

cmdow @ /HID
@echo off

date < "%tmp%\CurrentDate.txt"

exit

The "for" command is necessary to parse the date into the correct form which will be accepted by the date function. It took me a while to finally get this working, but now it works a charm and can be used for any program which has date sensitivity without disrupting the unattended installation! )

This post has been edited by DonDamm: 25 June 2005 - 12:05 PM

[sleepnmojo]

coucou, on Jun 21 2005, 05:05 AM, said:

How can i get ride from "Old Virus Definition File" (see enclosed image) message after a silent install
<{POST_SNAPBACK}>

I haven't tested this yet, but I noticed this key changed when clicking the box

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion]
"NoWarnPattern"=hex:23,04,12,00,00,00,00,00,

Then try deleting it, after install, to re-enable it so the user would know to update.

Edit: bad code tags

This post has been edited by sleepnmojo: 28 June 2005 - 04:09 PM

[sleepnmojo]

sorry, double post

This post has been edited by sleepnmojo: 26 June 2005 - 12:44 AM

[DonDamm]

Not certain, but that key looks like it pertains to the new built-in MS Security Center. I kdon't know if the mesagge box that pops up is from the security center or from Symantec! If it is MS, then that would work also.

In either case it requires running and cmd file before and after, which is a bit of a kluge and inelegant, even if it works. I would prefer to disable it in the msi file itself, but I don't have time to look into it right now because I have to finish my tax declaration by the end of the month!!!! I found a program, MakeMSI which is free and allows you to manipulate and look inside msi files. If I'm successful I'll post the results here. Until then, a quick change of the system date does the trick and after reboot it automatically goes out and gets the updates.

Addendum, I also found that if you set LiveUpdate to Express Mode you can copy over the ini file which is Setting.LiveUpdate to

%AllUsersProfile%\Application Data\Symantec\LiveUpdate\Settings.LiveUpdate

it will update without any necessary input from the user! :o)

[tbma]

DonDamm, on Jun 28 2005, 08:34 AM, said:

Not certain, but that key looks like it pertains to the new built-in MS Security Center. I kdon't know if the mesagge box that pops up is from the security center or from Symantec! If it is MS, then that would work also.
<{POST_SNAPBACK}>

Message pops up from the Symantec AV itself, when filedate of the virus definitions in the installation differs from current date for more than 30 days.
You can disable it either

• setting date back before installation, and returning it back after LiveUpdate.
  
  
• Or constantly updating definitions inside the installation.
  
  
• Or using a method I described here.

Fist do the test install.
Then run

reg query "HKLM\SOFTWARE\Intel\LANDesk\VirusProtect6\CurrentVersion" /v PatternFileDate

it will display something like

! REG.EXE VERSION 3.0

HKEY_LOCAL_MACHINE\SOFTWARE\Intel\LANDesk\VirusProtect6\CurrentVersion
    PatternFileDate     REG_BINARY      2305160000000000

Grab that long number (it's a filedate of the definitions installed) and insert it into your installation script.

Something like

reg add "HKLM\SOFTWARE\Intel\LANDesk\VirusProtect6\CurrentVersion" /v NoWarnPattern /t REG_BINARY /d 2305160000000000 /f

Running this before installation will supress the warning.

Quote

In either case it requires running and cmd file before and after, which is a bit of a kluge and inelegant, even if it works.

p.s. With this method there is no need to mess with the system dates, and remake your install every month (which looks very elegant to me;)). And since you will need to run cmd commands anyway if you want to get rid of the "AutoCreated Scan", - I see no problem adding some more.
Just hide the black ugly cmd windows (there is plenty of tools available) and it will look very elegant.

I am running all this from the 7zip SFX using StartX

;!@Install@!UTF-8!
RunProgram="StartX.exe /B /WAIT \"install.cmd\""
;!@InstallEnd@!

and cmd window never shows up.

This post has been edited by tbma: 28 June 2005 - 07:36 PM

[DonDamm]

Thank you for that, tbma!

By inelegant, I meant having to run a cmd file before and after to do something like cahnge a system date. That shouldn't be necessary and you've shown me how. I appreciate that! )

The AutoGenerated scan is a nuisance to me and you I'm sure, but I'm just as happy to leave it in there for clents, most of whom don't do anything until I show up again and find defs out of date and various spy/adware on the machine!

Thanks again.

[Thauzar]

I know i haven't read the whole thread, but I'm not ready yet to implement norton symantec 10 with all the troubles you guys seem to have. I'm just wondering, have symantec released a patch, or does anyone know when it should be more reliable and easy to setup? Should I expect updates during the summer? I'm waiting for it to be a sure bet before taking out SAV9 from my ua cd and replacing it with SAV10

[tbma]

The most significant new feature in 10.0 that differs from the 9.0 is "Tamper Protection", where AV will fight any programs (viruses) that are trying to damage it's registry or files.

After I've seen some viruses, that eat AV's from the inside and leave happy "pretend that I'm working" shell - any question for me about migrating to 10.0 disappeared.

[tarquel]

Sounds great (tamper protection)

....just wish they'd hurry up sending out the upgrades in Europe lol

Cheers,
N.

This post has been edited by it_ybd: 30 June 2005 - 08:42 PM

[JohnnyV]

A bit off topic but ... I've been testing out version 10 on a stand-alone PC. The updated defs downloaded to the 2005mmdd.vvv folders are supposed to automatically copy into the BinHub folder. However, after running the LiveUpdate the BinHub directory always seems to be a mixture of old files and new files. It only copies some of the new files.

Eventually, after awhile a message comes up saying the virus defs are missing and scanning is disabled. So I have to copy the files from the latest download folder and copy to the BinHub folder, reboot and then everything is ok again.

I have tried completely deleting the BinHub and 2005mmdd.vvv folders. I have tried downloading the virusdefs manually. And I have checked the attributes of the files to make sure they are not read-only.

Any Ideas?

[DonDamm]

Actually, don't wait. It is a better implementation with more features and controls. You can easily turn off what you don't want.

[Thauzar]

Ok, i'm convinced about upgrading, but again, I keep hearing so much good of nod32 but no real comparisons with symantec av, except user opinion saying i prefer one over the other because it's like that... I've always stick with symantec. Any of you can light me up even if it's a bit off topic? Im about to pack my ua cd and I want the best av, didnt try nod32 cause symantec av is so memory saving comparend to norton av...

This post has been edited by Thauzar: 03 July 2005 - 05:55 PM

[Jotnar]

SAV 10.0.1 is out now and should fix that nasty startup scan problem.

Cheers

[RyanVM]

Is there an MSP of 10.0.1 yet?

[shanren]

Where can we download SAV10?

[boooggy]

shanren, on Jul 6 2005, 05:25 AM, said:

Where can we download SAV10?
<{POST_SNAPBACK}>

sorry mate this is not allowed here cause it's considered warez....

[boooggy]

in 10.0.1 they change the way for installing lusetup. i mean is easier. just made an administrator install and then just remove lusetup from sav10 administrative folder\program files\Symantec AntiVirus with the new one and then that is it. pack it using winrar or 7zip and voila...

This post has been edited by boooggy: 10 July 2005 - 04:19 PM