Views: 1.5k  |  Created: 09/16/2005

Average Rating: 0
Norton AntiVirus has 4 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 3 / 5 (Average) based on 7 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (switch driven)
or cancel
119
Command Line
This command will silently install the client, set it as managed, and prevent it from rebooting after installation:

msiexec /i "Symantec Antivirus.msi" NETWORKTYPE=1 SERVERNAME=<SERVERNAME> /REBOOT=ReallySuppress /qn

For more command line parameters check here: http://service1.symantec.com/SUPPORT/ent-security.nsf/529c2f9adcf33a1088256e22005026f1/ca96626e4963a8cc88256e3e0075b278?OpenDocument&prod=Symantec%20AntiVirus%20Corporate%20Edition&ver=9.0&src=ent&pcode=sav_ce&dtype=corp&svy=&prev=&miniver=savce_9.0
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
If repackaging is done with a server with new virus definition files next problems can occur: Clicking "Scan Harddisk" wil cause the application to crash. This is caused by the Symantec Antivirus Service, witch is not started. When trying to start this service manualy you get the message: Error 10 : Environment is incorrect. In the eventviewer you will get the error: Virus Definition File incorrect!

So if you want to repackage the client installation with wise or installshield, make sure the symantec server has no new virus definition files. It is best to use a clean install of the server!

>> Note from AppDeploy.com : As this is provided as a native MSI package from the vendor, it should not be repackaged. To customize a MSI, create a transform (MST). <<
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note

Symantec supply a packager as part of the corporate edition. This allows you to create a single exe that can be designed to undertake a silent install, it will also allow any relevant grc.dat files to be included. There is no need for repackaging nor a .mst.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note

Take not of the installation source when using Symantec's EXE deployment option. It is simply wrapping the MSI in a self-extracting executable, that runs from %temp% and deletes itself. The problem is, if a reinstall or repair is needed, Windows Installer is going to look in %temp% for the source files it needs.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
Symantec Antivirus Enterprise ver. 8.1 is no problem to deploy, but I recommend to use the ver. 8.1 of the Packager. Just make 2 packages, one (a custom install) to deinstall the old version using msiexec /X with the GUID from registry, remember to turn of password in good time before the deinstallation starts in the SSC.

Deinstallation of older NAV versions before you install SAV 8.x is recommended by Symantec technitians.

Add the custom install to a Computerbased Startup script and this is running unattended with the neccessary rights.

When the computerclient reboot another computerbased startup script is running, checking if the first one is finished , then installing the nes SAV client.

The problem is when deploying the client from several application servers worldwide using different SAV servers. Then you need to add support for roaming clients, both in your SAv installation and your startup scripts.

We use a AD computer based script checking Active Directory for witch site you are connected to, then installing from the right application server and at last rewrite the registry values for the right SAV server.

The worst job is to deploy (send CDs) the packages to the servers.

Regards
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
It should be noted that you can not use the .msi that is created by the Symantec Packager application by itself. How ever it is constructed will not publish using intellimirror unless you use .zap files. But if your environment requires .msi elevated installation; good luck.
http://tinyurl.com/3f4ay
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
0
Note
msiexec /i "Symantec Antivirus.msi" NETWORKTYPE=1 SERVERNAME=<SERVERNAME> /REBOOT=ReallySuppress /qn Note: A utility is provided as part of the corporate edition to create a single exe that can be designed to undertake a silent install. It allows any relevant grc.dat files to be included.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (4)

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

Norton AntiVirus

Version

8

Questions & Answers (1)

Questions & Answers related to Symantec Norton AntiVirus

14
ANSWERS

Blogs (0)

Blog posts related to Symantec Norton AntiVirus

Reviews (0)

Reviews related to Symantec Norton AntiVirus