Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Distribution of SEP 12.1.1101.401

Created: 05 Sep 2012 | 6 comments

Hi all,

I have a question about distributing the SEP 12.1.1101.401 version. My problem is that I have client computers which have the 11.0.6000.550 version.

I upgraded the SEPM to the 12.. version and want to upgrade all the clients too. I created a package from SEPM and than put that into SCCM to distribute.

After it was installed on the test clients I realized that the files of the old version remained in the c:\program files\symantec\symantec endpoint protection folder and a new subfolder named 12.1.1101.401.105 created under it. And also live update remained there.

Did someone experience something similar?

What did I do wrong?

Is there any way to remove completly the older version before installing the new one?

Thank You in advance!

Zoltán Kinorányi

Comments 6 CommentsJump to latest comment

Chetan Savade's picture

Hi,

It's by a design.

Reboot is mandatory while doing an upgrade from SEP 11.x to SEP 12.1

SEP 12.1 is a side by side (SILO) installation i.e. it will be installed under the new directory (12.1.1101.401) & upon hard reboot old installation files would be completely removed.

When the software is installed, it'll be written to C:\Program Files\Symantec\Symantec Endpoint Protection\(Product code), and when the machine is rebooted, the loading points will be switched over to run the new version.  If something happens during install of the new version (or, presumably, the switch from the older to the newer version), the installer will put the pointers back to the old software so that you'll boot with something that works, rather than a half-installed broken newer version.

Chetan Savade
Sr.Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

.Brian's picture

This should be normal and expected behavior.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Chetan Savade's picture

Hi,

Any update on this.

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.

Chetan Savade
Sr.Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

jgreenberg@zebra.com's picture

What other options are their for bulk distribution besides SCCM and pushing from SEPM

DCourtel's picture

Hi Jgreenberg, if you have an Wsus infrastructure you can use it to distribute SEP by Publishing it.

If you are interested, take a look at Wsus Package Publisher on the CodePlex web site. I have wrote an HowTo showing how to Publish the installation package :

http://wsuspackagepublisher.codeplex.com/documentation

DCourtel.

End User Support Technician

Publish Third Party Applications in Wsus : http://wsuspackagepublisher.codeplex.com/

SebastianZ's picture

You can you as well the SEPM integrated Autoupgrade funtionality to upgrade the clients automatically to the desired version:

http://www.symantec.com/docs/HOWTO17911

https://www-secure.symantec.com/connect/videos/upg...