cer certificate file from the primary server to the C:\Program Files\Symantec AntiVirus\pki\roots\ folder on the client PC.
Norton antivirus definitions 2005 install#
Basically it shows the install progress (and errors) but does not allow the user to cancel the installation.ġ.It's best to do this install from a script because you're going to need to copy down the.
Change the name to match your primary server.Ħ.RUNLIVEUPDATE=0 means don't run LiveUpdate after the installation is completeħ.ADDLOCAL=SAVMain,SAVUI,SAVHelp,QClient means install all features except for the crappy email plugin that hoses the PC anyway.Ĩ./qb! is an msiexec.exe switch and is used to hide buttons on the installation dialog. Come on Symantec, use the 8.3 naming convention!!Ģ.ReallySuppress means the installation will NEVER prompt to reboot the PC.ģ.INSTALLSERVER=0 means this is a client installation (Windows XP, etc.) and not a server installation.Ĥ.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)ĥ.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. Msiexec.exe /i SAV10.msi REBOOT=ReallySuppress INSTALLSERVER=0 NETWORKTYPE=1 SERVERNAME=GIS RUNLIVEUPDATE=0 ADDLOCAL=SAVMain,SAVUI,SAVHelp,QClient /qb!ġ.The msi has been renamed to SAV10.msi and can be run directly. The following command should be on 1 line (no wraps): 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. BTW, this works - I've used it to deploy SAV to over 1200 PCs and 5000+ users. 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). Use the following command line to deploy SAV to a client via a login script or whatever.
0 kommentar(er)
