First time user here,,
how do I install "Symantec EndPoint Protection Ver 11 Client" from a network shared drive down to a desktop using the "msi" command line switches.
The Appdeploy site does not have the "Command Lines" filled in for this newer product.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Woe betide you if you believe Symantec that SEP 11 will cleanly upgrade NAV 10.

The customisations we had to apply to the MSI are a vision to behold. For example, they have the standard RemoveExistingProducts action conditioned-out (NeverRunThisAction - LOL) and replaced with 2 CAs: EarlyRemoveExistingProducts and LateRemoveExistingProducts. FindRelatedProducts is conditioned (NOT ISSETUPDRIVEN), too.

We use transforms rather than command line arguments. To find out the property names that you may need to alter, load up the MSI into Orca or, better, InstEdit and view the Property table. You'll probably want to check out the various tables connected with dialogs, too, so that you know all the various properties being used.
Answered 12/18/2009 by: VBScab
Red Belt

Please log in to comment
Hi Richard,

I recently packaged this application, so you're in luck.

If I'm not mistaken you can generate a setup.exe file for SEP from your central server (about 100MB big, basically a selfextracting archive)
What we did was change some settings in the files setup.ini and setaid.ini that are compressed in this setup.exe.

the commandline we passed for the msi in setup.ini was the following:

CmdLine=/qn /l*v "%TEMP%\SEP_INST.LOG" REBOOT=ReallySuppress

basically you can use any msiexec parameters in this commandline, for a list of these have a look here
I'm guessing you've already seen this, but the installation guide for SEP can be found here

One thing I need to mention is this: There are custom actions in the MSI for SEP that will go get property values from the setaid.ini file. This means that any setting in the setaid.ini file will take precedence over property values you pass directly to the MSI on the commandline. Beware of this! [;)]

Hope this helps

Answered 12/18/2009 by: pjgeutjens
Red Belt

Please log in to comment