Its a product design... upgrades always happen in the same path

The only way to avoid this is to set CUSTOM install feature set and specify the path for the package...

cheeers .... :)

Where do I set custom install feature sets?

1. Open the Symantec Endpoint Protection Manager Console
2. Click the Admin Tab
3. Click Install Packages at the bottom under Tasks. You will now see the current default client install packages on the right.
4. Under View Install Packages, Click Client Install Settings.
5. Under Tasks Click Add Client Install Settings.

cheeeeeers ... :)

Thanks I'll give that a shot.  The sad thing is I looked at that window yesterday and missed that setting.  Sometimes you just need to slow down and really think about what you're looking at.

:smileyhappy:

Unfortunaly that didn't work, it still installs to the old SAV directory.  I am also noticing now that the SEP_INST.log file isn't getting created either.  The values I have set for both are as below.

Install dir = %PROGRAMFILES%\Symantec\

Log dir = %TEMP%\SEP_INST.LOG

Any ideas?

I tried the same thing this morning after reading this post and it didn't work for me either. I created a custom install setting, with a "custom installation folder" of "C:\Program Files\Symantec\Symantec Endpoint Protection" (without the quotes), and exported the package. It just upgraded my client to the new version, but kept the existing folder.

I am having the same issue. I am upgrading from SAV 10.1.5.5000 to Sep 11.  Just to be unique I changed the dest directory to something other than the default however the install occurs under C:\program files\symantec Antivirus

; NOTE: Do not edit the config below
[PREDEFINED_SMC_CONFIG]
AppType=105
VendorID=4096
PlatformType=WIN32BIT

; User configureable options
PackageChecksum=12a723c95d2d25233a8a273275a3a195
[CUSTOM_SMC_CONFIG]
InstallNewInstanceOnly=0
InstallUserInterfaceLevel=s
KeepPreviousSetting=0
InstallationLogDir=%TEMP%\SEP_INST.LOG
DestinationDirectory=c:\program files\Symantec\SEP11
LaunchIt=1
AddProgramIntoStartMenu=1
UIRebootMode=2

[LU_CONFIG]
ServerProduct=SESM AntiVirus Client Win32
ServerLanguage=English
ServerVersion=11.0.4014
SequenceNumber=0
ServerMoniker={6FC87801-0A02-87E0-019C-D75A0A3BBC5F}
ClientProduct=SESC AntiVirus Client Win32
ClientLanguage=English
ClientVersion=11.0.4014
ClientMoniker={3572AC3E-0A02-87E0-019C-D75A48D9DC60}
SequenceTag=PATCH
ShortName=sesmAvClient32en_MR4
DisplayName=Symantec Endpoint Protection Win32 11.0.4014.26 (English)
CONNECT_LU_SERVER=1

[FEATURE_SELECTION]
SAVMain=1
EMailTools=1
OutlookSnapin=0
NotesSnapin=0
Pop3Smtp=1
ITPMain=1
Firewall=1
PTPMain=1
COHMain=1
DCMain=1
 

If you are using a 3rd party tool to run the MSI directly then the setaid.ini file wont get read.

The answer is to either have the 3rd party tool run the setup.exe instead, or use an MST file to make the changes desired.

Here is a reference document to back me up, note that it talks purely about GPO install, but it applies to any method that directly accesses MSI.

When installing SEP clients using GPO the clients get all features installed instead of only the features set in the installation package

http://service1.symantec.com/SUPPORT/ent-security....

The above post is correct, the best method for 3rd party deployment of SEP is always to use the setup.exe. Other methods have generally led to unexpected results.