Endpoint Protection

 View Only
Expand all | Collapse all

Upgrading SEPM/SEP from 11.0.5002 RU5 to 12.1.1101 RU1 MP1

  • 1.  Upgrading SEPM/SEP from 11.0.5002 RU5 to 12.1.1101 RU1 MP1

    Posted Jun 25, 2012 03:03 PM

    Hello all,

    We have had problems with Symantec EP updates chewing up our WAN bandwidth for years, and I'm now looking at upgrading to see if the bandwidth limiting to GUPs feature has finally been fixed.

    The problem that I'm facing is that it looks to be a major time investment to do anything with this stuff and thusly making the cost prohibitive.  Just trying to find how to download the latest version, getting the release notes, the installation and migration guide has taken me over an hour already.... and I have just read what seems to explain that I'll need to update the clients, GUPs, and servers seperately... 3 times... to go from 11.0.5002 to 12.1.671 RTM to 12.1.1.1000 RU1 before finally to 12.1.1101 RU1 MP1.

    My initial thought was just to go to 12.1 RTM... but after having read the release notes for the RU1 and the RU1 MP1 updates, it seems that 12.1 breaks a whole lot of stuff that cannot simply be left unfixed.

    Does anyone have any experience with the bandwidth limiting to GUPs?  What about better suggestions for how to be able to upgrade?

    Thanks in advance!

    Greg



  • 2.  RE: Upgrading SEPM/SEP from 11.0.5002 RU5 to 12.1.1101 RU1 MP1

    Posted Jun 25, 2012 03:13 PM

    Going straight from your 11.0.5 to 12.1.1000 (RU1) is a supported upgrade:

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

    Michael



  • 3.  RE: Upgrading SEPM/SEP from 11.0.5002 RU5 to 12.1.1101 RU1 MP1

    Trusted Advisor
    Posted Jun 25, 2012 05:06 PM

    Hello,

    Migrating from Symantec Endpoint Protection v.11.0.5002 clients to Install Symantec Endpoint Protection v.12.1.RU1 could migrate flawlessly without any issues.

    Yes, you migration would in the manner below:

    SEPM 11.x --->> SEPM 12.1 RU1 ----->> SEPM 12.1 RU1 MP1

    It is always recommended to perform a Disaster Recovery for SEPM 11.x before Migrating to SEP 12.1 as a Backup step.

    Here are few steps to look at for Migration:

    1) How to upgrade the Symantec Endpoint Protection Manager (SEPM) to Version 12.1 RU1

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

    2) a) Upgrading or migrating to Symantec Endpoint Protection 12.1.1000 (RU1)

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

    b) Upgrading or migrating to Symantec Endpoint Protection 12.1.1101 (RU1 MP1)

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

    3) Steps to prepare computers to install Symantec Endpoint Protection 12.1 client

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

    4) Activating your Symantec Endpoint Protection 12.1 product license

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

    Also, check the Articles for the Migration on :

    Quick Access to Symantec Knowledgebase Articles of Symantec Endpoint Protection 12.1

    https://www-secure.symantec.com/connect/articles/quick-access-symantec-knowledgebase-articles-symantec-endpoint-protection-121

    SEP 11.x to SEP 12.1 Upgrade process graphical overview

    https://www-secure.symantec.com/connect/articles/sep-11x-sep-121-upgrade-process-graphical-overview

    WhitePaper for Migration: https://www-secure.symantec.com/connect/downloads/migration-whitepaper-symantec-endpoint-protection-version-121

     

    Secondly about GUP and Bandwidth, check these Articles:

    Tips For Installing SEP In A Low Bandwidth Environment

    'How to configure GUP bandwidth throttling in Symantec Endpoint Protection 11.0 MR4?'

    Configuring the Group Update Provider (GUP) in Symantec Endpoint Protection 11.0 RU5 and later

    Hope that helps!! 



  • 4.  RE: Upgrading SEPM/SEP from 11.0.5002 RU5 to 12.1.1101 RU1 MP1

    Posted Jun 26, 2012 12:17 PM

    Thank you both for your responses.  It is good to know that I can at least skip one of the upgrades.  I swore that in the release notes for RU1 it said that you could only install from 12.1 RTM but it seems that I missed the part about SEPM 11!

    As for the other documents, I've either read or skimmed all of them.  I think other than opening the UDP ports on the client firewalls for the push deployment, all is in order.  As for the GUP related documents, specifically bandwidth throttling in RU5, it simply doesn't work, otherwise that would solve our problem!

    One other clarification that I would like is just on the chain of events that I'd need to execute in order to get to 12.1 RU1 MP1.  This is just approximate... I'm not listing everything here, just the basic steps.

    1. Backup the embedded database
    2. Stop the SEPM service
    3. Install 12.1 RU1 SEP Manager on the server
    4. Restart the SEPM service
    5. Make new 12.1 RU1 packages for client deployment
    6. Replicate packages to satellite offices
    7. Install SEP client on GUPs
    8. Deploy SEP client
    9. Backup the embedded database
    10. Stop the SEPM service
    11. Install 12.1 RU1 MP1 SEP Manager on the server
    12. Restart the SEPM service
    13. Make new 12.1 RU1 MP1 packages for client deployment
    14. Replicate packages to satellite offices
    15. Install SEP client on GUPs
    16. Deploy SEP client

    Is that about right?

    Regards,

    geva



  • 5.  RE: Upgrading SEPM/SEP from 11.0.5002 RU5 to 12.1.1101 RU1 MP1

    Posted Jul 18, 2012 06:18 AM

    As I've not heard back any confirmation from Symantec personel, I'm going to have to assume that I've got the steps correct to upgrade from our SEP 11 to SEP 12.

    Although this is not a complicated job, all of the steps and various focuses required (server, then GUPs, then clients), and the fact that the process needs to be done twice just means that this would be a very costly upgrade just to get a feature working that should work in v11.  My estimate is that this is easily 8 hours worth of work.

    Myself, and my customer would rather spend $50 to get bandwidth throttling working using known working tools rather than go through all of this effort only to potentially run into more problems along the road.

    You guys should really try to simplify your upgrade process.  This is pretty ridiculous if you ask me.



  • 6.  RE: Upgrading SEPM/SEP from 11.0.5002 RU5 to 12.1.1101 RU1 MP1

    Broadcom Employee
    Posted Jul 18, 2012 07:29 AM

    Hi Geva,

    Steps given by you are correct.

    1. Backup the embedded database
    2. Stop the SEPM service
    3. Install 12.1 RU1 SEP Manager on the server
    4. Restart the SEPM service --> No need to restart, it would start automatically.
    5. Make new 12.1 RU1 packages for client deployment
    6. Replicate packages to satellite offices
    7. Install SEP client on GUPs
    8. Deploy SEP client
    9. Backup the embedded database
    10. Stop the SEPM service
    11. Install 12.1 RU1 MP1 SEP Manager on the server
    12. Restart the SEPM service --> No need to restart, it would start automatically.
    13. Make new 12.1 RU1 MP1 packages for client deployment
    14. Replicate packages to satellite offices
    15. Install SEP client on GUPs

     

     



  • 7.  RE: Upgrading SEPM/SEP from 11.0.5002 RU5 to 12.1.1101 RU1 MP1

    Posted Jul 25, 2012 09:20 AM

    Thanks for the time saving tip MaRRuT@CC. I appreciate the suggestion.

    Due to the time implication and the fact that this customer has a tight budget, we've decided to just forget about the upgrade all together.



  • 8.  RE: Upgrading SEPM/SEP from 11.0.5002 RU5 to 12.1.1101 RU1 MP1

    Posted Jul 25, 2012 09:23 AM

    This is just way to long and drawn out.  This isn't the 1990s.  You guys should either get with the times or at least reduce your pricing in line with the quality of your software.



  • 9.  RE: Upgrading SEPM/SEP from 11.0.5002 RU5 to 12.1.1101 RU1 MP1
    Best Answer

    Posted Jul 27, 2012 07:11 AM

    In my opinion, its easier, and much more time saving, to install SEP12.1 from the scrach! (new).

    After the installation of a parallel SEP12.1 infrastructure you should "steal" your old SEP11.x Clients from your old SEP11.x environment with an exchange of the sylink.xml file to roll-out new SEP12.1 packages over your productive environment. Youll need to configure your SEP Package a bit to change the old from the old to the new SEPM, but thats piece of cake.

    Its much faster and time-saving! The only thing is that 2nd enquipment for the change management is needed (deployment time) but I recommend this way. After you have migrated your infrastructure, you can shut down your old SEPM (11.x).



  • 10.  RE: Upgrading SEPM/SEP from 11.0.5002 RU5 to 12.1.1101 RU1 MP1

    Posted Jul 27, 2012 07:15 AM

    np with that =)

    After more than 100+ SEP Installations/Implementations/Upgrades/Migrations I think I can prefer some good best practises & ways from the productive infrastructure side of view =)

    Notice:
    At all, SEP12.1 is a very good and stable product. Thats the reason why I don't like to migrate from an unknown, maybe corrupt SEP11.x DB, which is years old and not in a healthy state.