 SAV 9 - Symantec AntiVirus 9.0 |
Unattended CD/DVD Guide Homepage · MSFN Forum Rules
Welcome to the Applications Installs forum. Make sure you read the forum rules before you start posting.
Links/Requests to warez and/or any illegal material (porn, cracks, serials, etc..) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/keygens or any other illegal activity will also not be tolerated.
We try our best to keep this forum clean of illegal content. If you see any illegal activity use the "report" button you find in every post to report the specific post to the moderators. If you ignore any of the rules you will be banned without notice.
Read Forum Rules
  |
 Aug 10 2004, 07:14 PM
Post
#1
|
|
|
Follow the rules please :-)  Group: Patrons Posts: 7657 Joined: 14-November 03 From: Bangalore, India Member No.: 9470 
 |
could we have a detailed article on how to install/pre-configure SAV 9.0?
 And also, about how to have the updated patches and anti-virus definitions merged into install source? I'm sure many of you have done this before successfully. Please consider taking up the above request.  Update: here's a good, and confirmed to work properly, guide - made by mazin. QUOTE Guide for SAV's AIP
Before you use this guide, make sure SAV isn't installed on your system. Otherwise, you'll get errors when creating the Administrative Installation Point. Create a folder anywhere on your hard disk and name it whatever you like. I'll assume you name it "SAVSource". Copy the following files into "SAVSource": 1- 0x0409.ini (for French version, you need 0x040c.ini, instead) 2- Setup.ini 3- setup.exe 4- Data1.cab 5- Symantec AntiVirus.msi Those 5 files are copied from your CD (of version 9.0.0.338), of course. 6- SAVCE_9.0.0.1400_AllWin_EN .msp This file is extracted from SAVCE_9.0.0_mp2.zip (3 MB) downloadable from here. (for French version, you download this, instead.) 7- yyyymmdd-###-i32.exe It's usually 5+ MB in size and can be downloaded from here. The file I'm using in this guide is named 20040828-003-i32.exe! (for French version, you start here, instead.) 8- lusetup.exe It's 2.5+ MB in size and can be downloaded from here. 9- remote.cmd The following quote shows the contents of remote.cmd! QUOTE cls @echo off ECHO Creating AIP start /wait setup.exe /A /V"/QB TARGETDIR=%systemdrive%\SAV91400"  sleep 30 copy lusetup.exe %systemdrive%\SAV91400\CommonAppData\Symantec\LiveUpdate\LuMMInst\Lsetup.exe ECHO Patching AIP copy "SAVCE_9.0.0.1400_AllWin_EN .msp" %systemdrive%\SAV91400\savce1400.msp start /wait msiexec /p %systemdrive%\SAV91400\savce1400.msp /a "%systemdrive%\SAV91400\Symantec AntiVirus.msi" /QB del %systemdrive%\SAV91400\savce1400.msp ren "%systemdrive%\SAV91400\Symantec AntiVirus.msi" SAV.msi ECHO Updating AIP Virus Definitions attrib -r "%systemdrive%\SAV91400\program files\Symantec AntiVirus\Virus Defs\*.*" start /wait 20040828-003-i32.exe /Extract /Q "%systemdrive%\SAV91400\program files\Symantec AntiVirus\Virus Defs" exit Before you run remote.cmd, make sure you put sleep.exe in your system32 or Windows folder. After remote.cmd exits, you should have your AIP created (ready steady) as a folder in your system drive and named SAV91400. Now, delete "SAVSource" folder, as it's no longer needed. To install SAV using your AIP, add these lines to your batch file: QUOTE ECHO SAV 9.0.0.1400 V.Defs updated 28.8.2004 start /wait %systemdrive%\Install\SAV91400\SAV.msi /QB RUNLIVEUPDATE=0 REBOOT=ReallySuppress This post has been edited by prathapml: Sep 28 2004, 05:29 AM |
 |
 
