/build/static/layout/Breadcrumb_cap_w.png

Need some help...

I've recently been thrown into updating our Symantec Client Security at the accounting firm I work for. Recently There has been a patch to go from version 9.0.0.338 to 9.0.0.1400 (maintenance patch 2). Here's the rundown. This is an accounting firm with 5 branches, spread way out. There are around 200 laptops and 40 desktops on the network. I need to get this patch updated but there is a snag. Here is the excerpt from Symantec's website

Error: "1706 No valid source can be found for product Symantec AntiVirus" when installing Maintenance Patch 2 for Symantec AntiVirus Corporate Edition 9.0.0.338
----------------------------------------------------------------
Situation:
You are upgrading Symantec AntiVirus Corporate Edition 9.0.0.338 to version 9.0.0.1400 by applying Maintenance Patch 2 (MP2), either by double-clicking the SAVCE_9.0.0.1400_AllWin_EN .msp file, or by running it from a command line. You see the message "1706 No valid source can be found for product Symantec AntiVirus."

Solution:
This occurs when the files from which the product was originally installed are no longer available. Symantec is investigating this problem to determine a solution. This document will be updated when new information or a solution is available.

Workarounds
Use one of the following methods to work around this problem:

If you are installing the patch interactively, and are given the option to browse to the source files, browse to the \SAV folder on the 9.0 installation CD. This allows the installation to continue.
If you are installing the patch from a command line or a script, either ensure that the original source files are still available to the client or provide new source files by using the following command:

msiexec /fvamus "<path>\symantec antivirus.msi" PATCH="<path>\SAVCE_9.0.0.1400_AllWin_EN .msp" /qn /l*v install.log

Replace the two <path> with the correct paths to those files. Also, notice the space before the extension in the file name of the patch. This command downloads the source files along with the patch. The source files are about 34 MB in size.
Uninstall Symantec AntiVirus 9.0.0.338 and install Symantec AntiVirus 9.0.1.1000 instead.

--------------------------------------------------------------------

I have decided to go with the second one since this is a W2k active directory situation. My problem is that when I make a logon script this runs each time the user logs in. So SAV keeps getting re-installed. I can't put the script out there, then pull it back because the majority of the users are in and out of the office at various times of the day and night. So what I need to do is to know how to make the lines below run one time. I hope I'm posting this in the right place. THanks in advance


msiexec /fvamus "<path>\symantec antivirus.msi" PATCH="<path>\SAVCE_9.0.0.1400_AllWin_EN .msp" /qn /l*v install.log

0 Comments   [ + ] Show comments

Answers (3)

Posted by: kkaminsk 19 years ago
9th Degree Black Belt
0
Well MSIEXEC is not going to run that command line only once if it keeps getting run on every logon. I would suggest using more logic in the logon script like have VBS watch over the install and if there is no error raised write a registry key to say the install was successful. Then the next time the logon script runs you should have some logic to read the registry and deem if the command line needs to be run.
Posted by: gbailey 19 years ago
Senior Yellow Belt
0
That sounds good, but I don't really know how to go about doing that. I was just put in this position because I have hardware background so my company thinks that they don't need to outsource anything...if someone could point me in the right direction on the vbs, how to go about using it, and where to put it I would appreciate it.
Posted by: kkaminsk 19 years ago
9th Degree Black Belt
0
Well here is the reference. It might be a bit steep if you don't have a programing background though there are much more difficult languages you could tackle.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/vtoriVBScript.asp

If they want to spend some money you could try something like Winbatch but I think sticking with VBScript is better in the long run plus Winbatch is yet another language. If I had a script made a script that did something similar I would post it but I have not. Maybe someone else here has something they can share.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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