Endpoint Protection

 View Only

  • 1.  SEP 12.1 upgrade downtime.

    Posted Aug 20, 2013 10:18 AM

    Hi,

    Does Servers need restart post or during SEP 12.1 upgrade, 11 to 12 and 12 to 12 with AV and with All features.

    Servers are Windows 2000, 2003, 2008, 2012.



  • 2.  RE: SEP 12.1 upgrade downtime.

    Posted Aug 20, 2013 10:22 AM

    Yes, if upgrading from 11.x to 12.1, a reboot is mandatory.

    12.1 to 12.1 with AV only, no reboot should be needed. If you install NTP than yes a reboot is needed.



  • 3.  RE: SEP 12.1 upgrade downtime.
    Best Answer

    Trusted Advisor
    Posted Aug 20, 2013 10:24 AM
    Hello,
     
    I believe, this is from a Symantec Endpoint Protection (SEP) client perspective (not the manager).
     
    The SEP 11.x to 12.1 upgrade will need a reboot.
     
    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.
     
    (Nice-to-have feature to deal with short maintenance windows)  Note that this then necessitates that the system has to be rebooted before trying another upgrade.
     
    Note that in all cases, you can create the package to not force or even prompt for a reboot.
     
    This technique enables you to change the normal portion of the installation path during a migration, when applicable. 
    Hope that helps!!


  • 4.  RE: SEP 12.1 upgrade downtime.



  • 5.  RE: SEP 12.1 upgrade downtime.

    Broadcom Employee
    Posted Aug 20, 2013 10:45 AM

    Hi,

    Thank you for posting in Symantec community.

    I would be glad to answer your query.

    During an upgrade reboot is not required.

    After successful upgrade reboot is mandatory however it can be schedule to later time. Need to configure SEP client package with required settings.

    SEP 12.1 uses side-by-side installation process.

    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.

    If you are planning to upgrade the SEP clients on servers like Windows 2000, 2003, 2008, 2012, I would suggest to take a downtime & perform the steps during non production hours.

     



  • 6.  RE: SEP 12.1 upgrade downtime.

    Posted Aug 20, 2013 10:53 AM

    You say that "During an upgrade reboot is not required."

    Than you say that "After successful upgrade reboot is mandatory"

    Which is it?



  • 7.  RE: SEP 12.1 upgrade downtime.

    Broadcom Employee
    Posted Aug 20, 2013 11:09 AM

    I mean when SEP client initialize an upgrade process it won't required reboot in between to complete an upgrade.

    Once SEP completed an upgrade successfully (100%) then reboot is required.

    In many software's reboot is mandatory to go to the next step.



  • 8.  RE: SEP 12.1 upgrade downtime.
    Best Answer

    Posted Aug 20, 2013 12:17 PM

    Just wanted to point out that you will not be able to update your Windows 2000 servers to SEP 12.1, because that operating system is not supported. Any Windows 2000 server will have to stay on 11.x, but it can be managed by a 12.1 SEPM as a legacy client.

    sandra



  • 9.  RE: SEP 12.1 upgrade downtime.
    Best Answer

    Trusted Advisor
    Posted Aug 20, 2013 12:41 PM

    Hello,

    I agree with Sandra. Windows 2000 is not Supported by Symantec Endpoint Protection 12.1

    Check the Minimum System Requirements Article: http://www.symantec.com/docs/TECH163806

    You have the option to add the additional "legacy" installation of 11.0.6300 to your available Client Install Packages in 12.1. This source file can be found under:

    [install media]\Symantec_Endpoint_Protection_12.1_Full_EN\SEPM\AdditionalPackages\

    There will you see SAVLegacy32.info and SAVLegacy32.dat

    After you add this package to the database, you can then export an installation package for your Windows 2000 server, and it can be managed.

    Check this Article:

    How to Install Symantec Endpoint Protection v. 11.x from the Symantec Endpoint Protection Manager v.12.1?

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

    Hope that helps!!



  • 10.  RE: SEP 12.1 upgrade downtime.

    Posted Aug 21, 2013 09:38 AM

    Thank you everyone.smiley