Endpoint Protection

 View Only
  • 1.  Symantec Endpoint Client 11 - 12 update

    Posted Apr 08, 2014 09:30 AM

    Hello,

     

    I am looking into updating our Symantec 11 clients from Version 11RU 6 -12.1.4. 

     

    Due to our current configuration, and AD configuration, completing a group deployment would be problematic to say the least.

     

    After reading this article about upgrading: http://www.symantec.com/business/support/index?page=content&id=TECH9678

    I am a little confused by the auto deployment, is the new client (12.1.4) placed on the Symantec 11 management server and deployed from it? I do not see how it would work any other way since the heartbeat would be to the Version 11 server.

    Another question I have is if Symantec has a method to upgrade clients based on Subnet ranges. I know you can deploy by upgrading is typically a different process. Also, does Symantec 12 or another product allow for scanning for currently installed 11 client so I can take a targeted approach?

    Any tips on moving through this update from past experiences? Approximate numbers are 150 servers 450 workstations.

    Thank you for your help and advice in advance.



  • 2.  RE: Symantec Endpoint Client 11 - 12 update

    Posted Apr 08, 2014 09:34 AM

    You would first need to upgrade the SEPM to 12.1 After that is done you can do the auto upgrade.

    You can use the client deployment wizzard toi scan for 11.x machines to upgrade

    https://www-secure.symantec.com/connect/articles/client-deployment-wizard-sep-121



  • 3.  RE: Symantec Endpoint Client 11 - 12 update

    Posted Apr 08, 2014 09:40 AM

    Hello,

    You still need to follow Symantec best practice to ensure that your upgrade is successful. 

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

    You can do auto upgrade for the clients. But for the servers, i would not suggest to do it due to critical application that might running on it.

     

    Best regards,



  • 4.  RE: Symantec Endpoint Client 11 - 12 update

    Posted Apr 08, 2014 09:54 AM

    Hello,

     

    I forgot to mention that I will be building a new box for SEPM 12 and a seperate one for LUA.

    So deployment Wizard can work for upgrades rather than relying on SEPM?

     

     



  • 5.  RE: Symantec Endpoint Client 11 - 12 update

    Posted Apr 08, 2014 09:57 AM

    Thumbs up to the above posts yes

    Further to these posts, here's a best practice guide on upgrading:

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

    There are many more useful articles that are linked from the above article, so have a good look around.  Plus, the FAQ in the above article addresses some of your own queries, and is really handy (example below)

    Q: What's the recommended migration order? What do I migrate first in my environment?

    A: The recommended order is to upgrade all Symantec Endpoint Protection Managers, Group Update Providers (enterprise version only), and then the remaining clients as needed.



  • 6.  RE: Symantec Endpoint Client 11 - 12 update
    Best Answer

    Posted Apr 08, 2014 09:59 AM

    Just saw your latest post!

    In which case, you can just push out a new Client package that will upgrade and redirect the clients in one go.  The below article describes how to do so:

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



  • 7.  RE: Symantec Endpoint Client 11 - 12 update

    Posted Apr 08, 2014 10:26 AM

    Thank you SMLatCST, that is what I was looking for. Hopefully the upgrade will go as smoothly as it sounds. 



  • 8.  RE: Symantec Endpoint Client 11 - 12 update

    Broadcom Employee
    Posted Apr 08, 2014 10:38 AM

    Hi,

    Thank you for posting in Symantec community.

    SEP 12.1 employs a side-by-side, replace on reboot installation strategy. Side-by-side means that new files are written to a new folder, referred to as a silo, isolated from the existing operational folder. Because the two versions are separated from each other, during a migration the older software is left running unchanged until the next reboot.

    The primary benefit of side-by-side installation and replace on reboot is that the system continues to be protected by the existing software until the new version is in operation after the reboot.

    This technique enables you to change the normal portion of the installation path during a migration, when applicable.

    First upgrade SEPM to the latest version, upgrade GUP machines then SEP clients.

    If clients are on the WAN network then bandwidth can be a concern. Upgrade them using other options.

    Refer the following article if looking to move SEPM from one server to another.

    https://www-secure.symantec.com/connect/articles/hot-move-sepm-one-server-another-server