|
|
Aug 11 2004, 02:45 AM
Post
#2
|
|
|
Newbie Group: Members Posts: 11 Joined: 24-November 03 Member No.: 9918 |
I would like to know as well please.
|
|
|
|
|
Aug 11 2004, 03:06 AM
Post
#3
|
|
|
aka Wim Leers Group: Patrons Posts: 5719 Joined: 29-October 03 From: Hasselt, Belgium Member No.: 8748 OS: none 
|
How to install it can you find in this topic:
Direct from the CD: MSI_FAQ.txt CODE ****************************************************************************** Symantec AntiVirus Corporate Edition 9.0 MSI_FAQ.TXT Copyright 2004 Symantec Corporation. All rights reserved. March 2004 ****************************************************************************** This file is a list of the most commonly used MSI commands for Symantec AntiVirus and Symantec Client Security. For a complete list of commands, properties, and features, see the Symantec Knowledge Base. BASIC MSI commands ------------------ /QN - Quiet No UI /QB - Quiet Basic UI /L*V log.txt - full verbose logging to file log.txt BASIC MSI properties -------------------- REBOOT=REALLYSUPPRESS SAV properties -------------- INSTALLSERVER= (1 = Server, 0 = Client, Default is client) SERVERGROUPNAME= (New or prexisting servergroup) SERVERGROUPPASS= (New or prexisting servergroup password. The default is symantec) NETWORKTYPE= (1 = Managed, 2 = Unmanaged, default is Unmanaged) SERVERNAME= (preexisting SAV Servergroup) RUNLIVEUPDATE= (run LiveUpdate during install = 1, do not run LiveUpdate=0, default is On) ENABLEAUTOPROTECT= (1 = ON, 0 = OFF, default is On) INSTALLDIR= (Install target directory, default is C:\Program Files\ Symantec AntiVirus) SERVERPARENT= (e.g. SERVERPARENT=MySavServer) Note: For a secondary server silent install from the command line, you must set the SERVERPARENT property to the Parent server computer name. When doing a UI or Symantec System Center rollout install, setting this property is not required. SAV features ------------ EMailTools NotesSnapin OutlookSnapin Pop3Smtp QClient SAVHelp SAVUI Adding and removing features ---------------------------- To remove existing features: REMOVE=<feature1>,<feature2>,<feature3> To add new features: ADDLOCAL=<feature1>,<feature2>,<feature3>, <existing feature 1>, <existing feature 2>, etc. Note: When adding new features using ADDLOCAL, any existing features on the target computer that you want to retain must be included in the features that you are specifying. The installation will remove any features on the target computer that are not listed. Command line example -------------------- This example demonstrates a silent Symantec AntiVirus Server installation. The server is named MYSAVSERVER and uses the password MYSAVPASSWORD. LiveUpdate is not run, and the server is not restarted even if its required. Sample command line: setup /s /v"/l*v log.txt INSTALLSERVER=1 SERVERGROUPNAME=MYSAVSERVER SERVERGROUPPASS=MYSAVPASSWORD RUNLIVEUPDATE=0 REBOOT=REALLYSUPPRESS" The best way to install newest updates is this one in my opinion. And you can download the newest updates here But like this it won't be 'merged' into source, but at least it's easy maintainable. (Which is more important IMHO) |
|
|
|
|
Aug 11 2004, 03:34 AM
Post
#4
|
|
|
Newbie Group: Members Posts: 11 Joined: 2-March 04 Member No.: 15200 |
Actually, I've used the informations contained in the MSI_FAQ.txt in order to have a silent Installation, but it crashes with error... I have to recheck my commandline.
A patch exists for SAV9, but it is in .MSP format, so I don't now how to install it. Maybe we can slipstream it... I need help for this  Here is the link : http://www.symantec.com/techsupp/enterpris..._9.0/files.html For the virus definition, simple download the lastest Symantec Security Responce Intelligent Updater and run it with the /Q- switch. (downland the x86 and not the i32 version) Here is the link : http://securityresponse.symantec.com/avcen...s.download.html |
|
|
|
|
Aug 11 2004, 05:52 AM
Post
#5
|
|
|
Follow the rules please :-) Group: Patrons Posts: 7657 Joined: 14-November 03 From: Bangalore, India Member No.: 9470
|
That's great news!
You find the warez which already have the build1400 update integrated. How they do it is described below. Slipstream SAV9 Update 1. Run a setup.exe /A (admin install point) 2. Get AV-defs (get the i32 version) from here 3. Save it in a folder, and then change into that directory using the command-prompt. Create a new folder called "updts". 3. Extract the above-mentioned exe using "/EXTRACT .\updts" switch, and in the admin-install folder, over-write files in "\program files\Symantec AntiVirus\Virus Defs" with all files from the extracted i32 update. 2. extract "SAVCE_9.0.0.1400_AllWin_EN .msp" from the update (see previous post) .zip and place it into the SAV9 admin/server-image install dir. 3. Open a command-prompt into that directory, and use the following command: CODE msiexec /p "SAVCE_9.0.0.1400_AllWin_EN .msp" /a "Symantec AntiVirus.msi" /QB So there it is, AV-updates and latest SecurityCenter patch merged into the distribution source. Now, can we have more details from ppl who have successfully pre-configured their SAV? I mean, how to: 1. Disable the LiveUpdate that comes up at the end of install? 2. Disable Automatic updating 3. And whatever else, interesting things you ppl have found out. This post has been edited by prathapml: Aug 30 2004, 02:38 PM |
|
|
|
|
Aug 11 2004, 07:01 AM
Post
#6
|
|
|
Newbie Group: Members Posts: 17 Joined: 7-August 04 Member No.: 26444 |
Thanks for the info prathapml but unfortunately I have some minor issues still.
I followed yor instructions but after a succesfull install (in vmware) I still needed two liveupdates to get it updated. Any ideas how to solve this? :/ |
|
|
|
|
Aug 11 2004, 07:21 AM
Post
#7
|
|
|
Follow the rules please :-) Group: Patrons Posts: 7657 Joined: 14-November 03 From: Bangalore, India Member No.: 9470
|
QUOTE (Agent-X @ Aug 11 2004, 06:31 PM) I still needed two liveupdates to get it updated. Could you please mention which ones those are? |
|
|
|
|
Aug 11 2004, 08:13 AM
Post
#8
|
|
|
Newbie Group: Members Posts: 17 Joined: 7-August 04 Member No.: 26444 |
If you can tell me how to find out
For the moments some screens of the update: [edited] The virus definitions as stated in the programm were only updated after the seccond liveupdate. |
|
|
|
|
Aug 11 2004, 08:27 AM
Post
#9
|
|
|
Follow the rules please :-) Group: Patrons Posts: 7657 Joined: 14-November 03 From: Bangalore, India Member No.: 9470
|
OK, understood what the problem is.
(you can now edit out those screenies)The SAV isn't ever satisfied with what is already there (even if it is the latest already) - it necessary always wants to go out and download the latest updates - I saw this being discussed somewhere - there's probably a registry entry, or a file signature somewhere which we aren't able to update when we merge the newest virus definitions. Well, no probs as long as you can manually deny it permission to update itself, when you already *KNOW* that it has the latest it could get.
|
|
|
|
|
Aug 11 2004, 08:48 AM
Post
#10
|
|
|
Newbie Group: Members Posts: 17 Joined: 7-August 04 Member No.: 26444 |
Ok, my workaround so far is to simply call the manual virusupdate with the /Q switch.
I get an error doing this if I don't move/copy the file to the target system first (to be deleted afterwards). This wil result in an updated definition but as you mentioned SAV still likes to update anyway Also, executing a .msi file with the /qn switch gives me a nasty pop up if the publisher is unknown (fe the newly build SAV package) Will this show during unattended install? |
|
|
|
|
Aug 11 2004, 09:33 AM
Post
#11
|
|
|
Newbie Group: Members Posts: 19 Joined: 4-October 03 Member No.: 7710 |
nevermind
|
|
|
|
|
Aug 11 2004, 09:39 AM
Post
#12
|
|
|
Follow the rules please :-) Group: Patrons Posts: 7657 Joined: 14-November 03 From: Bangalore, India Member No.: 9470
|
QUOTE (Agent-X @ Aug 11 2004, 08:18 PM) executing a .msi file with the /qn switch gives me a nasty pop up if the publisher is unknown Will this show during unattended install? Hmm.... I suppose if it shows up during your testing in normal windows mode, it would do the same during uA setup as well. I would gladly use the update with /Q switch, but my only gripe with it is that it would end up swelling the size of my CD - so I prefer to replace the existing defs with new - which Symantec still isn't satisfied with - I suppose it thinks we are a bunch of lying kids, so it asks its mother and confirms the news.
|
|
|
|
|
Aug 12 2004, 07:36 AM
Post
#13
|
|
|
Newbie Group: Members Posts: 19 Joined: 4-October 03 Member No.: 7710 |
is there anyway to recompress all of this like it was before the updates?
|
|
|
|
|
Aug 12 2004, 07:50 AM
Post
#14
|
|
|
Follow the rules please :-) Group: Patrons Posts: 7657 Joined: 14-November 03 From: Bangalore, India Member No.: 9470
|
Yes.
Make that entire install folder compressed into an SFX archive which silently extracts to "%SystemDrive%\install\Applications\" folder from CD. The next command after that can be to run "%SystemDrive%\install\Applications\SAV\whatever.msi /whatever". Easy, and at the end of the process, the space SAV occupies on your CD is reduced from its original size. |
|
|
|
|
Aug 12 2004, 01:07 PM
Post
#15
|
|
|
Newbie Group: Members Posts: 12 Joined: 11-August 04 Member No.: 27211 |
bleh my install of SAV wont work :S
using QUOTE ECHO. and having :ECHO Installing SAV 9.0 start /wait %systemdrive%\install\Applications\SAV\sav.msi /QN INSTALLSERVER=1 SERVERGROUPNAME=Boxen SERVERGROUPPASS=****** NETWORKTYPE=Managed RUNLIVEUPDATE=1 REBOOT=REALLYSUPPRESS QUOTE Directory of c:\XPCD\$OEM$\$1\Install\Applications\SAV 12/08/2004 03:14 <DIR> . 12/08/2004 03:14 <DIR> .. 14/04/2004 21:21 4,817,612 SAV.msi 1 File(s) 4,817,612 bytes 2 Dir(s) 133,503,991,808 bytes free I get the "Installing SAV 9.0" echo.. and then there is a gap while it does something.. then it goes onto the next program. However when the process finishes SAV has not been installed into the \program files\ and there is no Sheild icon in the system tray. The program has not been installed.. and I dont know why, can any one help me please? many thanks Buzzons |
|
|
|
|
Aug 12 2004, 01:17 PM
Post
#16
|
|
|
Follow the rules please :-) Group: Patrons Posts: 7657 Joined: 14-November 03 From: Bangalore, India Member No.: 9470
|
Use "/QB" instead of "/QN" (atleast during testing). That way, you'll get an on-screen diag-box if anything is wrong during install. Do check that out and report back on what it says.
Also, you might like to un-install your current Anti-Virus, and install the SAV9 (which you are attempting to unattend) in the normal way while windows is fully operational - then you'd know if there's been any file-corruption. |
|
|
|