Upgrade from SAV 10x to SEP11 Destination path issue
scotjan
October 29th, 2009
After testing the msi install command options to upgrade server clients from SAV 10x to SEP11 we have discovered that it is not possible to set the install path during the upgrade.
We have around 10K servers and are aim is to install SEP11 into its own Symantec Endpoint directory; not into the legacy Symantec AntiVirus directory whilst minimising the reboots all the servers.
It seems now that our only option is to remove SAV 10 completely, reboot and then install SEP 11. This then installs into the SEP directory.
Has anyone else tested a work around for this issue? Have you got successful scripts that have resolved the problem?
Filed under: Endpoint Protection (AntiVirus), Security
Create a package with the
Create a package with the
help of below doc and try to install.(Fist you try this in test environment)
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/d1e02487e4d75e8b8825739200581baa?OpenDocument
Installation of SEP on a different drive
Thanks & Regards
Sandip C Sali
You cannot change the path
You cannot change the path when upgrading from SAV. Can you?
We are uninstalling SAV and then installing SEP for the same issue.
The issue we are seeing is
The issue we are seeing is when you have selected the destination path for a custom install.
If SAV was installed previously even though you configure the .msi to use the new Symantec Endpoint folder it will use the legacy Symantec AntiVirus folder. This is confirmed by Symantec.
There is no problem changing the destination drive just the directory.
It is important for us to have SEP installed into its own dir and NOT the legacy SAV dir for the purposes of standardising the company systems; this is to avoid support and remediation variations and allows for standard documented troubleshooting procedures.
It looks as though we will need to remove SAV and then install SEP.
Has anybody done an installation after removing SAV and NOT rebooting? If so did they create a script to remove any remaining threads and registry entries post uninstall?
We are doing it and are in
We are doing it and are in the QA right now.
You don't need a reboot post uninstall. I have done more than 100 machines this week...........Okay with RU5 our strategy with the packaging has changed since after SEP install a reboot is mandatory for the NTP to be active ( https://www-secure.symantec.com/connect/forums/teefer2sys-fix ). What I have done is to kill all SAV processes by hook or by crook and then proceed with the uninstall and then deleted all directories( Like items in quarantine that block migration) post install. Let me know if you have a tough time killing tamper protection or rtvscan.......I don't see a reason why not to go against the books.....irrespective of the scale size of the deployment.....BTW......What component is asking for a reboot.....?...Just to be sure....So that I check it as well.....Thanks........
Thanks for your
Thanks for your advice:)
Nothing is calling for a reboot, just that normally in previous upgrades that has been required to clean up the old legacy files etc.
I just installed a test machine and then installed SEP 11 straight after. The old dir structure was left behind but SEP did install into the path we configured ok.
We'll get a script to clean up the old legacy structure
refer the below blog entry by
refer the below blog entry by Rafeeq Connect And Protect
Story - SAV 8 to SEP 11.
he is explaining his experience with a deployment of
SEP11.He was having an environment a mixture of sav 8&10 .This may be
useful for you
You can also refer the below docs
MSI command line reference for Symantec Endpoint Protection 11.0
Windows Installer (.msi) command-line reference for Symantec Client Security 3.x and Symantec AntiVirus 10.x
With the help of above docs you can create a script for removing SAV and installing SEP
In the script you can add an entry for deleting the folders
c:\program files\symantec
c:\program files\symantec antivirus
C:\Documents and Settings\All Users\Application Data\Symantec
also
For creating package for installation tou can use this doc
How to create a Symantec Endpoint Protection install package that will install to a different drive
Would you like to reply?
Login or Register to post your comment.