/build/static/layout/Breadcrumb_cap_w.png

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 6.5k  |  Created: 09/16/2005

Average Rating: 0
Norton AntiVirus has 9 inventory records, 1 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (7)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 1 / 5 (Very Easy) based on 2 ratings
Most Commonly Reported Deployment Method
Windows Installer Command Line (No MST)
120
Note
This is the easyway...

1. install the symantec av server
2. copy from Programms\SAV\CLT-INST\ the folder WIN32 in a share
3. create a gpo to deploy the symantec*.msi file

thats it.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
119
Note
Use the following command line to deploy SAV to a client via a login script or whatever. Bear in mind that the installation requires local admin permissions (there are ways to get around this - google CPAU - it's a free RUNAS utility). BTW, this works - I've used it to deploy SAV to over 1200 PCs and 5000+ users. Just copy the entire contents of the SAV client installation folder to a temp folder on the client PC and run the installation from the client PC.

The following command should be on 1 line (no wraps):

msiexec.exe /i SAV10.msi REBOOT=ReallySuppress INSTALLSERVER=0 NETWORKTYPE=1 SERVERNAME=GIS RUNLIVEUPDATE=0 ADDLOCAL=SAVMain,SAVUI,SAVHelp,QClient /qb!

1.The msi has been renamed to SAV10.msi and can be run directly. Come on Symantec, use the 8.3 naming convention!!

2.ReallySuppress means the installation will NEVER prompt to reboot the PC.

3.INSTALLSERVER=0 means this is a client installation (Windows XP, etc.) and not a server installation.

4.NETWORKTYPE=1 means this is a managed installation (as opposed to be an unmanaged install that will not look to a primary server for virus def updates)

5.SERVERNAME=GIS means that the name of the primary server that this client will look to for virus defs and program settings is called GIS. Change the name to match your primary server.

6.RUNLIVEUPDATE=0 means don't run LiveUpdate after the installation is complete

7.ADDLOCAL=SAVMain,SAVUI,SAVHelp,QClient means install all features except for the crappy email plugin that hoses the PC anyway.

8./qb! is an msiexec.exe switch and is used to hide buttons on the installation dialog. Basically it shows the install progress (and errors) but does not allow the user to cancel the installation.

A couple of other notes.

1.It's best to do this install from a script because you're going to need to copy down the .cer certificate file from the primary server to the C:\Program Files\Symantec AntiVirus\pki\roots\ folder on the client PC. You'll need to do this so the client will communicate with the primary server and receive virus def updates. This was the biggest problem I had to solve!

2.You may also want to copy GRC.dat from the primary server to the C:\Documents and Settings\All Users\Application Data\Symantec\Symantec AntiVirus Corporate Edition\7.5\ folder on the local PC. This makes sure all of SAV's programs settings and options (that you configured on the primary server) are implemented on the client PC. This step may not be necessary are you are already identifying the primary server on the command line.

3. If you're using a firewall or Windows Firewall (in XP), be sure to make the necessary exceptions (2967 TCP and perhaps a program exception of C:\Program Files\Symantec AntiVirus\Rtvscan.exe).

4.Reboot the PC after the installation is complete.

5.Don't worry about installing SymEvent. SAV already has the latest version as of the date of this post.

I hope this helps other folks. I'll surely went through - HELL - troubleshooting this over Christmas and would like to see others benefit. Knowledge should be free!

Wally Beck
Network Admin - Gainesville State College
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
This content is currently hidden from public view.
Reason: Hidden by Admin For more information, visit our FAQ's.
118
Note
I utilize Zenworks 7 to distribute msi/mst. Had terrible time with mst for SAVCE 10.1.6000 client. What worked was on a clean vmware session of XP SP2 I installed the package and made all my time schedule changes, quarantine/delete options, no scan network drives etc. basically any customized modifications.Open regedit to HKLM/software/intel/landesk/virusprotect6 exported that registry key.

Locate the newest virus definition located in program files/common files/symantec shared/virusdefs/ex..20070510.025 Select all files within and utilize winzip to add and replace the files within the vdefhub.zip which is file within the sav directory where the symantec antivirus.msi is located. This is to not receive the virus defs older than 30 days message.
SAV directory place on network with created reg export, and modified vdefhub zip file.

Create an application object for symantec antivirus.msi with a distribution option where you would import the reg file you created. I push it out as unsecure system user so it will install with elevated priveledges-Power users etc.. Uninstals previous versions;installs new version;prompt for reboot;no problem.

I Use regmon to find those hard registry entry locations
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
117
Command Line
First thanks for the very good job done here !

You can add the RUNSCAN=0 to the command line to disable scan execution after installation.

To package updated definitions to your deployement package, replace files in VDefHub.zip files with last definition (from C:\Program Files\Fichiers communs\Symantec Shared\VirusDefs or similar).
The definition directory should contain files like viruscanxx.dat.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
117
Note

I was getting 1721 errors after I did a msiexec /a network install both before and after I patch the admin install point. It appears Live Update won't install because it can't find lusetup.exe. Navigate to your CD and copy it over to the root of your install point. The install finished for me after that.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
116
Command Line
The addition of the following property: LOCALCACHEDRIVE=C added to my transform resolved a Windows GPO deployment issue with Symantec Antivirus 10.0.0.359.

With the later release of Symantec Antivirus 10.0.1.1000, this Property is no longer required.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
116
Command Line
For Symantec Antivirus Corporate Edition v10, I am using the following script for silently installing, then silently updating. Currently I am using a batch file shown below via a Novell login script (works fine). Very basic I know, but it's one of my first deployments! :-

@echo off
cls

if exist "c:\program files\symantec antivirus\vpc32.exe" goto end1

echo Symantec Antivirus v.10 Corporate Edition
echo Software Installation Routine
echo.

:install

msiexec /i \\servername\volname\foldername\sav10\clt-inst\win32\symantecantivirus.msi /qb RUNSCAN=0 RUNLIVEUPDATE=1 REBOOT=REALLYSUPPRESS

:end1
copy \\servername\volname\foldername\sav10\clt-inst\win32\station8.grp c:\ins
goto end

:end


- I am using a basic marker file (.grp) to reference installation (or attempted installed) on the PC.

- The only thing this does not do is run a scan, but I use the MMC snapin for Symantec Antivirus Corporate Edition for which I have scheduled scans accordingly.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

Inventory Records (9)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Norton AntiVirus

Version

10.1.2

Uninstall String

/Applications/Norton AntiVirus

Questions & Answers (1)

Questions & Answers related to Symantec Norton AntiVirus

3
ANSWERS

Blogs (0)

Blog posts related to Symantec Norton AntiVirus

Reviews (0)

Reviews related to Symantec Norton AntiVirus

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