Endpoint Protection

 View Only
  • 1.  Upgrade SSC v.10 Clients and SEPM v.11 Clients to Latest SEPM Version

    Posted Jan 20, 2015 12:39 AM

    Hi,

    I am looking for a consultation on above deployment.

    Currently my client have many workstations using different version of antivirus symantec. Example: (there is a group of clients using SSC v.10.1.4.4000 (outdated), another group using SEPM v.11.0.5002.333 (outdated and without the SEP Manager), and another group without any anti-virus, all within the same network). I wish to consolidate all the clients under the latest version of SEPM (a new deployment with a new SEPM license).  How can I connect all clients to the new SEPM and upgrade to its latest version? 

    Pls advise. TQ

     



  • 2.  RE: Upgrade SSC v.10 Clients and SEPM v.11 Clients to Latest SEPM Version

    Posted Jan 20, 2015 12:47 AM

    You need to uninstall Old SSC v.10.1.4.4000 version and reinstall new SEP client.

    In Sep 11.x you need to change sylink.xml file.

    https://www-secure.symantec.com/connect/articles/sep-121-ru2-and-reset-client-communication

    Restoring client-server communications with Communication Update Package Deployment

    Article:HOWTO81109 | Created: 2012-10-24 | Updated: 2014-09-21 | Article URL http://www.symantec.com/docs/HOWTO81109

    Once all client showing sepm 12. you can using auto upgrade feature

    Upgrade Symantec Endpoint Protection 12.1 clients using AutoUpgrade

    Article:TECH96789 | Created: 2009-01-14 | Updated: 2014-10-09 | Article URL http://www.symantec.com/docs/TECH96789

     



  • 3.  RE: Upgrade SSC v.10 Clients and SEPM v.11 Clients to Latest SEPM Version

    Posted Jan 20, 2015 02:58 AM

    SAV 10.X and SEP 11.X have reached EOL , this will be a fresh start for you, 

    chose a server which will be your SEPM 12.1 . Install SEPM 12.1, create client package push it via SEPM. once installed they will start commuinicating with the manager.  it will uninstall the previous version and install the latest one.

    Install Endpoint Protection Manager 12.1 and deploy clients

    http://www.symantec.com/business/support/index?page=content&id=TECH163580



  • 4.  RE: Upgrade SSC v.10 Clients and SEPM v.11 Clients to Latest SEPM Version

    Posted Jan 20, 2015 04:22 AM

    Hi James,

    Thanks for the reply.

    However I need to clarify something, how do we uninstall OLD SSC v.10.1.4.4000 at client pc without doing it manually? Currently there is no SSC console managing the clients.

     



  • 5.  RE: Upgrade SSC v.10 Clients and SEPM v.11 Clients to Latest SEPM Version

    Posted Jan 20, 2015 04:31 AM

    You can try this

    Configuring client packages to uninstall existing third-party security software

    Article:HOWTO81113 | Created: 2012-10-24 | Updated: 2014-09-21 | Article URL http://www.symantec.com/docs/HOWTO81113


  • 6.  RE: Upgrade SSC v.10 Clients and SEPM v.11 Clients to Latest SEPM Version

    Posted Jan 20, 2015 04:39 AM

    the new package will uninstall old packages ( SAV) just run on top the existing install



  • 7.  RE: Upgrade SSC v.10 Clients and SEPM v.11 Clients to Latest SEPM Version

    Broadcom Employee
    Posted Jan 20, 2015 06:34 AM

    Hi,

    Thank you for posting in Symantec community.

    I would be glad to answer your query.

    Migration from Symantec AntiVirus 10.x or Symantec Client Security 3.x is not supported. You must uninstall these legacy products before you install Symantec Endpoint Protection 12.1.5.However migration from SEP 11.x to SEP 12.1 RU5 is fully supported.

    As a workaround to remotely uninstall SSC clients use Competitive uninstaller utility.

    SEPprep is an unsupported tool that is designed to uninstall any competitive product automatically. This tool can also launch another application before or after removing all competitive products.  Configure this tool to first remove all competitive products (including Norton products) and then launch the SEP installer automatically and silently.  SEPprep works on all supported Windows SEP client operating systems (both 32-bit and 64-bit). There are two different binaries: one for 32-bit systems and one for 64-bit systems.

    Refer this article for the same: http://www.symantec.com/docs/TECH148513