Endpoint Protection

 View Only
  • 1.  deploying a client update

    Posted Apr 03, 2015 11:02 AM

    Hi all, 

    my question is, if I do upgrade a client version of SEP from the SEPM and the user do not complete the procedure with a reboot of his computer (such that the upgrade of the new version is downloaded and installed but not yet running) and he has already another (older) version of the client up and running, is his old version fully working with all the funcionalities activated or some of the funcionalities will not work until the reboot? (Of course without forcing the reboot of the machine from SEPM, because I want to wait the user to reboot autonomously).

     

    Thanks for the answers



  • 2.  RE: deploying a client update
    Best Answer

    Posted Apr 03, 2015 11:05 AM

    Yes, no functionality is lost. A reboot is needed to complete the upgrade to the newer but you are still fully protected by the current version that is in place. If you are installing a new component, such as the firewall, and it wasn't on the client previously then you will need to reboot for the firewall fucntionality to take effect.



  • 3.  RE: deploying a client update

    Posted Apr 03, 2015 11:20 AM

    Thank you Brian!



  • 4.  RE: deploying a client update

    Posted Apr 03, 2015 11:50 AM

    welcome :)



  • 5.  RE: deploying a client update

    Broadcom Employee
    Posted Apr 07, 2015 04:25 AM

    Hi,

    Thank you for posting in Symantec community.

    Q. is his old version fully working with all the funcionalities activated or some of the funcionalities will not work until the reboot? (Of course without forcing the reboot of the machine from SEPM, because I want to wait the user to reboot autonomously).

    --> Old version functionalities will not be impacted. 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.