Full Version: SAV 9 - Symantec AntiVirus 9.0
I can confirm, It doesn't work.
here's how i installed sav 9 with RunOnceEx.cmd
enjoy. (i know i am)
QUOTE
set SAVSERVER=MySAVServer
REG ADD %KEY%\070 /VE /D "Symantec AntiVirus Corp 9.0" /f
REG ADD %KEY%\070 /V 1 /D "\"%CDROM%\software\sav\Symantec AntiVirus.msi\" ADDLOCAL=SAVMain,SAVUI,EMailTools,OutlookSnapin,Pop3Smtp,QClient NETWORKTYPE=1 SERVERNAME=%SAVSERVER% ENABLEAUTOPROTECT=1 RUNLIVEUPDATE=0 REBOOT=ReallySuppress /qn" /f
REG ADD %KEY%\070 /VE /D "Symantec AntiVirus Corp 9.0" /f
REG ADD %KEY%\070 /V 1 /D "\"%CDROM%\software\sav\Symantec AntiVirus.msi\" ADDLOCAL=SAVMain,SAVUI,EMailTools,OutlookSnapin,Pop3Smtp,QClient NETWORKTYPE=1 SERVERNAME=%SAVSERVER% ENABLEAUTOPROTECT=1 RUNLIVEUPDATE=0 REBOOT=ReallySuppress /qn" /f
enjoy. (i know i am)
QUOTE (ATTO @ Aug 24 2004, 09:34 AM)
Who ask you... Removed by admin
7.a You are expected to be mature when discussing in threads. Racism, pornography, threatening, profanity, or excessive vulgarity is not tolerated. You will be promptly banned. No Exceptions.
Thread cleaned up. Please stay on topic.
Thanks
thanks everyone for all the great info... 
I've got my unattended install package pretty much ready to go... a quick question, though..
does anyone know how to force the install to have certain options changed in SAV? for example:
- default to scheduling Live Update to run at a different time than Fridays at 8pm (when users have their machines off)
- default to scanning for "expanded threats" in every scan
- set file system auto-protect to automatically be on, and to turn back on 10 minutes after the end user turns it off (like you can do in a Managed environment)
it'd be great to know how to set these options, since having to touch every machine to set options is almost worse than having to install by hand!
cheers!
-joe
I've got my unattended install package pretty much ready to go... a quick question, though..does anyone know how to force the install to have certain options changed in SAV? for example:
- default to scheduling Live Update to run at a different time than Fridays at 8pm (when users have their machines off)
- default to scanning for "expanded threats" in every scan
- set file system auto-protect to automatically be on, and to turn back on 10 minutes after the end user turns it off (like you can do in a Managed environment)
it'd be great to know how to set these options, since having to touch every machine to set options is almost worse than having to install by hand!
cheers!
-joe
@Cee-Kay, do you have a link to the LuMMInst.exe file. the link is not working anymore. I was going to test it out.
QUOTE (sleepnmojo @ Aug 24 2004, 07:09 PM)
@Cee-Kay, do you have a link to the LuMMInst.exe file. the link is not working anymore. I was going to test it out.
Unfortunately people reported problems with that method so I removed the file from my FTP server. I'm currently working on a alternative solution.
Thanks for the info in this thread, it was greatly informative.
I've used the MSI and command line parameters to successfully include this in an unattended install, however don't know how to lock it down.
Our 8.1 was previously rolled out as a managed tool either by manually running a package created in the symantec packager or through the nt client install utility through the network. When they came down, these installs were locked down so that users couldn't uninstall, change settings, or manually kick off a liveupdate.
This is the same case with 9.0 if I use the nt client install tool in the symantec system center, but if I use an MSI file with the following parameters, it is completely open for tampering:
I'm under the impression that the symantec packager is no longer working with 9.0 since it's in MSI format ... so what are my options here?
Thanks!
I've used the MSI and command line parameters to successfully include this in an unattended install, however don't know how to lock it down.
Our 8.1 was previously rolled out as a managed tool either by manually running a package created in the symantec packager or through the nt client install utility through the network. When they came down, these installs were locked down so that users couldn't uninstall, change settings, or manually kick off a liveupdate.
This is the same case with 9.0 if I use the nt client install tool in the symantec system center, but if I use an MSI file with the following parameters, it is completely open for tampering:
CODE
ECHO.
ECHO Installing Norton Antivirus Corporate 9.0
NAV90\NAV90.msi /QN NETWORKTYPE=1 SERVERNAME=KNXW2K3-AD01
ECHO Installing Norton Antivirus Corporate 9.0
NAV90\NAV90.msi /QN NETWORKTYPE=1 SERVERNAME=KNXW2K3-AD01
I'm under the impression that the symantec packager is no longer working with 9.0 since it's in MSI format ... so what are my options here?
Thanks!
nevermind, it turns out the policy is inherited from the server at a later date. I came in this morning and the PC's that had it installed were locked down.
Hello folks,
I am sorry that I am to stupid to understand this... but I am having problems rolling up the SAV 9.0 installation with the patch 2. I have a copy of the installation cd in a folder on my desktop called "C:\Documents and Settings\jfmccord\Desktop\SAV Corporate Edition 9.0". I ran the command that was specified above and created the new installaiton folder called "C:\Documents and Settings\jfmccord\Desktop\New Install." I downloaded the virus definition update and have it copied over (I think) into the right folder which was "C:\Documents and Settings\jfmccord\Desktop\New Install\program files\Symantec AntiVirus\Virus Defs". I think I have it this far...
the problem I am having is the next step of actually combining the new installation of SAV 9.0 with patch two. Can anybody help a poor soul from WV?
Thanks,
John
I am sorry that I am to stupid to understand this... but I am having problems rolling up the SAV 9.0 installation with the patch 2. I have a copy of the installation cd in a folder on my desktop called "C:\Documents and Settings\jfmccord\Desktop\SAV Corporate Edition 9.0". I ran the command that was specified above and created the new installaiton folder called "C:\Documents and Settings\jfmccord\Desktop\New Install." I downloaded the virus definition update and have it copied over (I think) into the right folder which was "C:\Documents and Settings\jfmccord\Desktop\New Install\program files\Symantec AntiVirus\Virus Defs". I think I have it this far...
the problem I am having is the next step of actually combining the new installation of SAV 9.0 with patch two. Can anybody help a poor soul from WV?Thanks,
John
Maybe I should clarify a little I am trying to create a new installation CD.
QUOTE
I am sorry that I am to stupid to understand this...
Don't be silly, were all here to help one another out.
In order for us to make the appropiate suggestions, can I confirm what stages you have already completed:
- You copied the contents of the CD to "C:\Documents and ettings\jfmccord\Desktop\SAV Corporate Edition 9.0"
- From there you created an admin install point using "Setup.exe /A".
- In the install point itself, you extracted the newer Virus Definitions files to "C:\Documents and Settings\jfmccord\Desktop\New Install\program files\Symantec AntiVirus\Virus Defs" replacing the existing files and are stuck at the part of integrating the patch?
Now all you have left to do is navigate to the root of your install point and run the command kindly provided by prathapml which is as follows:
CODE
msiexec /p "SAVCE_9.0.0.1400_AllWin_EN .msp" /a "Symantec AntiVirus.msi" /QB
Braking the command down, the first filename is the name of the patch file, with an .MSP extension. The second of course is the filename of the MSI installer mentioned earlier.
Note: Although there is a space between EN and .msp the above command does work provided the correct filenames are mentioned. If you have not renamed any of the above files the command will work fine, if not simply replace the filename with the ones that you are using.
I hope this solves your problem.
I at least got an error message now so something is going better than before. Thank you so much for your time. I really appreciate it. I have attached a word document with a screen shot of the error message that I receive. You can see behind it what I actually typed so that should further help with the dianostics. Thanks again.
John
John
Attached is a screen shot of the "New Install" folder.
jmccord my suggestion would be rename both files to something more simple and try again. Windows Installer is very picky sometimes.
QUOTE
I at least got an error message now so something is going better than before.
By the looks of it, you are receiving that error message because the exact filename of the patch file hasn't been specified.
Upon looking at the extracted patch file, I have discovered an extra space at the end of the file name (just before the .MSP extension). Therefore, you can either rename the file and remove the extra space (meaning the command you entered on the Screenshot would work) alternatively enter the command, which I put in my previous post.
You should then find the patch works ok.
Good job Cee-Kay. I was looking to see what was wrong. Thats why I suggested renaming because that usually fixes things instead finding the error with extra space or something. But you got a good eye. I'm blind. Hehe. Later.
@Cee-Kay
Any further luck on slip streaming of LU 2.5 into the SAVCE 9.x install?
Felix
Any further luck on slip streaming of LU 2.5 into the SAVCE 9.x install?
Felix
Thank you all so very much for all of your time. I do appreciate it. Cee-Kay you were right about the space. That was the reason it was choking on me. I guess I need to just slow down and pay more attention. 
So all I have to do now is copy the contents of "New Install" onto a CD and run the install from it and everything should be up to date and patched (I hope).
If you ever have a question for me... I will try my best to help you out!
Thanks again,
John
So all I have to do now is copy the contents of "New Install" onto a CD and run the install from it and everything should be up to date and patched (I hope).
If you ever have a question for me... I will try my best to help you out!
Thanks again,
John
I'm currently working on a modified MSI installer, which will allow the newer LiveUpdate files (2.5) to be used instead of the older LU files included with the actual product.
Upon completion of the installer, I will test it as much as possibile before releasing it -- in the meantime if anyone wouldn't mind testing my installer once I release it, that would be a great help, just incase I've missed anything out (e.g. a customised install, installation on a server, etc).
EDIT: I have now finished work on my modified MSI installer and I am currently in the process of creating a guide for integrating LiveUpdate v2.5 into the SAV V9.0 install source.
Updates will follow...
Upon completion of the installer, I will test it as much as possibile before releasing it -- in the meantime if anyone wouldn't mind testing my installer once I release it, that would be a great help, just incase I've missed anything out (e.g. a customised install, installation on a server, etc).
EDIT: I have now finished work on my modified MSI installer and I am currently in the process of creating a guide for integrating LiveUpdate v2.5 into the SAV V9.0 install source.
Updates will follow...
Cee-Kay I was working on the same thing but the last couple days I haven't been able to work on it. I was going to start working on it again but you said you were working on an modified installer. I wouldn't mind testing it though. Let me know and try to help ya out. Later.
QUOTE (drthawhizkid @ Aug 27 2004, 05:14 PM)
Cee-Kay I was working on the same thing but the last couple days I haven't been able to work on it. I was going to start working on it again but you said you were working on an modified installer. I wouldn't mind testing it though. Let me know and try to help ya out. Later.
Thank you for the offer it's much appreciated, as soon as I make the download availabile, everyone is certainly welcome to test the heck out of it.
Obviously, I hope the installer to be as error-free and possibile, but having as many testers as possibile would certainly help speed up the process of ironing out any bugs that may still exist.
No prob Cee-Kay. I want a solution for this as bad as everyone. I like things integrated as much as possible at least with software. I don't like having lots of thing jumbled around. Anyway good luck with the installer. By the way what program are using to modify the installer?
hmm sounds cool this!
BUT: i got a little prob, i miss a file in my "installer" called: Setup.exe
i gotted a zip with the following files in it:
"Symantec AntiVirus.msi"
further the rest of the folders are called:
Common
CommonAppData
External
Program files
Redist
System32
Windows
it works great, installing is no problem with it, but how can i slipstream this?
for updating the virus def i'll probably need to be in this folder:
"program files\Symantec AntiVirus\Virus Defs"
but is there anything else that's usefull? i already found the liveupdate folder two so maby an update there? i don't know
anyone?
BUT: i got a little prob, i miss a file in my "installer" called: Setup.exe
i gotted a zip with the following files in it:
"Symantec AntiVirus.msi"
further the rest of the folders are called:
Common
CommonAppData
External
Program files
Redist
System32
Windows
it works great, installing is no problem with it, but how can i slipstream this?
for updating the virus def i'll probably need to be in this folder:
"program files\Symantec AntiVirus\Virus Defs"
but is there anything else that's usefull? i already found the liveupdate folder two so maby an update there? i don't know
anyone?
What do you want to know how to slipstream stevenp?
CODE
LU 2.0 (old) -------------- LU 2.5 (new)
LuComServer.exe ----------- LuComServer_2_5.EXE
LuComServerPs.dll --------- LuComServerPS_2_5.DLL
NetDetectController.dll --- NetDetectController_2_5.DLL
ProductRegCOM.dll --------- ProductRegCom_2_5.DLL
ProductRegCOMPs.dll ------- ProductRegComPS_2_5.DLL
X ------------------------- SESA.Settings.LiveUpdate
X ------------------------- unrar.dll
X ------------------------- winluproviderinst.jar
X ------------------------- luinventoryinst.jar
luproviderinst.jar -------- X
LuComServer.exe ----------- LuComServer_2_5.EXE
LuComServerPs.dll --------- LuComServerPS_2_5.DLL
NetDetectController.dll --- NetDetectController_2_5.DLL
ProductRegCOM.dll --------- ProductRegCom_2_5.DLL
ProductRegCOMPs.dll ------- ProductRegComPS_2_5.DLL
X ------------------------- SESA.Settings.LiveUpdate
X ------------------------- unrar.dll
X ------------------------- winluproviderinst.jar
X ------------------------- luinventoryinst.jar
luproviderinst.jar -------- X
This is why the new extracted LU does not work! The MSI doesn't know anything about files in the right column.
X means not found.
OK good, so what's the solution?
the files not found is the problem because you could always change the name of the first five files you listed. It tried it and it worked up until it didn't know about the files you marked x.
hmmm...
Inside SAV.msi, you rename the first 5 files as they appear in the right column; as drthawhizkid said.
You add the next 4 files on the right to SAV.msi, and delete the last file on the left from it; as mazin says.
Or, easier yet for the sake of sharing, you create a special MSP to patch the AIP with those changes. mazin says, too! : thumbup
That's it! I think this is what Cee-Kay is going to do. You see, Cee-Kay; I'm reading your mind!
Inside SAV.msi, you rename the first 5 files as they appear in the right column; as drthawhizkid said.
You add the next 4 files on the right to SAV.msi, and delete the last file on the left from it; as mazin says.
Or, easier yet for the sake of sharing, you create a special MSP to patch the AIP with those changes. mazin says, too! : thumbup
That's it! I think this is what Cee-Kay is going to do. You see, Cee-Kay; I'm reading your mind!
QUOTE (mazin @ Aug 29 2004, 01:25 AM)
That's it! I think this is what Cee-Kay is going to do. You see, Cee-Kay; I'm reading your mind!
@Mazin Close enough mate, however I have modifyied the MSI installer so no renaming is required! Just exract and go.
I've not had enough time to finish writing a guide to this yet, but using my new installer should be pretty straightforward.
Give me 10 mins and ill upload it to my web space and then I'll concentrate on finishing my guide.
Ok, I've uploaded the file, which is ready to be downloaded. Please be gentle in reporting bugs.
You can download the installer from here.
Simply double click the SFX archive to extract the MSI installer to the current directory... well you know the rest.
NOTE: This installer is intended for use with the updated client files, version 9.0.0.1400 only, otherwise problems will occur when you try and install using an unpatched version of SAV. (See prathapml's post on the first page for patching instructions).
Installer Change log:
1.0a : Initial Release
1.0b : Changed to correct bug reported by drthawhizkid, please download the latest version.
Bug Reports:
"There was a problem trying to register with Live Update. Live Update will not be available for this product" [Fixed].
Updates:
I been having some problems extracting the lastest definitions from the x86 updates, as far as I can tell this is only a problem on Windows XP SP2. If the x86 version doesn't work for you either, download the i32 version from here.
Extracting the contents from the i32 version, to replace the older definitions included with the Client works fine, without LiveUpdate downloading them again.
You can download the installer from here.
Simply double click the SFX archive to extract the MSI installer to the current directory... well you know the rest.
NOTE: This installer is intended for use with the updated client files, version 9.0.0.1400 only, otherwise problems will occur when you try and install using an unpatched version of SAV. (See prathapml's post on the first page for patching instructions).
Installer Change log:
1.0a : Initial Release
1.0b : Changed to correct bug reported by drthawhizkid, please download the latest version.
Bug Reports:
"There was a problem trying to register with Live Update. Live Update will not be available for this product" [Fixed].
Updates:
I been having some problems extracting the lastest definitions from the x86 updates, as far as I can tell this is only a problem on Windows XP SP2. If the x86 version doesn't work for you either, download the i32 version from here.
Extracting the contents from the i32 version, to replace the older definitions included with the Client works fine, without LiveUpdate downloading them again.
@C.K.
I'll check it and report back.
I'll check it and report back.
All right Cee-Kay I test it too.
Who invented the idea of extracting virus definitions? 
If I only can catch him/her!!!
Unfortunately, I couldn't test Cee-Kay's file due to that problem.
Neither x86 nor i32 works!
If I only can catch him/her!!!Unfortunately, I couldn't test Cee-Kay's file due to that problem.
Neither x86 nor i32 works!
Fortunately, I can get the i32 version to work
However, even when I try to double-click on the x86 version a very quick dialogue box comes up (I've got a screenshot somewhere) which says Windows cannot run 16-bit apps. Now I know for certain that I've never had this problem before, so I'm pretty confident that it's SP2 that's at fault.
However, even when I try to double-click on the x86 version a very quick dialogue box comes up (I've got a screenshot somewhere) which says Windows cannot run 16-bit apps. Now I know for certain that I've never had this problem before, so I'm pretty confident that it's SP2 that's at fault.
The i32 version worked for me. I extracted it to a seperate directory and moved the files to the virusdefs and it worked fine for me. On a bad note Cee-Kay I tried a silent installation of SAV (using /qb) and I got this error (See Screenshot)
@Cee-Kay
@drthawhizkid
Would you please give me a direct link to i32 you've downloaded?
Thanks.
@drthawhizkid
Would you please give me a direct link to i32 you've downloaded?
Thanks.
QUOTE
On a bad note Cee-Kay I tried a silent installation of SAV (using /qb) and I got this error (See Screenshot)
Sorry about that drthawhizkid, I hoped bugs wouldn't appear so quickly, 
nevertheless I'll start looking at what's causing this problem.UPDATE: Hopefully, I've fixed this bug, please download the latest version at the top of this page. Once this bug has been reported as solved, I will update the change log accordingly.
QUOTE
Would you please give me a direct link to i32 you've downloaded?
Sure thing, you can download the i32 version here
QUOTE (Cee-Kay @ Aug 29 2004, 08:04 PM)
Sure thing, you can download the i32 version here
Thanks. I haven't seen your updated post above, too.
I'll try again and see.
QUOTE (mazin @ Aug 29 2004, 09:59 PM)
Who invented the idea of extracting virus definitions? If I only can catch him/her!!!
LOL, symantec themselves. If I only can catch him/her!!!I saw that info and me and and a few others have been spreading that idea since many months.
The point is that it (when extracted) works perfectly with NAV 200x versions. But the SAV versions have a hiccup. Hoping that all you guys get that process working, and please give details of what you did to solve it.
@mazin I hope you get the latest virus defs to work for ya. @cee-kay I'm testing SAV now to see if it works. I will report any errors if I find any. Later.
@cee-kay Bad news I'm still getting the error I reported earlier when trying to install SAV. I tried both my Main OS (on my laptop) and a Virtual OS (VMWare).
Bad news about extracting V.Defs will come soon!
hi,
just downloaded the actual i32.exe and ran this:
copied it over to the admin install point and all runs fine...
hope this helps a bit
cya
Killer Bee
BTW: 1400-patch was applied and i ran a quiet LU v2.5-setup after it and no updates were available...
just downloaded the actual i32.exe and ran this:
CODE
20040828-003-i32.exe /Extract .\viri
copied it over to the admin install point and all runs fine...
hope this helps a bit
cya
Killer Bee
BTW: 1400-patch was applied and i ran a quiet LU v2.5-setup after it and no updates were available...
CODE
==========================================================
-- Orig Defs Files -- | i32 Defs Files -- | x86 Defs Files
==========================================================
01 X ---------------- | UPDATE.TXT ------ | UPDATE.TXT
02 VIRSCAN1.DAT ----- | VIRSCAN1.DAT ---- | X
03 VIRSCAN3.DAT ----- | VIRSCAN3.DAT ---- | X
04 VIRSCAN4.DAT ----- | VIRSCAN4.DAT ---- | X
05 VIRSCANT.DAT ----- | X --------------- | X
06 X ---------------- | X --------------- | DEFATTRS.DAT
07 X ---------------- | X --------------- | ECOMSRVR.NLM
08 X ---------------- | X --------------- | INSCANM.DAT
09 X ---------------- | X --------------- | LIC.DAT
10 X ---------------- | X --------------- | NAVENG.NLM
11 X ---------------- | X --------------- | NAVENG16.DLL
12 X ---------------- | X --------------- | NAVEX.EXP
13 X ---------------- | X --------------- | NAVEX.NLM
14 X ---------------- | X --------------- | NAVEX.SYS
15 X ---------------- | X --------------- | NAVEX.VXD
16 X ---------------- | X --------------- | NAVEX15.NLM
17 X ---------------- | X --------------- | NAVEX15.WLD
18 X ---------------- | X --------------- | NAVEX16.DLL
19 X ---------------- | X --------------- | NAVEX16A.DLL
20 X ---------------- | X --------------- | NAVEX32.DLL
21 X ---------------- | X --------------- | NAVLIC.DAT
22 X ---------------- | X --------------- | VERSION.DAT
23 X ---------------- | X --------------- | VIRSCAN.DAT
24 X ---------------- | X --------------- | VIRSCAN1.DEF
25 X ---------------- | X --------------- | VIRSCAN2.DEF
26 X ---------------- | X --------------- | VIRSCAN2.PAM
27 X ---------------- | X --------------- | VIRSCAN3.DEF
28 X ---------------- | X --------------- | VIRSCAN4.DEF
29 X ---------------- | X --------------- | VIRSCANM.DAT
30 X ---------------- | X --------------- | VIRWILD1.DAT
31 X ---------------- | X --------------- | VIRWILD2.DAT
32 X ---------------- | X --------------- | VIRWILD3.DAT
33 X ---------------- | X --------------- | VIRWILD4.DAT
==========================================================
-- Orig Defs Files -- | i32 Defs Files -- | x86 Defs Files
==========================================================
01 X ---------------- | UPDATE.TXT ------ | UPDATE.TXT
02 VIRSCAN1.DAT ----- | VIRSCAN1.DAT ---- | X
03 VIRSCAN3.DAT ----- | VIRSCAN3.DAT ---- | X
04 VIRSCAN4.DAT ----- | VIRSCAN4.DAT ---- | X
05 VIRSCANT.DAT ----- | X --------------- | X
06 X ---------------- | X --------------- | DEFATTRS.DAT
07 X ---------------- | X --------------- | ECOMSRVR.NLM
08 X ---------------- | X --------------- | INSCANM.DAT
09 X ---------------- | X --------------- | LIC.DAT
10 X ---------------- | X --------------- | NAVENG.NLM
11 X ---------------- | X --------------- | NAVENG16.DLL
12 X ---------------- | X --------------- | NAVEX.EXP
13 X ---------------- | X --------------- | NAVEX.NLM
14 X ---------------- | X --------------- | NAVEX.SYS
15 X ---------------- | X --------------- | NAVEX.VXD
16 X ---------------- | X --------------- | NAVEX15.NLM
17 X ---------------- | X --------------- | NAVEX15.WLD
18 X ---------------- | X --------------- | NAVEX16.DLL
19 X ---------------- | X --------------- | NAVEX16A.DLL
20 X ---------------- | X --------------- | NAVEX32.DLL
21 X ---------------- | X --------------- | NAVLIC.DAT
22 X ---------------- | X --------------- | VERSION.DAT
23 X ---------------- | X --------------- | VIRSCAN.DAT
24 X ---------------- | X --------------- | VIRSCAN1.DEF
25 X ---------------- | X --------------- | VIRSCAN2.DEF
26 X ---------------- | X --------------- | VIRSCAN2.PAM
27 X ---------------- | X --------------- | VIRSCAN3.DEF
28 X ---------------- | X --------------- | VIRSCAN4.DEF
29 X ---------------- | X --------------- | VIRSCANM.DAT
30 X ---------------- | X --------------- | VIRWILD1.DAT
31 X ---------------- | X --------------- | VIRWILD2.DAT
32 X ---------------- | X --------------- | VIRWILD3.DAT
33 X ---------------- | X --------------- | VIRWILD4.DAT
==========================================================
X means not found.
As seen from the table, we're fooled by the idea of extracting virus definitions files. Neither i32 files nor x86 files are capable of performing REAL updating!
Well, you might say that you used i32 files successfully. And I'd say that you're fooled! Why?
Because you overwrote the existing files, thus, you left the old "VIRSCANT.DAT" and added "UPDATE.TXT" which wouldn't be installed, of course.
If you want to believe me, do the following:
1- Go to: C:\Program Files\Symantec AntiVirus\Virus Defs\, and you'll be surprised! "UPDATE.TXT" isn't there. HUH!?
2- Get connected to the Internet, run LiveUpdate, and you'll be surprised! SAV downloads updates that are supposed to be, already, on your computer. HUH!?
What if you use x86 files? The worst, of course.
What if you delete all old files before pasting extracted files of i32 or x86? Installation of SAV will be interrupted asking for "VIRSCANT.DAT". This was exactly what happened to me!
There are worse events, but this is enough for now.
Solution? Maybe!
hi,
but i think it is working, because LiveUpdate(v2.5) says that everything is up to date and don't want to download anything...
hope this helps a bit
cya
Killer Bee
but i think it is working, because LiveUpdate(v2.5) says that everything is up to date and don't want to download anything...
hope this helps a bit
cya
Killer Bee
hi,
just done a second installation and LU says everything is up-to-date...
what i have done:
1. created a admin install point with setup.exe /A
2. downloaded newest i32-virus definitions from here.
3. created a folder named viri in the same dir as the virus-defs are
4. ran virdefs with ...-i32.exe /Extract .\viri
5. copied everything from .\viri to the admin install point \Program Files\Symantec Antivirus\virus defs
6. downloaded SAVCE_9.0.0.1400_AllWin_EN .msp
7. integrated the update within the main program with this one
8. put it on my CD and ran it with
9. downloaded and extracted the Liveupdate v2.5 update and installed it with
thats it and it works perfect
hope this helps a bit
cya
Killer Bee
BTW: it gets installed @ T-12min and is ofcourse unattended
just done a second installation and LU says everything is up-to-date...
what i have done:
1. created a admin install point with setup.exe /A
2. downloaded newest i32-virus definitions from here.
3. created a folder named viri in the same dir as the virus-defs are
4. ran virdefs with ...-i32.exe /Extract .\viri
5. copied everything from .\viri to the admin install point \Program Files\Symantec Antivirus\virus defs
6. downloaded SAVCE_9.0.0.1400_AllWin_EN .msp
7. integrated the update within the main program with this one
CODE
msiexec /p "SAVCE_9.0.0.1400_AllWin_EN .msp" /a "Symantec AntiVirus.msi" /QB
8. put it on my CD and ran it with
CODE
Symantec Antivirus.msi /QB
9. downloaded and extracted the Liveupdate v2.5 update and installed it with
CODE
lusetup -q
thats it and it works perfect
hope this helps a bit
cya
Killer Bee
BTW: it gets installed @ T-12min and is ofcourse unattended
Well for me mazin the virus defs say they are updated and works like killerbee said. I did what killerbee did and everything was fine.
@killerbee
@drthawhizkid
Thanks for the confirmation.
There may not be updates available for LU itself because you didn't integrate it, but performed live installation instead.
But did you try checking V.Defs updates more than one time? If you did and there were no updates available, then i32 works fine for you given that you overwrote the source, but not cleaned the source as I explained earlier.
However, can you tell me why people complained with SAV trying to download updates after installation despite V.Defs were integrated?
If my explanation did not provide the answer, then I'm completely wrong, despite the fact that MSIs install files by name!
Thanks.
@drthawhizkid
Thanks for the confirmation.
There may not be updates available for LU itself because you didn't integrate it, but performed live installation instead.
But did you try checking V.Defs updates more than one time? If you did and there were no updates available, then i32 works fine for you given that you overwrote the source, but not cleaned the source as I explained earlier.
However, can you tell me why people complained with SAV trying to download updates after installation despite V.Defs were integrated?
If my explanation did not provide the answer, then I'm completely wrong, despite the fact that MSIs install files by name!
Thanks.
@mazin I ran LiveUpdate more than once to see if it would show updates and it didn't. I don't know why its not working for ya. Sorry I hope you find an solution.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.