To prevent the "Old Virus Definitions File" po-up window from appearing there are a couple of options: 1. Update the package source with virus definitions on a regular basis. 2. Set the "WarnA… Read More

When using the Symantec uninstall utility, ensure your Windows OS has MSIEXEC version 3.x or higher installed. I've noted that Windows OS with an MSIexec version less than 3.x will reboot if y… Read More

I've used this, it appears to have worked fairly well to-date. msiexec /i "\\srvr\Symantec Antivirus.msi" ADDLOCAL=SAVMain,SAVUI,SAVHelp,QClient NETWORKTYPE=1 INSTALLSERVER=0 SERVERNAME=srvant… Read More

Download the NONAV.EXE utility and run it as a preliminary job prior to installing your new NAV client. Read More

The actual package is quite easy. You can use what they give you, just cusomise the setup.ini file. The main problem is unistalling previous versions. It does a great job from 8.1 to 9, but … Read More

Try using setting the property MIGRATESETTINGS to 0 (default is 1). This should allow the cpolicy.xml file in the same folder at setup.exe and the MSI to apply. Check out this related article:… Read More

Command line for MSI deployment inc Maintenance Patch 2. MsiExec.exe /I"\\servername\VPHOME\CLT-INST\WIN32\Symantec AntiVirus.msi" PATCH="\\servername\VPHOME\CLT-INST\WIN32\savce1400.msp" REBO… Read More

Be aware that when performing an administrative install to a network path the installer does not copy over two necessary file from the SCSClnt folder. ALErules.exe and INSTOPTS.DAT need to be … Read More

The best way to deliver this package is with a custom MST file. Although the Symantec provided switches do work, a tool such as Admin Studio or Wise will suite your needs better. For those wh… Read More

Confirmed: The custom Firewall policy file as well as the custom AV config file must be named Symantec's default namefor it to be applied. The firewall policy must be named Cpolicy.xml and th… Read More